DevHeads.net

Urgent attention required; ImageMagick update breakage

Hi all,

An ImageMagick update (6.9 => 7.0) with an SONAME bump and other breakage has been
pushed to F25 and higher.

First, the update introduces regressions on s390x and ppc64 arches.
- <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1484578" title="https://bugzilla.redhat.com/show_bug.cgi?id=1484578">https://bugzilla.redhat.com/show_bug.cgi?id=1484578</a>
- <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1484579" title="https://bugzilla.redhat.com/show_bug.cgi?id=1484579">https://bugzilla.redhat.com/show_bug.cgi?id=1484579</a>

Secondly, rebuilds are required for:

autotrace-0.31.1-44.fc26.src.rpm
converseen-0.9.6.2-1.fc27.src.rpm
dmtx-utils-0.7.4-2.fc27.src.rpm
drawtiming-0.7.1-20.fc26.src.rpm
F gtatool-2.2.0-4.fc27.src.rpm
imageinfo-0.05-25.fc26.src.rpm
inkscape-0.92.1-5.20170510bzr15686.fc27.src.rpm
kxstitch-1.2.0-7.fc26.src.rpm
perl-Image-SubImageFind-0.03-11.fc27.src.rpm
pfstools-2.0.6-1.fc27.src.rpm
F php-magickwand-1.0.9.2-9.fc24.src.rpm
F php-pecl-imagick-3.4.3-0.3.RC1.fc26.src.rpm
psiconv-0.9.8-20.fc26.src.rpm
q-7.11-27.fc27.src.rpm
ripright-0.11-3.fc26.src.rpm
rss-glx-0.9.1.p-29.fc26.src.rpm
F rubygem-rmagick-2.16.0-3.fc26.src.rpm
F synfig-1.2.0-5.fc27.src.rpm
(boost issues)
F synfigstudio-1.1.10-0.20160706gitd4e547.fc25.src.rpm
(needs synfig)
vdr-scraper2vdr-1.0.5-2.20170611git254122b.fc27.src.rpm
vips-8.5.6-1.fc27.src.rpm
WindowMaker-0.95.8-1.fc27.src.rpm
F cuneiform
(some c++ blowup)
k3d

The ones with F have possible compile issues.

Thirdly, two updates have been created. I've disabled autopush on them.
- <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-0a1f3de4eb" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-0a1f3de4eb">https://bodhi.fedoraproject.org/updates/FEDORA-2017-0a1f3de4eb</a>
- <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-c276ee400a" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-c276ee400a">https://bodhi.fedoraproject.org/updates/FEDORA-2017-c276ee400a</a>

It is really late here and I don't have the time to investigate the arch issues right now. I'll investigate when I can.

Comments

Re: Urgent attention required; ImageMagick update breakage

By Richard W.M. Jones at 09/06/2017 - 11:23

I only skimmed this thread and didn't see any reference to this.

Currently emacs is uninstallable in Rawhide, resulting in any Koji
build that depends on emacs failing:

DEBUG util.py:439: - nothing provides libMagickCore-7.Q16HDRI.so.3()(64bit) needed by emacs-1:25.2-9.fc28.x86_64

Is there a fix for this?

Rich.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 09/06/2017 - 11:51

On 09/06/2017 10:23 AM, Richard W.M. Jones wrote:
ImageMagick was downgraded from v7 to v6 today. A emacs rebuild will fix it. I've
submitted one.

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/06/2017 - 12:28

On Wed, 2017-09-06 at 10:51 -0500, Michael Cronenworth wrote:
I am doing the rebuilds. Unfortunately, the f28-build repository took a
long time to regenerate after the ImageMagick build went through, so I
couldn't get them done in time to all go into the same compose
together.

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/06/2017 - 14:12

On Wed, 2017-09-06 at 09:28 -0700, Adam Williamson wrote:
Rebuilds are now done for Rawhide, and this is the update for F27:

<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-f50d944ec7" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-f50d944ec7">https://bodhi.fedoraproject.org/updates/FEDORA-2017-f50d944ec7</a>

I've filed a bug and nominated it for a freeze exception:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1489124" title="https://bugzilla.redhat.com/show_bug.cgi?id=1489124">https://bugzilla.redhat.com/show_bug.cgi?id=1489124</a>

Re: Urgent attention required; ImageMagick update breakage

By Richard W.M. Jones at 09/06/2017 - 16:35

On Wed, Sep 06, 2017 at 11:12:14AM -0700, Adam Williamson wrote:
Thanks (both), emacs installs in Rawhide now.

Rich.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 08/28/2017 - 21:39

Rebuild status:
* All F25/F26 packages have been rebuilt against ImageMagick 6.9.9.9
* Most of the F27+ packages have been rebuilt with the following exceptions:
- cuneiform
FTBFS since Fedora 23, last upstream release is from 2011
- imageinfo
Requires porting, upstream is alive. I may come back and fix this later. CC'ing
maintainer.
- perl-Image-SubImageFind
Requires porting, upstream is dead
- psiconv
Requires porting, upstream is dead
- q
Obsolete back in 2008, replaced by "Pure" language... which is not in Fedora
- rubygem-rmagick
Requires porting, upstream is alive, but not interested. I'll have to come back
to this one. CC'ing maintainer.

The rebuilt packages are using a direct support style patch and not a comprehensive
support patch. I'll be making comprehensive patches when I have time and shipping
them upstream. If anyone wants to create a patch before I do please feel free. Just
link the upstream git commit or report with the patch.

Thanks,
Michael

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/01/2017 - 14:13

On Mon, 2017-08-28 at 20:39 -0500, Michael Cronenworth wrote:
Thanks Michael!

FESCo decided at today's meeting that 7 should not go to F27 (unless it
can be made parallel installable and not used by anything release-
blocking by default), and to go into F28 there must be a system-wide
Change:

<a href="https://pagure.io/fesco/issue/1766" title="https://pagure.io/fesco/issue/1766">https://pagure.io/fesco/issue/1766</a>

I'm happy to do the downgrade + rebuilds for F27 (when I'm back from
Flock), we'll have to decide precisely what to do with Rawhide.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 09/01/2017 - 18:14

On 09/01/2017 01:13 PM, Adam Williamson wrote:
The libs are definitely parallel installable. The binaries share a name so we could
use alternatives and default to version 6. Thoughts?

Re: Urgent attention required; ImageMagick update breakage

By Ralf Corsepius at 09/03/2017 - 04:32

On 09/02/2017 12:14 AM, Michael Cronenworth wrote:
If the latter doesn't apply, it would be better to those remove package
which requires these old libs from the distro.

Versioned binaries could make some sense if the these binaries are not
call-compatible.

Ralf

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/04/2017 - 11:39

On Sun, 2017-09-03 at 10:32 +0200, Ralf Corsepius wrote:
The 6 series is still maintained upstream at present, as discussed
earlier.

Re: Urgent attention required; ImageMagick update breakage

By Matthew Miller at 09/02/2017 - 09:10

On Fri, Sep 01, 2017 at 05:14:17PM -0500, Michael Cronenworth wrote:
Would we be keeping these separate for a long time? Alternatives are
really pretty ugly and I'd hate to see that introduced just for one
release.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 09/02/2017 - 10:05

On 09/02/2017 08:10 AM, Matthew Miller wrote:
After handling all the rebuilds for version 7, it is pretty rare for an upstream to
support version 7 right now. I would strike an uneducated guess at 1-2 years for
upstreams to come around to porting. It would not surprise me if some upstreams stay
at version 6 unless ImageMagick decides to stop supporting version 6. Not to mention
the dead upstreams where we will have to port ourselves or our friends at  Canonical
and Debian that don't even have version 7 (or a recent version 6) in their repos.

Re: Urgent attention required; ImageMagick update breakage

By Matthew Miller at 09/02/2017 - 10:34

On Sat, Sep 02, 2017 at 09:05:02AM -0500, Michael Cronenworth wrote:
Ugh. How many of these are using the library and how many are shelling
out? Could we just tack a 6 on the end of all of the older binaries?

