On 15:41 Tue 01 Feb , Joshua Murphy wrote:
>
> The trick I've been using for... a couple years now, across various
> machines (no cron involved), is syncing one box that shares portage
> *and* my distfiles on nfs, portage R/O, distfiles R/W, then when it's
> done syncing and starts its own met
>From: Peter Humphrey
>On Tuesday 01 February 2011 20:43:43 BRM wrote:
>> And you're doing a typically manual process for updating all the
>> systems - update your server first, then any rsync clients. Fine &
>> dandy if that is your process - but it's not mine. I may update my
>> laptop twice as
On Tuesday 01 February 2011 20:43:43 BRM wrote:
> And you're doing a typically manual process for updating all the
> systems - update your server first, then any rsync clients. Fine &
> dandy if that is your process - but it's not mine. I may update my
> laptop twice as often as the other two, esp
On Monday 31 January 2011 22:26:20 BRM wrote:
> "emerge --sync" works fine for your _normal_ portage tree.
> But if you are running a mirror on a gentoo system that also needs
> its own copy of portage, then you really need to have two portage
> trees on the system. One portage tree is hosted by r
On 18:13 Mon 31 Jan , Dale wrote:
> Nils Holland wrote:
> >
> > In fact, what I always do is sync one of my machines with an official
> > Gentoo mirror via "emerge --sync", and then I just use rsync to
> > distribute the updated tree to all my other local machines as in:
> >
> > rsync --d
BRM wrote:
And you're doing a typically manual process for updating all the systems -
update your server first, then any rsync clients. Fine& dandy if that is your
process - but it's not mine. I may update my laptop twice as often as the other
two, especially if I want to play with some software
- Original Message
> From: Dale
> To: gentoo-user@lists.gentoo.org
> Sent: Tue, February 1, 2011 12:20:56 PM
> Subject: Re: [gentoo-user] Re: Emerge Problems...
>
> Neil Bothwick wrote:
> > On Tue, 1 Feb 2011 05:48:32 -0800 (PST), BRM wrote:
> >
>
On Tue, Feb 1, 2011 at 12:20 PM, Dale wrote:
> Neil Bothwick wrote:
>>
>> On Tue, 1 Feb 2011 05:48:32 -0800 (PST), BRM wrote:
>>
>>
>>>
>>> If the machine is not fast enough - mine is a PII 233 w/160 MB RAM,
>>> takes a while do to updates - then you really have to separate out what
>>> you are ho
Neil Bothwick wrote:
On Tue, 1 Feb 2011 05:48:32 -0800 (PST), BRM wrote:
If the machine is not fast enough - mine is a PII 233 w/160 MB RAM,
takes a while do to updates - then you really have to separate out what
you are hosting from what you are using. Otherwise you end up in the
situation
On Tue, 1 Feb 2011 05:48:32 -0800 (PST), BRM wrote:
> If the machine is not fast enough - mine is a PII 233 w/160 MB RAM,
> takes a while do to updates - then you really have to separate out what
> you are hosting from what you are using. Otherwise you end up in the
> situation that you have start
- Original Message
> From: Dale
> Nils Holland wrote:
> > On 21:35 Mon 31 Jan , Francesco Talamona wrote:
> >> On Monday 31 January 2011, BRM wrote:
> >>> I just wrote a new script last night, but I'm still not sure that all
> >>> of the parameters are correct
> >>>
> >>
Nils Holland wrote:
On 21:35 Mon 31 Jan , Francesco Talamona wrote:
On Monday 31 January 2011, BRM wrote:
I just wrote a new script last night, but I'm still not sure that all
of the parameters are correct
Why not something proven and reliable like "emerge --sync"?
On 21:35 Mon 31 Jan , Francesco Talamona wrote:
> On Monday 31 January 2011, BRM wrote:
> > I just wrote a new script last night, but I'm still not sure that all
> > of the parameters are correct
>
> Why not something proven and reliable like "emerge --sync"?
In fact, what I always do is syn
- Original Message
> From: Francesco Talamona
> On Monday 31 January 2011, BRM wrote:
> > I just wrote a new script last night, but I'm still not sure that all
> > of the parameters are correct
>
> Why not something proven and reliable like "emerge --sync"?
>
"emerge --sync" works
On Monday 31 January 2011, BRM wrote:
> I just wrote a new script last night, but I'm still not sure that all
> of the parameters are correct
Why not something proven and reliable like "emerge --sync"?
Ciao
Francesco
--
Linux Version 2.6.36-gentoo-r6, Compiled #2 SMP PREEMPT Mon Jan 3
On Sunday 30 January 2011, BRM wrote:
> A little while back my server ran out of hard disk space (due to a
> failed hard drive) and as a result my local portage mirror got
> destroyed. Well, I fixed there server - initially by just grabbing a
> new copy of portage like a new install since it was ju
Will do, thanks for your assistance!
On Sun, Jan 4, 2009 at 7:57 PM, Nikos Chantziaras wrote:
> Nikos Chantziaras wrote:
>
>> /etc/portage/packages.use:
>>
>> dev-java/sun-jdk -doc
>>
>
> Typo. It's "/etc/portage/package.use". You need to "emerge -N world"
> after that.
>
>
>
Nikos Chantziaras wrote:
/etc/portage/packages.use:
dev-java/sun-jdk -doc
Typo. It's "/etc/portage/package.use". You need to "emerge -N world"
after that.
James Stull wrote:
What is the best way to block this package?
On Sun, Jan 4, 2009 at 6:35 AM, pk wrote:
James Stull wrote:
I switched my eselect profile from a generic gentoo system to desktop.
Unfortunately I keep getting this error when I run "emerge -uDNav world"
I
tried it with the --
19 matches
Mail list logo
