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