Summary: | [multilib-strict] sys-fs/dmraid-1.0.0_rc8-r1 has files not allowed in /lib | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sandro Bonazzola (RETIRED) <sanchan> |
Component: | Current packages | Assignee: | AMD64 Project <amd64> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | ian |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 139860 |
Description
Sandro Bonazzola (RETIRED)
2006-05-22 12:48:07 UTC
Someone please remove maintainer-wanted@g.o. from metadata.xml; it's for new ebuilds only. maintainer-needed@g.o. would be a "proper" one for orphaned ebuilds. Please test the new version -rc12 in portage. Im not sure exactly what the original issue is here (file path / naming?) but i believe it has been fixed, as files are now installed to usr/lib and there seems to be no file of similar name in the image. This is fixed in rc12. multilib-strict gets triggered by shared objects going into /lib or /usr/lib instead of /lib64 or /usr/lib64. While /lib is a symlink to /lib64 on regular amd64 installs this might be a problem on some profiles. Verified, works fine for me. Thanks. I hope dmraid will find soon a maintainer. |