> Out of interest, why? If the server only syncs once per week, you *know*
> that nothing will change as far as the client (i.e. desktop) is
> concerned 6 out of 7 of the times it syncs? Seems a waste?
No reason at all - just set one up a few weeks after the first and didn't
think. And of course i
Paul Sobey wrote:
I have my server --sync every Friday
evening, and my desktop was syncing against that on a daily basis. Thanks
for your help, that was driving me nuts.
Paul
Out of interest, why? If the server only syncs once per week, you *know*
that nothing will change as far as the cl
> Daniel Pielmeier wrote:
>> In case of the timestamp issue i think it is a bug [1]. I think portage
>> should first check the timestamps and if they are different it should
>> delete the cache!
>
> Interesting idea - I've been running eix-sync in my crontab. Perhaps
> that hasn't been updating the
Daniel Pielmeier wrote:
Paul Sobey schrieb:
For the last couple of weeks I've noticed that emerge -puv world takes
an absolute age on my machine (currently at 5 mins and counting),
while the cpu gows to 100%. The little emerge rotator bar that spins
while it calculates dependencies moves extre
Paul Sobey schrieb:
For the last couple of weeks I've noticed that emerge -puv world takes
an absolute age on my machine (currently at 5 mins and counting), while
the cpu gows to 100%. The little emerge rotator bar that spins while it
calculates dependencies moves extremely slowly. Is there any
For the last couple of weeks I've noticed that emerge -puv world takes
an absolute age on my machine (currently at 5 mins and counting), while
the cpu gows to 100%. The little emerge rotator bar that spins while it
calculates dependencies moves extremely slowly. Is there any known bug
that caus
6 matches
Mail list logo
