Summary: | xorg-x11-6.8.2-r1 fails on amd64: symlink "/usr/lib32" failed: File exists | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | bonyhips <deviant> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | amd64, tacvbo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 97572 |
Description
bonyhips
2005-04-01 01:29:03 UTC
ls -ld /usr/lib* please ian:~> ls -ld /usr/lib* drwxr-xr-x 64 root root 53248 Mar 30 12:31 /usr/lib drwxr-xr-x 4 root root 4096 Mar 29 15:18 /usr/lib32 lrwxr-xr-x 1 root root 3 Mar 29 16:03 /usr/lib64 -> lib drwxr-xr-x 7 root root 4096 Jan 23 02:23 /usr/libexec I got the exactly the same error. I had just updated my profile to 2005.0 from 2004.3. After the error I now get and INCOMPLETE MERGE message: dwallace# emerge -pv xorg-x11 These are the packages that I would merge, in order: Calculating dependencies ...done! INCOMPLETE MERGE: /var/db/pkg/x11-base/-MERGING-xorg-x11-6.8.2-r1 [ebuild U ] x11-base/xorg-x11-6.8.2-r1 [6.8.0-r3] (-3dfx) (-3dnow) +bitmap-fonts -cjk -debug -dlloader -dmx -doc +font-server* -hardened -insecure-drivers +ipv6 -minimal (-mmx) +nls +opengl +pam -sdk (-sse) -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv 0 kB (In reply to comment #2) > ian:~> ls -ld /usr/lib* > drwxr-xr-x 64 root root 53248 Mar 30 12:31 /usr/lib > drwxr-xr-x 4 root root 4096 Mar 29 15:18 /usr/lib32 > lrwxr-xr-x 1 root root 3 Mar 29 16:03 /usr/lib64 -> lib > drwxr-xr-x 7 root root 4096 Jan 23 02:23 /usr/libexec (/usr)/lib64 should be a dir in > 2005.0 with (/usr)/lib being a symlink pointing to it. Seems to be a `normal` (but not good) behaviour with migrated 2004.3->2005.0 systems. Try to fix it using busybox or sash. Improper migration to 2005.0 just to be clear here, i followed the 2005.0 migration instructions to the letter and ended up with the results in the bug log when it got to migrating xorg-x11. so i don't think the bug is invalid. but whatever, very few people seem to have hit it, and also someone suggested a workaround in the forums which sorts this particular problem out. |