Or port those to GraphicsMagick as suggested elsewhere.

Re: Urgent attention required; ImageMagick update breakage

By =?ISO-8859-1?Q?... at 09/02/2017 - 11:12

On Sat, 2017-09-02 at 10:34 -0400, Matthew Miller wrote:
I think is more simpler use version 7 just in F28 and we gain some
time.
I (also) saw that API change is not easy to fix [1] , issue opened in
Jul 18, and no one provide a patch ...

[1]
<a href="https://github.com/OpenShot/libopenshot/issues/60" title="https://github.com/OpenShot/libopenshot/issues/60">https://github.com/OpenShot/libopenshot/issues/60</a>

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/02/2017 - 11:05

On Sat, 2017-09-02 at 10:34 -0400, Matthew Miller wrote:
I don't think we looked at things which just use the CLI at all, at
least I was using a list based on library dependencies.

The list of things which at least express an explicit dependency on
ImageMagick or one of the binaries it provides is:

DVDAuthorWizard-0:1.4.6-9.fc26.noarch
ImageMagick-devel-0:7.0.6.9-4.fc27.i686
ImageMagick-devel-0:7.0.6.9-4.fc27.x86_64
a2ps-0:4.14-32.fc27.i686
a2ps-0:4.14-32.fc27.x86_64
anyremote-0:6.6.1-4.fc27.x86_64
c-graph-0:2.0-12.fc27.x86_64
caja-image-converter-0:1.18.1-4.fc27.x86_64
conky-manager-0:2.3.4-5.fc27.x86_64
dblatex-0:0.3.10-2.fc27.noarch
devedeng-0:4.8.9-1.fc27.noarch
dvd-slideshow-0:0.8.6-1.1.fc26.1.noarch
dvdrip-0:0.98.11-14.fc27.x86_64
epix-0:1.2.17-3.fc27.x86_64
fbida-0:2.09-13.fc27.x86_64
ffmulticonverter-0:1.8.0-5.fc26.noarch
freewrl-0:3.0.0-5.20170729git4f920cb.fc27.i686
freewrl-0:3.0.0-5.20170729git4f920cb.fc27.x86_64
gallery2-imagemagick-0:2.3.2-17.fc27.noarch
geeqie-0:1.3-5.fc27.x86_64
gegl03-0:0.3.20-1.fc27.i686
gegl03-0:0.3.20-1.fc27.x86_64
gnome-photos-0:3.25.91-1.fc27.x86_64
gyachi-0:1.2.11-14.fc24.x86_64
gyazo-0:1.2-3.fc27.noarch
icewm-clearlooks-0:1.3.8-14.fc27.noarch
jumpnbump-menu-0:1.60-4.fc27.noarch
latex2rtf-0:2.3.16-1.fc27.x86_64
libpst-0:0.6.71-3.fc27.x86_64
lives-0:2.8.7-2.fc27.x86_64
lyx-0:2.2.3-2.fc27.x86_64
mediawiki-0:1.29.0-2.fc27.noarch
mtpaint-0:3.40-23.fc27.x86_64
nautilus-image-converter-0:0.3.1-0.13.git430afce31.fc27.x86_64
nemo-image-converter-0:3.4.0-2.fc27.x86_64
perl-Panotools-Script-0:0.28-12.fc27.noarch
phatch-cli-0:0.2.7-28.fc27.noarch
playonlinux-0:4.2.12-3.fc27.x86_64
shutter-0:0.93.1-8.fc27.noarch
variety-0:0.6.5-1.fc27.noarch
w3m-img-0:0.5.3-34.git20170102.fc27.x86_64

These things Recommend it:

diffoscope-0:77-2.fc26.noarch
gnumed-0:1.6.7-4.fc27.noarch
gscan2pdf-0:1.8.6-1.fc27.noarch
python2-sphinx-0:1.6.3-2.fc27.noarch
python3-sphinx-0:1.6.3-2.fc27.noarch
recoverjpeg-0:2.6.1-4.fc27.x86_64
sway-0:0.14.0-2.fc27.x86_64

and these Suggest it:

abcde-0:2.8.1-4.fc27.noarch
gap-pkg-hap-0:1.11.14-3.fc27.noarch
winswitch-0:0.12.21-21.fc27.noarch

The existence of Recommends and Suggests dependencies are significant,
because it rather suggests there may be *other* things which can
optionally use IM where the maintainer previously didn't want to use a
hard Requires: - I would guess there may be cases where no-one thought
to add a Recommends or Suggests yet.

Note I did try building a few things against GM but none of them 'just
worked', so this would likely be a porting effort like the IM 6 -> 7
one - probably not worth the effort without co-ordination with
upstreams.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 09/02/2017 - 10:59

On 09/02/2017 09:34 AM, Matthew Miller wrote:
The rebuilds were for library linked packages. I have not touched any packages that
shell out. A reqpoquery returns about 46 packages that may do so. It may be more
effective to add a "7" to the newer binaries.

That's great, but that would be far beyond what I'm willing to work on. I also don't
know how receptive upstreams would be to patches for that conversion. I picked up
ImageMagick only two weeks ago to prevent a disaster from hitting stable Fedora
releases. I am not positive I want to become a permanent maintainer of it.

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/02/2017 - 11:06

On Sat, 2017-09-02 at 09:59 -0500, Michael Cronenworth wrote:
Well, the easy option is just to revert to 6.9.9 and not update to 7 at
all. It's not incumbent upon us to do so at least until upstream starts
making noises about killing the 6 series, and there doesn't seem to be
any particularly strong *reason* to do it...

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 09/02/2017 - 11:19

On 09/02/2017 10:06 AM, Adam Williamson wrote:
That may be the only option. I'm not convinced that version 7 is worth our time and
I don't have a relationship with upstream to know if it should be worth our time at
all (ever). I've opened a dialogue with ImageMagick to ask what they think.

<a href="https://www.imagemagick.org/discourse-server/viewtopic.php?f=2&amp;t=32622&amp;p=149403" title="https://www.imagemagick.org/discourse-server/viewtopic.php?f=2&amp;t=32622&amp;p=149403">https://www.imagemagick.org/discourse-server/viewtopic.php?f=2&amp;t=32622&amp;p...</a>

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/02/2017 - 12:36

On Sat, 2017-09-02 at 10:19 -0500, Michael Cronenworth wrote:
So I'm gonna start working on the 6.9.9 downgrade in F27, and I'm
tempted to just downgrade Rawhide at the same time, and if we actually
do decide to try 7 again, we can start over at that time. Do you agree
with that plan? Thanks! (It doesn't change anything about the required
epoch bumps, because even if we did 6.9.9 in F27 and stayed with 7 in
Rawhide, we'd need to bump the epoch on *both* to ensure Rawhide's 7
was ahead of F27's 6).

Re: Urgent attention required; ImageMagick update breakage

By =?ISO-8859-1?Q?... at 09/03/2017 - 11:13

On Sat, 2017-09-02 at 14:10 -0500, Michael Cronenworth wrote:
Well if we go to have ImageMagick6 and ImageMagick7 in F27+ and since
ImageMagick7 should be the main package, in my point of view , we
should add ImageMagick6 package and maintain ImageMagick as is , like,
for example, openssl-1.1 and compat-openssl10 .

Cheers,

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/04/2017 - 11:40

On Sun, 2017-09-03 at 16:13 +0100, Sérgio Basto wrote:
Nope, that's exactly the opposite of what FESCo agreed: IM7 can only go
in as the *variant* package, not the main one. The main one must be
IM6.

Re: Urgent attention required; ImageMagick update breakage

By Stephen Gallagher at 09/04/2017 - 13:55

On Mon, Sep 4, 2017 at 11:41 AM Adam Williamson < ... at fedoraproject dot org>
wrote:

We didn't specifically rule on the naming, FWIW. As far as IM7 being the
variant package, we mostly ruled that for F27, nothing using IM in the
release blocking media may require IM7. I'm personally neutral on how the
files and packages are named as long as the implementation accomplishes
that goal.

For F28, FESCo will consider any proposal brought to us as a Change
Proposal (complete with a plan for rebuilds and migrations).

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/04/2017 - 14:01

On Mon, 2017-09-04 at 17:55 +0000, Stephen Gallagher wrote:
well, okay, fine, I guess *technically* we could make ImageMagick be 7
and have ImageMagick6 and change the requirements in every single
package that currently requires ImageMagick. But...let's not do that?
:)

