Bug 29298 – default DISTCC_DIR uses wrong base variable

• Status: RESOLVED FIXED
• Product: Portage Development

[Description SpanKY 2003-09-21 17:58:58 UTC]

ebuild.sh: [ "${DISTCC_DIR-unset}"  == "unset" ] && export
DISTCC_DIR="${PORT_TMPDIR}/.distcc"

it should be PORTAGE_TMPDIR

[Comment 1 Brian Friday 2003-09-22 16:58:52 UTC]

I can confirm this bug as well. In addition to changing the PORT_TMPDIR to PORTAGE_TMPDIR I also had to create the directory refereced DISTCC_DIR. If it wasn't created I got lots of errors about unable to access directories.

In addition are the following two issues:

/etc/conf.d/distccd sets the DISTCC_DIR to be /var/tmp/distccd

/etc/make.conf when it is fixed points to /var/tmp/.distcc

I am assuming that both these DISTCC_DIR need to be set to the same variable perhaps even the /etc/conf.d/distccd version needs to be updated to remove the DISTCC_DIR line.

[Comment 2 Lisa Seelye (RETIRED) 2003-09-22 17:01:42 UTC]

bug 29171 has patches that makes user-setting DISTCC_DIR unnecessary.

[Comment 3 Marius Mauch (RETIRED) 2003-09-23 05:25:57 UTC]

*** Bug 29415 has been marked as a duplicate of this bug. ***

[Comment 4 Rob Davies 2003-09-23 05:46:06 UTC]

This effects /etc/make.conf as well which has had comment suggesting 
DISTCC_DIR="${PORT_TMPDIR}/.distcc" added, that also ought read PORTAGE_TMPDIR. 

[Comment 5 Aron Griffis (RETIRED) 2003-09-27 06:22:36 UTC]

Furthermore, the documentation reads

    Note: Set DISTCC_DIR=${PORTAGE_TMPDIR}/portage/.distcc

    Note: You should also uncomment the DISTCC_TMPDIR line.

I think the second line should read "You should also uncomment the PORTAGE_TMPDIR
line."  However this shouldn't be necessary unless you want to change DISTCC_DIR
from the default, right?

[Comment 6 Lisa Seelye (RETIRED) 2003-09-27 08:27:28 UTC]

with portage >=2.0.49-r6 and >=distcc-2.11, this is irrelevant.

[Comment 7 Aron Griffis (RETIRED) 2003-09-27 14:58:40 UTC]

# epm -q portage distcc
portage-2.0.49-r7
distcc-2.11-r2

I'm still getting these messages:

distcc[9385] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/.distcc/lock failed:
Permission denied
distcc[9385] (dcc_lock_one) ERROR: failed to lock
distcc[9385] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/.distcc/state failed:
Permission denied
distcc[9385] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/.distcc/state failed:
Permission denied
distcc[9387] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/.distcc/lock failed:
Permission denied
distcc[9387] (dcc_lock_one) ERROR: failed to lock
distcc[9387] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/.distcc/state failed:
Permission denied
distcc[9387] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/.distcc/state failed:
Permission denied

[Comment 8 Lisa Seelye (RETIRED) 2003-09-27 15:04:23 UTC]

Aron: do this:

grep 0644 /usr/lib/python2.2/site-packages/portage.py

If its doing chmodding 0644 to state/lock/.distcc, then the wrong patch has
been applied to Portage.  This 0644 needs to be 02755.

[Comment 9 Aron Griffis (RETIRED) 2003-09-27 15:18:54 UTC]

# grep 0644 /usr/lib/python2.2/site-packages/portage.py
os.chmod(settings["DISTCC_DIR"],0644)
os.chmod(settings["DISTCC_DIR"]+x,0644)

[Comment 10 SpanKY 2003-10-25 06:31:51 UTC]

*** Bug 31966 has been marked as a duplicate of this bug. ***

[Comment 11 Nicholas Jones (RETIRED) 2003-10-26 20:25:32 UTC]

This is already in -r15.