Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 439588 - app-portage/gentoolkit - eclean does not read /etc/portage/make.conf
Summary: app-portage/gentoolkit - eclean does not read /etc/portage/make.conf
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage Tools Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-25 07:56 UTC by Alexander Berntsen (RETIRED)
Modified: 2012-12-23 12:13 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Berntsen (RETIRED) gentoo-dev 2012-10-25 07:56:46 UTC
[root@lolbook/root]----------------------------------------------------------------------------------------------------
# eclean -d packages                                                                                                   
 * Building file list for packages cleaning...
!!! Error accessing PKGDIR.

!!! (Check your /etc/make.conf and environment).

!!! Error: [Errno 2] No such file or directory: '/usr/portage/packages'













Gentoolkit isn't up to date in some areas. I happened upon this particular bork just now. Please fix the path.
Comment 1 Brian Dolbec (RETIRED) gentoo-dev 2012-12-23 07:46:52 UTC
Eclean does not read make.conf at all.
It gets it path information from portage.
So, if it fails to find your packages directory, that is because your make.conf settings are incorrect, or you have never had/nor made any binpkgs for emerge to have created the default.

As for the make.conf path, that portion of this bug is a just an error message printed by eclean due to the failure.  That portion is a duplicate of bug 445904.
It has a better description and resolution.

The rest of the failure is user side from what info was listed, so unless you can supply more info as to the failure
Comment 2 Alexander Berntsen (RETIRED) gentoo-dev 2012-12-23 12:13:29 UTC
The error message threw me off as it came just after I moved make.conf. The problem is indeed not the make.conf move. Marked as INVALID. Thanks for the clarification.