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