Re: Urgent attention required; ImageMagick update breakage

By =?ISO-8859-1?Q?... at 09/04/2017 - 15:07

On Mon, 2017-09-04 at 11:01 -0700, Adam Williamson wrote:
That is the point, how many package fail to build with ImageMagick7 ?
we "just" need change requires on FTBFS packages (with ImageMagick7)

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/04/2017 - 19:11

On Mon, 2017-09-04 at 20:07 +0100, Sérgio Basto wrote:
No it isn't the point. More things actually use the ImageMagick *CLI*
than use the library, and the CLI of ImageMagick 7 is very different
from the CLI of ImageMagick 6. This is the *main* reason we do not just
want to make the ImageMagick package suddenly become ImageMagick 7 -
because IM 7 does not provide the CLI people currently expect from the
package called 'ImageMagick'. It's not primarily about things which
build against the libraries.

Re: Urgent attention required; ImageMagick update breakage

By Moez Roy at 09/06/2017 - 00:30

On Mon, Sep 4, 2017 at 4:11 PM, Adam Williamson < ... at fedoraproject dot org>
wrote:

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/06/2017 - 01:18

On Tue, 2017-09-05 at 21:30 -0700, Moez Roy wrote:
Uh...read this:

<a href="https://www.imagemagick.org/script/porting.php#cli" title="https://www.imagemagick.org/script/porting.php#cli">https://www.imagemagick.org/script/porting.php#cli</a>

There's two-three pages (depending on your browser settings) of changes
to how the CLI works, many of them backwards-incompatible.

Just because there's still a command called 'convert' doesn't mean
everything is the same.

Re: Urgent attention required; ImageMagick update breakage

By =?ISO-8859-1?Q?... at 09/04/2017 - 19:17

On Mon, 2017-09-04 at 16:11 -0700, Adam Williamson wrote:
OK, I understood your point of view and I change my opinion to youropinion .

Best regards,

Re: Urgent attention required; ImageMagick update breakage

By =?ISO-8859-1?Q?... at 09/04/2017 - 18:15

On Mon, 2017-09-04 at 20:07 +0100, Sérgio Basto wrote:
We already have ImageMagick 6.9.3 ABI compatibility package.

<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-20d59de2dc" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-20d59de2dc">https://bodhi.fedoraproject.org/updates/FEDORA-2017-20d59de2dc</a>

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/04/2017 - 19:13

On Mon, 2017-09-04 at 23:15 +0100, Sérgio Basto wrote:
I don't really see *why*. It doesn't seem to be very necessary. We've
already rebuilt everything in 25 and 26 for 6.9.9.9.

Re: Urgent attention required; ImageMagick update breakage

By =?ISO-8859-1?Q?... at 09/04/2017 - 09:06

Michael , I move thread to here [1] 

[1] <a href="https://pagure.io/fesco/issue/1766" title="https://pagure.io/fesco/issue/1766">https://pagure.io/fesco/issue/1766</a>

On Sun, 2017-09-03 at 16:13 +0100, Sérgio Basto wrote:

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 09/02/2017 - 15:37

On Sat, 2017-09-02 at 14:10 -0500, Michael Cronenworth wrote:
OK, I'll do the downgrades for both, then. I'll leave you to do the IM7
package, as I'm not really interested in IM per se - I only got
involved in this mess at all because I *am* very interested in making
sure F27 and Rawhide...work :) Thanks.

