Summary: | Need dev-libs/libgcrypt-1.1.94 and dev-libs/libgcrypt-1.1.12 in the same time | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Hummel <mike> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED REMIND | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Hummel
2004-09-03 13:56:04 UTC
In the example i did this by hand (emerge -p =dev-libs/libgcrypt-1.1.12), its the same problem if i every time do "emerge -uD world" The emerge world update, can you please run it with --tree and attach the output to this bug? bash-2.05b# emerge -uDtp world [nomerge ] app-crypt/newpg-0.9.4-r1 [ebuild UD] dev-libs/libgcrypt-1.1.12 [1.1.94] [nomerge ] kde-base/kdeaddons-3.3.0 [ebuild U ] kde-base/kdepim-3.3.0-r1 [3.3.0] after "emerge -u =dev-libs/libgcrypt-1.1.12": bash-2.05b# emerge -uDtp world [nomerge ] kde-base/kdeaddons-3.3.0 [ebuild U ] kde-base/kdepim-3.3.0-r1 [3.3.0] [nomerge ] app-crypt/gpgme-0.9.0-r1 [ebuild U ] dev-libs/libgcrypt-1.1.94 [1.1.12] Thanks for this hint, so its a quick solution to unmerge kdepim or newpg. I set kde-base/* to ~x86, this could be the reason for the conflict. Perhaps a hidden problem, that should be solved before setting kde-base/*-3.3.0 to stable? I tried to set newpg to ~x86, but it was no goal. Now i removed it, but this is no solution for the future... |