Package: python3-pycurl Version: 7.46.0-1 Severity: serious X-Debbugs-Cc: Scott Talbert <[email protected]>
https://tracker.debian.org/pkg/pycurl Migration status for pycurl (7.46.0-1 to 7.47.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Autopkgtest for fence-agents/4.17.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Reference test triggered, but real test failed already ♻ ∙ ∙ Autopkgtest for pcs/0.12.2-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Reference test triggered, but real test failed already ♻ ∙ ∙ Autopkgtest for pycurl/7.47.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻) ∙ ∙ Autopkgtest for pytest-recording/0.13.4-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Reference test triggered, but real test failed already ♻ ∙ ∙ Autopkgtest for python-jaeger-client/4.8.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻) ... 403s Traceback (most recent call last): 403s File "/usr/sbin/fence_dummy", line 8, in <module> 403s from fencing import * 403s File "/usr/share/fence/fencing.py", line 3, in <module> 403s import sys, getopt, time, os, uuid, pycurl, stat 403s File "/usr/lib/python3/dist-packages/pycurl/__init__.py", line 1, in <module> 403s from pycurl import _pycurl 403s ImportError: pycurl: libcurl link-time version (8.20.0) is older than compile-time version (8.21.0) ... There are two possibilities: 1. Most likely this check does not make sense in Debian, where the package dependencies already ensure recent enough libcurl. In this case the check should be patched out from pycurl. 2. If pycurl actually does anything with libcurl internals that is no covered by shlibs/symbols, then it should generate a stricter runtime dependency.
