Source: mercurial Version: 5.5.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:git
Dear maintainer(s),
With a recent upload of git the autopkgtest of mercurial 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
mercurial from testing 5.5.2-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 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
[1] https://qa.debian.org/excuses.php?package=git
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/9857175/log.gz
est-http-permissions.t
test-http-permissions.t ... # Test test-http-permissions.t
# Running sh "/tmp/hgtests.k6wnhqr_/child113/test-http-permissions.t.sh"
---
/tmp/autopkgtest-lxc.k1drd64q/downtmp/build.mL2/src/tests/test-convert-git.t
+++
/tmp/autopkgtest-lxc.k1drd64q/downtmp/build.mL2/src/tests/test-convert-git.t.err
@@ -680,6 +680,16 @@
$ mkdir git-testrevs
$ cd git-testrevs
$ git init
+ 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 $TESTTMP/git-testrevs/.git/
$ echo a >> a ; git add a > /dev/null; git commit -m 'first' > /dev/null
$ echo a >> a ; git add a > /dev/null; git commit -m 'master commit'
> /dev/null
@@ -882,6 +892,16 @@
convert using a different remote prefix
$ git init git-repo7
+ 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 $TESTTMP/git-repo7/.git/
$ cd git-repo7
TODO: it'd be nice to use (?) lines instead of grep -v to handle the
@@ -957,6 +977,16 @@
test for escaping the repo name (CVE-2016-3069)
$ git init '`echo pwned >COMMAND-INJECTION`'
+ 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 $TESTTMP/`echo pwned
>COMMAND-INJECTION`/.git/
$ cd '`echo pwned >COMMAND-INJECTION`'
$ git commit -q --allow-empty -m 'empty'
@@ -974,6 +1004,16 @@
test for safely passing paths to git (CVE-2016-3105)
$ git init 'ext::sh -c echo% pwned% >GIT-EXT-COMMAND-INJECTION% #'
+ 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 $TESTTMP/ext::sh -c echo% pwned%
>GIT-EXT-COMMAND-INJECTION% #/.git/
$ cd 'ext::sh -c echo% pwned% >GIT-EXT-COMMAND-INJECTION% #'
$ git commit -q --allow-empty -m 'empty'
ERROR: test-convert-git.t output changed
!# Ret was: 0 (test-convert-git.t)
OpenPGP_signature
Description: OpenPGP digital signature
