1 |
mr_L4N posted on Mon, 03 Oct 2016 10:42:27 +0200 as excerpted: |
2 |
|
3 |
> https://drive.google.com/file/d/0B3UY2_LU1HQOMlpmTGM4bTFzRDQ/view?usp=sharing |
4 |
|
5 |
> this works, |
6 |
|
7 |
Thanks, yes. |
8 |
|
9 |
Again with the disclaimer that I do kde not gnome and thus am unlikely to |
10 |
have a clue on gnome-specific issues, so the below is pretty general |
11 |
gentoo boilerplate, not really specific to your issue... |
12 |
|
13 |
The immediately obvious question is that given the problem appeared right |
14 |
after an update, did you do a revdep-rebuild and an emerge --depclean |
15 |
after your update? |
16 |
|
17 |
It's possible you need to rebuild something else against the newly |
18 |
installed package, and portage didn't catch it and do the rebuild |
19 |
automatically as the version deps for what you need to rebuild aren't yet |
20 |
that strict. Revdep-rebuild can catch and rebuild many such packages, tho |
21 |
it's gradually becoming less and less necessary as version deps are |
22 |
updated to include the previously missing deps information (only newer |
23 |
EAPIs allow specifying it properly, and particularly people on stable will |
24 |
likely still have a number of older packages that don't have the newer and |
25 |
stricter deps specified). |
26 |
|
27 |
Depclean simply tells portage to clean up any old packages that are no |
28 |
longer required by anything in @world but that haven't been uninstalled |
29 |
yet. As long as you run it regularly, you should have everything you want |
30 |
in @world and it won't clean up anything you obviously need, but if you |
31 |
have an install you've been updating for awhile without running depclean, |
32 |
be sure to do a --pretend or --ask first, and carefully check what it |
33 |
wants to remove, in case there's something in there you actually do want |
34 |
to keep. If so, you can add that to @world, and depclean won't try to |
35 |
remove it any longer. |
36 |
|
37 |
Also, do you do --deep updates, or not? Skipping --deep will mean less |
38 |
normally unnecessary updates to dependencies, but will occasionally miss a |
39 |
necessary one, if there's a mistake in the specified deps for a package. |
40 |
Be aware that if you don't normally do --deep and try it, you'll likely |
41 |
have quite a long list of updates. You can either just let them happen, |
42 |
or pick thru the list manually, updating anything that looks like it might |
43 |
be related to your problem, while leaving the rest alone. |
44 |
|
45 |
-- |
46 |
Duncan - List replies preferred. No HTML msgs. |
47 |
"Every nonfree program has a lord, a master -- |
48 |
and if you use the program, he is your master." Richard Stallman |