Your message dated Fri, 05 Sep 2014 11:00:07 +0000
with message-id <e1xprfp-0007k7...@franck.debian.org>
and subject line Bug#759913: fixed in nwdiag 1.0.3-1
has caused the Debian Bug report #759913,
regarding nwdiag: FTBFS: FAIL: nwdiag.tests.test_pep8.test_pep8
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.)


-- 
759913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nwdiag
Version: 1.0.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> set -e; \
> /«PKGBUILDDIR»/debian/test-runner
> ........................F..............................F.................................F.............................
> ======================================================================
> FAIL: nwdiag.tests.test_pep8.test_pep8
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
>     self.test(*self.arg)
>   File "/«PKGBUILDDIR»/src/nwdiag/tests/test_pep8.py", line 53, in test_pep8
>     assert report.total_errors == 0, message
> AssertionError: pep8: 1 errors / 0 warnings
> -------------------- >> begin captured stdout << ---------------------
> /«PKGBUILDDIR»/src/nwdiag/tests/test_pep8.py:46:9: E265 block comment should 
> start with '# '
> 1       E265 block comment should start with '# '
> pep8: 1 errors / 0 warnings
> 
> --------------------- >> end captured stdout << ----------------------
> 
> ======================================================================
> FAIL: test_pep8.test_pep8
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
>     self.test(*self.arg)
>   File "/«PKGBUILDDIR»/src/packetdiag/tests/test_pep8.py", line 53, in 
> test_pep8
>     assert report.total_errors == 0, message
> AssertionError: pep8: 1 errors / 0 warnings
> -------------------- >> begin captured stdout << ---------------------
> /«PKGBUILDDIR»/src/packetdiag/tests/test_pep8.py:46:9: E265 block comment 
> should start with '# '
> 1       E265 block comment should start with '# '
> pep8: 1 errors / 0 warnings
> 
> --------------------- >> end captured stdout << ----------------------
> 
> ======================================================================
> FAIL: test_pep8.test_pep8
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
>     self.test(*self.arg)
>   File "/«PKGBUILDDIR»/src/rackdiag/tests/test_pep8.py", line 53, in test_pep8
>     assert report.total_errors == 0, message
> AssertionError: pep8: 1 errors / 0 warnings
> -------------------- >> begin captured stdout << ---------------------
> /«PKGBUILDDIR»/src/rackdiag/tests/test_pep8.py:46:9: E265 block comment 
> should start with '# '
> 1       E265 block comment should start with '# '
> pep8: 1 errors / 0 warnings
> 
> --------------------- >> end captured stdout << ----------------------
> 
> ----------------------------------------------------------------------
> Ran 119 tests in 2.935s
> 
> FAILED (failures=3)
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/nwdiag_1.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.

--- End Message ---
--- Begin Message ---
Source: nwdiag
Source-Version: 1.0.3-1

We believe that the bug you reported is fixed in the latest version of
nwdiag, 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 759...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kouhei Maeda <mkou...@palmtb.net> (supplier of updated nwdiag 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: SHA256

Format: 1.8
Date: Mon, 01 Sep 2014 12:42:05 +0900
Source: nwdiag
Binary: python-nwdiag python3-nwdiag
Architecture: source all
Version: 1.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Kouhei Maeda <mkou...@palmtb.net>
Changed-By: Kouhei Maeda <mkou...@palmtb.net>
Description:
 python-nwdiag - generate network-diagram image file from spec-text file
 python3-nwdiag - generate network-diagram image file for Python3
Closes: 759913
Changes:
 nwdiag (1.0.3-1) unstable; urgency=medium
 .
   * New upstream release
     - Fixed FTBFS nwdiag.tests.test_pep8.test_pep8 (Closes: #759913)
   * Supported Python 3
     - Appended python3-nwdiag package
   * debian/control
     - Build-Depends
       * Removed quilt.
       * Appended: dh-python, python-reportlab, python3-all,
         python3-setuptools, python3-pep8, python3-nose, python3-blockdiag,
         python3-reportlab
     - Standards-Version: Bump version to 3.9.5.
   * debian/rules
     - Applied pybuild.
     - Appended targets:
       * override_dh_python, override_dh_python3, convert_manpage_nwdiag3
   * debian/patches
     - Removed append_test_data.patch, manpage_packetdiag_1.patch.
   * Updated debian/docs
Checksums-Sha1:
 b21fcfcc0425ba18bbe044760ba61d5a7c7301b2 2039 nwdiag_1.0.3-1.dsc
 782179972c01976fdf377d7088afa35514bfc5f3 97142 nwdiag_1.0.3.orig.tar.gz
 da2b2bf4436d77c40da83258eac6113811a2eb38 6348 nwdiag_1.0.3-1.debian.tar.xz
 5bffe0cbcc8e664daa143bddec8c23e70c044800 35224 python-nwdiag_1.0.3-1_all.deb
 1b46f6807e8f96e06d48ec410fae02133c1b2161 33514 python3-nwdiag_1.0.3-1_all.deb
Checksums-Sha256:
 8cb3abf6ec5b2b31b22ff6f43ef4562a25ee41b604ab30ed2375bc89a68ca7e2 2039 
nwdiag_1.0.3-1.dsc
 daff808b22f4581eb7e291c58b1280b4570b1d624bed12e642b33feb82cfea58 97142 
nwdiag_1.0.3.orig.tar.gz
 d37f7cb3a7969bebc7bb64b20f4252dc4b414ce05392159a2f3baee33e903610 6348 
nwdiag_1.0.3-1.debian.tar.xz
 d66bf0fcc90c176988bd58e720ab654198372f46a5155673ea7cc8fec63ab203 35224 
python-nwdiag_1.0.3-1_all.deb
 9d7f04b6f531437103a9b1b4ffe7a11ce88e9e6a22004717300e6292c40d1f43 33514 
python3-nwdiag_1.0.3-1_all.deb
Files:
 4c22d8222bdc8679163af7c0a785ad5f 35224 python optional 
python-nwdiag_1.0.3-1_all.deb
 c4968fbe92063536f1691d4e3ea2be28 33514 python optional 
python3-nwdiag_1.0.3-1_all.deb
 6d7bd285716ea64a25a0f65ca3f4a8b4 2039 python optional nwdiag_1.0.3-1.dsc
 84080b3759dcd500a7573ee10a54795c 97142 python optional nwdiag_1.0.3.orig.tar.gz
 69eaed3fe7eba5bb1417ee4ee1df9215 6348 python optional 
nwdiag_1.0.3-1.debian.tar.xz

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

iQIcBAEBCAAGBQJUB8jjAAoJEDIkf7tArR+mGm8P/inCE7QVPaxQb0CW/+4+91Ez
iR20/4imqj3Tfn7Ia9l6CGoBhgoDjYW9aDeNpr004vIIKTJnKmx9UH21qu97Y3lI
oYJ2ujYg/he51VOekau+EdG6KeBFhHubKTPBo2z5XHce9yAkqI7QyCGUNZZ6iTaH
9pTk2QawnPdaKW0o30AHuuPJ6WESERHI1McHa7SECgrtYUhS5/LGVzxke2Xwwqhe
ksUehPpZ4zR7t/le9cBEp7lSAPjqpZANRgzr13rA1My8H3vSwGI/6yxA7CCDfLun
9ub12kNvI64Yz0wlfhiEVhp+nmvE35cUTzOp4BqFYmKZ0WoXNaIUX0BEOMhU4pEs
aI46jx11mxz3WtKAohs+WBM9fAQ2UUmeonR/DnD2gXAnVe7uxi36zcndF2a5qucY
vGo9YoKUhWJHvRmK9ETFGABA/5tYGgqsC4HPYhkS39C3uTLjDcXmSNIDM6repM7l
YGGgJeXEyQQ5suNcUepKt6IhmBi4llsttD3d+TObxvkxTKqhq+yqcmtKv5hOMCsn
yr+IjOEq71cnRWlNciQ8Cbl+8EV72euV4ML1bsOntFpmuzdX/Ys1xF01J85yH+An
Zz6n7Fu7Woma/rAvcibngbMH8TvjviTr16OKGhPromi1hhD1Ya1T5M2k1dsPYLZ1
y34QKzKyFgWtuSBvy5x4
=/BcX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to