Bug 218579 - Update request: f-spot 0.3.0
Update request: f-spot 0.3.0
Product: Fedora
Classification: Fedora
Component: f-spot (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Depends On:
Blocks: FC7Target FC7UpdateRequests
  Show dependency treegraph
Reported: 2006-12-06 01:07 EST by Michel Alexandre Salim
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-31 16:05:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to f-spot spec file (1.83 KB, patch)
2006-12-06 01:07 EST, Michel Alexandre Salim
no flags Details | Diff

  None (edit)
Description Michel Alexandre Salim 2006-12-06 01:07:01 EST
Description of problem:
Spec: http://hircus.org/fedora/f-spot/f-spot.spec
SRPM: http://hircus.org/fedora/f-spot/f-spot-0.3.0-1.src.rpm

Could f-spot be updated to 0.3.0? It has (much) better tag-handling, and seems
more responsive as well (or it could just be Mono 1.2 being faster)

Version-Release number of selected component (if applicable):

Additional info:
Tested fine on my FC6 machine updated with Mono from -devel. The libdir patch
needs to be modified anyway, so I took the opportunity to streamline it by using
--libdir instead of --prefix/lib
Comment 1 Michel Alexandre Salim 2006-12-06 01:07:01 EST
Created attachment 142916 [details]
Patch to f-spot spec file
Comment 2 Michael Cronenworth 2006-12-14 16:52:59 EST
I just noticed that FC6 is shipped with 0.2.1 and there have been two newer
versions since then...

I built a package with your SRPM and it works great. Thanks!
Comment 3 Bart Vanbrabant 2007-01-20 05:00:37 EST
I've updated f-spot to 3.1.1

I think this update would also fix a lot of open bugs.
Comment 4 Matthias Clasen 2007-01-31 16:05:05 EST
I've built 0.3.2 in rawhide today

Note You need to log in before you can comment on or make changes to this bug.