Bug#811304: [Pkg-wmaker-devel] Bug#811304: Bug#811304: Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[kix]

El 2016-01-21 07:43, Andreas Metzler escribió:

On 2016-01-19 Doug Torrance  wrote:

On 01/19/2016 02:41 PM, Andreas Metzler wrote:

[...]

2a Patch the source to fix back the symbol versioning to
LIBWRASTER3

[...]
Option 2a sounds good to me.  Feel free to revert my last few 
commits if you

get to it before I do.


Thanks for preparing for my commit in advance. How about opening a
experimental branch for the package split, to spare us the 
commit/revert

cycle if we find another urgent issue?


+1

IMO, we should play with the experimental branch first.

Bug#811304: [Pkg-wmaker-devel] Bug#811304: Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Andreas Metzler]

On 2016-01-19 Doug Torrance  wrote:
> On 01/19/2016 02:41 PM, Andreas Metzler wrote:
[...]
>> 2a Patch the source to fix back the symbol versioning to
>> LIBWRASTER3
[...]
> Option 2a sounds good to me.  Feel free to revert my last few commits if you
> get to it before I do.

Thanks for preparing for my commit in advance. How about opening a
experimental branch for the package split, to spare us the commit/revert
cycle if we find another urgent issue?

> Just to clarify, would the best course of action for upstream to be to go
> ahead and bump the soname for libwraster to 6 for the next release? If so, I
> can prepare a patch.

I think 2a is also the best option for upstream, not a soname bump.
Perhaps a timely 0.95.7.1 issue?

BTW: Do you have admin privileges for the pkg-wmaker-devel list? If so
would you mind disabling addition of a the [Pkg-wmaker-devel] tag to 
the subject?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#811304: [Pkg-wmaker-devel] Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

On 01/19/2016 02:41 PM, Andreas Metzler wrote:

We can choose one of these hacks:
1 Find a way to ship unpatched libwraster 0.95.7 in Debian.

2a Patch the source to fix back the symbol versioning to
LIBWRASTER3

2b Patch the source to use a different soname. (If the ABI breaks in
an incompatible way, requiring rebuilds library maintance 101 says: bump
the soname.)

1 cannot be done /properly/. libwraster-0.95.6 and libwraster-0.95.7
have the same soname and are therefore not co-installable but would
need to conflict. So we cannot do the usual seamless partial upgrades,
it won't be possible to upgrade wmaker (built against
libwraster-0.95.7) while keeping wmweather+ 2.15-1.1 (built against
libwraster-0.95.6) functional.

Both 2a and 2b have the downside that Debian's libwraster/0.95.7 will
be binary incompatible with unpatched libwraster/0.95.7 (as possible
shipped by e.g. Fedora)

2a has the benefit of avoiding an actually useless library transition.
There is little to speak for 2b, except perhaps the fact that it shows
that our ABI differs from upstream.

So, having to choose I would strongly vote for 2a, adding attached
patch to debian/patches/ and updating the symbol file (again).

I have not got more time to spend on this today, but if you agree that
this is best course of action I can make an upload along these lines.
Ideally upstream would fix this instead of us.


Thank you for the clarification, Andreas!  I completely neglected to 
think about the fact that libwraster5 and my proposed libwraster5v2 
would both be trying to install the same file.


Option 2a sounds good to me.  Feel free to revert my last few commits if 
you get to it before I do.


Just to clarify, would the best course of action for upstream to be to 
go ahead and bump the soname for libwraster to 6 for the next release? 
If so, I can prepare a patch.


Doug

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Andreas Metzler]

On 2016-01-18 Doug Torrance  wrote:
> Control: tags -1 pending

> On 01/18/2016 02:55 PM, Doug Torrance wrote:
> > I think the solution is to rename libwraster5 to something like
> > libwraster5v2 and trigger an auto transition.

> I've pushed these changes to git.  Note that the new library already
> means we'll have to wait for the NEW queue, so I've kept the new
> wmaker-utils package for #78119 in.

> Andreas or kix, would either of you be able to take a look and upload?
[...]

Hello Doug,

