1 |
Gavin Seddon posted <1137324262.8981.5.camel@linuxstation>, excerpted |
2 |
below, on Sun, 15 Jan 2006 11:24:22 +0000: |
3 |
|
4 |
> I ran 'emerge -euDv portage |
5 |
> ' and it fixed the problem. Thanks |
6 |
> D = downgrade, (Best version seems lower) |
7 |
|
8 |
Glad you got the problem fixed, but that downgrade thing is a |
9 |
misunderstanding. |
10 |
|
11 |
In actuality, -D = --deep. |
12 |
|
13 |
When you normally run -u/--update, portage will update the packages you |
14 |
merged directly, but not any dependencies such as libraries that were |
15 |
merged not because you asked to emerge them but because the packages you |
16 |
ASKED to merge required them. |
17 |
|
18 |
I see you use evolution as your mail client, so I'll use it for an |
19 |
example. If you have the spell USE flag set, evolution will require |
20 |
gnome-spell, so portage will automatically merge gnome-spell first, before |
21 |
merging evolution. emerge -u evolution or emerge -u world will check for |
22 |
updates for evolution, but won't check for updates for gnome-spell, unless |
23 |
a new version of evolution requires the update, or the old gnome-spell |
24 |
currently merged is removed for some reason. When the current |
25 |
gnome-spell version already merged doesn't meet the requirements any more, |
26 |
either because evolution changed and required a different version, or |
27 |
because the old version was masked/removed (say a security issue caused |
28 |
its masking and removal), portage will of course /then/ look again to find |
29 |
the best version it can to merge to meet the new requirements. |
30 |
|
31 |
--deep causes portage to check all the dependencies as WELL, not just the |
32 |
stuff you emerged by name. Thus, even when your current version of |
33 |
gnome-spell continues to satisfy evolution's dependencies, the --deep (or |
34 |
-D) will force portage to check for new versions of gnome-spell as well, |
35 |
and upgrade if one is found. |
36 |
|
37 |
Of course, if you use -e/--emptytree, you shouldn't need -D/--deep anyway, |
38 |
because if portage thinks the tree is empty -- that you don't have |
39 |
anything merged yet -- it will naturally merge the latest version it can, |
40 |
because you are telling it not to count the currently merged stuff. |
41 |
|
42 |
As for downgrading, that's the -u/--update vs. -U/--upgradeonly thing. |
43 |
Portage will by default downgrade you if it thinks you need to downgrade |
44 |
-- basically, if your current package is masked, because they found |
45 |
something badly wrong with it. -U causes portage to ONLY upgrade. It |
46 |
won't downgrade packages with -U, even if there's a security issue or |
47 |
something that caused the devs to mask the version you are currently |
48 |
using. That's why the -U option is **NOT** recommended. Still, it's |
49 |
there, just in case you WANT it to keep "broken" packages, for some reason. |
50 |
|
51 |
-- |
52 |
Duncan - List replies preferred. No HTML msgs. |
53 |
"Every nonfree program has a lord, a master -- |
54 |
and if you use the program, he is your master." Richard Stallman in |
55 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
56 |
|
57 |
|
58 |
-- |
59 |
gentoo-amd64@g.o mailing list |