Summary: | sys-apps/portage: unmerge orphan symlinks when CONTENTS lists directory instead | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dschridde+gentoobugs, pesa, ssuominen |
Priority: | Normal | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 423127 | ||
Bug Blocks: | 428082, 423075 |
Description
Zac Medico
2012-06-14 21:15:00 UTC
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0c29f1531fe9787cd1bd96fcd5c34ec5e6128aa4 This is fixed in 2.1.11 and 2.2.0_alpha111. Since /lib is a symlink to /lib64 on my amd64 system, I'm getting a message like this when I rebuild my kernel modules: * One or more symlinks to directories have been preserved in order to * ensure that files installed via these symlinks remain accessible: * * /lib * I guess we can just whitelist /lib and /usr/lib here. (In reply to comment #3) > I guess we can just whitelist /lib and /usr/lib here. Sounds good. |