Summary: | media-gfx/gimp-2.10.8-r1 stabilization request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sebB <entisten> |
Component: | Stabilization | Assignee: | Sebastian Pipping <sping> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gtbgs, kroemmelbein, leio, leonard, pacho, t-mo |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: |
media-gfx/gimp-2.10.8-r1 amd64 x86
media-gfx/dcraw-9.28.0-r1 alpha amd64 arm hppa ia64 ppc ppc64 sparc x86
media-gfx/mypaint-brushes-1.3.0-r1 amd64 x86
media-libs/babl-0.1.62 alpha amd64 arm hppa ia64 ppc ppc64 x86
media-libs/gegl-0.4.14 amd64 x86
virtual/opencl-0-r6 amd64 x86
|
Runtime testing required: | --- |
Bug Depends on: | 572496, 620324, 655390, 679852, 683268 | ||
Bug Blocks: | 684522, 685254 |
Description
sebB
2019-03-20 20:30:30 UTC
ping; 2.10.8-r1 has been around 4 months already too. Looking through the https://bugs.gentoo.org/buglist.cgi?quicksearch=media-gfx%2Fgimp results, I'm not sure we're ready: Some of these affect 2.10.6 2.10.8-r1 too? :( Time issues on fixing them up, or need upstream fixes for some of these? From the list I think only bug 679852 affects it, and bug 659246 looks a libmypaint bug ACK on stabilizing fixed opencl in bug 572496, with that we could proceed as talked with Sebastian some days ago An automated check of this bug failed - repoman reported dependency errors (97 lines truncated):
> dependency.bad media-gfx/gimp/gimp-2.10.8-r1.ebuild: DEPEND: alpha(default/linux/alpha/17.0) ['>=media-libs/libmypaint-1.3.0', '>=media-gfx/mypaint-brushes-1.3.0', '>=media-libs/libheif-1.1.0:=']
> dependency.bad media-gfx/gimp/gimp-2.10.8-r1.ebuild: RDEPEND: alpha(default/linux/alpha/17.0) ['>=media-libs/libmypaint-1.3.0', '>=media-gfx/mypaint-brushes-1.3.0', '>=media-libs/libheif-1.1.0:=']
> dependency.bad media-gfx/gimp/gimp-2.10.8-r1.ebuild: DEPEND: alpha(default/linux/alpha/17.0) ['>=media-gfx/mypaint-brushes-1.3.0', '>=media-libs/libheif-1.1.0:=']
Oops, gimp-2.10 is amd64/x86 only Let me reorder things For the other arches, I would go obsolete bug 589098 and probably open a new one with the new deps(if they still want gimp there) amd64 stable Actually https://bugs.gentoo.org/682958 prevents gimp-2.10.8-r1 from building on my system, so it should not be stabilized yet. sparc stable (In reply to Timo Ollech from comment #10) > Actually https://bugs.gentoo.org/682958 prevents gimp-2.10.8-r1 from > building on my system, so it should not be stabilized yet. it compiles fine for me, that patches are an enhancement (from Fedora only) to not be able to deprecate slot :0.3 in the future ia64 stable ppc64 stable Hi, I'm trying to do an emerge update. It looks like you've marked gimp-2.10.8-r1.ebuild stable for amd64, but it has a DEPEND on dev-libs/appstream-glib, and all versions of dev-libs/appstream-glib are keyworded with ~amd64 or ~amd64-linux. Does dev-libs/appstream-glib need to be stabilized as well? There has been a stable amd64 appstream-glib for years now. Currently dev-libs/appstream-glib-0.7.9, which was stabled (as an upgrade from previous versions) back in December 2018. Hm, when I try to "emerge -uD --newuse world", I get the error: The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by media-gfx/gimp-2.10.8-r1::gentoo # required by @selected # required by @world (argument) =dev-libs/appstream-glib-0.7.15 ~amd64 It looks like appstream-glib-0.7.9.ebuild has KEYWORDS="amd64 ~amd64-linux". I'm not familiar with how KEYWORDS interact, but could the "~amd64-linux" be preventing me from emerging it? Or am I looking at the wrong thing entirely? hppa stable alpha stable x86 stable arm stable ppc stable. Closing. |