Package is blocking itself [SOLVED]

[jerann]

OK, first of all, please forgive my newbness - I'm still learning my way around Gentoo, and even GNU/ Linux itself. I haven't updated my system in a while, so I was going to to a deep update, but I've found that gnupg is blocking itself. When I run emerge --pretend --update --deep world, two lines reference gnupg:

[madisonicus]

When this happens, it's almost always portage saying you have to unmerge the old package before emerging the new. There can be many reasons, usually it's because something fundamental about the package has changed enough that simply upgrading isn't enough. The solution is simple. Just emerge -C the blocking package and try the emerge again.

More information here.

HTH,
m
_________________
Please add [SOLVED] to your message title if you feel that your question has been answered.
------
Intel Q9300 Core2 Quad * Gigabyte GA-EP35C-DS3R
Samsung x360
AMD64 x2 4200+ * TF7050-M2 * HTPC
ZOTAC ION A-U Mini-ITX * HTPC

[moocha]

Addendum: It's not blocking itself as such. Translated into English, that message says: "The GNUPG 2.0.1-r2 ebuild mandates that it can't be installed if there's already an installed GNUPG package older than or equal to 2.0.1. Your system has such an older GNUPG installed, therefore installation of GNUPG 2.0.1-r2 has been blocked."
_________________
Military Commissions Act of 2006: http://tinyurl.com/jrcto

"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
-- attributed to Benjamin Franklin

[jerann]

Well, I figured it was something simple, but I didn't figure on it being that simple. Thanks madisonicus - that fixed it right up. I'm not sure how I missed the "When Portage is Complaining..." section - that's quite helpful. Thanks again!

EDIT: Oop - I missed moocha's post. Yes, that makes much more sense - I assumed it would just upgrade it in a case like that. I guess that's what I get for assuming