After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 348091 - Move the UniqueName method from FileImportBackend to elsewhere
Move the UniqueName method from FileImportBackend to elsewhere
Status: RESOLVED OBSOLETE
Product: f-spot
Classification: Other
Component: General
CVS
Other Linux
: Normal trivial
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-20 07:31 UTC by Stephane Delcroix
Modified: 2006-11-07 21:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stephane Delcroix 2006-07-20 07:31:12 UTC 
I raise this bug now that the bug #335935 is closed.
The solution for bug #335935 call FileImportBackend.UniqueName in an Export procedure.
UniqueName is now too general to belong any further to FileImportBackend. I propose to move it to i.e. Util.cs
Comment 1 Bengt Thuree 2006-08-20 11:29:15 UTC 
Bug #348091 by Han-Wen Nienhuys had the following comment:
---
I have a camera that generates files like HASH-PREFIX/dscCOUNT.jpg . I can
import this with f-spot from USB disk. The result is that I many different
photos named dsc0001.jpg. 

When I create a CD containing all of these different dsc0001.jpgs, all of these
overwrite each other, and I end up with too few photos on the CD.

Please add -DISAMBIGUATION-COUNT suffix to the file names when encountering
duplicate names.
---
Comment 2 Bengt Thuree 2006-08-20 11:29:34 UTC 
*** Bug 352118 has been marked as a duplicate of this bug. ***
Comment 3 Stephane Delcroix 2006-11-07 21:02:33 UTC 
I'm closing this, this issue is no longer uptodate... the code changed too much since I submitted that