Re: [HEADS UP] ImageMagick side-tag for epel8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Wed, Apr 27, 2022 at 4:38 PM Sérgio Basto <sergio@xxxxxxxxxx> wrote:
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

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux