-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 25 Jun 2002 17:07:47 +0100
Source: setserial
Binary: setserial
Architecture: source i386
Version: 2.17-29
Distribution: unstable
Urgency: high
Maintainer: Gordon Russell <gor@debian.org>
Changed-By: Gordon Russell <gor@debian.org>
Description:
setserial - Controls configuration of serial ports.
Changes:
setserial (2.17-29) unstable; urgency=high
.
* Basically after a long discussion on debian-devel, the operation of
setserial is changed so that
o what was /etc/serial.conf is relocated to
/var/lib/setserial/autoserial.conf
o The priority of setserial using automatic configuration information
in init.d is altered to run after /var is mounted (S46).
o If /etc/serial.conf exists, its configuration overrides the
autoserial.conf permanently and utterly. It is handled at the old
priority level of S30. Thus if priority is essential to you you
must create a /etc/serial.conf file yourself.
.
This will allow:
o /etc to be mounted read-only
o Policy concerning configuration files to be upheld.
.
When you install this version of setserial it will detect hand-crafted
serial information and preserve it in serial.conf, otherwise it will be
translated into the new structures. At worst, your hand-crafted
serial.conf file will be preserved indefinitely in
/var/lib/setserial/etc.serial.conf.bkp
Do not delete this backup for any reason.
.
Hope this works out for everyone. If a user had an issue with this
setup do not file a bug without (1) reviewing the discussion on
debian-devel, and (2) posing a workable solution in debian-devel
which has a concensus of agreement. At worst, at least enter a
discussion with me first before a bug report is filed.
o For the moment I am leaving in the debconf option so that the use of
update-modules can be disabled. I will remove this option when
modutils handles modules.conf in a way which matches Policy. However
Policy makes it clear that the sensible handling of modules.conf is
down to modutils and not setserial. Thus worried people should file
bugs with modutils concerning this specific issue.
o In short, chaotic people can create /etc/serial.conf and that becomes
definitive, or package-friendly people can indicate their desire to
manage serial.conf themselves and then create /etc/serial.conf, with
both approaches to manual serial management being equivalent. Asking
for automatic management and then directly editing
/var/lib/setserial/autoserial.conf is still suicide.
Files:
e2b26face8643d84835f1ee376ae336b 580 base important setserial_2.17-29.dsc
e39b2a31c7b66f5a9ac8987649ba2570 54115 base important setserial_2.17-29.diff.gz
69c120b841238dafad3512a3ce591b10 45262 base important setserial_2.17-29_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iEYEARECAAYFAj0Y1rQACgkQsbjrHwXvAePsegCdFmcAx9naD23F16OlthqeoipJ
AO4An0xSR8y3Cqd+aOl5bs4zfprPf4lI
=43Fc
-----END PGP SIGNATURE-----
Accepted:
setserial_2.17-29.diff.gz
to pool/main/s/setserial/setserial_2.17-29.diff.gz
setserial_2.17-29.dsc
to pool/main/s/setserial/setserial_2.17-29.dsc
setserial_2.17-29_i386.deb
to pool/main/s/setserial/setserial_2.17-29_i386.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
