Wanted for countless fixes, many security related, that were not backported to 0.26, and to finally get away from the snapshot business. In preparation. Problems we need to solve yet (scheduled stabilisation far away): >=media-gfx/digikam-6.0.0_beta3 >=kde-apps/gwenview-18.12.1 >=kde-apps/libkexiv2-18.12.0
Arches, please stabilise. Not yet adding amd64/x86 because of digikam.
sparc stable
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=639e0df732ff59522ffda6f83757edb6b8abf6e3 commit 639e0df732ff59522ffda6f83757edb6b8abf6e3 Author: Tobias Klausmann <klausman@gentoo.org> AuthorDate: 2019-02-07 12:30:56 +0000 Commit: Tobias Klausmann <klausman@gentoo.org> CommitDate: 2019-02-07 12:31:13 +0000 media-gfx/exiv2-0.27.0-r2: alpha stable Bug: http://bugs.gentoo.org/674968 Signed-off-by: Tobias Klausmann <klausman@gentoo.org> media-gfx/exiv2/exiv2-0.27.0-r2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
ppc64 stable
ppc stable
arm stable
Adding amd64/x86.
x86 stable
amd64 stable
This version of exiv2 is breaking darktable, bug 657586. It is also breaking former versions of darktable (2.2.5). Perhaps it's not ready for stabalization. I tested that it's exiv2 by putting "=media-gfx/exiv2-0.27.0-r2" in package.mask, rebuilding it, and then forcing darktable to rebuild (it didn't need to rebuild having already unupgraded exiv2).
Nvm, apparently bug 678426 will fix this.
ia64 stable