Summary: | sys-libs/tdb-1.2.1 package collision with sys-libs/tdb-1.2.0-r2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pekka-Matti Nieminen <pmn> |
Component: | [OLD] Library | Assignee: | Patrick Lauer <patrick> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caster, jaggerz, Martin.vGagern, samba |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pekka-Matti Nieminen
2010-04-11 05:39:14 UTC
other workaround is to delete /usr/lib64/libtdb.so.1 symlink I encounter the same thing, although I have no clue where the symlink came from in the first place. Still have the old package around, but even a look at its saved ebuild and environment don't explain this behaviour to me. The soname is libtdb.so.1. My guess is that an earlier tdb version did not install the libtdb.so.1 symlink but ldconfig created it instead. Isn't (shouldn't) there be a qa check to detect the missing symlinks? (In reply to comment #1) > other workaround is to delete /usr/lib64/libtdb.so.1 symlink This workaround did not work for me. I'm on a 32-bit install, so my libpath is '/usr/lib/', but I don't think that's actually relevant. Pekka-Matti's workaround *did* work, however (i.e., 'emerge -C tdb && emerge tdb'). Even if sys-libs/tdb-1.2.0-r2 is no longer in portage, I've added a double block to the previous tdb version |