Summary: | =sys-apps/net-tools-1.60_p20100815160931 can't be installed due to a sandbox violation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | boris64 <genzilla> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge output
emerge --info emerge output |
Description
boris64
2010-08-15 19:30:48 UTC
Created attachment 243099 [details]
emerge output
Created attachment 243101 [details]
emerge --info
Created attachment 243103 [details]
emerge output
BASEDIR="/var/portage" Why is that set and where did you set it? = This is set in /etc/make.conf because my complete portage stuff is in a custom directory (/var/portage of course) for quite some years now. If this is somehow considered to be wrong, why the hell is it the _only_ ebuild that breaks because of this? After commenting out BASEDIR=/var/portage in /etc/make.conf i am able to install net-tools without any problems. However, this is still strange. The BASEDIR once was a variable from /etc/make-{conf,globals} some days (or years?) ago. Is my make.conf really so outdated? (In reply to comment #6) > This is set in /etc/make.conf because my complete portage > stuff is in a custom directory (/var/portage of course) > for quite some years now. If this is somehow considered > to be wrong, why the hell is it the _only_ ebuild that > breaks because of this? Maybe it's the only Makefile that actually uses the variable. No harm in unsetting it as it isn't used anywhere else. I simply changed BASEDIR into PORTAGE_BASEDIR (makes more sense to me). No problems anymore so far, i think this bug can be closed. I guess the message to future users of the BASEDIR variable in make.conf is that you shouldn't. Marking as such. :) |