Re: Urgent attention required; ImageMagick update breakage

By Dan =?ISO-8859-... at 08/24/2017 - 03:04

On Wed, 23 Aug 2017 22:16:40 -0500

these issues shouldn't have been solved with an ExcludeArch immediately
as there is a risk of breaking buildroots for other packages and
for other teams like modularity. If such problem happens, please contact
us (the alternative-arches team) first, so we can plan the best action.

Thanks

Dan

Re: Urgent attention required; ImageMagick update breakage

By Dan =?ISO-8859-... at 08/24/2017 - 08:05

On Thu, 24 Aug 2017 09:04:51 +0200

so I've applied a workaround [1] to get ImageMagick built on all arches
again until we have a proper fix, it's in Rawhide now, feel free to
apply it to other branches as well

It adds one more reason to run a CI on the upstream level that would
cover alternative arches, we have already something in progress.

[1]
<a href="http://pkgs.fedoraproject.org/rpms/ImageMagick/c/9d8a0e0d350a8d02ae40b76ea03f70d118798f23?branch=master" title="http://pkgs.fedoraproject.org/rpms/ImageMagick/c/9d8a0e0d350a8d02ae40b76ea03f70d118798f23?branch=master">http://pkgs.fedoraproject.org/rpms/ImageMagick/c/9d8a0e0d350a8d02ae40b76...</a>

Dan

Re: Urgent attention required; ImageMagick update breakage

By Remi Collet at 08/24/2017 - 10:25

Le 24/08/2017 à 14:05, Dan Horák a écrit :

I really think we have to revert to 6 in stable branch
(and perhaps even in F27, which is very close to feature freeze)

- soname bump
- lot of removed API
- HDRI enabled by default

Remi.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 08/24/2017 - 10:47

On 08/24/2017 09:25 AM, Remi Collet wrote:
The SONAME is changing in 6.9 as well so I'm not sure reverting is great either
otherwise I would have done it.

I'm prepared to perform rebuilds and push updates to get this resolved. Assuming no
objections in the next day I'll get it rolling. Worst case if there's negative karma
on the updates I'll push a revert to 6.9.

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 08/24/2017 - 11:24

On Thu, 2017-08-24 at 09:47 -0500, Michael Cronenworth wrote:
As Remi said, the changes in 6.9.9 are far less significant than those
in 7.0.6. As several people pointed out, sending 7.x to stable releases
is clearly against the updates policy. I'd agree we definitely must
revert to 6.x for F25 and F26 updates; for those we should send out a
6.9.9-9 update with rebuilds of all deps. I don't care if F27 and
Rawhide go to 6.9.9-9 or 7.0.6, but whichever, it should get done soon
at least for F27.

I'm also willing to work on this, but everyone who's interested should
agree on a plan first, and then we could possibly split the work up
(e.g. into 6.x and 7.x work).

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 08/24/2017 - 11:43

On 08/24/2017 10:24 AM, Adam Williamson wrote:
I'll compromise with F25/26 with 6.9 and F27+ getting 7.0.

I'll get an Epoch bump started... when it completes if you want to do rebuilds for
F25/26 I'll work on F27+.

Thanks,
Michael

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 08/24/2017 - 19:24

On Thu, 2017-08-24 at 10:43 -0500, Michael Cronenworth wrote:
Note, I am rebuilding ImageMagick itself again for F27 and Rawhide,
because the versioning was wrong: Moez incorrectly moved the patchlevel
from %{version} to %{release}. This is wrong because it is part of the
upstream versioning, not the downstream. Note the NEVRs listed in the
%changelog were still in the old, correct form, but the *actual* NEVRs
of the recent builds were wrong. I have reverted the relevant parts of
the spec to exactly how it was before, and corrected the changelog so
it gives the real NEVRs for each build.

This is significant to rubygem-rmagick.spec , which must specify the
exact version (including patchlevel) of ImageMagick it's built against.
So I had to go ahead and fix this in order to be able to rebuild
rubygem-rmagick correctly (I'm going to do the F27+ rebuilds of it as
well as the F25/F26 rebuilds for git consistency reasons).

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 08/24/2017 - 16:38

