Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()
On 2019-05-20 11:25, Samuel Thibault wrote: > Hello, > > This bug is making papi marked to be auto-removed from Buster. Do we > want to tag it as buster-ignore, or fix it there and not only in > experimental? I'd prefer to do the transition for buster, but haven't heard from the RT, yet. Andreas
Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()
Hello, This bug is making papi marked to be auto-removed from Buster. Do we want to tag it as buster-ignore, or fix it there and not only in experimental? Samuel
Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()
Control: tag -1 pending patch fixed-upstream On 2019-05-12 20:15, Andreas Tille wrote: > in the thread on the upstream mailing list[1] you proposed a patch that > was confirmed working by upstream. Do you think this patch should be > submitted to Debian BTS and the bug tagged patch? It's already sitting in experimental/NEW . Andreas
Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()
Hi Andreas, in the thread on the upstream mailing list[1] you proposed a patch that was confirmed working by upstream. Do you think this patch should be submitted to Debian BTS and the bug tagged patch? Kind regards Andreas. [1] https://groups.google.com/a/icl.utk.edu/forum/#!topic/perfapi-devel/Qgv4BpZl64U -- http://fam-tille.de
Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()
Source: papi Version: 5.7.0-1 Severity: serious Tags: upstream Forwarded: https://groups.google.com/a/icl.utk.edu/forum/#!topic/perfapi-devel/Qgv4BpZl64U applications built against libpapi5 (5.6.*-*) don't run with libpapi5 (5.7.*-*) (and vice versa and for all other mismatching major.minor combinations as well) due to the runtime check in PAPI_library_init() and the way PAPI_library_init() is to be called. Andreas
