| 1 |
On Tue, Sep 13, 2016 at 9:12 AM, Bertram Scharpf |
| 2 |
<lists@×××××××××××××××.de> wrote: |
| 3 |
> |
| 4 |
> The rfkill install interferes with Git! |
| 5 |
> |
| 6 |
> Error log: |
| 7 |
> P: /usr/portage/.git/index.lock |
| 8 |
> A: /usr/portage/.git/index.lock |
| 9 |
> R: /usr/portage/.git/index.lock |
| 10 |
> C: git update-index --refresh --unmerged |
| 11 |
> |
| 12 |
>>>> '/usr/portage/tmp/portage/net-wireless/rfkill-0.5/temp/build.log' |
| 13 |
> |
| 14 |
> I helped myself by renaming the .git directory, but that's |
| 15 |
> only a workaround. |
| 16 |
> |
| 17 |
> How can I fix this? Should I report this? |
| 18 |
> |
| 19 |
|
| 20 |
It looks like you have your PORTAGE_TMPDIR set as /usr/portage/tmp? |
| 21 |
I'm not sure if that is supposed to work or not, but I suspect that |
| 22 |
might be the problem. Since it is located INSIDE a git repository (if |
| 23 |
you have /usr/portage checked out from git), I suspect there is some |
| 24 |
confusion if the package is trying to check something else out using |
| 25 |
git or otherwise manipulate it. The .git directory is outside of the |
| 26 |
sandbox so it shouldn't be able to be modified. |
| 27 |
|
| 28 |
I suggest moving PORTAGE_TMPDIR to someplace like /var/tmp or /tmp or |
| 29 |
someplace else. It isn't really ideal to have volatile information in |
| 30 |
/usr anyway (this is the part where everybody chimes in and points out |
| 31 |
that /usr/portage is in the wrong place to begin with). |
| 32 |
|
| 33 |
-- |
| 34 |
Rich |
Archives