Summary: | portage-2.0.51-r3 traceback with dangling symlink | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aron Griffis (RETIRED) <agriffis> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | devil, linux, sascha-gentoo-bugzilla |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | 2.0.51-r3.bad.symlink.patch |
Description
Aron Griffis (RETIRED)
2004-11-12 11:37:57 UTC
Fixed a while ago, but there was no bug. I'll attach the fix in a minute. Created attachment 43841 [details, diff]
2.0.51-r3.bad.symlink.patch
*** Bug 70828 has been marked as a duplicate of this bug. *** *** Bug 70819 has been marked as a duplicate of this bug. *** Hi Jason. Thanks for pointing me this way. I'll try the patch and report on my experiences with it. Hi, the patch worked, xorg installed okay. Thanks :) *** Bug 73057 has been marked as a duplicate of this bug. *** thx. fixed my texi2html-problem on ~ppc This worked fine for my problem with xorg. :-) I'm having the same problem while installing lapack after unmerging lapack-atlas. Will file a separate bug about lapack-atlas leaving this link behind. Any idea when the fix will get into mainstream Portage? Yes, patch necessary. Please mainstream. (This for openssl on a system that went some months between updates.) Saw this again today, running portage-2.0.51.19 this time. This instance was on a file /etc/._cfg*, so there might be some CONFIG_PROTECT magic mixed in. I sincerely doubt that it was the same bug. Please open a new one with the error if it happens again. |