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
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
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
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
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
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,
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
7 matches
Mail list logo