Your message dated Mon, 5 Feb 2018 11:11:48 -0800
with message-id <20180205191148.hbjhq4n3kwfnj...@virgil.dodds.net>
and subject line Re: Bug#889623 closed by Andreas Tille <ti...@debian.org>
(Bug#889623: fixed in tifffile 20170929-1)
has caused the Debian Bug report #889615,
regarding python-tifffile: broken autopkgtest, broken package
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.)
--
889615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tifffile
Version: 20170914-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
Dear Andreas,
Since the upload of tifffile 20170914-1, the autopkgtests for this package
hav been consistently failing in both Debian and Ubuntu. While the test
failure is (unfortunately) not considered a blocker for Debian testing,
autopkgtest regressions are blockers for Ubuntu releases.
The failure shows that the module simply fails a python import test,
indicating that the package has missing dependencies; therefore I am marking
this bug 'serious'.
autopkgtest [19:30:42]: test python-import: [-----------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.1pxu7uus/downtmp/build.LXT/src/debian/tests/python-import",
line 5, in <module>
import tifffile
File "/usr/lib/python2.7/dist-packages/tifffile.py", line 313, in <module>
import enum
ImportError: No module named enum
autopkgtest [19:30:42]: test python-import: -----------------------]
autopkgtest [19:30:42]: test python-import: - - - - - - - - - - results - - -
- - - - - - -
python-import FAIL non-zero exit status 1
https://ci.debian.net/packages/t/tifffile/unstable/amd64/
After installing the python-enum34 package, the autopkgtest still fails with
another import error about concurrent.futures (package:
python-concurrent.futures).
And if all of these undeclared dependencies are installed, the test still
fails:
$ ./debian/tests/python-import
2017.09.14
Traceback (most recent call last):
File "./debian/tests/python-import", line 16, in <module>
for page in tif:
TypeError: 'TiffFile' object is not iterable
$
This part looks like it might be a bug in the test rather than the package,
but without being familiar with the package it's hard for me to know.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Control: reopen 889623
Version: 20170929-1
Looks like the wrong bug was referenced in the changelog; closing the right
one and reopening.
On Mon, Feb 05, 2018 at 01:27:11PM +0000, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:kraken package:
>
> #889623: kraken: failing autopkgtest, possibly broken package
>
> It has been closed by Andreas Tille <ti...@debian.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Andreas Tille
> <ti...@debian.org> by
> replying to this email.
>
>
> --
> 889623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889623
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> Date: Mon, 05 Feb 2018 13:24:25 +0000
> From: Andreas Tille <ti...@debian.org>
> To: 889623-cl...@bugs.debian.org
> Subject: Bug#889623: fixed in tifffile 20170929-1
>
> Source: tifffile
> Source-Version: 20170929-1
>
> We believe that the bug you reported is fixed in the latest version of
> tifffile, 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 889...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Andreas Tille <ti...@debian.org> (supplier of updated tifffile 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, 05 Feb 2018 14:02:32 +0100
> Source: tifffile
> Binary: python-tifffile
> Architecture: source
> Version: 20170929-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Med Packaging Team
> <debian-med-packag...@lists.alioth.debian.org>
> Changed-By: Andreas Tille <ti...@debian.org>
> Description:
> python-tifffile - Read and write image data from and to TIFF files
> Closes: 889623
> Changes:
> tifffile (20170929-1) unstable; urgency=medium
> .
> [ Andreas Tille ]
> * New upstream version
> * Depends: python-enum34, python-concurrent.futures
> Closes: #889623
> * debhelper 11
> * cme fix dpkg-control
> .
> [ Sascha Steinbiss ]
> * Update autopkgtest with new upstream test example.
> Checksums-Sha1:
> 57610c8ec4fc3b9e3a72a6b304443c42b983d838 2086 tifffile_20170929-1.dsc
> 25a94e3b06144d8a322ccd9d2ba76e610650011e 87457 tifffile_20170929.orig.tar.gz
> 6b68dcfbed9c87d449c2cae86bad2912f3aa081e 5308
> tifffile_20170929-1.debian.tar.xz
> Checksums-Sha256:
> 41369be95b69bb28cea08b886ffbd0f5d70cffccf2b3fc4889cad1d6c8c30187 2086
> tifffile_20170929-1.dsc
> 2f90428623b1460032a1efdedb71c2fa14ed9751fbb66124730624a4e1100963 87457
> tifffile_20170929.orig.tar.gz
> 355b906ad215750f301e2ddbdb3d66da9f522cf0768c652f8c607005acab99ee 5308
> tifffile_20170929-1.debian.tar.xz
> Files:
> b691b29156ad973866566cbb55fb42a9 2086 python optional tifffile_20170929-1.dsc
> 5b6ebff98b0d9efe576ef9a0b520d05d 87457 python optional
> tifffile_20170929.orig.tar.gz
> 34822ff55e3de71942462a40880521de 5308 python optional
> tifffile_20170929-1.debian.tar.xz
>
> -----BEGIN PGP SIGNATURE-----
>
> iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlp4VqYRHHRpbGxlQGRl
> Ymlhbi5vcmcACgkQV4oElNHGRtGc9g/+K3N9arsoQ4ElPijGSIrWMGdK23ZyvOH9
> 7cnOuBnD186rD3kaDtKmSUwLq5V0AmoGTqq9PbFMTvZG5UbVNcSkN9KP5vZbmL48
> o+nkMttWsof/Y+ksarraxDzY9cr4ZF7tKjwRsY3NZ8lOs0C/o3dL2NxtoIZ4AL3Z
> 6Ls+viRry0brKWpHIa6jjglqQF4wXbjh2vJQHpVYJiWf3NkrMlQfDYRJb/H+IvSg
> J6eMwhvJskU9PpKZjERHCFLbaSr9nizqPcez2ROcZR4h0m5Tp9312vz33HrLYTYq
> Xkd0VuU2mtqQeB3CkjBpKlD2D3JfttLKsHd0cC34wr+iRS2oG6SJLsEuqeR608dG
> NZYoinys+FNv+7hd4KrZQ5mR/d4XFzEFw/AP39X85i6ZkHU3dooD/XwLXsYpYTwb
> GhieYUaX798/3YHZk3m6eeiYzVLU4DskVUKsz37LRPGxjs8mTrV1wW0VpQCmqyRk
> 6XPQJM388TL9RQnhkkOlXgNSO1wve1Ff+rqf4/6Foe/0FbdcB5eKG8tEvXWTWMlY
> 1KDGaDEuCj7kBh25WsPst9Dyasn7NxPGpPcWiOsbv05x17LqssYzjp8bVr/yi3GD
> AtRQUOgXC+D0dEv+MKOduXFqmv7gP6KLheQmwK5eyAqlktx39/lN0bqgyp+rpMwE
> n9hJk9B7SqE=
> =7jAA
> -----END PGP SIGNATURE-----
> Date: Sun, 4 Feb 2018 20:13:48 -0800
> From: Steve Langasek <steve.langa...@canonical.com>
> To: sub...@bugs.debian.org
> Subject: kraken: failing autopkgtest, possibly broken package
> User-Agent: NeoMutt/20170609 (1.8.3)
>
> Source: kraken
> Version: 1.0-1
> Severity: important
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu bionic autopkgtest
>
> Dear Andreas,
>
> Since the upload of kraken 1.0-1, the autopkgtests for this package
> have been consistently failing in both Debian and Ubuntu. While the test
> failure is (unfortunately) not considered a blocker for Debian testing,
> autopkgtest regressions are blockers for Ubuntu releases.
>
> autopkgtest [18:36:18]: test run-unit-test: [-----------------------
> scan_fasta_file.pl: unable to determine taxonomy ID for sequence gi|441431932|
> autopkgtest [18:36:19]: test run-unit-test: -----------------------]
> autopkgtest [18:36:19]: test run-unit-test: - - - - - - - - - - results - -
> - - - - - - - -
> run-unit-test FAIL non-zero exit status 25
>
> https://ci.debian.net/packages/k/kraken/unstable/amd64/
>
> There is very little output from the test, so I'm unsure whether this
> represents serious breakage in the package; but I do see that the tests
> themselves have not changed from the previous version of the package where
> the test did pass, so it does seem likely to me that this is a bug in the
> package rather than in the test.
>
> --
> Steve Langasek Give me a lever long enough and a Free OS
> Debian Developer to set it on, and I can move the world.
> Ubuntu Developer http://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
--- End Message ---
