Am Tue, 13 Sep 2016 19:49:04 +0200
schrieb Bertram Scharpf <li...@bertram-scharpf.de>:

> On Tuesday, 13. Sep 2016, 11:12:11 -0400, Rich Freeman wrote:
> > On Tue, Sep 13, 2016 at 9:12 AM, Bertram Scharpf
> > <li...@bertram-scharpf.de> wrote:  
> > >
> > > The rfkill install interferes with Git!
> > >
> > > Error log:
> > > P: /usr/portage/.git/index.lock
> > > A: /usr/portage/.git/index.lock
> > > R: /usr/portage/.git/index.lock
> > > C: git update-index --refresh --unmerged
> > >  
>  [...]  
> > >
> > > I helped myself by renaming the .git directory, but that's
> > > only a workaround.
> > >
> > > How can I fix this? Should I report this?  
> > 
> > It looks like you have your PORTAGE_TMPDIR set
> > as /usr/portage/tmp?  
> 
> Indeed. I have a "build partition" that I use for both,
> package downloading and building in /usr/portage/tmp.
> 
> The rfkill make suite looks for a version number and in case
> the work directory is a Git repo it tries to query the
> version number there. Then, it finds the Git repo in
> /usr/portage and fails. Not very friendly!
> 
> > I suggest moving PORTAGE_TMPDIR to someplace like /var/tmp or /tmp
> > or someplace else.  It isn't really ideal to have volatile
> > information in /usr anyway (this is the part where everybody chimes
> > in and points out that /usr/portage is in the wrong place to begin
> > with).  
> 
> I'll see how I solve it. I do not have time to make a
> decision this evening.

You could

# mount -o bind /usr/portage/tmp /var/tmp/portage

and then point the portage tmp dir to that directory. From there,
ebuilds cannot see the .git of /usr/portage.


-- 
Regards,
Kai

Replies to list-only preferred.


Reply via email to