On Wednesday, 16 January 2019 10:29:38 GMT Renzo Poddighe wrote:
> On Wed, Jan 16, 2019, at 11:29 AM, gentoo-user+h...@lists.gentoo.org wrote:
> > Somebody (and we hope it was you) has requested that the email address
> > be removed from the list.
> >
> > To confirm you want to do this, please se
On Wednesday, 16 January 2019 10:15:22 GMT Neil Bothwick wrote:
> On Wed, 16 Jan 2019 09:50:58 +, Peter Humphrey wrote:
> > This box acts as an emerge server for a 32-bit Atom. So I NFS-mount the
> > Atom's portage tree in a 32-bit chroot, build the packages it needs and
> > then emerge the pac
On Wed, Jan 16, 2019, at 11:29 AM, gentoo-user+h...@lists.gentoo.org wrote:
>
>
> Somebody (and we hope it was you) has requested that the email address
> be removed from the list.
>
> To confirm you want to do this, please send a message to
>
> which can usually be done simply by replying
On Wed, 16 Jan 2019 09:50:58 +, Peter Humphrey wrote:
> This box acts as an emerge server for a 32-bit Atom. So I NFS-mount the
> Atom's portage tree in a 32-bit chroot, build the packages it needs and
> then emerge the packages on the Atom.
>
> This morning I found something odd: the Atom wa
On Wednesday, 16 January 2019 09:50:58 GMT I wrote:
> This morning I found something odd: the Atom wanted to emerge perl 5.24,
> even though 5.26 was already present, so I got a long list of clashes.
I forgot to say that the emerge host had no trouble with this daily update;
just the client Atom
Hello list,
This box acts as an emerge server for a 32-bit Atom. So I NFS-mount the Atom's
portage tree in a 32-bit chroot, build the packages it needs and then emerge
the packages on the Atom.
This morning I found something odd: the Atom wanted to emerge perl 5.24, even
though 5.26 was alread
6 matches
Mail list logo
