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