Uploaded libpaper 1.0.3-10 (source i386) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.5
Date: Sun, 14 Jun 1998 20:02:11 +0200
Source: libpaper
Binary: libpaperg libpaper
Architecture: source i386
Version: 1.0.3-10
Distribution: unstable frozen
Urgency: low
Maintainer: Marco Pistore <pistore@di.unipi.it>
Description:
libpaper - Library for handling paper characteristics [libc5]
libpaperg - Library for handling paper characteristics [libc6]
Changes:
libpaper (1.0.3-10) unstable frozen; urgency=low
.
* Now libpaper does not depend anymore on libpaperg (this was
the release critical bug#22942). In previous versions, the
dependency was added so that the executables /usr/bin/paperconf and
/usr/sbin/paperconfig (that were present only in libpaperg), could
be used also from the old (i.e., bo) packages that depends on libpaper
(in bo, libpaper provided both the libraries and the executables,
so both of them should be provided to a package that depends on libpaper).
Now, the executables are present in both packages, and libpaperg
uses dpkg-divert to "move away" the libpaper binaries when
libpaperg is installed (closes: Bug#22942)
* Removed "sparc" in debian/rules from the libraries that require
libc5 support (closes: Bug#22082)
* Added some new #include in the source (changes in the c headers?)
Files:
737829c2cf5bd8b4821e59ebf89ed769 595 text optional libpaper_1.0.3-10.dsc
b04db6aa2efe9c0fa644da237ffafc8b 20779 text optional libpaper_1.0.3-10.diff.gz
46aab4b2a723f39316273a65aa92c8f0 14314 text optional libpaper_1.0.3-10_i386.deb
91b433cda915e1b4d55e770e59d9394c 29866 text optional libpaperg_1.0.3-10_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQB1AwUBNYQRIC4T+lbFIwO9AQFPHgL/RmiTWCQX4GQ0UffSra5oynfM+4hNRy/O
VYLO+IueEBAs3kELeFDmJw++tMFh0XOLqRzNM+DNQDNGx+JRvGQTKBQAjajOCfD0
8d8UXyMUeC9ozdI5qXZfkH2uB/kTZXg8
=XelR
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-devel-changes-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: