I'm afraid Sysadmin doesn't manage the store ot have any control over it.

Looks good to me.

@tcberner has sorted this out now.

Given that transfer of the mailing list archives would also involve transfer of personal information (as names + email addresses are contained in them) if we were to take that view then those wouldn't be transferrable either.

I see. If possible please do try to batch the commits together into a single push to avoid such breakages in the future.

This change appears to have broken Windows builds (when using the QRC bundles anyway, which it seems regular Windows CI builds don't enable)

I assume this fetches the icons from your local system?

These changes were part of switching it away from Pirate's backup space, so were to be expected.

Given we've only got VMs there, I doubt the 3ware-tools or hp-raid tools are needed on our systems, so i've disabled those repositories.
The apt update process now completes successfully.

I've asked the folks who look after our FreeBSD machines to install llvm-symbolizer.
In the meantime, the above change should resolve this issue.

I assume you've gone through the steps needed to ensure this is a false positive and not an actual bug which needs to be fixed?

Please note that it is generally better to post links to things like this in #kde-sysadmin on IRC rather than #kde-www as they are more likely to be missed there.

Reassigning to the correct project (Sysadmin doesn't maintain the builds themselves, just the underlying systems that do the builds)

This has now been corrected in dc6d474c24cf16b12cf1e3e4b7756c5203da044c and 6b3c05b109d30eead90bd064602819cf2feda553

I've performed an upgrade from LibreOffice Online 3.x to 4.x this evening as part of a server move for it, and at the same time changed some of the settings for it to ensure worker processes stay around for longer - which will hopefully resolve the issue.

Given that Baloo Widgets isn't the only project showing that class of failure, it's more likely to be a case of ECM getting something wrong.
(The CI system doesn't do anything special when it comes to this part of the execution)

As this information is relatively sensitive, i'll need to know how you're intending on using this before we provide these figures i'm afraid.

Sorry, I don't see where it's complaining about not finding the right binary?
(Not finding Dr Konqi is expected, given that it's part of Plasma and not a dependency of baloo-widgets)

Yes, that is quite safe to land.

From my understanding of this at least it looks fine.

The files have now been replaced with symlinks.

This will date back to when Paramiko classes were used directly here, prior to being factored out to CommonUtils.establishSSHConnection

Looks fine to me.

You don't have to wait for a Frameworks release.

Okay, that ties in with the log entries I've observed. Will have to investigate further to see if we can tune any behaviour here with regards to the authorisation time-out which Nextcloud imposes.

So we can get some diagnostic information on this, would you mind opening the browser inspector (Right Click anywhere on the page > Inspect, in Chrome at least) before you open the document and leaving it open in the background?

They weren't removed to preserve compatibility for those with links to the old files - we often get complaints regarding the removal of files.

The files have now been released as requested.

Sorry about that, the configuration fault causing that has now been corrected.