1 |
On Wed, 21 Nov 2018 07:27:23 +0000 |
2 |
Neil Bothwick <neil@××××××××××.uk> wrote: |
3 |
|
4 |
> On Wed, 21 Nov 2018 13:52:50 +1100, Zoltán Kócsi wrote: |
5 |
> [...] |
6 |
> > As per the "5 config files ..." bit, well, dispatch-conf and |
7 |
> > etc-update tell me that they have nothing to do, so I have no idea |
8 |
> > what 5 files need updating, to what and how to update them. |
9 |
> |
10 |
> find /etc/portage -name ._cfg\* |
11 |
> |
12 |
> Config files for updating start with ._cfg |
13 |
|
14 |
Thanks, I'll take a look. |
15 |
|
16 |
> The Gentoo Handbook and man portage are good starting points. |
17 |
|
18 |
I read them, but what I'm missing is the understanding of the database |
19 |
content that portage maintains and the exact interpretation of the files |
20 |
and directories in the /etc/portage tree. I.e. the magic behind the |
21 |
scenes. |
22 |
|
23 |
> This would appear to be your problem, you are trying to emerge version |
24 |
> 9999 of portage. Version 9999 usually refers to a git version, so not |
25 |
> usually desirable, especially for a critical system tool. So the first |
26 |
> step is to find out why portage wants version 9999. |
27 |
> |
28 |
> grep -r portage /etc/portage |
29 |
> |
30 |
> will tell you if you have set it for installation. Otherwise repeat |
31 |
> the emerge command with the -t option, which shows what is pulling in |
32 |
> a particular package. |
33 |
|
34 |
Thanks a lot, I will investigate that further. |
35 |
|
36 |
By the way, an other (probably dumb) question. At the end of the listing |
37 |
of the errors there is a complaint about certifi. |
38 |
|
39 |
The interesting thing is that the conflict refers to the exact same |
40 |
piece of code: certifi-2018.4.16:0/0::gentoo is scheduled for merge but |
41 |
it is already installed. So what's wrong with it? |
42 |
|
43 |
Best Regards, |
44 |
|
45 |
Zoltan |