** Changed in: fslint (Ubuntu)
Status: In Progress = Fix Released
** Changed in: fslint
Status: Fix Committed = Fix Released
--
fails on files with names ending in space
https://bugs.launchpad.net/bugs/87246
You received this bug notification because you are a member of Ubuntu
There was an issue in FSlint when dealing with filenames with trailing spaces.
That has been fixed upstream.
I've confirmed on 2.6.23.1-49.fc8 the separate vfat issue,
where one can't create a file with a trailing space in the first place.
$ touch t
touch: setting times of `t ': No such file or
I contacted OGAWA Hirofumi the linux VFAT maintainer,
who said trailing spaces are not allowed in FAT :)
--
fails on files with names ending in space
https://bugs.launchpad.net/bugs/87246
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
It might not be a problem with fslint specifically - I think it's in the
vfat drivers.
eg you can't even do this command if /media/vfat-drive is a fat32 drive:
mv /media/vfat-drive/file /media/vfat-drive/file\
If you try, it complains that it can't move the file to a subdirectory
of itself.
** Also affects: fslint (upstream)
Importance: Undecided
Status: New
** Changed in: fslint (upstream)
Importance: Undecided = Medium
Assignee: (unassigned) = Pádraig Brady
Status: New = Fix Committed
** Changed in: fslint (Ubuntu)
Assignee: (unassigned) = Pádraig
If it helps -
I discovered a similar bug dragging dropping for copy purposes. When
working with a file with a trailing space in the name, drag-n-drop copy
from folderA on my hard drive to folderB on my hard drive worked as
expected. Drag-n-drop copy from anywhere on my hard drive to my usb
flash
