Your message dated Sun, 17 Sep 2006 22:01:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug closed in experimental and now also closed in unstable
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: pilot-link
Version: 0.9.5.0-8
Severity: minor
I'm running Testing, and I'm currently upgrading pilot-link to 0.11.8-7.
I'm getting a debconf question about whether I'd like to have /dev/pilot
be a symlink to the relevant serial port device.
However, I already have such a symlink set up since before. IMO, if the
symlink is already there, the debconf question shouldn't be asked.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux foo 2.4.20-3-686 #1 Sun May 18 20:26:19 EST 2003 i686
Locale: LANG=sv_SE, LC_CTYPE=sv_SE
Versions of packages pilot-link depends on:
ii debconf 1.3.22 Debian configuration management sy
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
ii libpisock4 0.9.5.0-8 Libraries for communicating with a
ii libstdc++2.10-glibc2.2 1:2.95.4-19 The GNU stdc++ library
-- debconf information:
shared/pilot/create-link: true
shared/pilot/port: ttyS0
--- End Message ---
--- Begin Message ---
Hello,
The bug you reported has been closed by a version of pilot-link uploaded
in experimental. Version 0.12.1 is now stable upstream and has been
uploaded in Debian unstable so the bug is really closed now.
Thanks,
--
Dr. Ludovic Rousseau [EMAIL PROTECTED]
-- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
--- End Message ---
