On Sunday, 27 October 2019 13:21:04 GMT Peter Humphrey wrote: > On Sunday, 27 October 2019 15:11:56 GMT n952162 wrote: > > When I enter: > > sudo emerge =sys-apps/portage-2.3.69 > > > > I get the response: > > emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". > > > > but this version is listed on > > packages.gentoo.org/packages/sys-apps/portage as being an available > > Version > > > > https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2. > > 3. 69.ebuild > > > > I'm trying to emerge 2.3.69 because when I don't specify any version, > > emerge gives me this: > > > > The following keyword changes are necessary to proceed: > > ... > > > > =sys-apps/portage-2.3.67 ~amd64 > > > > and 2.3.67 isn't even listed as being available. > > What does eix tell you after 'emerge --sync && eix-update'?
I sync'ed this morning and sys-apps/portage-2.3.76 is the current stable version. A re-sync as Peter suggests ought to fix this problem. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
