The team was able to get koji 1.17 released today. :) So, while the YUM
deprecation got moved out to F31, you may want to pull 1.17 into F30.
On Fri, Mar 1, 2019 at 3:18 PM Dennis Gregorovic <dgregor(a)redhat.com> wrote:
On Fri, Mar 1, 2019 at 4:25 AM Michal Domonkos <mdomonko(a)redhat.com>
> On Fri, Mar 1, 2019 at 2:24 AM Dennis Gregorovic <dgregor(a)redhat.com>
> > I have an update on the koji end. The 1.17 release will not only drop
> the yum dependency, it will also have full python 3 support (except for
> image building that uses oz / imagefactory). Unfortunately, there is only
> medium confidence that the 1.17 release will be ready by the F30 devel
> freeze on Tuesday. It depends on whether QE uncovers any issues in its
> final testing. If we're not able to land the release on Tuesday, what is
> the backup plan?
> I suppose you're concerned about the Python 3 support part and not
> about the DNF port, but in case it's the latter -- please note the YUM
> deprecation has been approved for F31 (and is already happening in
> Rawhide now) as opposed to F30, to give everyone a bit more time to
> finish their porting efforts.
Ah, I didn't know that! In that case, we'll still try to land koji 1.17
for F30 if we can, but we'll make sure that it's had sufficient testing and
not rush it out prematurely.
Also, I forgot to include koji-devel@ on the previous emails. Looping in
that list now.
Manager, PnT DevOps
dgregor(a)redhat.com T: +1-978.392.3112 M: +1-617.901.9799