| 1 |
On 4/2/19 8:34 PM, Adam Carter wrote: |
| 2 |
> On Wed, Apr 3, 2019 at 12:00 PM Daniel Frey <djqfrey@×××××.com |
| 3 |
> <mailto:djqfrey@×××××.com>> wrote: |
| 4 |
> |
| 5 |
> On 4/2/19 5:17 PM, Daniel Frey wrote: |
| 6 |
> > Well, I haven't been bitten for quite a while now (years)... |
| 7 |
> > |
| 8 |
> > I have been doing updates to my mythtv frontends and I noticed |
| 9 |
> this time |
| 10 |
> > around updating has been taking FOREVER. Something in this round of |
| 11 |
> > updates broke distcc (which worked the last update run.) In |
| 12 |
> addition, I |
| 13 |
> > have multiple packages failing the same way: |
| 14 |
> > |
| 15 |
> > distcc[3596] (dcc_open_lockfile) ERROR: failed to creat |
| 16 |
> > |
| 17 |
> /var/tmp/portage/dev-libs/glib-2.58.3/homedir/.distcc/lock/cpu_localhost_0: |
| 18 |
> |
| 19 |
> > Permission denied |
| 20 |
> |
| 21 |
> |
| 22 |
> I have to set this to get distcc to work (the file is created with root |
| 23 |
> ownership) - not sure why your lockfile is in a different location. |
| 24 |
> |
| 25 |
> chown portage /var/tmp/portage/.distcc/lock/cpu_localhost_0 |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
What's stranger still is I haven't made any configuration changes. I |
| 30 |
think I might have figured out the other problem (recompiling glibc |
| 31 |
now), but I've disabled distcc for now. |
| 32 |
|
| 33 |
I wonder if it's possible to manually specify a lock directory. |
| 34 |
|
| 35 |
Dan |
Archives