Summary: | shadow-4.0.4.1 doesn't provide libshadow.so.0? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrei Ivanov <andrei.ivanov> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | agriffis, ehmsen, gentoo, iggy, listen, vermyndax |
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 37725 | ||
Bug Blocks: |
Description
Andrei Ivanov
2004-01-23 04:20:02 UTC
Anyway... I've rebuilt screen, and everything seems to fine now.... but this shouldn't have happened, I guess.. Hmm.. I don't really care if shadow provides a .so or an .a All I want is my system not to be screwed up my changes like these... This causes issues with KDE apps as well (including but not limited to kuser). For the record, this is persistent with versions of shadow both as x86, and ~x86, and likely for other arches as well. This affects courier also. Maybe someone could add a note to the postinst of the ebuild on the off chance that a user will actually see it. The thing is that I might miss such a comment if I update many packages at once... maybe the comments for all packages should be displayed after all the packages got emerged... but I guess that's another problem. spanky, comment #2 doesn't make sense to me. I don't see why libshadow.so went away. I made shadow-4.0.3-r10.ebuild which enables the shared object. It appears that my changes were reverted in the version bump. i know aron and i was giving a link to another bug about why the .so was being added/removed i dont really care whether .so exists or not so long as my stuff doesnt break when i upgrade Aron, because we cannot move login, etc. Best bet is with the -fPIC fix. ok, not going to provide libshadow.so |