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.
Andrea
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
Processing control commands:
> tag -1 pending patch fixed-upstream
Bug #928367 [src:papi] libpapi5: SOVERSION is too wide for the runtime check in
PAPI_library_init()
Added tag(s) pending, fixed-upstream, and patch.
--
928367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928367
Debian Bug
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
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/per
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
combi
6 matches
Mail list logo
