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

Uploaded tiff 3.5.2-1 (source i386) to master



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.5
Date: Tue, 26 Oct 1999 16:20:46 +0200
Source: tiff
Binary: libtiff-tools libtiff3g-dev libtiff3g libtiff3
Architecture: source i386
Version: 3.5.2-1
Distribution: unstable
Urgency: low
Maintainer: Josip Rodin <jrodin@jagor.srce.hr>
Description: 
 libtiff-tools - TIFF manipulation and conversion tools
 libtiff3   - TIFF runtime library [libc5]
 libtiff3g  - TIFF runtime library
 libtiff3g-dev - TIFF development files
Changes: 
 tiff (3.5.2-1) unstable; urgency=low
 .
   * New upstream version.
   * Renamed source package to just "tiff", like upstream tarball name.
   * New maintainer (thanks Guy!). Renewed packaging, with debhelper,
     using Joey's nifty multi2 example, with several adjustments.
   * Ditched libtiff3-altdev, nobody's using that and nobody should be
     using that. Packaging for it still exists, it's just commented out.
   * Uses doc-base for -dev docs now. Uncompressed HTML docs, 100kb space
     saved is pointless when you can't use any links between documents.
Files: 
 556ccc3b6f53fe7e8a3597991b2d4462 653 libs optional tiff_3.5.2-1.dsc
 2c498457556723485d488eb12c12fe95 631491 libs optional tiff_3.5.2.orig.tar.gz
 f273aed05d913085d35299098cc97f30 5055 libs optional tiff_3.5.2-1.diff.gz
 7d0115fa93c3671c546114eeacafab6d 80306 libs optional libtiff3g_3.5.2-1_i386.deb
 b696b3c35d7e8b92873fa40f77c4f8ee 387494 devel optional libtiff3g-dev_3.5.2-1_i386.deb
 62a43a6332bab81a0ac11be5f7e4da32 109394 graphics optional libtiff-tools_3.5.2-1_i386.deb
 490cd99c3b25a28b86f011cc8923a711 77102 oldlibs optional libtiff3_3.5.2-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBOBcJLIdGxXDOoJfVAQG1PgP/Sew0AXDNvDNxw/HtxURKy+YAjbspIeFk
k93Z0aWxrMr1hXXE+03ZOxniAG4MYJUcK4Bt1hNVjfsIvQGTx9rtJ9WRgakzp6uY
WDASufFelSFYwPkPvJV6skJv8Cac6pcMmbictzF8b4T3V3iwu6ue0ZAWm4Wn43dQ
9Gagmhazino=
=l75L
-----END PGP SIGNATURE-----


Reply to: