-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Package: nano
Version: 2.4.1-1
Severity: normal
Dear Maintainer,

After upgrading nano to 2.4.1-1, when I attempt to launch nano in an
xterm which was already running at the time of the upgrade, I receive
the following error:

   bash: /usr/bin/nano: No such file or directory

I have now seen this happen on two separate computers.


Interestingly, I have at least one running terminal in which this
behavior does not occur. It was opened long before any of the ones in
which I have seen the behavior, so it is possible that it is running a
different version of some software, such as bash. However, I do not know
of any way to determine what version of bash was used to launch a given
active bash session.


This behavior appears to be a consequence of the fix for bug #767929.

The patch provided for that bug claims to create the /usr/bin/nano ->
/bin/nano symlink "only if it is needed", appears to include an attempt
to do that if /usr/bin/nano does not exist in postinst, which seems at
first glance like a reasonable approach.

However, the 2.3.99pre3-1 changelog claims to 'Remove the /usr/bin/nano
+ /bin/nano entirely', which sounds like the final package does not
include any such attempt - and indeed, the installed nano.postinst does
not include any code like that patch.

Is there a reason why the approach in that patch would not have been
acceptable? If so, what is that reason, and why was it not explained
under that bug?


Any given occurrence of this error can be "fixed" by simply exiting and
re-launching the terminal in question, but that's still not ideal when
there are many background programs under that terminal or when there are
large numbers of active terminals. In any case, requiring the user to
take separate action after upgrade to avoid known issues is something to
be avoided whenever possible.

Please either find a way for this failure to not occur on upgrade, or
provide a more prominent upgrade-time announcement that this behavior
will occur, preferably with a mention of the "close and relaunch"
workaround.


- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nano depends on:
ii  libc6         2.19-18
ii  libncursesw5  5.9+20140913-1+b1
ii  libtinfo5     5.9+20140913-1+b1
ii  zlib1g        1:1.2.8.dfsg-2+b1

nano recommends no packages.

Versions of packages nano suggests:
pn  spell  <none>

- -- debconf-show failed

- -- 
  Andrew J. Buehler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVYIBZAAoJEASpNY00KDJrEcIP/2ZbmjeCrbEsOXNba5RgNWha
kgNQa3s9Bhby6SxsnrejmVo0O/ykBPe0fFIEjDtioSTzf0/qYq92lvLy/Ga3qhOJ
dYToGUi7B4Yv9yJMkXQTSZNYcFr6/hfbpnhaVaFN4HURxp6e8vDkSk4zg72GUnU8
0xFB08F5J7d5/ndgWDwgqcui5qc65si6ZsReSrLCNKmN0vmSId80z0r1o7EYakAq
c5N7Iz5nioROZyd5eLJPzMFgQVvNbmGmxVei6Iv7RwvONV2+djys379rLTv9Kd0R
V4wrNHGGxNkAlnppoiaOon2deCuZGR4rh/26CEs9rgHchR9YjnF02IGey38iTNJL
9ZgP6L7dKI8CZxIU7YfxlDJPsPT+xe6o1hnGjdyz1P21vO93CjbgaKijXz+zbEx+
3AhYcrOQ6psGFlg/HUkCncsEU07ao3QrtFj9I28QYwSAH/Ic7aFv15aQulA+IrA4
d/uJbf9A9DmdRMtLGwznsm6ZD/m5A9zjeEsCBQEdYdSVAmhVQWeBsw6IrPSgGC1Z
dkjXFQ7pnh1C02awdEt3oj4yP9Xarsl1ljTm20I/zBi07mRVT0mUZK5Ei0aPvvEq
7waEqx9TLJF+qRVQk7E3rxnkFm0d9bud4BKZT6x1OVNfEm3tjt/l3tn7SPDkrId8
AVkIOqY8F+/f9TRkVOqk
=BPA0
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to