Your message dated Tue, 15 Apr 2008 23:20:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line possible user errror, please reopen if reobserved
has caused the Debian Bug report #394799,
regarding brltty upgrade overwrites brltty.conf while unwanted
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
394799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394799
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: brltty
Version: 3.7.2-4
Severity: normal
Hi,
yesterday during an Etch packages upgrade I encountered the next problems:
1: no any question asked by debconf
2 while /etc/brltty.conf were overwritten by the "default" new brltty.conf,
causing to not have braille when i rebooted.
Another problem is, that dpkg-reconfigure brltty have no effect, it simply
prompts the prompt:~# again:
please if brltty.conf found, then ask if replacement is needed; or leave it
unchanged, as it is in general for many other apps.
Note: my Alva Satellite is connected on ttyS0, after the upgrade it was
turned to USB while I hadn't asked for it.
Grtnx,
Osvaldo.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages brltty depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libncurses5 5.5-3 Shared libraries for terminal hand
brltty recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi.
/etc/brltty.conf is a CONFFILE, which means modifications from to it by the
package are subject to confirmation by the user during upgrade.
I cant see a way how this could not have happened.
Its possible the original reporter accidentally confirmed the new configuration
file without noticing.
Closing, please reopen if you feel otherwise.
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger [EMAIL PROTECTED]
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>
--- End Message ---
