On Sun, 27 Oct 2019 17:37:53 +0100, n952162 wrote:
> Okay, I'm working on that, but apparently, the *emerge --sync* I did a
> few minutes ago left this link dangling:
>
> lrwxrwxrwx 1 root root 59 Jan 23 2018 make.profile ->
> ../../usr/portage/profiles/default/linux/amd64/13.0/desktop
Use
Okay, I'm working on that, but apparently, the *emerge --sync* I did a
few minutes ago left this link dangling:
lrwxrwxrwx 1 root root 59 Jan 23 2018 make.profile ->
../../usr/portage/profiles/default/linux/amd64/13.0/desktop
The contents of //usr/portage/profiles/default/linux/amd64is
Please don't top-post in this group.
On Sunday, 27 October 2019 16:44:28 GMT n952162 wrote:
> On 10/27/19 15:40, Peter Humphrey wrote:
> > On Sunday, 27 October 2019 16:03:45 GMT n952162 wrote:
> >> On 10/27/19 14:21, Peter Humphrey wrote:
> >>> What does eix tell you after 'emerge --sync &&
$ eix -e portage
[?] sys-apps/portage
Available versions: *2.3.6 *2.3.8 ~*2.3.13 *2.3.13-r1 ~*2.3.14
~*2.3.16 *2.3.19-r1 ~*2.3.20 ** {build doc epydoc +ipc
+native-extensions python_targets_pypy python_targets_python2_7
python_targets_python3_4 python_targets_python3_5
On Sunday, 27 October 2019 16:03:45 GMT n952162 wrote:
> On 10/27/19 14:21, Peter Humphrey wrote:
> > What does eix tell you after 'emerge --sync && eix-update'?
>
> * To update portage, run 'emerge --oneshot portage' now.
No, that's not from eix; it's from portage.
Now that you've updated
On 10/27/19 14:21, Peter Humphrey wrote:
What does eix tell you after 'emerge --sync && eix-update'?
* To update portage, run 'emerge --oneshot portage' now.
Right. But I can't --sync.
But beyond that, why does emerge say there are no ebuilds when there are?
On 10/27/19 14:32, Mick wrote:
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
On Sunday, 27 October 2019 16:02:53 GMT n952162 wrote:
> But ~amd64 means that it's unstable. I want to use a stable version of
> portage.
>
> That's why I went to 2.3.69
I beg your pardon, I copied the portage version from the title of your post
erroneously.
Let me start again:
But ~amd64 means that it's unstable. I want to use a stable version of
portage.
That's why I went to 2.3.69
(Sorry, Mick, for the private msg - I always forget that thunderbird
replies directly, and that I have to re-enter the list every time)
On 10/27/19 14:48, Mick wrote:
On Sunday, 27
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".
> >
> >
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
>
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
12 matches
Mail list logo
