Please help coordinate with gexiv2 maintainers and get the shotwell-0.26 series stable over 0.24 finally, as talked about without disagreements on various occasions on IRC. (we need a newer media-libs/gexiv2 stable acked, maybe more)
ping, Nicolas, spell out on whose ack we are waiting for please for what, so they notice better what they need to ack and maybe help chasing them down on IRC :) The "what" part might be achieved via filling package list
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=33fb847f59a19dab992620b79a0044a9c70214bf commit 33fb847f59a19dab992620b79a0044a9c70214bf Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2018-01-10 05:58:23 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2018-01-10 06:11:01 +0000 gnome-base/gnome-extra-apps: bump to 3.24.2, lower shotwell dep Bug: https://bugs.gentoo.org/641984 Package-Manager: Portage-2.3.19, Repoman-2.3.6 .../gnome-extra-apps-3.24.2.ebuild | 75 ++++++++++++++++++++++ 1 file changed, 75 insertions(+)}
Unf
There are still two open tickets against this package and I need to look into those to see how we can fix them.
ping, this is getting too much delayed here. If there are issues, fix them and call stabilization or call stabilization immediately, especially if these issues aren't regressions over the previous stable. Not state there are issues and wait another month, with stable users still stuck with 0.24, missing many upstream bug fixes found in the 0.26 series :(
I agree, I don't want to delay this further either. The biggest blocker though (https://bugs.gentoo.org/show_bug.cgi?id=636088) I haven't been able to fix so far. I don't know how many users install gexiv2 without the 'introspection' USE flag. Maybe this issue should not be much of a blocker?
It's not a stabilization blocker for shotwell, but it is for gexiv2. It should just be fixed in the relevant bug by always build DEPENDing on gobject-introspection-common then, when having an eautoreconf call. The previous stable version didn't call eautoreconf, thus the m4 files shipped by gobject-introspection-common weren't needed (they were already shipped in tarball aclocal.m4 and didn't need regenerated from an eautoreconf call).
An automated check of this bug failed - repoman reported dependency errors (43 lines truncated): > dependency.bad media-gfx/shotwell/shotwell-0.26.4.ebuild: DEPEND: amd64(default/linux/amd64/17.0) ['>=media-libs/gexiv2-0.10.4'] > dependency.bad media-gfx/shotwell/shotwell-0.26.4.ebuild: RDEPEND: amd64(default/linux/amd64/17.0) ['>=media-libs/gexiv2-0.10.4'] > dependency.bad media-gfx/shotwell/shotwell-0.26.4.ebuild: DEPEND: amd64(default/linux/amd64/17.0/desktop) ['>=media-libs/gexiv2-0.10.4']
x86 stable
amd64 stable. Closing.
