Arch Linux

I'm unfimiliar with the exfat ecosysstem. Is this related?

hmm, I'll need to check a few lines in the buildmaster - it appears, that the version information was ignored.
I moved cyrus-sasl* to stable

I'll give it a try - but that machine does not have too much ram (it must be an i686 vm to allow for skipping systemd-nspawn) - andreas: do you have a slave running on i686 with 3-4GB RAM? Then you could try to build with "-s :without_systemd_nspawn:"

That's possible for some, but not all build slaves.
E.g. nlopc46 and nlopc43 have 64 and 32GB memory respectively.
I can schedule firefox on one of those to make sure it was tried to build there.

Any other options I need to set on the host?

That was me. Your mirror appeared inactive and I sent you an email on 2018-10-03 but got no response, so I just assumed you moved along. Thus I removed the mirror from the mirrorlist.

I reverted that commit now.

regards,
deep42thought

yes, logwatch rules.
Have a look in /usr/share/logwatch/scripts/services/ - and put modifications thereof into /etc/logwatch/scripts/services/

regards,
deep42thought

A new hard disk often accelerates the system a lot - especially if you happen to changed from a hard disk to an ssd.

andreas_baumann: is this something we should run on the package by default?

hmm, upstream does not _have_ libmariadbclient - just replace it by mariadb-libs, I just removed libmariadbclient from the repositories, too.

mariadb and libmariadbclient are now in sync again

Thanks for the fix!

I'm not sure, but afaik: reproducibility does not mean, that you must not update incrementally - you simply need to "define" what packages are required for building ...

jonathon: do you have some intermediate package around, so we can skip some steps of the bootstrapping?

cheers,
deep42thought

yeah, the logic is not error-free, it seems - in the past I was always assuming human (=mostly my) error: you can overrule the buildmaster's logic ("force").
regarding holding back a move: the bugtracker is (=should be) considered for that! ... but again, it can be overruled by --force

P.S.: no offense taken