On Tue, 2016-12-06 at 21:15 +0100, Florian Weimer wrote: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1393164 (owncloud) > > https://bugzilla.redhat.com/show_bug.cgi?id=1401172 (libldb) > > https://bugzilla.redhat.com/show_bug.cgi?id=1401175 (libtdb) > > https://bugzilla.redhat.com/show_bug.cgi?id=1401886 (gnome-shell build > > failed because of libtdb issue, breaking GNOME on Rawhide) > > These all go back to the same Samba/waf build system issue, right? Well, I *think* so, it all basically comes down to versioned soname provides disappearing from libldb and libtdb when they were rebuilt with this change. But that's breaking an awful lot of stuff, and per Jakub's reply it sounds quite likely that similar problems could affect other packages too. > > Installs of virtually any Rawhide package set besides minimal are > > broken (because they all run through samba, libldb, or both). Many > > package builds cannot run because they run through samba or libldb or > > libtdb. > > I'm just wondering if there is more widespread breakage beyond Samba. Well, assuming you're including ldb and tdb in 'samba', no, I don't think we know that yet. > If it were just Samba, fixing Samba would be the right course of action. Assuming they're all sharing some kind of bad check in their waf scripts and we can fix that and they'll all build properly again, I guess, sure, we could do that and see whether anything else breaks. Really what I want out of this is a Rawhide compose without major dependency violations that prevent all kinds of things from being rebuilt and prevent large chunks of the automated tests from running properly, and also prevent several key deliverables being composed at all. If someone can wave a magic wand and fix that in the next day or two, great, but if not, I stick to the idea that the change should be reverted. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
