gexiv2 FTBFS with new libexiv2

[Jamie Strandboge]

gexiv2 in natty was built against libexiv2-9 but this is not built from source (NBS). Binaries from this package are part of installation
media and need to build against current packages. Trying a no change rebuild against libexiv2-10 is FTBFS:

libtool: compile: g++ -c -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -I. gexiv2/gexiv2-metadata-exif.cpp -fPIC -DPIC -o x86_64-linux-gnu/.libs/gexiv2-metadata-exif.o
gexiv2/gexiv2-metadata-exif.cpp: In function 'const gchar* gexiv2_metadata_get_exif_tag_label(const gchar*)':
gexiv2/gexiv2-metadata-exif.cpp:254:16: error: 'tagLabel' is not a member of 'Exiv2::ExifTags'
gexiv2/gexiv2-metadata-exif.cpp: In function 'const gchar* gexiv2_metadata_get_exif_tag_description(const gchar*)':
gexiv2/gexiv2-metadata-exif.cpp:268:16: error: 'tagDesc' is not a member of 'Exiv2::ExifTags'
make[1]: *** [x86_64-linux-gnu/gexiv2-metadata-exif.o] Error 1
make[1]: Leaving directory `/build/jamie-gexiv2_0.2.2-1ubuntu2-amd64-krTSPa/gexiv2-0.2.2'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

[Jim Nelson (yorba-jim)]

This will be fixed in the next release of gexiv2, 0.3.0: http://trac.yorba.org/changeset/2550

[Dave Walker (davewalker)]

I see ~ubuntu-desktop maintain this package, is someone from this team looking to cherry pick the upstream changeset in time for Alpha 2? Or should this just be fixed with the next upload? Wouldn't seem to be A2 critical?

[Jamie Strandboge (jdstrand)]

gexiv2 (0.3.0-0ubuntu1) natty; urgency=low

  * New upstream release

[Jim Nelson (yorba-jim)]

We plan on releasing 0.3.0 in the next couple of days. Hopefully it'll be ready in time for Alpha 2.

[Jamie Strandboge (jdstrand)]

Jim, gexiv2 has already been uploaded. See:
https://launchpad.net/ubuntu/+source/gexiv2/0.3.0-0ubuntu1

Was this a pre-release? If so, that should be represented in the version.

[Jim Nelson (yorba-jim)]

I changed the upstream ticket to http://trac.yorba.org/ticket/3141 to reflect that we need to release a tarball.

[Jim Nelson (yorba-jim)]

Okay -- some confusion on my part. In my advancing age I forgot we released 0.3.0 on January 10. So, we're *not* going to be releasing 0.3.0 or a new 0.3.1 -- what is out there is fine.

Sorry for all the trouble!