Summary: | cryptplug 0.3.16-r1 blocks gpgme update | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jurek Bartuszek (RETIRED) <jurek> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | sascha-gentoo-bugzilla |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jurek Bartuszek (RETIRED)
2004-11-06 04:10:41 UTC
Please read the bugzilla product descriptions, this is NOT a bugzilla problem. Problems regarding ebuilds are not bugzilla problems? Well, I'm confused. do not use gpgme-0.3.16 Use 0.3.14-r1 for old version programs and 0.9.0+ for newer programs Both can be installed because they are on different slots. Please include emerge --deubug -u --deep world -output to determine what is requireing 0.3.16. I never said emerge wants to install gpgme-0.3.16... After doing emerge sync today, emerge -pvuD world doesn't show the new gpgme as a blocker. It will install it in a new slot - as you said. I think that the problem has been fixed. Manually unmerging "=gpgme-0.3.14" seems to "fix" this problem. Hm... unmerging 0.3.14, emerging 0.9.x and then emerging 0.3.14 fixes the problem, I suppose... can you confirm? |