| 1 |
On Tuesday, 13. Sep 2016, 11:12:11 -0400, Rich Freeman wrote: |
| 2 |
> On Tue, Sep 13, 2016 at 9:12 AM, Bertram Scharpf |
| 3 |
> <lists@×××××××××××××××.de> wrote: |
| 4 |
> > |
| 5 |
> > The rfkill install interferes with Git! |
| 6 |
> > |
| 7 |
> > Error log: |
| 8 |
> > P: /usr/portage/.git/index.lock |
| 9 |
> > A: /usr/portage/.git/index.lock |
| 10 |
> > R: /usr/portage/.git/index.lock |
| 11 |
> > C: git update-index --refresh --unmerged |
| 12 |
> > |
| 13 |
> >>>> '/usr/portage/tmp/portage/net-wireless/rfkill-0.5/temp/build.log' |
| 14 |
> > |
| 15 |
> > I helped myself by renaming the .git directory, but that's |
| 16 |
> > only a workaround. |
| 17 |
> > |
| 18 |
> > How can I fix this? Should I report this? |
| 19 |
> |
| 20 |
> It looks like you have your PORTAGE_TMPDIR set as /usr/portage/tmp? |
| 21 |
|
| 22 |
Indeed. I have a "build partition" that I use for both, |
| 23 |
package downloading and building in /usr/portage/tmp. |
| 24 |
|
| 25 |
The rfkill make suite looks for a version number and in case |
| 26 |
the work directory is a Git repo it tries to query the |
| 27 |
version number there. Then, it finds the Git repo in |
| 28 |
/usr/portage and fails. Not very friendly! |
| 29 |
|
| 30 |
> I suggest moving PORTAGE_TMPDIR to someplace like /var/tmp or /tmp or |
| 31 |
> someplace else. It isn't really ideal to have volatile information in |
| 32 |
> /usr anyway (this is the part where everybody chimes in and points out |
| 33 |
> that /usr/portage is in the wrong place to begin with). |
| 34 |
|
| 35 |
I'll see how I solve it. I do not have time to make a |
| 36 |
decision this evening. |
| 37 |
|
| 38 |
Bertram |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
Bertram Scharpf |
| 43 |
Stuttgart, Deutschland/Germany |
| 44 |
http://www.bertram-scharpf.de |
Archives