On Monday 01 Aug 2016 10:03:53 John Blinka wrote:
> Glad to see that someone else has experienced the same thing, and I'm not
> going crazy (although some might argue this is hardly proof...)
No, but it'll do as a bit of evidence pro tem. :)
--
Rgds
Peter
On Sun, Jul 31, 2016 at 6:47 AM, Peter Humphrey
wrote:
>
> How is it possible for genlop's reported ETA to increase while its time
> spent so far also increases? Could the concurrent gnutls merging have
> affected it? Surely not.
I've noticed the same oddity recently while building a couple of
On Sunday 31 Jul 2016 18:52:23 Fernando Rodriguez wrote:
--->8
> Just out of curiosity what are the differences between the original genlop
> calculation and yours, and how long did it actually take? and what is the
> output of 'genlop -t '.
$ genlop -t gcc -f /mnt/rescue/var/log/emerge.log
usin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/31/2016 12:14 PM, Peter Humphrey wrote:
> On Sunday 31 Jul 2016 10:48:33 Fernando Rodriguez wrote:
>> On 07/31/2016 06:47 AM, Peter Humphrey wrote:
>>> I've just encountered something I can't explain. Can anyone here?
>>>
>>> ~ $ genlop -c -f /
On Sunday 31 Jul 2016 10:48:33 Fernando Rodriguez wrote:
> On 07/31/2016 06:47 AM, Peter Humphrey wrote:
> > I've just encountered something I can't explain. Can anyone here?
> >
> > ~ $ genlop -c -f /mnt/rescue/var/log/emerge.log
> > using logfile /mnt/rescue/var/log/emerge.log
> > Currently mer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/31/2016 06:47 AM, Peter Humphrey wrote:
> Hello list,
>
> I've just encountered something I can't explain. Can anyone here?
>
> ~ $ genlop -c -f /mnt/rescue/var/log/emerge.log
> using logfile /mnt/rescue/var/log/emerge.log
>
> Currently mer
Hello list,
I've just encountered something I can't explain. Can anyone here?
~ $ genlop -c -f /mnt/rescue/var/log/emerge.log
using logfile /mnt/rescue/var/log/emerge.log
Currently merging 281 out of 287
* net-libs/gnutls-3.3.24
current merge time: 1 minute and 44 seconds.
ETA
7 matches
Mail list logo
