2379 – emerge Problems when there is a link in /var/tmp or /var/tmp/portage

Bug 2379 - emerge Problems when there is a link in /var/tmp or /var/tmp/portage

Summary: emerge Problems when there is a link in /var/tmp or /var/tmp/portage

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-05-03 04:09 UTC by Markinho
Modified:	2011-10-30 22:18 UTC (History)
CC List:	1 user (show)

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 Markinho 2002-05-03 04:09:44 UTC

I'm using automount to mount the nesseceary partitions for emerge und kernel.
The automount directory is at /mnt/.systemExtension
So My secondary HDD only needs to spin up when building a kernel or mergings 
something.
The directory /var/tmp is a link to /mnt/.systemExtension/portageTemp.
But with this configuration emerge goes crazy and seems to extract the sources 
to /var/tmp/packages-source instead of /var/tmp/portage/package-source
So every emerge fails.
It is unimportant whether /var/tmp is a link or /var/tmp/portage same error

Workaround: not really ;-)

Mounting the Partition directly to /var/tmp/ and everthing is fine except ...
The automounting and links :-(

Comment 1 Markinho 2002-05-03 04:25:44 UTC

another Workaround: make an separate autmount entry for /var/tmp

Comment 2 Ole Tange 2002-06-27 17:59:08 UTC

It seems to be the same bug as 4256.

4256 does not work either /var or /var/tmp is a link. I am guessing the problem
is a simple test that test if /var is a dir. The test should be if what /var
links to is a dir.

Comment 3 Daniel Robbins (RETIRED) gentoo-dev

2002-07-11 03:11:12 UTC

Fixed in Portage 2.0.12