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

Uploaded setserial 2.15-16 (sparc) to master



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

Format: 1.6
Date: Thu, 13 Jan 2000 10:03:57 +0000
Source: setserial
Binary: setserial
Architecture: sparc
Version: 2.15-16
Distribution: unstable
Urgency: low
Maintainer: Debian SPARC Build Daemon <buildd@marcus.debian.net>
Description: 
 setserial  - Controls configuration of serial ports.
Closes: 51972 53802 54966 55294
Changes: 
 setserial (2.15-16) unstable; urgency=low
 .
   * Complaint that it is too easy to destroy your serial configuration if
     something happens to the serial module and you have to reboot. This
     version of setserial only maintains serial.o persistent information in
     /var/run/setserial.conf, and this information is not preserved over
     reboots. The default is not to have AUTOSAVE in the serial.conf file,
     and instead on the first install of setserial all ports are saved once
     only. This may break the boot disks, but I hope not...
    (closes: #54966)
   * Add a wait for return prompt in postinst.
    (closes: #51972)
   * Added a test involving update-modules to the postrm
    (closes: #53802)
   * Removed a dependency to modutils
   * Add section and priority to control file using -isp
   * Updated readme files to reflect changes
   * Multiple Bug report -
     - postinst and prerm has /usr/doc and /usr/share handling removed
       as debstd now apparently does this automatically...
     - Added more detail to the readme explaining 0setserial.pre-2.15
     - renamed README.debian to README.Debian
    (closes: #55294)
Files: 
 d283eb16a126e5bc75a271617242a9d4 32356 base required setserial_2.15-16_sparc.deb

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

iQCVAwUBOIhvwio9WkFm9rsJAQFRBAQAh6RG+gRG2ArLQysjWc/d+o/5UEpfZOSr
/uVgMn2RLTupeC4oauNm668bEEMyAzZHusidfDgb1QM1/YXwmIIQ9H3dMBDW+47M
oo7BB+nfy5n3GFDCWguqpepqzt9kqdDRkZfOSRx2vBgd8o2Qkw4Jag9JGhLdKhl+
4Bcld69sykc=
=py11
-----END PGP SIGNATURE-----


Reply to: