From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Gnupg doesn't build
Date: Mon, 6 Nov 2006 17:24:57 +0000 [thread overview]
Message-ID: <20061106172457.37d64c04@hactar.digimed.co.uk> (raw)
In-Reply-To: <454F6BB0.90108@ercbroadband.org>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Mon, 06 Nov 2006 12:06:56 -0500, Mark Haney wrote:
> >> octavian ~ # emerge -u gnupg
> >> Calculating dependencies... done!
> >> >>> Auto-cleaning packages...
> >>
> >> >>> No outdated packages were found on your system.
> >>
> >>
> >> * GNU info directory index is up-to-date.
> >>
> >> And it never gets upgraded. Has anyone else seen this?
> >>
> >
> > Yeah, I get this on every package that's already up-to-date ;)
> >
> >
> Yeah well that's not what portage says. (And I probably should have
> explained a bit deeper. It was a LONG weekend.)
>
> [ebuild U ] [1.4.5] USE="-X* -bindist%
> -usb*"
>
> That's what I have showing up in portage.
gnupg is slotted, and the highest version slot is up to date. try
emerge --oneshot =app-crypt/gnupg-1.4.5-r2
--
Neil Bothwick
"There's more to life than sex, beer and computers.
Not a lot more admittedly..."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-06 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 16:56 [gentoo-amd64] Gnupg doesn't build Mark Haney
2006-11-06 16:55 ` Daniel Gryniewicz
2006-11-06 18:00 ` Christoph Mende
2006-11-06 17:06 ` Mark Haney
2006-11-06 17:24 ` Neil Bothwick [this message]
2006-11-07 1:31 ` [gentoo-amd64] coreutils-6.4 - cannot install Mauro Maroni
2006-11-07 1:36 ` [gentoo-amd64] coreutils-6.4 - cannot compile Mauro Maroni
2006-11-07 8:39 ` [gentoo-amd64] " Duncan
2006-11-08 23:25 ` Mauro Maroni
2006-11-09 10:51 ` Duncan
2006-11-11 20:54 ` Mauro Maroni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061106172457.37d64c04@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox