Bug#859524: libpfm4: Unexpected libpfm abi change between libpfm-4.7 and libpfm-4.8

2017-05-03 Thread Andreas Beckmann
On 2017-04-11 22:07, Andreas Beckmann wrote:
> I just uploaded a git snaphot reverting the abi change (and implementing
> an alternate solution) plus an s390x patch from the mailing list to
> experimental. If that builds everywhere and 4.9 doesn't come in time,
> I'll upload it to unstable. And thereafter upload papi with a bumped
> build dependency.

4.9 didn't get released so far, therefore a new libpfm4 snapshot
(including the s390x patch) is now in unstable and a papi with a bumped
B-D, too.


Andreas




Bug#859524: libpfm4: Unexpected libpfm abi change between libpfm-4.7 and libpfm-4.8

2017-04-11 Thread Andreas Beckmann
On 2017-04-11 18:35, Niels Thykier wrote:
> Could you ping upstream for a status on this ?  I think we would really
> like to have this fixed properly in stretch (the alternative being a
> transition right now with a new Debian-specific ABI ... )

I just uploaded a git snaphot reverting the abi change (and implementing
an alternate solution) plus an s390x patch from the mailing list to
experimental. If that builds everywhere and 4.9 doesn't come in time,
I'll upload it to unstable. And thereafter upload papi with a bumped
build dependency.


Andreas



Bug#859524: libpfm4: Unexpected libpfm abi change between libpfm-4.7 and libpfm-4.8

2017-04-11 Thread Niels Thykier
On Tue, 04 Apr 2017 18:54:45 +0200 Andreas Beckmann  wrote:
> Source: libpfm4
> Version: 4.8.0-1
> Severity: serious
> Tags: upstream
> Forwarded: https://sourceforge.net/p/perfmon2/mailman/message/35744830
> 
> An unintended abi change between libpfm 4.7 (compatible with libpfm 4.5+git
> in stable) and libpfm 4.8 (in stretch/sid) has been reported upstream
> (changed a struct member from int to uint64_t, moving offsets of further
> members).
> A new upstream release 4.9 reverting this change (and implementing a
> different solution for its internal needs) is being prepared.
> 
> 
> Andreas
> 
> 

Hi Vincent,

Could you ping upstream for a status on this ?  I think we would really
like to have this fixed properly in stretch (the alternative being a
transition right now with a new Debian-specific ABI ... )

Thanks,
~Niels



Bug#859524: libpfm4: Unexpected libpfm abi change between libpfm-4.7 and libpfm-4.8

2017-04-04 Thread Andreas Beckmann
Source: libpfm4
Version: 4.8.0-1
Severity: serious
Tags: upstream
Forwarded: https://sourceforge.net/p/perfmon2/mailman/message/35744830

An unintended abi change between libpfm 4.7 (compatible with libpfm 4.5+git
in stable) and libpfm 4.8 (in stretch/sid) has been reported upstream
(changed a struct member from int to uint64_t, moving offsets of further
members).
A new upstream release 4.9 reverting this change (and implementing a
different solution for its internal needs) is being prepared.


Andreas