On Fri, 2022-04-29 at 14:52 +0100, Sérgio Basto wrote:
> A qui, 28-04-2022 às 15:18 +0100, Sérgio Basto escreveu:
> > On Thu, 2022-04-28 at 07:09 -0700, Troy Dawson wrote:
> > > 
> > > 
> > > On Thu, Apr 28, 2022 at 2:57 AM Sérgio Basto <ser...@serjux.com>
> > > wrote:
> > > > A qui, 28-04-2022 às 10:48 +0100, Sérgio Basto escreveu:
> > > > > A qua, 27-04-2022 às 16:58 -0700, Troy Dawson escreveu:
> > > > > > 
> > > > > > 
> > > > > > On Wed, Apr 27, 2022 at 4:38 PM Sérgio Basto
> > > > > > <ser...@serjux.com> 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.
> > > > > 
> > > > > Notification time stamped 2022-04-28 00:48:53 UTC
> > > > > 
> > > > > sergiomb's digikam-6.4.0-5.el8 failed to build
> > > > > http://koji.fedoraproject.org/koji/buildinfo?buildID=1957109
> > > > > 
> > > > > :( 
> > > > 
> > > > 
> > > > BTW if someone want to fix it, please built it in the side-tag
> > > > epel8-build-side-52356
> > > > 
> > > > fedpkg build --target=epel8-build-side-52356
> > > > 
> > > 
> > > 
> > > Ugg ... why must digikam be this way.  :(
> > > *Sigh* I know why.  It's the nature of the "let's pull it all
> > > together" program.
> > > Looking into this.
> > 
> > I will try the fix suggest  here 
> > https://forum.qt.io/topic/122702/error-aggregate-qpainterpath-path-has-incomplete-type-and-cannot-be-defined/3
> > ( include <QPainterPath> may be missing. Just add it. ) 
> 
> The fix worked .
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-62b1a9e158 h
> as been submitted .
> 
> The side-tag  changed because the previous has disappeared , I think
> it was deleted because had more than 30 days ... 
> 
> New side-tag is:  epel8-build-side-53268 


I decided to update ImageMagick on epel8 and sync it with Fedora with
some modifications
 
(https://src.fedoraproject.org/rpms/ImageMagick/c/4a0cb27f7f0603f259463e3052c4aa2b8cafec59?branch=epel8
 )

 so IM update will stay  in testing  more 8 days

Best regards,

-- 
Sérgio M. B.
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to