You are not logged in.
ah, yes, I see - the move cyrus-sasl is also too old ... the right one is still stuck on the build list, I'll have a look why that is the case.
regards,
deep42thought
I'm unfimiliar with the exfat ecosysstem. Is this related?
I see two possibilities there:
Either compile the packages you need yourself from aur (preferably with devtools32 from [releng] on mirror.archlinux32.org) or ask the maintainers of linux-ck if they are willing to provide i686 packages, too.
regards,
deep42thought
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
thanks, levi, I fixed that
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:"
I fixed reflector - abaumann, I'll look into why you don't have push rights ... you should now have the necessary rights.
btw: we moved packages.archlinux32.org to archlinux32.org/packages, but packages.archlinux32.org/$subdir/ should now be archlinux32.org/$subdir/ for certain subdirs (e.g. mirrors, buildmaster)
sry for the trouble - I didn't have these urls in mind when migrating.
Could your build host be running out of RAM?
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?
there are builds scheduled and failing
I didn't have a look into them yet, sry
regards,
deep42thought
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
pacman -Qlp (or pacman -Ql) is the cleaner way to look at the included files: rubygems.rb is not included and was not included in ruby-2.5. Something else seems to be the problem, but I don't know (yet) what.
regards,
deep42thought
When you mention rules, are you referring to logwatch rules or are there rules somewhere for what gets journaled?
yes, logwatch rules.
Have a look in /usr/share/logwatch/scripts/services/ - and put modifications thereof into /etc/logwatch/scripts/services/
regards,
deep42thought
What command do you run by cron?
Does that also happen when you run the command manually?
logwatch sees much stuff as "unmatched" on my system - usually I add rules to ignore that noise
to 1&2 I cannot say much as you didn't mention the command which is being executed.
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.
yeah, my mistake - I meant postfix. courier (actually "courier-mta") is another email server ... I got confused at that late hour.
andreas_baumann: is this something we should run on the package by default?
ah, damn, courier also needed to be moved from testing to extra - what else depends on libmariadbclient which I'm missing here?
hmm, upstream does not _have_ libmariadbclient - just replace it by mariadb-libs, I just removed libmariadbclient from the repositories, too.
the canadian mirror is no longer active - remove it and _then_ update the mirrorlist
mariadb and libmariadbclient are now in sync again
thank you, we successfully built rust
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
these issues should be resolved.
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
I meant "the buildmaster" moved - not "I" (or anybody else) moved ...
This is really strange, as the dependencies are all there and recognized in our mysql database