control: tags -1 patch
for py in $(py3versions -s); do
echo "========= Running tests with $py =========="
if ! $py3 -m unittest dulwich.tests.test_suite; then
rv=1
this should really be
for py3 in $(py3versions -s); do
echo "========= Running tests with $py =========="
if ! $py3 -m unittest dulwich.tests.test_suite; then
rv=1
(the for loop variable is called py and then py3 inside the if statement. I
presume they should both be called py3
patch here:
http://launchpadlibrarian.net/582665575/dulwich_0.20.31-1_0.20.31-1ubuntu1.diff.gz
G.
On Sun, 2 Jan 2022 21:08:25 +0100 Paul Gevers <elb...@debian.org> wrote:
Source: dulwich
Version: 0.20.26-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of dulwich the autopkgtest of dulwich fails in
testing when that autopkgtest is run with the binary packages of dulwich
from unstable. It passes when run with only packages from testing. In
tabular form:
pass fail
dulwich from testing 0.20.26-1
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?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=dulwich
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dulwich/17999494/log.gz
========= Running tests with python3.9 ==========
/tmp/autopkgtest-lxc.n4tqfogv/downtmp/build.r97/src/debian/tests/testsuite3:
10: -m: not found
autopkgtest [23:08:36]: test testsuite3
