update f-spot to 0.5

f-spot 0.4.4 in intrepid with bad translation.
f-spot 0.5.0 has updated translations and bugfixes

thank you for your bug report, no that's not an intrepid blocker and should not be nominated, could you give details on why the new version deserves a freeze exception?

    * new sidebar, reworked editors (Ruben, SoC)
    * color profile support (Wasja, SoC)
    * duplicate detection at import (Thomas)
    * reworked db interractions, with O(1) queries
    * reducing and batching db access
    * light-speed tagging
    * FullScreen mode enhancement
    * new extensions, updated docs, updated translations
    * hundreds of bugfixes (Lorenzo)

Thats not good justification for a freeze exception. From what I can see, the changes from 0.4.4 to 0.5.0 are quite significant, with lots of new features. F-spot 0.4.4 works quite well at the moment.

Paul: Please have a look at https://wiki.ubuntu.com/FreezeExceptionProcess

Even though it introduces new features, it still fixes a lot of bugs of the current version in Intrepid.

Also f-spot is the default photo management software in Ubuntu and therefore should be as feature-rich as possible.

For new features especially the new sidebar and the reworked editors seem interesting, as they will make it even easier to quickly edit pictures.
The editors are already pretty useful and if they were even better in 0.5 users would not have to start a huge editing programm like Gimp for just a quick red-eye-removal or color adjustment in general.

Also color profile support seems pretty cool since usually pictures on the monitor screen look bright and natural, but if you print them paper they look not too brilliant.
Color structures correct the image in view of physical opportunities of devices of a conclusion. So it is is possible to facilitate the life of users and present them too more functionality with adding the support of color profiles in f-spot.
(taken from: http://code.google.com/soc/2008/gnome/appinfo.html?csaid=1EF7F7EDFE7E57BE )

This seems pretty urgent for anybody who wants to print out those really cool pictures just taken with the new camera and especially a DSLR.

I am sorry that my skills are not enough to provide the diffstat here, but nontheless I would really give f-spot 0.5 a warm welcom to Intrepid since users will generally benefit from a more polished version of the default photo management programm in Ubuntu.

Cheers,
Michael

Here is the diffstat

diff -ruN f-spot-{0.4.4,0.5.0}/ | diffstat > diffstat.txt

This would really be awesome..color profile support is a big thing for me, and I know I'm not alone in that.

The benchmarks I've seen in 0.5.0, promises to make the program usable again for me. Version 0.4.4 is barely usable with my current setup; 15k + photos, 1,5Gig RAM and 1,2 gHz CPU.

Please, update it before BetaFreeze

Confirming as a valid bug, although I don't think it should/will be in Intrepid.

As it is installed by default in Ubuntu I feel it would be nice to have a newer / latest version included.

Theres been a bug fix release aswell (0.5.0.1)

Updates only happen at this stage in the release cycle if the benefits outweigh the risks. We need to know exactly which bugs are fixed, and a link to their bug numbers.

Also gsoc has *just* finished. How much testing has new gsoc code received?

There's no doubt it'll end up in jaunty, but newest and shiniest isn't a good enough justification post feature freeze.

Fixed bugs from 0.4.4 to 0.5.0.1...
http://bugzilla.gnome.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=f-spot&long_desc_type=substring&long_desc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&resolution=FIXED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=2008-05-29&chfieldto=2008-09-22&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

Has someone prepared a package for this update? Can you point us to a debdiff?

Otherwise, if no one has committed to doing the update, there doesn't seem to be much point in the release team granting a freeze exception.

I've had a look at doing this, but there are currently 19 patches to the upstream source that need porting to the new version (if they are still applicable). It's a lot of work and my knowledge of mono is pretty limited.

there is a package in ppa: https://edge.launchpad.net/~michelinux/+archive

Paul - That package doesn't address the 19 patches that are currently maintained against 0.4.4. Have these patches been incorporated upstream, meaning we can drop them?

Chris - I really don't know this. I only wanted to point on this ppa package hoping that it could help.

The ppa version works great for me but I'm not using many features. Today a second bugfix release was done. Changes: http://tinyurl.com/4vgsgq

Judging from the GNOME bugtracker:
* 1 blocker
* 10 critical and
* 1 major bug
were fixed between May 29th and Oct. 6th (0.4.4 and 0.5.0.2 release dates, respectively)

Link to the list of those bugs: http://ur1.ca/7zn

I've packaged 0.5.0.2 now, and uploaded it to my PPA. Unfortunately though, the amd64 build failed even though I built this one successfully running PBuilder and I'm now running it at home.

It seems to run okay, although I haven't done any extensive testing yet.

I will supply a debdiff once I understand why the amd64 build failed in my PPA.

It seems that the build failure is not a problem with my build of F-Spot, but an issue with the PPA (bug 270031). Therefore, I've attached a debdiff for the new version.

***Ignore the above debdiff. I interupted the upload when I realised how ridiculously huge it was***

Here's a slightly saner debdiff.tar.gz

thank you for your work on this update. the tarball you used seem to not be the upstream on though, the md5sum doesn't correspond to the GNOME one. Could you also update the autoreconf patch to not list the autom4te.cache directory nor config.h.in~ there? otherwise the update looks correct good job on this one!

Ah yes, I forgot to remove the autom4te.cache directory - that's an oversight on my part. The md5sum's probably don't match because the upstream tarball is tar.bz2, and I converted it to tar.gz. I should probably mention that in the changelog?

I'll have a look at it when I get home this evening.

Thanks

Sebastien - here is the new diff.gz. I've removed the autom4te.cache directory and config.h.in~ from the autoreconf patch. I've also added a changelog entry to say that I converted the upstream tarball to tar.gz

thanks, not sure where you downloaded your tarball but http://ftp.acc.umu.se/pub/GNOME/sources/f-spot/0.5/ has a tar.gz, I'll sponsor the update using the upstream tarball and update the changelog before though

This bug was fixed in the package f-spot - 0.5.0.2-0ubuntu1

---------------
f-spot (0.5.0.2-0ubuntu1) intrepid; urgency=low

  * New upstream release (LP: #271895)
    - Dropped svn-044-4010_gio-sharp-destdir.dpatch - implemented upstream.
    - debian_unlink-nunit.dpatch: Ported to new upstream source.
    - debian_link-system-flickrnet.dpatch: Ported to new upstream source.
    - Dropped debian_flickrnet-2.1.5-port.dpatch - implemented upstream.
    - ubuntu_importer-targetdir-selector.dpatch: Ported to new upstream
      source.
    - Dropped ubuntu_fix-gtk-deprecated.dpatch - implemented upstream.
    - Dropped debian_link-system-mono-addins.dpatch - This seems to break
      the new Edit sidebar.
    - Re-generated 98_autoreconf.dpatch.
    - debian/control:
      - Bumped libmono-dev dependency to 1.2.4.

 -- Chris Coulson <email address hidden> Mon, 06 Oct 2008 23:11:41 +0100

please test Zooomr export. F-Spot bundles a modified version of flickrnet for this purpose (also). upstream libflickrnet doesn't work with zooomr.
if what i've seen on packages.ubuntu.com is right it's not likely to work.