On April 18, 2020 10:03:01 AM UTC, Adrian Bunk <b...@debian.org> wrote:
>On Mon, Mar 23, 2020 at 09:43:19PM +0100, Paul Gevers wrote:
>> Source: pythonmagick
>> Version: 0.9.19-6
>> X-Debbugs-CC: debian...@lists.debian.org
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: regression
>>
>> Dear maintainer(s),
>>
>> With a recent upload of pythonmagick the autopkgtest of pythonmagick
>> fails in testing when that autopkgtest is run with the binary
>packages
>> of pythonmagick from unstable. It passes when run with only packages
>> from testing. In tabular form:
>>
>> pass fail
>> pythonmagick from testing 0.9.19-6
>> versioned deps [0] from testing from unstable
>> all others from testing from testing
>>
>> I copied some of the output at the bottom of this report.
>>
>> Currently this regression is blocking the migration to testing [1].
>Can
>> you please investigate the situation and fix it?
>>...
>> Testing with python3.7:
>> + python3.7
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> File "/usr/lib/python3/dist-packages/PythonMagick/__init__.py",
>line
>> 1, in <module>
>> from . import _PythonMagick
>> ImportError: cannot import name '_PythonMagick' from 'PythonMagick'
>>...
>
>This is not a regression in the package, the root cause is:
>https://lists.debian.org/debian-release/2020/04/msg00228.html
No. This one started to early to be caused by that issue.
In this case the issue was that the autopkgtest was run for all installed
python3 versions, but the package only builds for the default version.
It's trivially fixable by making the autopkgtest run only for the default
version, but it would be much better to solve it by having the package build
for all supported python3 versions and running the autopkgtest against all of
them.
Scott K
