On Wed, 2022-04-27 at 23:44 +0100, Sérgio Basto wrote:
> On Wed, 2022-04-13 at 17:54 -0500, Carl George wrote:
> > > This was approved [0] in today's EPEL Steering Committee meeting.
> > > Please continue with the process for incompatible upgrades from
> > > step 4
> > > forward [1].
> > >
> > > [0]
> > > https://meetbot.fedoraproject.org/teams/epel/epel.2022-04-13-20.00.html
> > > [1]
> > > https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/#process_for_incompatible_upgrades
> > >
> > > --
> > > Carl George
> >
> > Based on repoquery it looks like only three packages need to be
> > rebuilt for this.
> >
> > converseen
> > digikam
> > dvdauthor
>
> Correct the other packages "just" use Imageagick tools , I need to
> check
> also packages that use perl(ImageMagick)
>
> I'm going start now !
digikam is updated in epel8-next , I'm doing a side-tag in epel8 .
This case brings one question , the packages of epel8-next will be
branch to epel8 ?
The way I see it is rhel 8.5 + epel 8 and centos stream 8 + epel 8 next
, rhel 8.6 is branched from centos stream 8 and epel 8 should also be
branched from epel 8 next . This implies that packages on epel 8 must
have lower versions than epel 8 next .
what I should do with digikam ?
The version in digikam epel8 and epel8-next are different. The reason is because of a package update (opencr) that is currently in CentOS Stream 8 that won't make it into RHEL 8 until RHEL 8.6.
For the epel8 version, just do a bump and build like you have the other packages on your list, keeping it's version the same.
I can do the epel8-next rebuild after you are done. And when RHEL 8.6 is released, I'll be bringing the higher version that is in epel8-next, over to epel8.
Troy