Is this a genlop bug?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Is this a genlop bug?

Peter Humphrey-3
Hello list,

When I run "genlop -c" is it supposed to include the whole cat/pkg name in its
calculations, or just the pkgname? I saw this today:

$ genlop -c  
 Currently merging 8 out of 16
 * dev-lang/rust-1.29.1
       current merge time: 13 minutes and 38 seconds.
       ETA: 1 minute and 58 seconds.
$ genlop -t rust | grep second
       merge time: 29 minutes and 26 seconds.
       merge time: 4 seconds.
       merge time: 10 seconds.
       merge time: 32 minutes and 44 seconds.
$ genlop -t dev-lang/rust | grep second
       merge time: 29 minutes and 26 seconds.
       merge time: 32 minutes and 44 seconds.

This looks like a bug to me.

--
Regards,
Peter.




Reply | Threaded
Open this post in threaded view
|

Re: Is this a genlop bug?

Andrew Udvare

> On 2018-10-01, at 05:25, Peter Humphrey <[hidden email]> wrote:
>
> Hello list,
>
> When I run "genlop -c" is it supposed to include the whole cat/pkg name in its
> calculations, or just the pkgname? I saw this today:
>
> $ genlop -c  
> Currently merging 8 out of 16
> * dev-lang/rust-1.29.1
>       current merge time: 13 minutes and 38 seconds.
>       ETA: 1 minute and 58 seconds.
> $ genlop -t rust | grep second
>       merge time: 29 minutes and 26 seconds.
>       merge time: 4 seconds.
>       merge time: 10 seconds.
>       merge time: 32 minutes and 44 seconds.
> $ genlop -t dev-lang/rust | grep second
>       merge time: 29 minutes and 26 seconds.
>       merge time: 32 minutes and 44 seconds.
>
> This looks like a bug to me.

It is not a bug. The manpage says it takes name or category/name. In the former case it has to match anything named rust. There are two packages named exactly 'rust': dev-lang/rust and virtual/rust.

Andrew
Reply | Threaded
Open this post in threaded view
|

Re: Is this a genlop bug?

Arve Barsnes
On Mon, 1 Oct 2018 at 14:03, Andrew Udvare <[hidden email]> wrote:
> > On 2018-10-01, at 05:25, Peter Humphrey <[hidden email]> wrote:
> > This looks like a bug to me.
>
> It is not a bug. The manpage says it takes name or category/name. In the former case it has to match anything named rust. There are two packages named exactly 'rust': dev-lang/rust and virtual/rust.

The '-c' parameter doesn't (need to) take either name or category/name
so I don't see how this isn't a bug. Getting an ETA average for more
than one package and comparing it against the currently merging
package makes no sense.

Cheers,
Arve

Reply | Threaded
Open this post in threaded view
|

Re: Is this a genlop bug?

Peter Humphrey-3
On Monday, 1 October 2018 13:22:42 BST Arve Barsnes wrote:

> On Mon, 1 Oct 2018 at 14:03, Andrew Udvare <[hidden email]> wrote:
> > > On 2018-10-01, at 05:25, Peter Humphrey <[hidden email]> wrote:
> > > This looks like a bug to me.
> >
> > It is not a bug. The manpage says it takes name or category/name. In the
> > former case it has to match anything named rust. There are two packages
> > named exactly 'rust': dev-lang/rust and virtual/rust.
> The '-c' parameter doesn't (need to) take either name or category/name
> so I don't see how this isn't a bug. Getting an ETA average for more
> than one package and comparing it against the currently merging
> package makes no sense.

https://bugs.gentoo.org/667534 submitted.

--
Regards,
Peter.