[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#980575: kworkflow: autopkgtest needs update for new version of git



Source: kworkflow
Version: 20191112-1.1
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org, git@packages.debian.org
Tags: sid bullseye
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

With a recent upload of git the autopkgtest of kworkflow fails in
testing when that autopkgtest is run with the binary packages of git
from unstable. It passes when run with only packages from testing. In
tabular form:

                       pass            fail
git                    from testing    1:2.30.0-1
kworkflow              from testing    20191112-1.1
all others             from testing    from testing

I copied some of the output at the bottom of this report. git is
printing a warning to stderr, and your autopkgtest fails on that (you
can ignore it with the allow-stderr, you can of course prevent the output).

Currently this regression is blocking the migration of git to testing
[1]. Of course, git shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in git was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from git should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
git/1:2.30.0-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=git

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kworkflow/9861987/log.gz

OK
=========================================================
Total: 12 test file(s)
Test file(s) SUCCEEDED
test_codestyle
test_maintainers
test_explore
hint: Using 'master' as the name for the initial branch. This default
branch name
hint: is subject to change. To configure the initial branch name to use
in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this
command:
hint:
hint: 	git branch -m <name>
Initialized empty Git repository in
/tmp/autopkgtest-lxc.e4dt0kgy/downtmp/autopkgtest_tmp/.git/

Ran 3 tests.

OK
autopkgtest [14:14:07]: test kw-basic-test: -----------------------]
autopkgtest [14:14:07]: test kw-basic-test:  - - - - - - - - - - results
- - - - - - - - - -
kw-basic-test        FAIL stderr: hint: Using 'master' as the name for
the initial branch. This default branch name
autopkgtest [14:14:08]: test kw-basic-test:  - - - - - - - - - - stderr
- - - - - - - - - -
hint: Using 'master' as the name for the initial branch. This default
branch name
hint: is subject to change. To configure the initial branch name to use
in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this
command:
hint:
hint: 	git branch -m <name>
autopkgtest [14:14:08]: @@@@@@@@@@@@@@@@@@@@ summary
kw-basic-test        FAIL stderr: hint: Using 'master' as the name for
the initial branch. This default branch name

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: