Current stable media-gfx/inkscape-0.91-r1 cannot be built under current stable Gentoo, due to bug 592178 which is apparently fixed in 0.91-r3. Recent stabilizations are triggering inkscape rebuilds and leaving a broken emerge as a result. Quoting Alexander Miller from that bug: > Note that recent stabilizations will trigger failing inkscape rebuilds for > stable users (imagemagick->rebuild; glibmm-2.48.1->error). This bug might > get quite a bit of attention now...
Can confirm this is a problem with the current stable build, the current stable gdkmm just isn't compatible with r1: ui/clipboard.cpp: In member function ‘void Inkscape::UI::ClipboardManagerImpl::_inkscape_wait_for_targets(std::list<Glib::ustring>&)’: ui/clipboard.cpp:1405:22: error: ‘ScopedPtr’ is not a member of ‘Glib’ target = Glib::ScopedPtr<char>(atom_name).get(); //This frees the gchar*. ^ ui/clipboard.cpp:1405:22: note: suggested alternative: In file included from /usr/include/gdkmm-2.4/gdkmm/region.h:67:0, from /usr/include/gdkmm-2.4/gdkmm/screen.h:33, from /usr/include/gdkmm-2.4/gdkmm/display.h:31, from /usr/include/gtkmm-2.4/gtkmm/clipboard.h:31, from ui/clipboard.cpp:24: /usr/include/gdkmm-2.4/gdkmm/types.h:371:7: note: ‘Gdk::ScopedPtr’ class ScopedPtr ^ ui/clipboard.cpp:1405:38: error: expected primary-expression before ‘char’ target = Glib::ScopedPtr<char>(atom_name).get(); //This frees the gchar*. ^ Makefile:8055: recipe for target 'ui/clipboard.o' failed
I can confirm, that inkscape compiles (using distcc-FEATURE) in version 0.91-r3 with latest stable glibmm for amd64: # emerge -av @preserved-rebuild [ebuild U ] media-gfx/inkscape-0.91-r3 [0.91-r1] USE="cdr dbus exif gnome jpeg lcms nls openmp spell -dia -imagemagick -inkjar -latex% -postscript -static-libs -visio -wpg" PYTHON_TARGETS="python2_7" Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Running pre-merge checks for media-gfx/inkscape-0.91-r3 >>> Emerging (1 of 1) media-gfx/inkscape-0.91-r3::gentoo >>> Installing (1 of 1) media-gfx/inkscape-0.91-r3::gentoo >>> Jobs: 1 of 1 complete Load avg: 1.03, 1.01, 1.02 $ eix -e glibmm [I] dev-cpp/glibmm Verfügbare Versionen: (2) 2.44.0 2.46.3 2.46.4 2.48.1 {debug doc examples test ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"} Installierte Versionen: 2.48.1(2)(17:50:09 12.10.2016)(-debug -doc -examples -test ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32") (sorry for the german LOCALE-setting) I can provide my `emerge --info` if needed.
This really needs to be fixed, like, yesterday. Since inkscape cannot be rebuilt, and imagemagick update due to recent stabilization is forcing an inkscape rebuild, this issue is causing unresolvable dependency conflicts for stable users. This completely prevents @world updates on "stable" systems.
Why is it taking so long to stabilize this?
I'm also encountering this. Why is the stabilization taking so long?
Arches go ahead.
amd64/x86 stable
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
An automated check of this bug failed - repoman reported dependency errors (39 lines truncated): > dependency.bad media-gfx/inkscape/inkscape-0.91-r3.ebuild: DEPEND: ppc(default/linux/powerpc/ppc32/13.0) ['>=dev-cpp/glibmm-2.48'] > dependency.bad media-gfx/inkscape/inkscape-0.91-r3.ebuild: RDEPEND: ppc(default/linux/powerpc/ppc32/13.0) ['>=dev-cpp/glibmm-2.48'] > dependency.bad media-gfx/inkscape/inkscape-0.91-r3.ebuild: DEPEND: ppc(default/linux/powerpc/ppc32/13.0/desktop) ['>=dev-cpp/glibmm-2.48']
ppc stable
ppc64 stable.
Stable for HPPA. Closing.
