We have seen reports that glibc-headers.i686 comes and goes from the x86_64 updates compose. Previously, we have seen this only for the updates-testing compose: <https://pagure.io/releng/issue/7071> This leads to a very bad update experience. Users file bugs against the glibc package, but I don't think we can do anything on our side, at least not until we know what the actual compose bug is and what triggers it. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
