| 1 |
On Tuesday 25 April 2006 12:51, Mick wrote: |
| 2 |
> I only have a couple of minutes so I apologise for not writing a |
| 3 |
> complete answer. FWIW the gpg-agent was hard masked (yesterday?) and |
| 4 |
> just adding it to your /etc/portage/package.keywords won't work. You |
| 5 |
> need to use package.mask instead. |
| 6 |
> |
| 7 |
> However, I'm not sure why the hard masking was put in place - there |
| 8 |
> may be a good reason to stop using gpg-agent and instead switch to |
| 9 |
> another package. What should we use instead guys? |
| 10 |
|
| 11 |
# emerge -vp gpg-agent |
| 12 |
|
| 13 |
These are the packages that would be merged, in order: |
| 14 |
|
| 15 |
Calculating dependencies |
| 16 |
!!! All ebuilds that could satisfy "gpg-agent" have been masked. |
| 17 |
!!! One of the following masked packages is required to complete your request: |
| 18 |
- app-crypt/gpg-agent-1.9.19 (masked by: package.mask, ~x86 keyword) |
| 19 |
# Stefan Schweizer <genstef@g.o> (23 Apr 2005) |
| 20 |
# Please use app-crypt/gnupg-1.9.* now |
| 21 |
|
| 22 |
- app-crypt/gpg-agent-1.9.18 (masked by: package.mask, ~x86 keyword) |
| 23 |
|
| 24 |
So: |
| 25 |
|
| 26 |
# emerge -Cv gpg-agent |
| 27 |
# emerge -va gnupg |
| 28 |
|
| 29 |
-- |
| 30 |
Bo Andresen |
Archives