Furtermore F-Spot completley screwed me up by applying different rules to the imported files. If I mount an SD card as a disk the files were named XXX.JPG. I copied these to local disk and then had F-spot import them and they remained named ".JPG". I then stuck another SD card in and F-spot apparently grabbed it (I was a bit mystified why the window looked completely different than the import window) but when F-spot imported the files directly it renamed them to XXX.jpg (lowercase). It then failed to find collisions and put both files on the disk.
I was relying on F-spot renaming the files to -1.JPG when there was a collision in order to get rid of duplicates (why they can't remove even the most obvious duplicates is another question!). I now had lots of .jpg files as well. Trying to clean up this mess and I deleted a lot of non-duplicate .jpg files.
They certainly should *not* be doing this at all. Mount the damn disk and maybe detect and offer to import using the same code as before! Even the user-friendly OS/X mounts the disk and the user has to eject it.