These are the packages that I would merge, in order: Calculating world dependencies ...done! [blocks B ] >=app-crypt/gpgme-0.9 (from pkg app-crypt/gpgme-0.3.16) [blocks B ] =app-crypt/gpgme-0.3.16 (from pkg app-crypt/gpgme-0.9.0-r1) [ebuild N ] app-crypt/gpgme-0.3.16 +nls 0 kB How to solve this problem happening on a ~x86 system? Reproducible: Always Steps to Reproduce:
What is depending on gpgme-0.3.16? If its licq I've asked voxus to fix it back to 0.3.14-r1. Use the emerge --debug to give you what ties into these dependancies. I plan to remove gpgme-0.3.16 and migrate remaining packages to either gpgme-0.3.14 or 0.9.0+ if possible. All other versions will be removed.
Same issue, licq is not emerged. Need help :(
For me it works, when i disabled the "crypt" USE-Flag of licq-1.3.0_pre2 in /etc/portage/package.use echo "=net-im/licq-1.3.0_pre2 -crypt" >> /etc/portage/package.use But i hope someone has a real fix for this issue :)
Thanks! It seems to work! :)
depend =app-crypt/gpgme-0.3.14-r1 for licq. If you want to try the crypt support for licq. emerge =app-crypt/gpgme-0.3.14-r1 and tme emerge -O licq
Okay, emerge -O licq works with the USE-Flag crypt and gpgme 0.3.14-r1. Unfortunately emerge will fail to update world because it knows, that licq need another gpgme. Maybe somebody could change the most recent licq ebuild so that it depends on <app-crypt/gpgme-0.3.16 itchy ~ # emerge -upvtD world These are the packages that I would merge, in reverse order: Calculating world dependencies ...done! [blocks B ] >=app-crypt/gpgme-0.9 (from pkg app-crypt/gpgme-0.3.16) [nomerge ] x11-themes/licq-themes-0.0.1 [nomerge ] net-im/licq-1.3.0_pre2 +crypt +kde +ncurses +qt -socks5 +ssl [ebuild N ] app-crypt/gpgme-0.3.16 +nls 0 kB
I saw an update on http://www.licq.org: September 30, 2004 It has been over a year since the last stable release, but we are sure that you won't be disappointed with all the new changes! Licq 1.3.0 is now available for release! So 1.3.0 is now stable ;)
yep, i'm testing it now..
committed in portage thanks, everyone :-)
*** Bug 66004 has been marked as a duplicate of this bug. ***