Bill Kenworthy wrote: > On 28/04/16 01:33, Dale wrote: >> Michael Mol wrote: >>> I have my system automatically update nightly, and check the build results >>> in >>> the morning. If there's a persistent build error for a couple days, I file >>> a >>> bug report. That's my threshold, anyway. >>> >> >> This started on Sunday. So it has met that part anyway. Since I run a >> mix of stable and unstable, it has been known to cause issues that are >> weird. I just don't want to file a bug report and take up a devs time >> if it is some weird one off thing that affects no one else. It's not >> like they don't have enough stuff to deal with already. Then again, >> they do want info on failures so that it doesn't affect others. Where's >> my coin to flip? lol >> >> I plan to sync again and if it persists, Raid comes out. :/ >> >> Thanks. >> >> Dale >> >> :-) :-) >> > I have a couple of background "things" happening at the moment: > > prelink and glibc: odd failures that make no sense - unprelink the > system and everything works fine (at some point you get a failure to > fork.) I hit it when trying to build multiple lxc instances ... it > builds two and then the server becomes "toast" :( There is a bug on bgo ... > > btrfs and kernels 4.4.6 and 4.4.7: fails to convert/balance a raid 10 > (system hard lock, no errors) and maybe some file system related build > errors (which might also be glibc related, though it might not ...) > 4.4.8 works fine (includes a number of btrfs fixes) > > Either of those fit? > > BillK > > >
Oddly, I had some google hits to that effect. I can't recall exactly what I was searching for but on one of them, I did see glibc mentioned as the issue. I just figured it would fail on other packages as well if it was the problem so thought it unrelated. Well, maybe it is after all. I dunno. Good question. I seem to recall glibc being one of those packages that you can't downgrade. Sort of chicken to upgrade, just in case the problem gets even worse. Here's a little more info on my system. root@fireball / # uname -r 3.18.7-gentoo root@fireball / # equery list -p glibc * Searching for glibc ... [-P-] [ ] sys-libs/glibc-2.17:2.2 [-P-] [ ~] sys-libs/glibc-2.18-r1:2.2 [-P-] [ ] sys-libs/glibc-2.19-r1:2.2 [-P-] [ ] sys-libs/glibc-2.20-r2:2.2 [-P-] [ ] sys-libs/glibc-2.21-r2:2.2 [IP-] [ ] sys-libs/glibc-2.22-r4:2.2 [-P-] [ ~] sys-libs/glibc-2.23-r1:2.2 [-P-] [ ~] sys-libs/glibc-2.23-r2:2.2 [-P-] [ -] sys-libs/glibc-9999:2.2 root@fireball / # Yea, I'm using a old kernel. I haven't rebooted in a while now. I just wonder what that glibc 2.23-r2 would be like?? Anyone here took a drive around the block with that version? I just synced again. Going to see if anything changes or not but I doubt it will. I didn't see any changes to the qtwebkit ebuild. Dale :-) :-)
