Your message dated Wed, 23 Jul 2014 23:22:59 +0100
with message-id
<CAD=6cZpC6pawh9KrouvoUSGv=etr3joj0qqzf+fvcutsytb...@mail.gmail.com>
and subject line Close #660131 - mount mishandles backslash characters
has caused the Debian Bug report #660131,
regarding mount mishandles backslash characters
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.)
--
660131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660131
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mount !!!
sorry hey, following up bug reports is a lot of work I know. However people
who want to help by filing them also hav alot of work and alot of bugs...
Your bug tracking system is a minefield though. I would have given up long
ago but this bug is kind of crucial as far as I can tell...
---------- Forwarded message ----------
From: Debian Bug Tracking System <[email protected]>
Date: Sun, Feb 5, 2012 at 3:18 AM
Subject: Message with no Package: tag cannot be processed! (bug report for
mount)
To: Naja Melan <[email protected]>
Your message didn't have a Package: line at the very first line of the
mail body (part of the pseudo-header), or didn't have a Package: line
at all. Unfortunatly, this means that your message has been ignored
completely.
Without this information we are unable to categorise or otherwise deal
with your problem report. Please _resubmit_ your report to
[email protected] and tell us which package the
report is for. For help, check out
http://www.debian.org/Bugs/Reporting.
Your message was dated Sun, 5 Feb 2012 03:15:40 +0000 and had
message-id <
cagc4hjsoslsopvg_8w0uaxmnd0lmsg_mq34m49ahqo6aotw...@mail.gmail.com>
and subject bug report for mount.
The complete text of it is attached to this message.
If you need any assistance or explanation please contact
[email protected] and include the the attached
message.
If you didn't send the attached message (spam was sent forging your
from address), we apologize; please disregard this message.
--
-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
Debian Bug Tracking System
Contact [email protected] with problems
---------- Forwarded message ----------
From: Naja Melan <[email protected]>
To: [email protected]
Cc:
Date: Sun, 5 Feb 2012 03:15:40 +0000
Subject: bug report for mount
hi,
my apologies for reporting a bug through this channel, but I fail to report
bugs with the reportbug tool. It fails me on all conceivable levels and at
4 am after a long day I cant be bother to type a bug report for the 4th
time in it. You will have to do without proper formatting.
package: mount
system: wheezy
script to reproduce bug:
#!/bin/bash
mkdir 'te\st\'
sudo mount -r /dev/sdf2 'te\st\'
ls 'te\st\'
echo -e "\n\n"
mount
echo -e "\n\n"
cat /proc/mounts
echo -e "\n\n"
sudo umount /dev/sdf2
rmdir 'te\st\'
Output:
-------
user@computer:[...]$ ./testmount
[a list of files]
[...]
/dev/sdf2 on [...]/te\st\134 type ext3
(ro,relatime,errors=continue,barrier=1,data=ordered)
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
[...]
/dev/sdf2 [...]/te\134st\134 ext3
ro,relatime,errors=continue,barrier=1,data=ordered 0 0
umount: [...]/te\st\134: not found
rmdir: failed to remove `te\\st\\': Device or resource busy
--- End Message ---
--- Begin Message ---
version: 2.24.2-1
I'm closing this bug now since the fix for the bug you reported was
included in the new (upstream) version.
If you can still reproduce it feel free to reopen and provide more info.
thanks
regards
althaser
--- End Message ---
