Hello, Matti. On Sun, Nov 15, 2015 at 01:15:16PM +0200, Matti Nykyri wrote: > > On Nov 15, 2015, at 13:01, Alan Mackenzie <a...@muc.de> wrote:
> >> Well it's not. It just checks all the manifests and complains about > >> errors. It doesn't affect the building of 1.23.1-r1. > Ok. I must be using some different switch then. > > Ah, OK. But it causes emerge to bail out, so never gets round to > > building 1.23.1-r1. > >> If I were you I'ld download the latest portage snapshot. That should > >> take care of any remaining issues. Is your portage upto date? I deleted my /usr/portage (with the exception of /usr/portage/distfiles), and ran emerge --sync again. I get precisely the same error message, still. > > I'd just synched my portage tree immediately before attempting the build. > > I'll try again tomorrow, in the hope everything will have been sorted out > > by then. > Syncing and getting a new snapshot is a bit different. With a snapshot you > get a new clean start. Download it and unpack. > After that check that your portage package is upto date (emerge -av portage). Yes, my portage is fully up to date. I think the Gentoo maintainers haven't fixed this problem, yet. > -- > -Matti -- Alan Mackenzie (Nuremberg, Germany).
