(Reading database ... 115164 files and directories currently installed.)
Preparing to replace brltty 3.7-0ubuntu1 (using .../brltty_3.7.2-2ubuntu2_i386.deb) ...
Unpacking replacement brltty ...
Preparing to replace gnopernicus 1.0.4-0ubuntu1 (using .../gnopernicus_1.0.4-0ubuntu2_i386.deb) ...
Unpacking replacement gnopernicus ...
(Reading database ... 115159 files and directories currently installed.)
Removing libbrlapi ...
Selecting previously deselected package libbrlapi1.
(Reading database ... 115155 files and directories currently installed.)
Unpacking libbrlapi1 (from .../libbrlapi1_3.7.2-2ubuntu2_i386.deb) ...
Setting up libbrlapi1 (3.7.2-2ubuntu2) ...
Setting up brltty (3.7.2-2ubuntu2) ...
Installing new version of config file /etc/brltty/brltty-bm.hlp ...
Installing new version of config file /etc/brltty/en-us-g2.ctb ...
Installing new version of config file /etc/init.d/brltty ...
Configuration file `/etc/brltty.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** brltty.conf (Y/I/N/O/D/Z) [default=N] ? d
Thanks for reporting it, but this is not a bug... rather, its a fix for the bug that forced everyone dist-upgrading (and getting brltty) to go through the configuration screens for brltty.
The package is in flux right now, so the configuration will settle down soon.