From: Thomas Kahle <tom111@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about difference between emerge --update world and emerge vigra
Date: Thu, 25 Sep 2008 07:13:56 +0200 [thread overview]
Message-ID: <48DB1E14.3080305@gmx.de> (raw)
In-Reply-To: <384d42da0809242105k67b8e3feja376df615350a10c@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
~ > Then, revdep-rebuild display like this.
| [ebuild R ] media-libs/tiff-3.8.2-r5
| [ebuild R ] media-gfx/imagemagick-6.4.3.5
| [ebuild R ] media-libs/lcms-1.17
| [ebuild U ] media-libs/vigra-1.6.0 [1.5.0-r1]
| [ebuild R ] net-print/cups-1.3.8-r1
| [ebuild R ] x11-libs/gtk+-2.12.12
| [ebuild R ] app-text/ghostscript-gpl-8.63
| [ebuild R ] app-text/evince-2.22.2-r1
| [ebuild R ] media-gfx/gthumb-2.10.9
|
|
~ > But there is no "vigra" in result of "emerge -p --update world"(with
| --deep also).
| Of course, it still shows flag "U" if I do "emerge -p vigra"
|
| What is difference with emerge --update world and emerge vigra?
| And how can I update all new package without exceptions?
I am also curious to know why portage just "forgets" to update certain
packages. What I used to do to find them is a plain
eix -I | grep "\[U\]"
which just greps for the pattern [U] marking an upgradeable package.
Then you can format this list and run
emerge -1 `insert packagelist here`
The -1 is important to not register these packages in your world file,
which you probably don't wont for some package that only is a dependency.
Still, I would like to know how this happens...
hth
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjbHhQACgkQrpEWPKIUt7MaBwCghPThHp8lCQbfQyvSG/UwaYN+
zgsAmgL3W8mcNfvjEJZxc+aUKTeNTLX1
=luJw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-09-25 5:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 4:05 [gentoo-user] Question about difference between emerge --update world and emerge vigra SOrCErEr
2008-09-25 5:13 ` Thomas Kahle [this message]
2008-09-25 6:16 ` Volker Armin Hemmann
2008-09-25 5:24 ` Marc Joliet
2008-09-25 6:24 ` Alan McKinnon
2008-09-25 9:54 ` SOrCErEr
2008-09-25 10:12 ` Vladimir Rusinov
2008-09-25 10:26 ` Alan McKinnon
2008-09-26 3:56 ` SOrCErEr
2008-09-25 10:23 ` Neil Bothwick
2008-09-25 10:27 ` Daniel Pielmeier
2008-09-25 15:08 ` [gentoo-user] " James
2008-09-25 15:29 ` Neil Bothwick
2008-09-25 15:51 ` Daniel Pielmeier
2008-09-25 18:32 ` James
2008-09-29 20:33 ` Daniel Pielmeier
2008-09-30 11:28 ` Paul Stear
2008-09-30 12:32 ` Daniel Pielmeier
2008-09-25 20:15 ` Alan McKinnon
2008-09-25 20:55 ` Paul Hartman
2008-09-25 21:43 ` Neil Bothwick
2008-09-25 21:59 ` Alan McKinnon
2008-09-25 22:53 ` Neil Bothwick
2008-09-25 15:51 ` [gentoo-user] " Hilco Wijbenga
2008-09-25 20:38 ` Alan McKinnon
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=48DB1E14.3080305@gmx.de \
--to=tom111@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