Current (stable) version of F-Spot is 0.8.0, released 2010-09-15.

See also bz#631287 ?

An update for rawhide and upcoming F14 to 0.8.0 is on its way. F13 and F12 will be updated if there are no major regressions found.

Thank you, Christian.
I don't know whether 'loss of functionality due to a large rewrite' qualifies as major regression ...  ;)

(note : I recompiled 0.8.0 for F13, based on the 0.6.x .SPEC files, and found no major showstoppers).

f-spot-0.8.0-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/f-spot-0.8.0-2.fc14

f-spot-0.8.0-2.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update f-spot'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/f-spot-0.8.0-2.fc14

This new version seems to have problems to import from gphoto2. It appears that the camera must be mounted in .gvfs to be available in the f-spot import menu. So removing "gvfs-mount --unmount-scheme gphoto2" from the import-script is needed to make the camera appear in the f-spot import menu.

*** Bug 642830 has been marked as a duplicate of this bug. ***

(In reply to comment #6)
> This new version seems to have problems to import from gphoto2. It appears that
> the camera must be mounted in .gvfs to be available in the f-spot import menu.
> So removing "gvfs-mount --unmount-scheme gphoto2" from the import-script is
> needed to make the camera appear in the f-spot import menu.

Yes, according to f-spot's changelog only gvfs-mounted cameras are now supported.

Unfortunately my camera is not mounted at all right now in F14, but once I've solved this problem I'll fix and test the f-spot-import script.

(In reply to comment #8)
> (In reply to comment #6)
> > This new version seems to have problems to import from gphoto2. It appears that
> > the camera must be mounted in .gvfs to be available in the f-spot import menu.
> > So removing "gvfs-mount --unmount-scheme gphoto2" from the import-script is
> > needed to make the camera appear in the f-spot import menu.
> 
> Yes, according to f-spot's changelog only gvfs-mounted cameras are now
> supported.

A new package with a fixed f-spot-import script is on its way into updates-testing.

f-spot-0.8.0-3.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update f-spot'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/f-spot-0.8.0-3.fc14

Thank for this update!
The import script is correctly triggered when browsing the gphoto2 gvfs mount. The only remaining glitch I can see, is that the Import window still proposes the default choice "Choose Import source..." in its drop-down menu, instead of the camera hardware URI passed via the --import option. But this behaviour is very acceptable as-is.

(In reply to comment #11)
> The only remaining glitch I can see, is that the Import window still proposes
> the default choice "Choose Import source..." in its drop-down menu, instead of
> the camera hardware URI passed via the --import option. But this behaviour is
> very acceptable as-is.

Yes, I've seen this issue as well and I've already filed an upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=632398 ;-)

f-spot-0.8.0-3.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

f-spot appears to break cr2 display and import.
Here is partial debug for importing (with a new database) cr2 from camera flash card:

(f-spot:16278): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
[1 Debug 12:00:59.062] Received controller event: SourceChanged
[1 Debug 12:00:59.070] Received controller event: PhotoScanStarted
[1 Debug 12:00:59.266] Invalid thumbnail, reloading: file:///media/EOS_DIGITAL/DCIM/661CANON/CRW_6192.CRW
[1 Debug 12:00:59.287] Loading of metadata failed for file: file:///media/EOS_DIGITAL/DCIM/661CANON/CRW_6192.CRW, trying extension fallback
[1 Debug 12:00:59.287] Loading of metadata failed for file: file:///media/EOS_DIGITAL/DCIM/661CANON/CRW_6192.CRW
[1 Warn  12:00:59.298] Caught an exception - TagLib.UnsupportedFormatException: file:///media/EOS_DIGITAL/DCIM/661CANON/CRW_6192.CRW (taglib/crw) (in `TagLib')

Here is partial debug for opening original database with cr2 images:

[1 Debug 12:04:40.901] Loading of metadata failed for file: file:///home/stephen/Photos/2010/10/29/CRW_6186.CRW, trying extension fallback
[1 Debug 12:04:40.902] Loading of metadata failed for file: file:///home/stephen/Photos/2010/10/29/CRW_6186.CRW
[1 Warn  12:04:40.911] Caught an exception - TagLib.UnsupportedFormatException: file:///home/stephen/Photos/2010/10/29/CRW_6186.CRW (taglib/crw) (in `TagLib')
  at TagLib.File.Create (IFileAbstraction abstraction, System.String mimetype, ReadStyle propertiesStyle) [0x00143] in /builddir/build/BUILD/f-spot-0.8.0/lib/TagLib/TagLib/src/TagLib/File.cs:1489

(In reply to comment #14)
> f-spot appears to break cr2 display and import.
> Here is partial debug for importing (with a new database) cr2 from camera flash
> card:

This bug report is already closed. Please create a new one and add the information again. Please also add:

- a link to such a picture which can't be displayed anymore
- the output of "rpm -q f-spot libopenraw"

@Christian Krause - Thanks - have submitted a new bug with the heading:
f-spot.0.8.0-3.fc14 appears to break CRW display and import.