The following ebuilds are make use of RESTRICT=strip without nostrip leading to exact opposite of desired result when using the current portage from the stable tree. (7 weeks, 5 days ago) by vapier was when the initial RESTRICT=strip got added to prepstrip but these changes are not in the stable portage tree yet so we really cant make use of them yet. Some of these packages are in stable and some are not. But you are here anyway as it would prevent the pkg you maintain from ever going stable. dev-util/valgrind/valgrind-2.4.0.ebuild: RESTRICT="strip" games-strategy/coldwar-demo/coldwar-demo-1.ebuild: RESTRICT="strip fetch" games-server/bf1942-lnxded/bf1942-lnxded-1.61.ebuild: RESTRICT="mirror strip" net-misc/nxserver-freenx/nxserver-freenx-0.4.0.ebuild: RESTRICT="nomirror strip" net-misc/nxserver-freenx/nxserver-freenx-0.5.0.ebuild: RESTRICT="nomirror strip" This ebuild does it right for the migration time needed. dev-util/diffball/diffball-0.7.1.ebuild: RESTRICT="nostrip strip" My grepfoo was pretty minimal for this check. Please feel free to ferret out any cases I may have missed.
why dont we just fix portage i'm not exactly inclined to revert back to deprecated notation
Even if you fix portage by backporting the prepstrip to the 2.0.x branch it would still be a while before we can safely expect most users are using it. I'm in favor of backporting it and seeing any existing ebuild in stable do the right thing and add back the nostrip for now.
Yea, during the "transition" we will need to keep both...atleast until a portage with the new notation is in stable for a few months, so that we know that most users are running a Portage that understands it.
> Even if you fix portage by backporting the prepstrip to the 2.0.x branch it > would still be a while before we can safely expect most users are using it. maybe, but this isnt exactly a "critical" feature > Yea, during the "transition" we will need to keep both unrelated to the bug at hand
As far as valgrind is concerned, I commented out RESTRICT="strip" in the 2.4.1 ebuild, because I could not reproduce the problem and the RESTRICT line was inherited from old ebuilds. I don't expect users to run into problems, but if they do I don't mind getting bug reports. I'll leave it in there for now if you don't mind.
ive backported the strip/nostrip fixes to 2.0.54
portage-2.0.54-r1 is in the tree now with this fix
k
(In reply to comment #8) > k just needs to be marked stable now. bug #130527
