Re: [gentoo-user] Re: Emerge interferes with Git (Was: Wlan disappeared after suspend)

2016-09-17 Thread Bertram Scharpf
On Saturday, 17. Sep 2016, 10:36:28 -0400, Rich Freeman wrote:
> On Sat, Sep 17, 2016 at 9:54 AM, Bertram Scharpf
>  wrote:
> 
> > This should be part of the documentation. Where do I best
> > report it?
> 
> Well, for anything on the wiki I'd suggest just adding it.  For the
> manpages I'd submit a bug on bugs.gentoo.org against portage (the
> software).

Do you have an address of the wiki you mean? Reporting
should take less time than finding the fix.

Bertram


-- 
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de



[gentoo-user] Re: Emerge interferes with Git (Was: Wlan disappeared after suspend)

2016-09-17 Thread Kai Krakow
Am Sat, 17 Sep 2016 10:36:28 -0400
schrieb Rich Freeman :

> On Sat, Sep 17, 2016 at 9:54 AM, Bertram Scharpf
>  wrote:
> >
> > On Saturday, 17. Sep 2016, 10:31:17 +0200, Kai Krakow wrote:  
> > > Am Tue, 13 Sep 2016 19:49:04 +0200
> > > schrieb Bertram Scharpf :
> > >  
>  [...]  
> > >
> > > 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.  
> >
> > As long as I do not set GIT_DISCOVERY_ACROSS_FILESYSTEM...  
> 
> I don't think that if you navigate upwards after following a bind
> mount that you end up in the tree that was mounted.  Ie,
> /var/tmp/portage/.. = /var/tmp, not /usr/portage.  With a symbolic
> link it would resolve to /usr/portage unless the shell does something
> clever.
> 
> You can mount bind mounts into containers, and I'm pretty confident
> the container can't navigate out into the rest of the filesystem that
> way.

True. This is why I suggested a bind mount and not a symlink.

-- 
Regards,
Kai

Replies to list-only preferred.




Re: [gentoo-user] Re: Emerge interferes with Git (Was: Wlan disappeared after suspend)

2016-09-17 Thread Rich Freeman
On Sat, Sep 17, 2016 at 9:54 AM, Bertram Scharpf
 wrote:
>
> On Saturday, 17. Sep 2016, 10:31:17 +0200, Kai Krakow wrote:
> > Am Tue, 13 Sep 2016 19:49:04 +0200
> > schrieb Bertram Scharpf :
> >
> > > 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!
> >
> > 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.
>
> As long as I do not set GIT_DISCOVERY_ACROSS_FILESYSTEM...

I don't think that if you navigate upwards after following a bind
mount that you end up in the tree that was mounted.  Ie,
/var/tmp/portage/.. = /var/tmp, not /usr/portage.  With a symbolic
link it would resolve to /usr/portage unless the shell does something
clever.

You can mount bind mounts into containers, and I'm pretty confident
the container can't navigate out into the rest of the filesystem that
way.

>
> I decided to add the following line to /etc/portage/make.conf:
>
>   GIT_CEILING_DIRECTORIES="$GIT_CEILING_DIRECTORIES:$PORTAGE_TMPDIR"
>
> This should be part of the documentation. Where do I best
> report it?

Well, for anything on the wiki I'd suggest just adding it.  For the
manpages I'd submit a bug on bugs.gentoo.org against portage (the
software).


-- 
Rich



Re: [gentoo-user] Re: Emerge interferes with Git (Was: Wlan disappeared after suspend)

2016-09-17 Thread Bertram Scharpf
On Saturday, 17. Sep 2016, 10:31:17 +0200, Kai Krakow wrote:
> Am Tue, 13 Sep 2016 19:49:04 +0200
> schrieb Bertram Scharpf :
> 
> > 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!
> 
> 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.

As long as I do not set GIT_DISCOVERY_ACROSS_FILESYSTEM...

I decided to add the following line to /etc/portage/make.conf:

  GIT_CEILING_DIRECTORIES="$GIT_CEILING_DIRECTORIES:$PORTAGE_TMPDIR"

This should be part of the documentation. Where do I best
report it?

Bertram


-- 
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de



[gentoo-user] Re: Emerge interferes with Git (Was: Wlan disappeared after suspend)

2016-09-17 Thread Kai Krakow
Am Tue, 13 Sep 2016 19:49:04 +0200
schrieb Bertram Scharpf :

> On Tuesday, 13. Sep 2016, 11:12:11 -0400, Rich Freeman wrote:
> > On Tue, Sep 13, 2016 at 9:12 AM, Bertram Scharpf
> >  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.