Your message dated Tue, 5 Jun 2007 15:03:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug fixed in 2.0.6-1
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: nano
Version: 2.0.2-1
Editing a file called ~data/diary-full works fine, but saving it causes a
segmentation fault.
Steps to invoke:
1) create a directory called ~data (mkdir ~data)
2) create a file and edit it (nano ~data/diary-full)
3) edit the file (make any changes you like)
4) start to save the file (ctrl-X)
5) agree to saving the file (press 'Y' at the save prompt)
5) you will be prompted for a filename, as usual, so accept (press return)
6) observe a segmentation fault
Tests indicate that the name of the file within the ~data directory is not
important.
However, the name of the directory may be significant. Renaming ~data to
~t and attempting the same process generates the error :
[ Error writing /nonexistent/diary-full: No such file or directory ]
Using ~dd as the directory name fails with a segmentation fault.
Using ~d as the directory name fails with :
[ Error writing /usr/sbin/diary-full: Permission denied ]
(yes, this is the correct error report - it's picked up /usr/sbin/ for no
apparent reason)
As the files load correctly from a directory starting with a tilde, and as
there are no users of the given name, I would expect the editor to edit
the files and save them correctly. The above invention of obscure system
directory names (in this case /usr/sbin/) would seem to have been highly
irregular - if the user had attempted to edit ~d/tcpdump (or any other
name which is also the name of an executable in /usr/sbin) and saved the
file back (with the correct user permissions) then the executable file
would have been erased, almost silently.
uname -a gives:
Linux buttercup 2.6.18-4-486 #1 Mon Mar 26 16:39:10 UTC 2007 i686 GNU/Linux
I dist-update'd last night from last stable to the new stable. Old nano
worked just fine. This doesn't seem so stable to me.
--
Gerph <http://gerph.org/>
--- End Message ---
--- Begin Message ---
Source: nano
Source-Version: 2.0.6-1
This big was closed one mnth ago, but the changelog failed to note this.
The changelog follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 02 May 2007 11:29:24 +0200
Source: nano
Binary: nano-tiny nano-udeb nano
Architecture: source i386
Version: 2.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Jordi Mallach <[EMAIL PROTECTED]>
Changed-By: Jordi Mallach <[EMAIL PROTECTED]>
Description:
nano - free Pico clone with some new features
nano-tiny - free Pico clone with some new features - tiny build
nano-udeb - free Pico clone with some new features - tiny build (udeb)
Changes:
nano (2.0.6-1) unstable; urgency=low
.
* The "Ja en tenim prou" release.
* New upstream release.
Files:
6d715e721b35f8d07f9888b83daac57e 701 editors optional nano_2.0.6-1.dsc
619107f0fc3c4383d668cef15aa3ca32 1315207 editors optional
nano_2.0.6.orig.tar.gz
d33f1898c2dcc130cbe9c197ee5b9e12 23618 editors optional nano_2.0.6-1.diff.gz
73f57f3ae14b9a9e6830610f0b43a7fa 558768 editors important nano_2.0.6-1_i386.deb
0986fb9210aedb9814beb236317d8867 160676 editors optional
nano-tiny_2.0.6-1_i386.deb
9d946079c01d5945d9f6664453e4ebdf 27444 debian-installer standard
nano-udeb_2.0.6-1_i386.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGOxfKJYSUupF6Il4RAkx3AJ9zihhaysVFUbtdRdsbqXghFMb8OACeJilC
tP/j0x5b01NtuEDC9BDJPQ4=
=qxDK
-----END PGP SIGNATURE-----
--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/
--- End Message ---
