Latest upstream release: 0.7.0pr1 Current version/release in Fedora Rawhide: 0.6.1-2.fc20 URL: http://yorba.org/download/gexiv2/0.7/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 0.7.0pr2 Current version/release in Fedora Rawhide: 0.6.1-2.fc20 URL: http://yorba.org/download/gexiv2/0.7/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
I can help with rebuilds for F20 if you want to push the update out.
I'm not sure about this one. It's only a pre-release, and even the NEWS file hasn't been updated: http://redmine.yorba.org/projects/gexiv2/repository/revisions/master/entry/NEWS It looks like an ABI change to 3.0.0 caused this pre-release: http://git.yorba.org/cgit.cgi/gexiv2/commit/?id=16568949c50d7f588178566e7449c25c1a3e92f6 I'd rather wait for the actual 0.7 release personally. What do you think Kalev? Thanks, Ankur
> I'm not sure about this one. It's only a pre-release, and even the NEWS file > hasn't been updated: Seems to be the same for other Yorba projects -- no updated NEWS for Shotwell pre-releases either. (F20 now has https://admin.fedoraproject.org/updates/shotwell-0.15.0-0.1.pr3.fc20 by the way) > It looks like an ABI change to 3.0.0 caused this pre-release: > http://git.yorba.org/cgit.cgi/gexiv2/commit/ > ?id=16568949c50d7f588178566e7449c25c1a3e92f6 Err, this looks wrong. The commit that this links to adds a new symbol, but this is usually _not_ considered an ABI change and shouldn't warrant a soname bump. I'll open a ticket and ask about this. Also, I've noticed that we have a downstream libgexiv2-pkgconf.patch. Do you know what's up with this, and could you maybe submit it upstream? Or ask whoever commited this to submit it upstream?
http://redmine.yorba.org/issues/7557 Would probably make sense to hold off the update until this is resolved one way or the other.
The soname bump is now reverted in gexiv2 git master.
The final release is out now: http://yorba.org/download/gexiv2/0.7/libgexiv2-0.7.0.tar.xz
Ah! Great! I'll update the package tomorrow and drop a mail to the devel list. It'll be great if you can help with the rebuilds whenever you have the cycles Kalev. Thanks again, Warm regards, Ankur
The soname bump was reverted, I don't think there's a need to rebuild other packages. Should be just a straightforward update now.
*** Bug 1016229 has been marked as a duplicate of this bug. ***
libgexiv2-0.7.0-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libgexiv2-0.7.0-1.fc20
Package libgexiv2-0.7.0-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libgexiv2-0.7.0-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18550/libgexiv2-0.7.0-1.fc20 then log in and leave karma (feedback).
libgexiv2-0.7.0-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.