111189 – emerge doesn't work with PORT_LOGDIR enabled

Bug 111189 - emerge doesn't work with PORT_LOGDIR enabled

Summary: emerge doesn't work with PORT_LOGDIR enabled

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Gentoo/Alt
Classification:	Unclassified
Component:	Other (show other bugs)
Hardware:	x86 FreeBSD

Importance:	High normal (vote)
Assignee:	Gentoo/BSD Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-11-01 13:48 UTC by Sergio Bevilacqua
Modified:	2006-04-14 10:14 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sergio Bevilacqua 2005-11-01 13:48:00 UTC

if I uncomment the PORT_LOGDIR=/var/log/portage, emerge doesn't work.
it stops at begin of work, after MD5sum. top shows python2.4 in waiting state.

this is the directory in /var/log:
drwxrws---  2 portage  portage     512 Nov  1 16:51 portage/

note that the directory permission will be reset every time I launch emerge

Reproducible: Always
Steps to Reproduce:
1. uncomment PORT_LOGDIR=/var/log/portage, in make.conf
2. mkdir /var/log/portage
3. chown portage:portage /var/log/portage
4. emerge <any-package>, or emerge -C <any-package>

Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev

2006-02-28 15:20:49 UTC

Can you confirm this with newer versions of portage?

Comment 2 Diego Elio Pettenò (RETIRED) gentoo-dev

2006-04-14 10:14:15 UTC

Can't reproduce here, maybe fixed with recent portages.