Public bug reported:
Binary package hint: f-spot
I keep all of my photos in ~/photo. To add new photos into f-spot I
click import, uncheck the "Copy files to Photos folder" option, and then
choose the ~/photo folder.
This has worked great for me since breezy, and even worked a month ago
in hardy when it was still in development.
Now, with the release version of hardy, when I follow the steps above to
import new photos, all old photos that have a literal space in the file
name, such as "Last soccer game 04.JPG" are imported again. (Photos
with a space in the path but not the filename are not reimported.)
After the import when I compare a photo that was just imported with its
old copy, I find that the name (as seen in the sidebar) on the new one
is "Last%20soccer%20game%2004.JPG". Both the old and new photos can
still be opened with f-spot.
I back up my f-spot database and so I can reproduce the import problem
at will. I could change all of the spaces to %20 in the database with
the sqlite3 command-line tool before the import to work around the
problem (and live with the display issue) or could delete the duplicates
with the same tool.
I believe the steps to reproduce the bug would be:
1. Downgrade f-spot to feisty's version using apt pinning.
2. Import a directory containing a few photos, some with spaces in the name and
some without.
3. Upgrade to hardy's f-spot.
4. Try to import the directory again. The photos with spaces in the name
should import again.
I'll post more information as requested or as I find it.
** Affects: f-spot (Ubuntu)
Importance: Undecided
Status: New
--
f-spot reimports all photos with space in name after upgrade to hardy
https://bugs.launchpad.net/bugs/222136
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
