Summary: | emerge @preserved-rebuild behaves strangely after uninstalling wine/steam | ||
---|---|---|---|
Product: | Portage Development | Reporter: | cpu <cpuandroidmarket> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | bog, gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=215242 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
cpu
2022-10-22 21:35:12 UTC
Probably related to bug 215242. Hi, I went through this about a year ago on one of my systems after purging Wine. If you've removed abi_x86_32 and are expecting those 32-bit libraries to be cleaned up, then this is bug 652382. There is a dependency cycle between the 32-bit libraries: libharfbuzz.so.0.50100.0 and libfreetype.so.6.18.3 depend on each other. Portage is currently unable to clean this up. You can work around that by explicitly rebuilding 32-bit freetype without the harfbuzz dependency, which will break the cycle. Use something like: # ABI_X86=32 USE=-harfbuzz emerge -av1 media-libs/freetype I can't recall if I had to emerge any other packages after that for Portage to remove the preserved libs, but I don't think I did. |