On Mon, Nov 19, 2018 at 6:43 AM Kevin Kofler <kevin.kof...@chello.at> wrote:
> If you follow exactly this procedure, the set of "the multilib packages > installed before" will be empty and you will not reproduce the issue at > hand. Multilib cruft has not been installed by default for years now! (And > that is a good thing! Pure 64-bit just works.) Yeah, of course, the "Verify that upgrade and update went fine and that the multilib packages installed before are still present" should have been in the later paragraph. > On Mon, Nov 19, 2018 at 2:06 AM Adam Williamson <adamw...@fedoraproject.org> wrote: > I don't think the bug had anything to do with upgrades, did it? AIUI it > would also affect a fresh F29 install to which multilib packages had > been added. I've got an impression from all the rant around that on the internet that it happened just on upgraded systems. But it makes sense to also affect clean installs.
_______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
