setserial (2.15-12) unstable; urgency=low
* Made the postinst script question easier to understand (I hope).
(closes: #47697)
* If the user has a non-standard module configuration, then setserial-
induced error messages concerning update-modules may be lost. setserial
now pauses if update-modules exits abnormally.
(closes: #47698)
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Mon, 18 Oct 1999 11:49:07 +0100
setserial (2.15-11) unstable; urgency=low
* Added support for /usr/doc and /usr/share/doc automatic linkage
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 6 Oct 1999 09:34:56 +0100
setserial (2.15-10) unstable; urgency=low
* Error message displayed when you postinst with a setup without
update-modules is now hidden from the user.
(closes: #41546)
* Recomplation now supports the 16750 uart on the latest kernels.
(closes: #44484)
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Tue, 7 Sep 1999 13:46:07 +0100
setserial (2.15-9) unstable; urgency=low
* The bug reports are starting to back up now. Sorry for any delay.
This release is more experimental than usual. PCMCIA users please
investigate with a little caution. The routines which protected you
have been removed from the control script and put into the C code.
* The patch to make compilation on sparcs and alphas was not applied
correctly. It was broken anyway. I have now read the manual on autoconf
and fixed it. Hope this is better for everyone...
(closes: #40051)
* setserial does not check for the existence of update-modules - I use
this in the postinst file, to support module loading and unloading from
the kernel. Although modutils is "required", and thus I should not have
to worry about it not being there, in truth if the serial module is
hardwired in the kernel, then it will never be unloaded, and thus I
do not really need modutils. So I will agree with the bug submitter, and
ignore its absence if that is the case.
(closes: #40957)
* In the postinst file for i386, I talk about saving when you "logout". I
really ment to say "shutdown or halt your machine".
(closes: #40993)
* Apparently the setserial as supplied from upstream does not AUTOSAVE
all the needed information to make a successful reload of all useful data.
I have edited the setserial.c code to do it properly, and send the changes
upstream.
A moan about the size of the /etc/init.d/setserial file was present.
Personally I don't see why it matters, but I have recoded much of the
code in c and put it into the executable. Again I will forward the
changes upstream. Of course, this is likely to produce even more bug
reports...
Please try to put only one bug in each report. This one griped about a few
things, which makes it hard to close. However, everything else is really
wishlist stuff so I am making the bold step of closing it anyway. If people
are unhappy they should resubmit the bugs seperately...
The additional problems were:
o manual page does not contain some useful information which is only
found in the docs - wishlist stuff, and maintaining a changed manual
page when the upstream maintainer changes is frequently is not my
idea of fun.
o complaint that if root sets the wrong configuration on the serial
ports, shutdowns and then reboots, then wrong configuration is still
there - root is a dangerous user and I don't know what to do to make
it safer!
(closes: #40964, #40965) (duplicated reports)
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Tue, 13 Jul 1999 10:25:00 +0100
setserial (2.15-8) unstable; urgency=low
* Up to now, the serial module in the kernel can be unloaded and reloaded
by both kerneld and kmod dynamically whenever the system desires. I had
thought that all the setserial settings made to serial ports would
persist between unloads and reloads of the serial module. Apparently
this is not the case, and so I have added some additions which means
that "/etc/init.d/setserial stop" is called when the serial module is
unloaded, and "/etc/init.d/setserial start" is called when the serial
module is loaded. Hopefully this will solve this issue. Note however that
if you have switched off AUTOSAVE in the serial.conf file, then the
settings will be lost when the module is unloaded, and the settings
stored in serial.conf will be the ones loaded into the serial module when
it is next loaded into the kernel. Personally, serial is never unloaded
for me as I use both gpm and X, which uses the serial module all the time.
Thus the testing I have performed on this has been less than ideal.
However, it should work as advertised. I wasn't sure how to log the output,
so if someone wants to check that out and raise a report if I got it wrong
that would be useful.
(closes: #39441)
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 7 Jul 1999 11:46:35 +0100
setserial (2.15-7) unstable; urgency=low
* Tackled the pcmcia modem/serial card problem. The init.d script is
now exceptionally long-winded, and does every check I can think of
to make sure that the serial device setserial is controlling is not
a pcmcia device. It does the following in addition to the upstream
methods:
(1) AUTOSAVE now does not save ports which are UART "unknown"
(2) a serial port must be /dev/ttyS? or /dev/ttyS??
(3) if the I/O address of a port is within an I/O window as
reported by "cardctl config", it is not saved
(4) if the device is listed in /var/run/stab, do not save it.
Hopefully everything will now work as intended. People with pcmcia
problems due to an earlier version of 2.15 will have to do some
repairs (check out pcmcia.repair).
closes: #40471
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 1 Jul 1999 13:20:04 +0100
setserial (2.15-6) unstable; urgency=low
* Problems with the copyright message and README.debian
#40043
Corrected the URLs in question.
* #40109, #40051 - Problems with alpha and sparc builds
Added the supplied patch to configure.in and then did an autoconf
* Still struggling to fix the pcmcia problems, so a new version is coming
soon.
Fixed: #40043, #40109, #40051
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 24 Jun 1999 08:50:37 +0100
setserial (2.15-5) unstable; urgency=low
* When AUTOSAVE is taken out of the config file, it falls over
#39279 #39724 -
Added a patch from Oskar Liljeblad
* Moving the old config file to /var/tmp could be a security hole.
#29434 -
File is renamed in the same directory with the extension .pre-2.15
* Blank lines in the config file are not handled properly
#38764 -
Uses a patch from Patrik Rak - Thanks...
* Still more problems wrt pcmcia card-based modems.
#39382 -
Added information into postinst and README.debian instructing pcmcia
serial-type card owners to edit the file themselves.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Mon, 21 Jun 1999 09:39:44 +0100
setserial (2.15-4) unstable; urgency=low
* Bug #38131 - the new autosaving of serial port configuration broke
pcmcia-cs. I changed /etc/init.d/setserial so that saving state does,
by default, save only "known" ports, rather than all ports present
as "/dev/ttyS*" files.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 26 May 1999 10:25:07 +0100
setserial (2.15-3) unstable; urgency=low
* used "make clean" rather than "make distclean". Should be better for
all you users wanting to compile your own version. This should make things
better for the mc68k and sparc people too...
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Fri, 21 May 1999 15:39:51 +0100
setserial (2.15-2) unstable; urgency=low
* Bug #38083 - mc68xxx port checked and unnecessary config removed. I had
to rewrite rc.serial.mc68k and some debian/ files to do this.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Fri, 21 May 1999 15:09:04 +0100
setserial (2.15-1) unstable; urgency=low
* New upstream version. I was unable to check the mc68000 patches.
Someone on the mc68000 team will have to do this instead.
The new release uses a completely new configuration procedure, so be
on your guard...
Bug #31542 - problems using -W : the new config does not use -W (fixed)
Bug #34637 - sparc problems : you have your own serial.conf (fixed)
Bug #13682 - very old version : if this is still true reopen (closed)
Bug #30696 - autoconfigure in man is autoconfig in prog (fixed)
Bug #32434 - use init.d not rc.boot - If it makes you happy... (fixed)
Bug #36487 - infinte to infinite in setserial.c (fixed on Debian only)
Bug #36488 - duplicate of bug 36487
Bug #36489 - duplicate of bug 30696
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 19 May 1999 16:59:38 +0100
setserial (2.14-3) unstable; urgency=low
* Now uses supplied ./configure, with installation from rules file, rather
than from hand-crafted Makefile. This should allow it to be more easily
compiled on the Alpha. - Bug #25865,#25379
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 9 Sep 1998 15:16:24 +0100
setserial (2.14-2) unstable; urgency=low
* Changed "configuring serial ports....done." to
"configuring serial ports...done.", fixing bug #24755.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Mon, 20 Jul 1998 09:27:57 +0100
setserial (2.14-1) unstable; urgency=low
* new upstream version. This fixes bug #23966.
I have readded the mc68000 patches to the new version of setserial to
the best of my ability, but without someone to test these I have no way of
knowning if this was successful.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Tue, 30 Jun 1998 10:50:32 +0100
setserial (2.12-7) unstable; urgency=low
* Fixed bug #21286 - If the setserial package has been uninstalled,
then the configuration file could still be present. There is a check
in the config file, which aborts configuration if the package is
not installed.
* Fixed bug #23162 - part of this bug report was that status information
for the ports appeared in the wrong order, and that ports which were
unconfigured but present caused a huge list of messages to appear which
were not relevent to the user. This has been tided up.
* Fixed bug #21658 and #23162 - kernel 2.1 and above does not allow
wild initialisation of the serial port. For now, I force-load the
serial driver module, discarding any error messages. This should
improve the situation, but I have yet to test this.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Tue, 12 May 1998 11:28:05 +0100
setserial (2.12-6) unstable; urgency=low
* Fixed bug #15421 wrt compressing the changes file
* Fixed bug #14064 for 680x0 compilation
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Oct 1997 09:34:24 +0100
setserial (2.12-5) unstable; urgency=low
* Fixed bug #11398 - Now works with ash.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Fri, 3 Oct 1997 10:46:51 +0100
setserial (2.12-4) unstable; urgency=low
* uses libc6
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Mon, 9 Jun 1997 15:48:59 +0100
setserial (2.12-3) unstable; urgency=low
* Fixed bug #8401 - Hope the output is less ugly now...
* Fixed bug #8764 for Alpha platforms
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 17 Apr 1997 09:39:22 +0100
setserial (2.12-2) unstable; urgency=low
* Fixed bug #7685
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 27 Feb 1997 12:35:47 +0000
setserial (2.12-1) unstable; urgency=low
* New upstream version. I have tried to repatch this release with the
* changes from previous debian releases, but some things have changed
* and I am not 100ure I have them all
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 19 Feb 1997 09:47:44 +0000
setserial (2.10-12) unstable; urgency=low
* m68k packages will have a different 0setserial config file
* Support for serial devices defined in m68k machines added
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 13 Feb 1997 09:47:44 +0000
setserial (2.10-11) unstable; urgency=low
* Due to the number of bug reports concerning bootup failures during setserial,
* I have removed all but com1 and 2 from the automatic configuration process. I
* suggest that if you have a more complex setup, you edit this file by hand.
* Com[1-2] is set to the standard port and irq, but uart probing is still done
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Thu, 23 Jan 1997 15:36:40 +0000
setserial (2.10-10) unstable; urgency=low
* Added tests to make sure their is a serial module driver loaded
* Switched to the new source layout
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-9) unstable; urgency=low
* Brought the Debian maintenance files up to date.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-8) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-7) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-6) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-5) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-4) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-3) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-j) unstable; urgency=low
* Bug fixes in the maintenance files
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 12:23:53 +0000
setserial (2.10-1) unstable; urgency=low
* Initial Release.
-- Gordon Russell <g.russell@dcs.napier.ac.uk> Wed, 22 Jan 1997 11:22:25 +0000
Local variables:
mode: debian-changelog
End: