[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#705208: marked as done (O: pylibtiff -- wrapper to the libtiff library to Python using ctypes)

Your message dated Tue, 25 Oct 2016 07:31:37 +0000
with message-id <E1bywCv-0007hH-Dl@franck.debian.org>
and subject line Bug#705208: fixed in pylibtiff 0.4.1+20160502-1
has caused the Debian Bug report #705208,
regarding O: pylibtiff -- wrapper to the libtiff library to Python using ctypes
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 owner@bugs.debian.org
immediately.)


-- 
705208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705208
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal

I intend to orphan pylibtiff. My initial intention was to package pylibtiff as dependency of cellprofiler.

Since it is not clear how cellprofiler will be installed on debian system, I doubt this dependency will ever be used.
I have no more interest in cellprofiler and hence in pylibtiff

Description is:

 PyLibTiff is a package that provides:
 .
  * a wrapper to the libtiff library to Python using ctypes.
  * a pure Python module for reading and writing TIFF and LSM files. The images
    are read as numpy.memmap objects so that it is possible to open images that
    otherwise would not fit to computers RAM.
 .
 There exists many Python packages such as PIL, FreeImagePy that support reading
 and writing TIFF files. The PyLibTiff project was started to have an efficient
 and direct way to read and write TIFF files using the libtiff library without
 the need to install any unnecessary packages or libraries. The pure Python
 module was created for reading "broken" TIFF files such as LSM files that in
 some places use different interpretation of TIFF tags than what specified in
 the TIFF specification document. The libtiff library would just fail reading
 such files. In addition, the pure Python module is more memory efficient as the
 arrays are returned as memory maps. Support for compressed files is not
 implemented yet.
 .
 Warning: pylibtiff currently supports reading and writing images that are
 stored using TIFF strips. Patches are welcome to support tiled TIFF images.

--- End Message ---
--- Begin Message --- 
Source: pylibtiff
Source-Version: 0.4.1+20160502-1

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

Debian distribution maintenance software
pp.
Andreas Tille <tille@debian.org> (supplier of updated pylibtiff 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Tue, 25 Oct 2016 08:50:11 +0200
Source: pylibtiff
Binary: python-libtiff
Architecture: source amd64
Version: 0.4.1+20160502-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Tille <tille@debian.org>
Description:
 python-libtiff - wrapper to the libtiff library to Python using ctypes
Closes: 705208 838266
Changes:
 pylibtiff (0.4.1+20160502-1) unstable; urgency=medium
 .
   * QA (group) upload
   * New checkout from Github
     Closes: #838266
   * Rewrote debian/get-orig-source to automatically detect latest change
     date
   * Document exclusion of bitarray code copy
   * Move packaging to Git
   * cme fix dpkg-control
   * Orphan the package
     Closes: #705208
   * hardening=+bindnow
Checksums-Sha1:
 a5b76cd3968218797df7caadba4e8533b5e0745f 1966 pylibtiff_0.4.1+20160502-1.dsc
 80e2e66736e87934dfc8fbb6a8c8f17a27b6d64a 72668 pylibtiff_0.4.1+20160502.orig.tar.xz
 15a469ff8cd773f34e453f0f148912484549d546 6204 pylibtiff_0.4.1+20160502-1.debian.tar.xz
 dda6df96b60dbad622cdc23fd25c55a03cd2e499 34756 python-libtiff-dbgsym_0.4.1+20160502-1_amd64.deb
 9b189a1c1c9e7ff4782a269ce97607e17812326d 69980 python-libtiff_0.4.1+20160502-1_amd64.deb
Checksums-Sha256:
 b5add2f7e849ca0bcb0c7a50fd3c6fee6d313a309a7d08887e5d672712be2b2a 1966 pylibtiff_0.4.1+20160502-1.dsc
 179aae02ac2a2b72282c2ea686ff2450786ffa8f2e5250ccdb874b01ef7f4768 72668 pylibtiff_0.4.1+20160502.orig.tar.xz
 23c8568c8fbd6185392d7f23328bd52e2103106e544548c05719ece11fa20693 6204 pylibtiff_0.4.1+20160502-1.debian.tar.xz
 418eb1a0ebf4c7dd851b64d3779edb68dcb4cead63f955b71a13499a2b1f791d 34756 python-libtiff-dbgsym_0.4.1+20160502-1_amd64.deb
 df4ddbcaca86b4beb5ccd9212b3370910812cd96fc14239207783d6735cb844d 69980 python-libtiff_0.4.1+20160502-1_amd64.deb
Files:
 aad9b192c0a06d8a1427afee3ed3cab6 1966 python optional pylibtiff_0.4.1+20160502-1.dsc
 ee654d9261a1d418a716cfb28e65ece0 72668 python optional pylibtiff_0.4.1+20160502.orig.tar.xz
 61f58e83dee3ee9b830f69fb2eab2248 6204 python optional pylibtiff_0.4.1+20160502-1.debian.tar.xz
 5cf9b97876ceb5eb144e61e032f78819 34756 debug extra python-libtiff-dbgsym_0.4.1+20160502-1_amd64.deb
 15e5bc93919ed5823b76a79b57474bbb 69980 python optional python-libtiff_0.4.1+20160502-1_amd64.deb

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

iQIcBAEBCAAGBQJYDwQKAAoJEFeKBJTRxkbR6vMQAIjfGSwghCc6L0BpVdD8Z7Gd
zAvNOusSO8FoiJlffVAaDrsdn3QaoEHSPmisIJBOyYoYqi9BesYib+b5MpS0bwah
nZeQ+/s5s55X/anDNiXnPrKElk58MJG0jWjXmsWj4UP/ouM6T1rVzh2lu+mO4Ob+
gJQI1bwGau/GSni2zaPhEZjvIq+BCJvRnEli2WxKIeqhnKG5En239AmFpWSF/IKg
tfw+Zqh9dxg3VAIXukTidkeTjy3wuDm2EukuO/6pyfp/vvAr1ZibWNGh4gLFXJUA
0Ubiko3hymAky4wPLyoMFCxPS85WVd4ru8/E0jHQ+wGoPNKcGzAdQzsKrWH+03TD
L0fPzy+zrCebSMbfz+KUxB/mzaek7mtpSk4tVEur6YM6GuqtOVBc48sTlSWVloi6
m4dEzNLdjLqp29g3ROCD3+XDIEFerPFY87BhH6rWamGU/DT00bBGNnUnakbaeVXC
12qHaRulSWata08VuUGh/xE26nijkOUcnx8vSauDg1i0pMsD2W6gpHN7/5CxVuzj
0sMzjKaw8EurRd0hdVVgtjIwHW8bit5rMWcoWyHEZ8WUl+1lI9yUNExGRkVKRY3i
kaDlmnTRMTzaPngfkA/2A346ETtkVxJjeLKfiYLPsFE0jn2qUF8KR2EK/F1Mcp1m
nwc2GrvtL8Nbc6GKsKYu
=eLDo
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: