Please add GIMP-2.10. https://www.gimp.org/release-notes/gimp-2.10.html
Related https://bugs.gentoo.org/651830
It also requires media-libs/gegl-0.4.0 (as new slot because libympaint does not compile against >=0.4.0).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c65f3122b5e0996bdb9c143d3d6393d3dddb9ffa commit c65f3122b5e0996bdb9c143d3d6393d3dddb9ffa Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2018-04-29 17:46:46 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2018-04-29 17:50:44 +0000 media-libs/gegl: 0.4.0 Bug: https://bugs.gentoo.org/654240 Package-Manager: Portage-2.3.31, Repoman-2.3.9 media-libs/gegl/Manifest | 1 + media-libs/gegl/gegl-0.4.0.ebuild | 179 ++++++++++++++++++++++++++++++++++++++ media-libs/gegl/gegl-9999.ebuild | 2 +- 3 files changed, 181 insertions(+), 1 deletion(-)}
*** Bug 654618 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/gnome.git/commit/?id=cb5f891157ac7466aba39d98050ec002138d052f commit cb5f891157ac7466aba39d98050ec002138d052f Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2018-05-02 19:15:34 +0000 Commit: Sebastian Pipping <sebastian@pipping.org> CommitDate: 2018-05-02 19:46:24 +0000 media-gfx/gimp: 2.10.0 Bug: https://bugs.gentoo.org/654240 media-gfx/gimp/Manifest | 20 +--- media-gfx/gimp/gimp-2.10.0.ebuild | 198 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 199 insertions(+), 19 deletions(-)
Lars and I teamed up and there is 2.10.0 in the gnome overlay now (because it still needs post-main-tree glib at the moment). To give it a shot: layman -a gnome emerge -av =media-gfx/gimp-2.10.0
I see you now tried to push to gnome overlay and found out you actually had access all this time since old times (I kept it on purpose when reviewing gnome overlay access months ago, but forgot all about it) :) With gtk+-2.24.32 out of the way, I hope the necessary glib to reach to main tree finally soon now in some form. Meanwhile some misc suggestions to the gimp ebuild found in gnome overlay: * Remove "due to our call to eautoreconf below (bug #386453)" and "# If you remove this: remove dev-util/gtk-doc-am from DEPEND, too" comments, as they are outdated. gtk-doc-am should always be depended on at buildtime when it is an autotools based project that ships pregenerated gtk-docs in its release tarballs. gtk-doc-am package ships /usr/bin/gtkdoc-rebase, which the standard autotools rules will run over the pregenerated docs to very quickly update documentation paths for offline viewing during the build process. No full gtk-doc needed. This will unfortunately change with meson (no pregenerated gtk-docs there) * Consider using GNOME2_EAUTORECONF="yes" before inherits instead of inheriting autotools and calling eautoreconf yourself. Otherwise gnome2_src_prepare is calling elibtoolize, and afterwards you call eautoreconf and that could be trouble (I think mostly prefix related though). For the seds to work correctly (configure.ac ones to be applied before eautoreconf), just move gnome2_src_prepare to the place where you have eautoreconf now. I think that should work out. * Interesting that there's a gtk-update-icon-cache RDEPEND * Consider using eapi7-ver.eclass instead of versionator. It's much faster and when updating to EAPI-7 it'll then just be a matter of removing the eapi7-ver inherit, I believe. I think that's just $(ver_cut 1-2) instead of $(get_version_component_range 1-2) in two places
2.10.2 is out: https://www.gimp.org/news/2018/05/20/gimp-2-10-2-released/
Created attachment 532546 [details] gimp-2.9999 (gtk3-port)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/gnome.git/commit/?id=dedfa6dd142b038266caa69f7b3ea32d2220d064 commit dedfa6dd142b038266caa69f7b3ea32d2220d064 Author: Sebastian Pipping <sebastian@pipping.org> AuthorDate: 2018-05-21 12:37:07 +0000 Commit: Sebastian Pipping <sebastian@pipping.org> CommitDate: 2018-05-21 12:37:57 +0000 media-gfx/gimp: 2.10.2 Bug: https://bugs.gentoo.org/654240 Package-Manager: Portage-2.3.38, Repoman-2.3.9 media-gfx/gimp/Manifest | 1 + media-gfx/gimp/gimp-2.10.2.ebuild | 200 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 201 insertions(+)
(In reply to Mart Raudsepp from comment #7) Thanks for the review!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=110466cbb41aca4e284c0d6992458c0cab8170b5 commit 110466cbb41aca4e284c0d6992458c0cab8170b5 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2018-06-13 17:34:10 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2018-06-13 17:36:25 +0000 media-gfx/gimp: 2.10.2 Closes: https://bugs.gentoo.org/654240 Package-Manager: Portage-2.3.40, Repoman-2.3.9 media-gfx/gimp/Manifest | 1 + media-gfx/gimp/gimp-2.10.2.ebuild | 200 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 201 insertions(+)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/gnome.git/commit/?id=b0d5e2441d55b1f1502fcc06fe121a1a085b6f10 commit b0d5e2441d55b1f1502fcc06fe121a1a085b6f10 Author: Sebastian Pipping <sebastian@pipping.org> AuthorDate: 2018-06-13 17:37:36 +0000 Commit: Sebastian Pipping <sebastian@pipping.org> CommitDate: 2018-06-13 17:37:36 +0000 media-gfx/gimp: Remove, 2.10.2 in gentoo now Bug: https://bugs.gentoo.org/654240 media-gfx/gimp/Manifest | 2 - media-gfx/gimp/gimp-2.10.0.ebuild | 198 ------------------------------------- media-gfx/gimp/gimp-2.10.2.ebuild | 200 -------------------------------------- media-gfx/gimp/metadata.xml | 15 --- 4 files changed, 415 deletions(-)
