every time i emerge, its switching from 1.1.94 to 1.1.12 and back: bash-2.05b# emerge -uDvp world [ebuild UD] dev-libs/libgcrypt-1.1.12 [1.1.94] -doc +nls 0 kB after i remove it (emerge unmerge dev-libs/libgcrypt): bash-2.05b# emerge -uDpv world [ebuild N ] dev-libs/libgcrypt-1.1.94 +nls 0 kB [ebuild N ] dev-libs/libgcrypt-1.1.12 -doc +nls 0 kB after i emerge 1.1.94: emerge -UDvp world [ebuild UD] dev-libs/libgcrypt-1.1.12 [1.1.94] -doc +nls 0 kB after i emerge 1.1.12 (emerge -p =dev-libs/libgcrypt-1.1.12): bash-2.05b# emerge -UDvp world [ebuild U ] dev-libs/libgcrypt-1.1.94 [1.1.12] +nls 0 kB this looks very stange to me.....so i can emerge all day long What i have hidden, "emerge -uD world" wants to install app-crypt/gpgme-0.3.14, what needs libgcrypt. And the following: bash-2.05b# qpkg -q dev-libs/libgcrypt dev-libs/libgcrypt-1.1.12 * DEPENDED ON BY: dev-libs/libgcrypt-1.1.92 DEPENDED ON BY: dev-libs/libgcrypt-1.1.94 DEPENDED ON BY: dev-libs/libgcrypt-1.1.91 DEPENDED ON BY: dev-libs/libgcrypt-1.2.0 DEPENDED ON BY: dev-libs/libgcrypt-1.1.12 DEPENDED ON BY: bash-2.05b# ? Reproducible: Always Steps to Reproduce: 1. 2. 3.
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...