SOLVED Re: [proaudio] amsynth permission denied

[Paul Winkler <pw_lists@xxxxxxxxxx>]

On Sun, Oct 22, 2006 at 11:24:56AM -0700, Mark Knecht wrote:
> On 10/22/06, Paul Winkler <pw_lists@xxxxxxxxxx> wrote:
> >On Sun, Oct 22, 2006 at 10:29:48AM -0700, Mark Knecht wrote:
> >> Hi Paul,
> >>   Where is your overlay? Is it on a separate partiton?
> >
> >Nope.  /home and /usr are all part of the root partition.
> >I can emerge stuff from gentoo just fine, but nothing from
> >the overlay.
> >
> 
> Nothing at all? Very strange.

OK, I found the problem.
I added this at line 1454 just before the offending line in
/usr/lib/portage/bin/ebuild.sh:

echo XXXXXX What user do i think I am? $USER
echo what groups do I belong to? `groups`
echo can I get to the file?
ls -l $EBUILD

And then when I do "emerge horgand" I see this (excerpt):

 * checking horgand_1.07-1.diff.gz ;-) ...
 * [ ok ]
XXXXXX What user do i think I am? root
what groups do I belong to? root bin daemon sys adm disk wheel floppy
dialout tape video
Can I see anything?
-rw-r--r-- 1 pw users 992 Oct  1 16:31
/home/pw/Downloads/Apps/Audio/proaudio_overlay/proaudio/media-sound/horgand/horgand-1.07-r1.ebuild
XXXXXX What user do i think I am? portage
what groups do I belong to? portage
Can I see anything?
ls:
/home/pw/Downloads/Apps/Audio/proaudio_overlay/proaudio/media-sound/horgand/horgand-1.07-r1.ebuild:
Permission denied

So apparently, portage switches the effective user and re-runs ebuild.sh
before trying to source the ebuild.

For my first attempt at a fix, I used "usermod -a -G users portage"
to add portage to the users group, but apparently this doesn't work;
I still see:
what groups do I belong to? portage

... so the effective user is switched but the groups file is
not respected.

So I got sensible and did what everybody else does...
I read http://www.gentoo.org/proj/en/overlays/userguide.xml
and emerged layman and started using that instead :)
Which involved a bit of pain since the docs are slightly wrong,
see bug http://bugs.gentoo.org/show_bug.cgi?id=149867
... you need to manually add something like 
PORTDIR_OVERLAY="$PORTDIR_OVERLAY"
to /usr/portage/local/layman/make.conf to start out.

After that it's all fine and I can finally use the freakin' overlay again.

-- 

Paul Winkler
http://www.slinkp.com