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

Bug#1060103: transition: imagemagick7



Le dimanche 2 juin 2024, 11:17:33 UTC Sebastian Ramacher a écrit :
> On 2024-02-02 17:21:43 +0000, Bastien Roucariès wrote:
> > Le vendredi 2 février 2024, 16:53:10 UTC Sebastian Ramacher a écrit :
> > > Control: tags -1 moreinfo
> > > 
> > > Hi Bastien
> > > 
> > > On 2024-01-05 22:35:44 +0000, Bastien Roucariès wrote:
> > > > Package: release.debian.org
> > > > Severity: important
> > > > User: release.debian.org@packages.debian.org
> > > > Usertags: transition
> > > > X-Debbugs-CC: ftpmaster@debian.org
> > > > 
> > > > Imagemagick will need a new major bump
> > > > 
> > > > I achieved to get imagemagick 7 build for experimental (it is only on salsa not
> > > > uploaded yet).
> > > > 
> > > > Every package include a version in the package name (except legacy package name
> > > > and perl*) so I plan to do some step by step migration, because it is mainly
> > > > coinstallable with imagemagick 6.
> > > 
> > > Why does this migration require co-instabillity with the old version?
> > > This makes the transition overly complicated. Do you expect major
> > > changes required in reverse dependencies of imagemagick's shared
> > > library?
> > 
> > The problem is not the library but the command line interface that may need change.
> > 
> > Librarry will break (I think here about php module that will need a update), but it is treatable.
> > 
> > convert6 is not fully compatible with convert7
> > 
> > convert6 will be co installable with convert7 in order to test, and convert will be provided by alternative system.
> 
> If they are not fully compatible, then alternatives are not an option.

They are 95% compatible

> How many packages are we talking about? Have bugs been filed for
> packages thar are not compatible with convert7?

The problem is chicken and eggs problem. If you could not test then you could not report bug.
A least both should be in experimental for running a full archive rebuild

Not also that imagemagick6 is supported upstream only until 2027... So we should migrate to 7.

That why I think my way is a good way.

Suse and redhat transitionned see https://fedoraproject.org/wiki/Changes/ImageMagick7

Discussion point to a least broken on redhat
* autotrace - plan to notify upstream
* dvdauthor - point to GraphicsMagick or IM6, plan to notify upstream
* q - dead upstream, planned to point to IM6
* vdr-skinnopacity - current upstream dead, plan to notify new upstream
* vdr-tvguide - plan to notify upstream

We could also drop imagemagick6 and use graphickmagick if needed but it introduce other problem

Thanks

Bastien
> 
> Cheers
> 

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: