1 |
Am Tue, 13 Sep 2016 19:49:04 +0200 |
2 |
schrieb Bertram Scharpf <lists@×××××××××××××××.de>: |
3 |
|
4 |
> On Tuesday, 13. Sep 2016, 11:12:11 -0400, Rich Freeman wrote: |
5 |
> > On Tue, Sep 13, 2016 at 9:12 AM, Bertram Scharpf |
6 |
> > <lists@×××××××××××××××.de> wrote: |
7 |
> > > |
8 |
> > > The rfkill install interferes with Git! |
9 |
> > > |
10 |
> > > Error log: |
11 |
> > > P: /usr/portage/.git/index.lock |
12 |
> > > A: /usr/portage/.git/index.lock |
13 |
> > > R: /usr/portage/.git/index.lock |
14 |
> > > C: git update-index --refresh --unmerged |
15 |
> > > |
16 |
> [...] |
17 |
> > > |
18 |
> > > I helped myself by renaming the .git directory, but that's |
19 |
> > > only a workaround. |
20 |
> > > |
21 |
> > > How can I fix this? Should I report this? |
22 |
> > |
23 |
> > It looks like you have your PORTAGE_TMPDIR set |
24 |
> > as /usr/portage/tmp? |
25 |
> |
26 |
> Indeed. I have a "build partition" that I use for both, |
27 |
> package downloading and building in /usr/portage/tmp. |
28 |
> |
29 |
> The rfkill make suite looks for a version number and in case |
30 |
> the work directory is a Git repo it tries to query the |
31 |
> version number there. Then, it finds the Git repo in |
32 |
> /usr/portage and fails. Not very friendly! |
33 |
> |
34 |
> > I suggest moving PORTAGE_TMPDIR to someplace like /var/tmp or /tmp |
35 |
> > or someplace else. It isn't really ideal to have volatile |
36 |
> > information in /usr anyway (this is the part where everybody chimes |
37 |
> > in and points out that /usr/portage is in the wrong place to begin |
38 |
> > with). |
39 |
> |
40 |
> I'll see how I solve it. I do not have time to make a |
41 |
> decision this evening. |
42 |
|
43 |
You could |
44 |
|
45 |
# mount -o bind /usr/portage/tmp /var/tmp/portage |
46 |
|
47 |
and then point the portage tmp dir to that directory. From there, |
48 |
ebuilds cannot see the .git of /usr/portage. |
49 |
|
50 |
|
51 |
-- |
52 |
Regards, |
53 |
Kai |
54 |
|
55 |
Replies to list-only preferred. |