| 1 |
On Sunday, 27 October 2019 15:11:56 GMT n952162 wrote: |
| 2 |
> When I enter: |
| 3 |
> |
| 4 |
> sudo emerge =sys-apps/portage-2.3.69 |
| 5 |
> |
| 6 |
> I get the response: |
| 7 |
> |
| 8 |
> emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". |
| 9 |
> |
| 10 |
> but this version is listed on |
| 11 |
> packages.gentoo.org/packages/sys-apps/portage as being an available Version |
| 12 |
> |
| 13 |
> https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3. |
| 14 |
> 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 |
> =sys-apps/portage-2.3.67 ~amd64 |
| 22 |
> |
| 23 |
> and 2.3.67 isn't even listed as being available. |
| 24 |
|
| 25 |
What does eix tell you after 'emerge --sync && eix-update'? |
| 26 |
|
| 27 |
-- |
| 28 |
Regards, |
| 29 |
Peter. |
Archives