On Mon, Oct 28, 2019 at 03:36:00PM +1100, Adam Carter wrote
> On Mon, Oct 28, 2019 at 3:23 PM Walter Dnes wrote:
>
> > I went 41 days without emerging (yeah, I know). Anyhow, emerge first
> > wants me to update portage, but I run into problems. Can I safely
> > unmerge gentoolkit and
On Mon, Oct 28, 2019 at 3:23 PM Walter Dnes wrote:
> I went 41 days without emerging (yeah, I know). Anyhow, emerge first
> wants me to update portage, but I run into problems. Can I safely
> unmerge gentoolkit and re-emerge it afterwards?
>
Its not part of @system, so should be fine.
I went 41 days without emerging (yeah, I know). Anyhow, emerge first
wants me to update portage, but I run into problems. Can I safely
unmerge gentoolkit and re-emerge it afterwards?
=
[i660][root][~] emerge --oneshot portage
Calculating
Howdy,
I subscribe to -dev and read things to get a heads up mostly. I noticed
a news item being started concerning consolekit and switching to
elogind. From my understanding it is similar to the difference of udev
and eudev in that it just pulls the code needed when not using systemd
and
Some messages to you could not be delivered. If you're seeing this
message it means things are back to normal, and it's merely for your
information.
Here is the list of the bounced messages:
- 188350
[2019-10-27 18:47] Dale
>
> part text/plain 30K
> Howdy,
Hi,
> I'm trying to do my weekly update. I use eudev but something seems to
> want plain udev and to remove eudev while at it. I have udev masked so
> emerge knows not to install it. This is what emerge spits out
Howdy,
I'm trying to do my weekly update. I use eudev but something seems to
want plain udev and to remove eudev while at it. I have udev masked so
emerge knows not to install it. This is what emerge spits out with the
-t option in use. Keep in mind, some options are in make.conf but the
Mick wrote:
> On Friday, 25 October 2019 18:01:57 BST Dale wrote:
>> Mick wrote:
>>> PS. In an ideal AI world, portage would know how much memory is necessary
>>> for a given package and would auto-adjust the number of jobs to minimise
>>> swapping given any amount of RAM. In an even more ideal
On Sun, 27 Oct 2019 11:20:20 -0400, Alan Grimes wrote:
> 1. Grub2 menu DOES NOT ACCEPT KEYBOARD INPUT!
>
> -- Upgraded my ram to 64gb, couldn't run memtest because grub2 is
> broken.
Try toggling the legacy USB setting in BIOS.
>
>
> 2. My current combination of Linux-Headers-5.2, kernel 5.2
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
Here are the issues I'm currently having.
1. Grub2 menu DOES NOT ACCEPT KEYBOARD INPUT!
-- Upgraded my ram to 64gb, couldn't run memtest because grub2 is broken.
2. My current combination of Linux-Headers-5.2, kernel 5.2 and nvidia
drivers is UNSTABLE and crashes X11 to command line when the
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
22 matches
Mail list logo
