Your message dated Thu, 03 Apr 2014 07:33:26 +0000
with message-id <[email protected]>
and subject line Bug#735578: fixed in mercurial 2.9.2-1
has caused the Debian Bug report #735578,
regarding autopkgtest hgsubversion shouldn't need network connectivity
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 [email protected]
immediately.)


-- 
735578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735578
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mercurial
Version: 2.8.1-2
User: [email protected]
Usertags: autopkgtest

Hello,

mercurial's autopkgtest currently fails [1] in two different ways:

 * testsuite:

   | adt-run: & dsc0t-testsuite:  - - - - - - - - - - stderr - - - - - - - - - -
   | warning: Tested with unexpected mercurial lib: 
/usr/lib/python2.7/dist-packages/mercurial
   |         (expected /usr/bin/mercurial)

   autopkgtests must not write anything to stderr by default, so that
   unexpected warnings etc. are caught. If this is expected and cannot
   easily be suppressed, then you can add "Restrictions: allow-stderr"
   to its control stanza, as in attached debdiff.

 * hgsubversion:

   In Ubuntu's CI machinery we don't have access to outside servers
   like alioth. This of course does not directly affect Debian, I
   mostly mentioned it to explain why I disabled that particular test
   in Ubuntu in case you wonder.

   Would you accept a patch that sets up a local svn repository with
   some example commits and then imports from that? This makes the
   test independent of network, connectivity, or alioth problems, and
   as autopkgtest is primarily meant to be a "do I have everything
   required in the package" smoketest, it should suffice.

I attach the current Ubuntu debdiff for reference, but please don't
apply it as-is to Debian.

Thanks for considering,

Martin

