| 1 |
Okay, I'm working on that, but apparently, the *emerge --sync* I did a |
| 2 |
few minutes ago left this link dangling: |
| 3 |
|
| 4 |
lrwxrwxrwx 1 root root 59 Jan 23 2018 make.profile -> |
| 5 |
../../usr/portage/profiles/default/linux/amd64/13.0/desktop |
| 6 |
|
| 7 |
The contents of //usr/portage/profiles/default/linux/amd64////is now: |
| 8 |
|
| 9 |
$ lf /usr/portage/profiles/default/linux/amd64/ |
| 10 |
17.0/ 17.1/ eapi package.use.mask parent |
| 11 |
|
| 12 |
Is my system now killed? |
| 13 |
|
| 14 |
|
| 15 |
On 10/27/19 15:10, Mick wrote: |
| 16 |
> On Sunday, 27 October 2019 16:02:53 GMT n952162 wrote: |
| 17 |
>> But ~amd64 means that it's unstable. I want to use a stable version of |
| 18 |
>> portage. |
| 19 |
>> |
| 20 |
>> That's why I went to 2.3.69 |
| 21 |
> I beg your pardon, I copied the portage version from the title of your post |
| 22 |
> erroneously. |
| 23 |
> |
| 24 |
> Let me start again: |
| 25 |
> |
| 26 |
> sys-apps/portage-2.3.76 |
| 27 |
> |
| 28 |
> is the *current* stable version of portage, irrespective of what your present |
| 29 |
> state of portage tree, which is out of sync with the mirrors, thinks. |
| 30 |
> |
| 31 |
> The way forward is to mark sys-apps/portage-2.3.76 as ~amd64 *temporarily* |
| 32 |
> only, then emerge it, then re-sync and finally unmark sys-apps/portage-2.3.76 |
| 33 |
> as ~amd64 in your /etc. |
| 34 |
> |
| 35 |
> Following a resync your local tree will be brought up to date and portage will |
| 36 |
> no longer require further updates, since you will have installed the latest |
| 37 |
> stable version (as of this morning at least). |
| 38 |
> |
| 39 |
>> (Sorry, Mick, for the private msg - I always forget that thunderbird |
| 40 |
>> replies directly, and that I have to re-enter the list every time) |
| 41 |
> No problem. :-) |
| 42 |
> |
Archives