On 04/01/12 21:52, Michiel Detailleur wrote:
Ok, so as I said in my previous message, I had 2 small F-Spot import
hickups, well, actually 3 now that I think of it:
* Shotwell used to crash badly (with ugliness at the terminal) at
earlier attempts of importing my F-Spot library. But I think I found
the cause: I had a tag in F-Spot with a / in it. I replaced the / with
a & and tried again and BAM, I got a whole lot further in the import
(but not till the end, see below)!
So I'm not 100% sure if this was due to the removing of the / or
because of my Shotwell version got updated in the meantime, but maybe
this is worth checking out? I know Shotwell doesn't allow creating
tags with / in it itself, but maybe it doesn't check for them during
import from other software?
That probably falls under ticket 4487
(http://redmine.yorba.org/issues/4487). I can see why a / character
would make it fail. I'll try to reproduce with a small database to see
what it does.
* Further along, Shotwell crashed during import, without a message in
GUI or terminal. I'm sorry, I can't give you anything more on this. I
think it was due to memory shortage as others have reported here
(which would explain the lack of messages, if it got killed by the
kernel). Luckily I could restart Shotwell, see that it had already
imported a whole bunch of photos and start importing again. Shotwell
succesfully added the remaining photos (while detecting the photos it
had already imported).
That would be defect 4498 (http://redmine.yorba.org/issues/4498). I am
currently working on migrating the F-Spot import code to the SPIT
architecture (see http://redmine.yorba.org/issues/3614) and I'm hoping
that we can address that issue in the refactoring.
* Tags were still imported in hierarchical *and flat* form. So I
manually removed all flat tags. Luckily I don't have that many.
Some work was done on this as part of defect 4081
(http://redmine.yorba.org/issues/4081) but it seems that the issue still
exists somewhat. From what I understand, this can happen when tags are
also stored in the image file as IPTC or XMP meta-data so they may get
imported twice: hierarchically via F-Spot, flat via the IPTC / XMP
meta-data. Any photo file and details of how it's tagged in F-Spot would
help a lot in narrowing down this issue.
Thanks for the issue report!
Cheers,
Bruno
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell