Re: Fedora Upgrade - release criteria update proposal

2018-11-20 Thread Kamil Paral
On Sun, Nov 18, 2018 at 9:49 PM Frantisek Zatloukal wrote: > We have encountered a bug[0] which seemingly “broke” offline updates after > systems were upgraded from an older Fedora to Fedora 29 and had some > multilib packages installed. After the discussion at last week's Release > Retrospective

Re: Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Frantisek Zatloukal
On Mon, Nov 19, 2018 at 6:43 AM Kevin Kofler 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 thi

Re: Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Kevin Kofler
Frantisek Zatloukal wrote: >Install Fedora n-1 >Upgrade to Fedora n (updates-testing disabled) >Enable updates-testing >Update to latest packages >Verify that upgrade and update went fine and that the multilib packages >installed before are still present If you follow exact

Re: Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Adam Williamson
On Sun, 2018-11-18 at 21:48 +0100, Frantisek Zatloukal wrote: > We have encountered a bug[0] which seemingly “broke” offline updates after > systems were upgraded from an older Fedora to Fedora 29 and had some > multilib packages installed. After the discussion at last week's Release > Retrospectiv

Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Frantisek Zatloukal
We have encountered a bug[0] which seemingly “broke” offline updates after systems were upgraded from an older Fedora to Fedora 29 and had some multilib packages installed. After the discussion at last week's Release Retrospective meeting, I am proposing some changes to our blocking criterions in o