On Thu, 2017-08-24 at 10:43 -0500, Michael Cronenworth wrote:
BTW, it occurred to me for F27+ it may be worth checking if each
project supports a less messy alternative, like GraphicsMagick, which I
think seems to be a rather saner option. For F25/F26 of course I won't
make such switches.

Re: Urgent attention required; ImageMagick update breakage

By Remi Collet at 08/24/2017 - 11:50

Le 24/08/2017 à 17:43, Michael Cronenworth a écrit :

I don't think epoch bump is needed
(package never go in the repo)

Remi

Re: Urgent attention required; ImageMagick update breakage

By Kevin Fenzi at 08/24/2017 - 11:49

On 08/24/2017 08:43 AM, Michael Cronenworth wrote:
Epoch bump? Why? The f25/f26 packages never even got to testing... Just
revert the commits, etc.

kevin

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 08/24/2017 - 11:54

On 08/24/2017 10:49 AM, Kevin Fenzi wrote:
I thought Koji did an NVR check? Won't let a lower version or is it only when it's
been pushed?

Re: Urgent attention required; ImageMagick update breakage

By Dan =?ISO-8859-... at 08/24/2017 - 12:15

On Thu, 24 Aug 2017 10:54:12 -0500

koji won't let you build one NVR twice for non-scratch builds

bodhi has some NVR checks, but they are not blocking

Dan

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 08/24/2017 - 12:27

On Thu, 2017-08-24 at 18:15 +0200, Dan Horák wrote:
Yep, +1 others, for F25/F26 we don't need to do any new build for
imagemagick itself, just revert the commits in the repo, set up a
buildroot override for the 6.9.9-9 package, and then get to rebuilding
dependencies.

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 08/24/2017 - 12:36

On Thu, 2017-08-24 at 09:27 -0700, Adam Williamson wrote:
Sorry, of course we have to actually build 6.9.9-9. It looks like
you're on this already, thanks.

Re: Urgent attention required; ImageMagick update breakage

By Michael Cronenworth at 08/24/2017 - 14:47

On 08/24/2017 11:36 AM, Adam Williamson wrote:
I've also created updates in Bodhi. Please feel free to attach your builds to it.

F26: <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f27031c8f" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f27031c8f">https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f27031c8f</a>
F25: <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-3a568adb31" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-3a568adb31">https://bodhi.fedoraproject.org/updates/FEDORA-2017-3a568adb31</a>

Re: Urgent attention required; ImageMagick update breakage

By Adam Williamson at 08/24/2017 - 21:31

On Thu, 2017-08-24 at 13:47 -0500, Michael Cronenworth wrote:
I have done nearly all the rebuilds and added them to the updates, just
waiting on inkscape for f25 to finish up, and buildroot overrides for
synfig to kick in so I can build synfigstudio.

Note: php-magickwand does not build with PHP 7 and no-one upstream
seems terribly inclined to fix it any time soon, so that one's just
going to have to stay broken (I doubt the current package is even
installable on F25 or F26, so this is not likely a regression) unless
someone wants to step up and do the PHP 7 port (I...do not).

Re: Urgent attention required; ImageMagick update breakage

By Remi Collet at 08/25/2017 - 00:59

Le 25/08/2017 à 03:31, Adam Williamson a écrit :
Thanks for your work on this.

About php-pecl-imagick, I think we'll have to apply patch from

<a href="https://github.com/mkoppanen/imagick/pull/186" title="https://github.com/mkoppanen/imagick/pull/186">https://github.com/mkoppanen/imagick/pull/186</a>

In Fedora 25 / 26, so users will be aware of some removed methods in
Fedora 27

Waiting for upstream feedback about this very old PR, and will try to
manage it (probably after the current update will be in stable to not
differ it more than needed)

Remi

P.S. I also need to manage update of ImageMagick6 and ImageMagick7 for
users of my repository, to not break everything, and push new build at
same time than official updates...