Re: Multilib inconsistencies between fedora/updates/updates-testing composes

2018-12-18 Thread Dennis Gilmore
https://pagure.io/releng/issue/4084 its an issue that has existed for nearly a decade and not been solved. Time was not taken to fixing it after we disabled installing multilib by default as there was no reports of it for years. Dennis El mié, 12-12-2018 a las 11:32 +0100, Florian Weimer

Re: Multilib inconsistencies between fedora/updates/updates-testing composes

2018-12-14 Thread Carlos O'Donell
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:

Re: Multilib inconsistencies between fedora/updates/updates-testing composes

2018-12-14 Thread Kevin Fenzi
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: >> >> This leads to a

Re: Multilib inconsistencies between fedora/updates/updates-testing composes

2018-12-14 Thread Florian Weimer
* 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: > > This leads to a very bad update experience. Users file bugs against

Re: Multilib inconsistencies between fedora/updates/updates-testing composes

2018-12-12 Thread Tom Stellard
On 12/12/2018 02:32 AM, Florian Weimer wrote: > 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: > > This leads to a very bad update

Multilib inconsistencies between fedora/updates/updates-testing composes

2018-12-12 Thread 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: This leads to a very bad update experience. Users file bugs against the glibc package, but I