asks about non-touched conf file on upgrade

[Tormod Volden]

Binary package hint: brltty

On upgrade from karmic, there is this diff:

--- /etc/default/brltty 2009-06-14 08:48:21.000000000 +0200
+++ /etc/default/brltty.dpkg-new 2009-11-17 06:12:38.000000000 +0100
@@ -1,3 +1,13 @@
-# Set RUN_BRLTTY=yes to start brltty at boot time. You may need to
-# configure it in /etc/brltty.conf.
-RUN_BRLTTY=no
+# This is a configuration file for /etc/init.d/brltty; it allows you to
+# perform common modifications to the behavior of the brltty daemon
+# startup.
+
+# Arguments to pass to BRLTTY
+ARGUMENTS="-q"
+
+# If true (or yes) BRLTTY will be started during initramfs execution.
+# If you change this setting, you have to run "update-initramfs -u" to have it
+# take effect. If this setting is on, "update-initramfs -u" also needs to be
+# run if /etc/brltty.conf gets changed.
+START_IN_INITRAMFS=false
+

I never touched that file myself.

ProblemType: Bug
Architecture: i386
Date: Fri Nov 27 20:31:23 2009
DistroRelease: Ubuntu 10.04
Package: brltty 4.0-8ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-5.6-generic
SourcePackage: brltty
Uname: Linux 2.6.32-5-generic i686

[Dave Walker (dogatemycomputer)]

I can reproduce the bug.

- Vanilla installation of Kubuntu 9.10 directly from the CD inside a VM.
- Confirm brltty is installed (sudo apt-get install brltty)
- sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list && sudo aptitude update && sudo aptitude dist-upgrade
- the user is prompted to update /etc/default/brltty

I am new to Triaging bugs. I'm marking the bug as 'confirmed' but let me know if I missed something.