On 12/14/18 1:50 PM, Kevin Fenzi wrote: > On 12/14/18 4:06 AM, Florian Weimer wrote: >> * Florian Weimer: >> >>> 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. >> >> We really need to fix this issue, it breaks updates for many users. >> >> Any suggestion how we can move this forward? > > I had another question for lsedlar, but the prepopulate might work. That > means we bloat our updates/updates-testing repos by all the .i686 stuff > that was in the GA repo, but at least it means it will always be there. Yes please. Consistency is the key here. Either all gone, or all there. > This also would mean it would require changing this list if someone > changed a package in a update such that it was no longer multilib, but > hopefully that doesn't happen too often. This is so rare I've never observed it ;-) -- Cheers, Carlos. _______________________________________________ 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
