On Wed, 2019-01-30 at 12:36 -0800, Kevin Fenzi wrote:
On 1/30/19 9:45 AM, Miro HronĨok wrote:
> On 28. 01. 19 18:27, Ben Cotton wrote:
> > (Note this change was previously submitted for Fedora 29:
> >
https://pagure.io/fesco/issue/2064)
> >
> >
https://fedoraproject.org/wiki/Changes/Retire_YUM_3
>
> Based on the entire discussion so far, here's my proposal:
>
> - we change this to a system wide change
> - we move it to Fedora 31
> - we retire the packages from rawhide as soon as f30 is branched
> regardless of the dependent packages
> - packages with broken deps / FTBFS due to this will be retired if not
> fixed by beta freeze
+1, but I would like to see some comment from koji developers that this
is realistic with their plans or why not.
> Contingency mechanism:
>
> - if some process (releng or similar) needs the packages in order to
> ship Fedora 31, the packages are added into a designated copr repo
> maintained by the person/team responsible for the tool that needs yum
> (or other packages retired)
>
> - if the above is not possible and the packages are indeed needed in
> the actual f31 repos, packages are unretired but the person/team
> responsible for the tool that needs yum maintains them as long as they
> need them and retires them once that is no longer true
I don't think we want to use a copr for this, but we could build the
needed packages in our infra-f30 tag, so they would exist and be usable
by infra but not in the main repos. Of course we would really like to
avoid this...
Question: how plausibly can we sort of "test retire" yum? i.e. just
somehow run a single compose process without it included, and see what
breaks?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net