Summary: | app-crypt/heimdal-1.2.1-r1 install issues with /usr/bin/compile_et | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Hammill <michael> |
Component: | New packages | Assignee: | Gentoo Kerberos Maintainers <kerberos> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Hammill
2009-02-21 19:43:16 UTC
# which compile_et /usr/bin/compile_et # equery b /usr/bin/compile_et [ Searching for file(s) /usr/bin/compile_et in *... ] app-crypt/heimdal-1.2.1-r1 (/usr/bin/compile_et) sys-libs/e2fsprogs-libs-1.41.3-r1 (/usr/bin/compile_et) My last comment pointed to a work around, which was to: 1. unemerge heimdal (which wipes /usr/bin/compile_et) 2. re-emerge sys-libs/e2fsprogs-libs (to get correct compile_et) 3. emerge sys-libs/e2fsprogs While that works, I now see the problem was collision between heimdal and e2fsprogs-libs. That seems a bit nasty. Where should that be reported? Do I resubmit this bug with heimdal or e2fsprogs-libs? As is, I need heimdal, but am afraid to emerge it if it hoses e2fsprogs-libs. the kerberos packages should have stopped providing the et related files a while ago ... that means binaries, includes, and libraries (In reply to comment #3) OK, I guess this should be closed then. You make the final decision. I added collision-protect to FEATURES and re-emerged heimdal. There was no collision on compile_et (or anything else). Double checking I found # equery b /usr/bin/compile_et [ Searching for file(s) /usr/bin/compile_et in *... ] sys-libs/e2fsprogs-libs-1.41.3-r1 (/usr/bin/compile_et) So all looks as it should. I guess that app-crypt/heimdal-1.2.1-r1 owned compile_et as shown earlier was something inherited from an older version of heimdal. /Mike you're saying you re-emerged the same exact version (down to the -r#) and heimdal stopped installing certain files ? ugh, that's no good ... heimdal should get a rev bump to force that change out to systems. (In reply to comment #5) Yes, that is exactly it. Same version down to the -r#. What I don't know is if heimdal-1.2.1-r1 originally installed /usr/bin/compile_et or if it was an earlier version of heimdal and heimdal-1.2.1-r1 simply picked up ownership from its predecessor. the kerberos guys can double check to make sure I do not see such a collision with e2fsprogs-libs-1.41.12 and heimdal-1.3.3-r1 on my ~x86. Maybe fixed since: *heimdal-1.2.1-r4 (27 Aug 2009) 27 Aug 2009; Michael Hammer <mueli@gentoo.org> +files/heimdal-mit-krb5-free.patch, +heimdal-1.2.1-r4.ebuild: added heimdal-1.2.1-r4 with a patch fixing bug #282459 06 Aug 2009; Michael Hammer <mueli@gentoo.org> heimdal-1.2.1-r3.ebuild: pulled util-linux in as dependency because libuuid is going to move there 05 Aug 2009; Michael Hammer <mueli@gentoo.org> heimdal-1.2.1-r3.ebuild: changed depend for e2fsprogs-libs - it is now stable and we don't have to chooce beetwen this and com_err and ss Aye, not an issue anymore. Closing. |