1 |
On Sunday, 27 October 2019 13:21:04 GMT Peter Humphrey wrote: |
2 |
> On Sunday, 27 October 2019 15:11:56 GMT n952162 wrote: |
3 |
> > When I enter: |
4 |
> > sudo emerge =sys-apps/portage-2.3.69 |
5 |
> > |
6 |
> > I get the response: |
7 |
> > emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". |
8 |
> > |
9 |
> > but this version is listed on |
10 |
> > packages.gentoo.org/packages/sys-apps/portage as being an available |
11 |
> > Version |
12 |
> > |
13 |
> > https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2. |
14 |
> > 3. 69.ebuild |
15 |
> > |
16 |
> > I'm trying to emerge 2.3.69 because when I don't specify any version, |
17 |
> > emerge gives me this: |
18 |
> > |
19 |
> > The following keyword changes are necessary to proceed: |
20 |
> > ... |
21 |
> > |
22 |
> > =sys-apps/portage-2.3.67 ~amd64 |
23 |
> > |
24 |
> > and 2.3.67 isn't even listed as being available. |
25 |
> |
26 |
> What does eix tell you after 'emerge --sync && eix-update'? |
27 |
|
28 |
I sync'ed this morning and sys-apps/portage-2.3.76 is the current stable |
29 |
version. A re-sync as Peter suggests ought to fix this problem. |
30 |
-- |
31 |
Regards, |
32 |
|
33 |
Mick |