public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Александър Л. Димитров" <aleks_d@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage inconsistency?
Date: Tue, 17 Jul 2007 03:36:07 +0200	[thread overview]
Message-ID: <20070717013607.GB23906@brmbr> (raw)
In-Reply-To: <548133.69625.qm@web31706.mail.mud.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

Hello Maxim

On 15:46 Mon 16 Jul, maxim wexler wrote:
> At tail of emerge --sync its says now emerge portage.

Yes, it does that every time there is a new portage version available.
 
> emerge -u portage lines up 5 or 6 packages plus
> portage, 18Mb.
 
from the emerge manpage:

"--update (-u)
      Updates  packages  to  the  best version available, which may not always be the
      highest version number due to masking for testing and development.   This  will
      also  update direct dependencies which may not be what you want.  Package atoms
      specified on the command line are greedy, meaning  that  unspecific  atoms  may
      match multiple installed versions of slotted packages."

> So why doesn't it list the upgrade part now?

If you look carefully at the first line 'emerge -pv portage' gives you,
you will notice that it says `[ebuild   R   ] sys-apps/portage'. The `R'
is for `Rebuild' - as your portage is already at the latest version
emerge wants to rebuild it. If you use the -u flag it just searches for
updates, finds none and hence does not suggest any installation.

I suggest you should read throgh emerge(1) and portage(5) mapages and
also read the online docs in the handbook to get familiar with the
portage system.


Regards,
	Aleks

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-17  2:15 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 ` Александър Л. Димитров [this message]
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
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=20070717013607.GB23906@brmbr \
    --to=aleks_d@gmx.de \
    --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