[ubuntu-mono] [Bug 582879] Re: Merge database does not work

[John Hall]

I can confirm this bug in 9.10.  I could be fixed in 10.04 or in the dev distro branch. A back port would be nice. There coudl be an upstream patch, plugin or scirpt that could solve the problem.
Possilbe work around solutions:
Hide db files, or hints through renaming or moving of special files to get the photos to merge.
Write a script that merges the two databases and directory trees. 
Change the directory f-spot uses in preferences to the old, mobile, or smaller database. If the old database and photos come up then export them then switch back to the main database and re-import.  

Other ideas:
Photos from many cameras and certainly most d-slrs often have serialized numbers which could be used along with file fingerprints to identify a new source location automagically.  This should be a feature of the main program but it could be a plug-in using createdb and locate to index and find photos and heal the database when photos exist as only data and thumbnails. The same plugin could offer another view to see all photos on the system or in specified file trees without interacting with the database.

-- 
Merge database does not work
https://bugs.launchpad.net/bugs/582879
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to f-spot in ubuntu.

Status in “f-spot” package in Ubuntu: New

Bug description:
Binary package hint: f-spot

I want to merge the db of my travel notebook with the db of my home notebook. I'm using a backup of my home directory. If I select the db in my backup directory, choose any option (only new, only singe imports,...) and press ok the import starts. After a while a dialog appears and ask for the path to the photos. It says that the original path does not exists any more. I select the same relative path in my backup. But the dialog appears and appears. Then I have to kill the process. 

If I copy all the pictures manually from the backup into the pictures folder the same happens no matter which of the options I'm using.

Thanks,

Steffen