> To all Rawhide users, be careful with update of mutter. It seems that > mutter-3.23.2-2.fc26 is broken [1], which prevents you from log in to > your system. Downgrade to mutter-3.23.1-2.fc26.x86_64 workarounded the > issues for me. > > > Vít > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1401317 This serves as a nice example why we need to tweak how Rawhide works if we want people actually running on it. I talked to rtcm on #fedora-desktop and the reason is that gnome-shell 3.23.2 needs to be updated in sync with mutter. Mutter has been built just fine [1], but gnome-shell build failed [2]. And, snap, GNOME users are immediately (at the next repo push) screwed because of a failed build. Of course developers will sooner or later fix the broken build, but often there are issues can't be fixed immediately. And the successful mutter build can't be taken back either. No good solution there. So, we either need: a) updates-testing for Rawhide - e.g. with auto-push even with 0 karma after 3 days, doesn't matter, it would still allow us to prevent many of these issues or b) decouple building and submitting to Rawhide - because the idea that everything and anything built is immediately part of the release seems very broken to me. At least if we want people to use it. If we want just a huge repo of frequently broken bleeding edge packages, yes, that's exactly what we have. With b) solution the QA still can't stop bad updates, but at least the maintainer can decide to not push it to Rawhide (seeing that only one of two mandatory packages has been successfully built). With a) solution the maintainers can do the same thing, and other people can detect and stop broken updates as well. [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=820286 [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=822182 _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
