From: Tim Allingham <deserted@westnet.com.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage inconsistency?
Date: Mon, 06 Aug 2007 01:13:46 +1000 [thread overview]
Message-ID: <1186326826.18701.0.camel@localhost> (raw)
In-Reply-To: <200708051632.36725.bo.andresen@zlin.dk>
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
On Sun, 2007-08-05 at 16:32 +0200, Bo Ørsted Andresen wrote:
> On Tuesday 17 July 2007 00:46:08 maxim wexler wrote:
> > So, emerge portage results in one package being
> > installed, portage, 61kb.
> >
> > emerge -u portage lines up 5 or 6 packages plus
> > portage, 18Mb.
> >
> > Went ahead and just did the one package, figuring
> > later I could do an emerge -u for the rest of it.
> >
> > But this is what happens:
> >
> > heathen@localhost ~ $ emerge -pv portage
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> > [ebuild R ] sys-apps/portage-2.1.2.9 USE="-build
> > -doc -epydoc (-selinux)" LINGUAS="-pl" 0 kB
> >
> > Total: 1 package (1 reinstall), Size of downloads: 0
> > kB
> >
> > What I expected.
> >
> > heathen@localhost ~ $ emerge -puv portage
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> >
> > Total: 0 packages, Size of downloads: 0 kB
> >
> > So why doesn't it list the upgrade part now?
>
> Because --update stops calculating deps when none of the specified targets
> need updating. Only --deep checks the consistency of all dependencies even
> when none of the targets need updating. You could argue it's a deficiency in
> portage (although well-known)..
>
meaning that an emerge -pvuD world/portage should show the upgrades
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-05 15:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 22:46 [gentoo-user] portage inconsistency? maxim wexler
2007-07-17 1:36 ` Александър Л. Димитров
2007-07-17 12:35 ` Iván Pérez Domínguez
2007-07-17 19:27 ` maxim wexler
2007-08-05 14:32 ` Bo Ørsted Andresen
2007-08-05 15:13 ` Tim Allingham [this message]
2007-08-05 15:20 ` Mark Shields
2007-08-05 16:33 ` Bo Ørsted Andresen
2007-08-06 8:45 ` Abraham Marín Pérez
2007-08-06 9:11 ` [gentoo-user] " Remy Blank
2007-08-06 9:59 ` Abraham Marín Pérez
2007-08-06 10:40 ` Remy Blank
2007-08-06 10:53 ` Abraham Marín Pérez
2007-08-06 10:57 ` Neil Bothwick
2007-08-06 9:17 ` [gentoo-user] " Neil Bothwick
2007-08-06 10:19 ` Abraham Marín Pérez
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=1186326826.18701.0.camel@localhost \
--to=deserted@westnet.com.au \
--cc=gentoo-user@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