After update system emerge fails everytime

Nefreyu

I've done a emerge --update system yesterday, The fileutils package (the 4th or 5th package in row) failed with errors very much like the errors below. since then every package i've tried to update gives me the same errors.

The only special thing of my system may be that /usr is a symlink to /mnt/hdb1/sys/usr

But that is working for a while now and has not stopped me from installing new packages so I think it's not related.

Has anyone seen this before :?:

(I've used the search and found related topics but those all had the problem of one specific package failing, not all packages)

>>> Completed installing into /var/tmp/portage/tar-1.13.25-r3/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------
LOG FILE = "/tmp/sandbox-tar-1.13.25-r3-4290.log"

unlink: /mnt/hdb1/sys/usr/lib/cf4307/conftest9012345
unlink: /mnt/hdb1/sys/usr/lib/cf4307/conftest9012346
--------------------------------------------------------------------------------

rac · Posted: Mon Oct 28, 2002 9:09 am Post subject:

Is there any way to find out what the package that got compiled right before fileutils was? If it was autoconf or automake or something like that, that might be an avenue of inquiry.
_________________
For every higher wall, there is a taller ladder

jondkent · Apprentice Joined: 26 Jul 2002 Posts: 289 Location: London

Hi,

I have exactly the same problem, I had a link from /usr/lib to /extra/lib to free up some space, but any package that merges into /usr/lib gives me the same error you are seeing.

Sorry, have no work around, but this smells like a bug, at worst, or an over fussy merging system. You could switch off the sandbox, but that not really ideal. Whatever the problem there _is_ a problem with portage/emerge that causes this and not anything to do with a particular ebuild.

I would really like an answer to this as well. Anyone??

Cheers

Jon

Nefreyu · Posted: Mon Oct 28, 2002 1:27 pm Post subject:

Hmm, i've tried to find wich package was updated before fileutils but I was unable to find it. autoconf and automake where on the list as far as I can remember and they are not on the list anymore so I suppose they where updated before fileutils.

So pobably the new version of either of these tools can't work with a linked /usr directory.

I'm now copying the /usr to the same partition and i'll test it again. If I can update then we have a search direction

Regards

Nefreyu · Posted: Mon Oct 28, 2002 1:33 pm Post subject:

It's works, the system is currently very busy updating. So the problem resides in the linked /usr directory.

Is there a prettier way to solve that problem? I don't want to mount a seperate partion for it if its possible (I get so much partitions that clutters the system

)

jondkent · Apprentice Joined: 26 Jul 2002 Posts: 289 Location: London

Yeh, thats the only way I got it work as well :evil:

Jon