it is not that simple. :-(

We can choose one of these hacks:
1 Find a way to ship unpatched libwraster 0.95.7 in Debian.

2a Patch the source to fix back the symbol versioning to
LIBWRASTER3

2b Patch the source to use a different soname. (If the ABI breaks in
an incompatible way, requiring rebuilds library maintance 101 says: bump
the soname.)

1 cannot be done /properly/. libwraster-0.95.6 and libwraster-0.95.7
have the same soname and are therefore not co-installable but would
need to conflict. So we cannot do the usual seamless partial upgrades,
it won't be possible to upgrade wmaker (built against
libwraster-0.95.7) while keeping wmweather+ 2.15-1.1 (built against
libwraster-0.95.6) functional.

Both 2a and 2b have the downside that Debian's libwraster/0.95.7 will
be binary incompatible with unpatched libwraster/0.95.7 (as possible
shipped by e.g. Fedora)

2a has the benefit of avoiding an actually useless library transition.
There is little to speak for 2b, except perhaps the fact that it shows
that our ABI differs from upstream.

So, having to choose I would strongly vote for 2a, adding attached
patch to debian/patches/ and updating the symbol file (again).

I have not got more time to spend on this today, but if you agree that
this is best course of action I can make an upload along these lines.
Ideally upstream would fix this instead of us.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Patch back libwraster symbol version to LIBWRASTER3.
Author: Andreas Metzler 
Bug-Debian: https://bugs.debian.org/811304
Origin: vendor

--- a/configure.ac
+++ b/configure.ac
@@ -76,6 +76,11 @@ WRASTER_REVISION=0
 WRASTER_AGE=0
 WRASTER_VERSION=$WRASTER_CURRENT:$WRASTER_REVISION:$WRASTER_AGE
 AC_SUBST(WRASTER_VERSION)
+dnl After next soname bump drop this and use WRASTER_VERSION as argument
+dnl for generate-mapfile-from-header.sh
+dnl http://bugs.debian.org/811304
+WRASTER_SYMBOL_VERSION=3
+AC_SUBST([WRASTER_SYMBOL_VERSION])
 dnl
 dnl libWINGs
 WINGS_CURRENT=4
--- a/wrlib/Makefile.am
+++ b/wrlib/Makefile.am
@@ -99,5 +99,5 @@ wrlib.pc: Makefile
 if HAVE_LD_VERSION_SCRIPT
 libwraster.map: $(include_HEADERS) $(top_srcdir)/script/generate-mapfile-from-header.sh
 	$(AM_V_GEN)$(top_srcdir)/script/generate-mapfile-from-header.sh \
-		-n LIBWRASTER -v $(WRASTER_VERSION) $(srcdir)/$(include_HEADERS) > libwraster.map
+		-n LIBWRASTER -v $(WRASTER_SYMBOL_VERSION) $(srcdir)/$(include_HEADERS) > libwraster.map
 endif

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

On Sun, 17 Jan 2016 20:58:13 +0100 Julien Puydt
 wrote:
> upgrading libwraster5 broke wdm with the above error message.

As Andreas noted in his forwarding message to the dev mailing list [1],
this is due to a change made upstream between versions 0.95.6 and 0.95.7
which changed the version from LIBWRASTER3 to LIBWRASTER5.

When I try rebuilding wdm against libwraster5 from version 0.95.7, it
works fine.  However, it still shows Depends on libwraster5 (>=
0.95.6).  So there's still a problem if, say, wdm had a binNMU against
0.95.7 and then someone were to install it alongside libwraster5 from
0.95.6.

I think the solution is to rename libwraster5 to something like
libwraster5v2 and trigger an auto transition.

Doug

[1]
http://permalink.gmane.org/gmane.compw.window-managers.windowmaker.devel/9757

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

Control: tags -1 pending

On 01/18/2016 02:55 PM, Doug Torrance wrote:
> I think the solution is to rename libwraster5 to something like
> libwraster5v2 and trigger an auto transition.

I've pushed these changes to git.  Note that the new library already
means we'll have to wait for the NEW queue, so I've kept the new
wmaker-utils package for #78119 in.

Andreas or kix, would either of you be able to take a look and upload?

Thanks!
Doug

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Julien Puydt]

Package: libwraster5
Severity: grave
Version: 0.95.7-2

Hi,

upgrading libwraster5 broke wdm with the above error message.

I hope that helps,

Snark on a few Debian IRC channels