Unannounced soname bump - libwmf-0.2.so.7 -> libwmf-0.2.so.8

[Zdenek Dohnal]

Hi,

there is unannounced soname bump in the buildroot of rawhide and F29:

libwmf-0.2.so.7 -> libwmf-0.2.so.8

It breaks several components like gimp, ImageMagick, libabiword etc and
packages dependent on them (like emacs, gutenprint...) . These updates
are now unpushed, so they did not get into stable.

-- 
Zdenek Dohnal
Associate Software Engineer
Red Hat Czech - Brno TPB-C

[Björn 'besser82' Esser]

Am Freitag, den 01.02.2019, 14:09 +0100 schrieb Zdenek Dohnal:
>  Hi,
>  
>  there is unannounced soname bump in the buildroot of rawhide and F29:
>  
>  libwmf-0.2.so.7 -> libwmf-0.2.so.8
>  
>  It breaks several components like gimp, ImageMagick, libabiword etc
>  and
>  packages dependent on them (like emacs, gutenprint...) . These updates
>  are now unpushed, so they did not get into stable. 

As the libwmf update is important since it fixes a CVE, I've rebuilt all
the comsumers (abiword, gimp, GraphicsMagick, and ImageMagick) of
libwmf.so and added them to the update for fc2{8,9}.  Rawhide should be
fine again as well.

The maintainer of libwmf should have communicated the soname bump and
possibly ask for help rebuilding the affected packages *before* pushing
or building the new version to any branch, though…

[Caolán McNamara]

On Fri, 2019-02-01 at 15:56 +0100, Björn 'besser82' Esser wrote:
>  Am Freitag, den 01.02.2019, 14:09 +0100 schrieb Zdenek Dohnal:
>  > 
>  The maintainer of libwmf should have communicated the soname bump and
>  possibly ask for help rebuilding the affected packages *before*
>  pushing or building the new version to any branch, though… 
Yeah, my mistake. I was rushing before heading to the airport and
inadvertently bumped the soname upstream. I should have just waited
until the next day. I'll sort it out.

[Björn 'besser82' Esser]

>  Yeah, my mistake. I was rushing before heading to the airport and
>  inadvertently bumped the soname upstream. I should have just waited
>  until the next day. I'll sort it out. 
Don't worry, we have already fixed everything, including the updates for
Fedora 28 and 29.

[Björn 'besser82' Esser]

Am Freitag, den 01.02.2019, 19:27 +0100 schrieb Björn 'besser82' Esser:
>  > Yeah, my mistake. I was rushing before heading to the airport
> and
>  > inadvertently bumped the soname upstream. I should have just waited
>  > until the next day. I'll sort it out.
>  
>  Don't worry, we have already fixed everything, including the updates
>  for
>  Fedora 28 and 29. 

Rolling back the soname would be another bunch of additional work, at
least in Rawhide.

[Rex Dieter]

Björn 'besser82' Esser wrote:

>  Am Freitag, den 01.02.2019, 19:27 +0100 schrieb Björn
> 'besser82' Esser:
> > > Yeah, my mistake. I was rushing before heading to the airport and
> > > inadvertently bumped the soname upstream. I should have just waited
> > > until the next day. I'll sort it out.
> > 
> > Don't worry, we have already fixed everything, including the updates
> > for
> > Fedora 28 and 29.
>  
>  
>  Rolling back the soname would be another bunch of additional work, at
>  least in Rawhide. 
Rolling back is still probably the "right thing to do(tm)"

-- Rex

[Pete Walter]

02.02.2019, 15:54, "Rex Dieter" <rdieter(a)gmail.com&gt;:
>  Rolling back is still probably the "right thing to do(tm)"
Completely agree. Thanks for fixing it, Caolán!

Pete

[Björn 'besser82' Esser]

Am Freitag, den 01.02.2019, 17:55 +0000 schrieb Caolán McNamara:
>  Yeah, my mistake. I was rushing before heading to the airport and
>  inadvertently bumped the soname upstream. I should have just waited
>  until the next day. I'll sort it out. 

And now you have broken fast-forwardable release-branches for at least
two packages, just to trigger unneccessary NVR bumps and rebuilds for
F28 and F29.  :/  As with the new version of libwmf the soname doesn't
change anymore, no rebuild for the consumer packages was neccessary.

*Please* ask expirienced packagers how to do things right *before* just
doing something…

I've already modified the updates for libwmf to just have the new NVR in
them, other packages are *NOT* needed in this case.