Separated from the tracker Bug 81745 QA Notice: the following files contain insecure RUNPATH's Please file a bug about this at http://bugs.gentoo.org/ For more information on this issue, kindly review: http://bugs.gentoo.org/81745 /var/tmp/portage/orbit-0.5.17/image//usr/lib usr/bin/ior-decode /var/tmp/portage/orbit-0.5.17/image//usr/lib usr/bin/name-client /var/tmp/portage/orbit-0.5.17/image//usr/lib usr/bin/old-name-server /var/tmp/portage/orbit-0.5.17/image//usr/lib usr/bin/orbit-event-server /var/tmp/portage/orbit-0.5.17/image//usr/lib usr/bin/orbit-name-server !!! ERROR: gnome-base/orbit-0.5.17 failed. Does anything depend on that ancient version now? If not, best punted.
works for me
Yes, stuff does still depend on this. xosd needs media-libs/gdk-pixbuf media-libs/gdk-pixbuf needs gnome-base/gnome-libs gnome-base/gnome-libs needs =gnome-base/orbit-0*
Fixed in 0.5.17-r1, marked as unstable as some other minor changes were needed (econf/make DESTDIR).
Arches please test 0.5.17-r1 and mark stable : Target KEYWORDS="alpha amd64 arm hppa ia64 mips ppc ppc64 sparc x86"
amd64 stable
ppc stable
x86 stable
Stable on SPARC
Stable on alpha
stable on ppc64
Stable on hppa
The next ~arch portage revision will auto repair evil rpaths and not bail. Maintainers should still fix the packages they maintain as portage will only die with FEATURES=stricter (but that is a maintainer & QA problem) no longer security@ http://bugs.gentoo.org/show_bug.cgi?id=124962
can we close it now ?
(In reply to comment #13) > can we close it now ? Assigning to mips, they haven't stabilized the fixed 0.5.17-r1 yet.
<gnome-base/orbit-2 p.masked for gnome-1 removal; closing this.