entangle is another reverse dependency; please check it doesn't depend
on any removed API and continues to work.
If so, I don't see much reason to object since the transition is only
two packages. I don't see any especially compelling reason /for/ the
transition, though - the pygexiv2 stuff isn't
Confirmed entangle works with the new version, will update once gexiv2
flows into the archive.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gexiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1157475
Title:
[FFE] new gexiv2 version
** Changed in: gexiv2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gexiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1157475
Title:
[FFE] new gexiv2 version
Status in “gexiv2”
Changes are:
gexiv2 0.6.1 - 19 March 2013
-
* Increases the libtool so version to 2.0.0 to reflect ABI
changes introduced in 0.6.0.
gexiv2 0.6.0 - 18 March 2013
-
* API has been cleaned up: several unnecessary or questionable
Tested and confirmed it works with shotwell. Packaging is in lp:~robert-
ancell/gexiv2/update-0.6.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gexiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1157475
Title:
[FFE] new gexiv2
** Branch linked: lp:~robert-ancell/gexiv2/update-0.6.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gexiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1157475
Title:
[FFE] new gexiv2 version
Status in “gexiv2” package in Ubuntu:
6 matches
Mail list logo
