Your message dated Mon, 01 Feb 2021 17:26:11 +0000
with message-id <e1l6cxn-000hjp...@fasolo.debian.org>
and subject line Bug#980576: fixed in mercurial 5.6.1-2
has caused the Debian Bug report #980576,
regarding mercurial: autopkgtest needs update for new version of git
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 5.6.1-2
Done: Julien Cristau <jcris...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mercurial, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Cristau <jcris...@debian.org> (supplier of updated mercurial package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 01 Feb 2021 17:47:09 +0100
Source: mercurial
Architecture: source
Version: 5.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Julien Cristau <jcris...@debian.org>
Closes: 980576
Changes:
mercurial (5.6.1-2) unstable; urgency=medium
.
* tests: make test-subrepo-git.t compatible with git's master->main
rename (closes: #980576).
Checksums-Sha1:
8038d3109103de86ed48e3b3a3ee10f1ff36ad1e 2709 mercurial_5.6.1-2.dsc
4ef6fb6521b960430a9a0c330234c7ffda0199c1 64120 mercurial_5.6.1-2.debian.tar.xz
Checksums-Sha256:
9dbef682e7c3e95ef7f4ffbb4af1ee48cef345c1855f661dbdc9ebdeca66c9bb 2709
mercurial_5.6.1-2.dsc
8e0dab6e154def53acb5b391396d80f8c5ae0e2bfda3620bae546d12f9869625 64120
mercurial_5.6.1-2.debian.tar.xz
Files:
8f0912914e630c6ccfc4beaa2d500702 2709 vcs optional mercurial_5.6.1-2.dsc
af00a7727fa5daea7c8d1307f6aa1074 64120 vcs optional
mercurial_5.6.1-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmAYMooUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z62COBAAkiHpr8S4fRbddV1IYZ5Xnwoz9w3Y
Uvb/fAREt1P5rM7dNBJWwC5O+9WhkqRqnbno9XCqoGkfJ6PMSqb8Gb6IRn9vjOSx
EzF3lCQoPW2xWtVe8capGelLpD9JgZo/2EvuthqOIoGXJUUQ2icnQZ4K3Yvzadb2
gYuF8jAwTJpJpGFtWrXYvJzgNpdh9KMtLppAt5hciWNQcGPICK8NLi9/sqqE4S5g
6h73RoDHYAC4v6lTJ7fmecvmSOK9ZyGXu7zMLA0hZBKilXJvTWYpsEqJOt//ZCp1
u52t22wwdOfJQj1+EJOFnTqO0VZiSG4w9FYnRhr62UamT1/z6Gb14I0FJaLnD7Hs
XhXdg1Ylp/FTF3gRp82DtYiuQn6nzJYPu8RMgVL7CnMDvN481PhSey9W1TSAL+uI
WtzNegfgKDxvwdrD2JzS4Cp9rhl6YRdo3X18FPyGAzZzs4Yrv4bRKzliyz/o/SYA
S6F/hEXikQm8drkvTl17LgC1Dy3+1osSVb19ZaJm4pdXYaGKSivSUmfpP+bCE2R9
vfNOfjDtKNTC+XkMeXq9ncFN2pRVDhAESYiQjb0XE6veiagJivaAFH6/8gspoU1R
71AwziGZlLaTlqtzkHH1YTLejEPQkp9r0xB3WNwOiU0WCFiu7buAJUPgoWECOQcs
gFN4ePQaso7wEPQ=
=Fqd9
-----END PGP SIGNATURE-----
--- End Message ---