[1] 
http://d-jenkins.ubuntu-ci:8080/view/Trusty/view/AutoPkgTest/job/trusty-adt-mercurial/15/ARCH=i386,label=adt/
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru mercurial-2.8.1/debian/changelog mercurial-2.8.1/debian/changelog
--- mercurial-2.8.1/debian/changelog    2013-12-08 01:04:06.000000000 +0100
+++ mercurial-2.8.1/debian/changelog    2014-01-16 16:47:40.000000000 +0100
@@ -1,3 +1,13 @@
+mercurial (2.8.1-2ubuntu1) trusty; urgency=medium
+
+  * debian/tests/control:
+    - Add "allow-stderr" restriction to "testsuite" as it prints out a "Tested
+      with unexpected mercurial lib:" warning.
+    - Disable hgsubversion test as it needs access to anonscm.debian.org which
+      we don't have in Ubuntu CI.
+
+ -- Martin Pitt <[email protected]>  Thu, 16 Jan 2014 16:46:31 +0100
+
 mercurial (2.8.1-2) unstable; urgency=low
 
   * Pass -f to rm so that repeated builds succeed (Closes: #731623).
diff -Nru mercurial-2.8.1/debian/tests/control 
mercurial-2.8.1/debian/tests/control
--- mercurial-2.8.1/debian/tests/control        2013-11-25 07:24:36.000000000 
+0100
+++ mercurial-2.8.1/debian/tests/control        2014-01-16 16:46:24.000000000 
+0100
@@ -1,8 +1,9 @@
 Tests: testsuite
 Depends: @, zip, unzip, netbase, python-subversion, monotone, cvs, bzr, tla, 
darcs
+Restrictions: allow-stderr
 
-Tests: hgsubversion
-Depends: @, hgsubversion
+#Tests: hgsubversion
+#Depends: @, hgsubversion
 
 Tests: mercurial-git
 Depends: @, mercurial-git, git

--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 2.9.2-1

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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javi Merino <[email protected]> (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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 03 Apr 2014 08:11:58 +0100
Source: mercurial
Binary: mercurial-common mercurial
Architecture: source all amd64
Version: 2.9.2-1
Distribution: unstable
Urgency: low
Maintainer: Python Applications Packaging Team 
<[email protected]>
Changed-By: Javi Merino <[email protected]>
Description: 
 mercurial  - easy-to-use, scalable distributed version control system
 mercurial-common - easy-to-use, scalable distributed version control system 
(common
Closes: 735578 741514 743288
Changes: 
 mercurial (2.9.2-1) unstable; urgency=low
 .
   [ Javi Merino ]
   * New upstream release
   * Fix "please downgrade 'wish' Recommends to Suggests" by removing the
     Recommends from the mercurial package (but keeping the Suggests in
     mercurial-common) (Closes: #741514)
   * Drop Suggests of vim or emacs
   * Fix "autopkgtest hgsubversion shouldn't need network connectivity"
     by making the test create a local svn repository (Closes: #735578)
   * Mercurial 2.9 breaks hgsubversion prior to 1.6
 .
   [ Julien Cristau ]
   * mercurial-common Replaces mercurial << 2.6.3 (the bash_completion file and
     /etc/mercurial/hgrc moved) (Closes: #743288)
Checksums-Sha1: 
 904267f02d6bad89553e6e9e875418ecb24382ab 2231 mercurial_2.9.2-1.dsc
 35668f2d88afe55d10aa7dbce821021bf0be4f73 3855689 mercurial_2.9.2.orig.tar.gz
 34ac180a34845decc7c7b6afaeb725bc3b41f570 43428 mercurial_2.9.2-1.debian.tar.xz
 654d8a37a38275dcd741d69032ecb3cee43eafd8 1557686 
mercurial-common_2.9.2-1_all.deb
 831b27853418476f2c62fcd0a50170b5d6b0714a 62010 mercurial_2.9.2-1_amd64.deb
Checksums-Sha256: 
 6cb83e2cb9e89de104e23eb4296d78116c838b634c66cd5aa40da5b719ddc98b 2231 
mercurial_2.9.2-1.dsc
 86462b3a1518e137cfe813dc273b8acb120ad71230a1813c0dc9335223b38f53 3855689 
mercurial_2.9.2.orig.tar.gz
 902d6ab195d74d246c8b002a57073ce93b78cf35baaca4123ff2d36352751d01 43428 
mercurial_2.9.2-1.debian.tar.xz
 0d6ed523139a1fa456fceb37e18d7dba3e8001b8c34296aa6ba0845704c375c7 1557686 
mercurial-common_2.9.2-1_all.deb
 8fe91bc18ad317844662bc9d2c87c1dd930ee60c3e3fc8f85fc298f0503c7214 62010 
mercurial_2.9.2-1_amd64.deb
Files: 
 2219053604281af32a24915ebe4122a6 2231 vcs optional mercurial_2.9.2-1.dsc
 1caeed1bea1232598fc5ce5d6d109f56 3855689 vcs optional 
mercurial_2.9.2.orig.tar.gz
 ce3d86a78a55a8391bb671cd1e688e91 43428 vcs optional 
mercurial_2.9.2-1.debian.tar.xz
 0d8ddc941f1d0813bca5414c67b58626 1557686 vcs optional 
mercurial-common_2.9.2-1_all.deb
 d033826d648cc896db229e054ddd19ff 62010 vcs optional mercurial_2.9.2-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTPQvtAAoJEAe0hFJ2jTgkQhIQAIC8ICk8foqQimpk3vxVC3jz
eR1p+ZSGGXsAON5gDaw/rfvRlf0uCTXdX0+YFHqWVcE3Bk5vc8cjhk7KnufHQJ+S
1mXy1CoZl4V40o0neUqn184RMe7+KRXrlwShps3bdLlmQvNpUs0JOYxOlG+ZrE4e
IyVpBbU67Q0IGOOHJA7TbCicM21NcWO1+m6Ij/OKo6d206/jKUkO6Ewku/ao1f7E
FzXfP/MA9PVqX0g4n4trJNHSGly2u4OpQXdS93fdCHqgcTGAcFJhmcY+VeHvgNOj
tmfakSPQrn+sLjRNzy0ZV8D+X2o0wGpfpnma/CDRaH1dyo+Ki7zybPDcXmFyeogU
a3NqSlNMrNGH3PR0RjvBf02MLrrSCVREI7kmE7EGL0n7vCPSlNQyKcvhr5GGYr2N
XEcsAFjgB96zXwng2ADVYbnYH+B8M6X3BM0yzoapUSM8ws2D13wMS++qAZHxIcWD
w8sEiRlee5kvrbiPVrVn29fT836RvNgBegKukfEjqO55hj/FIY2z+ZnVmwB1eYwg
OpDBCu3PxDevowZ/1srvz1vIGaRTejZnJO0lTim83gRB0+G/e8q0tCyuxtX33zgN
H4rkJtHR0tnaiV9dEPK9RIqURTwzNmBN1p8fXg8XC7d1yDl06t+lXiN+VKwyJ1Ir
RHSW14awN0xPjOqtAhwo
=Yh+A
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to