queue tool can't filter on source package

Bug #59281 reported by Adam Conrad
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

It would be nice if "queue info linux-source-2.6.17" actually showed me all 5 queue items relating to the linux-source-2.6.17 source package, rather than the one (i386) build that produced a binary by that name.

Tags: lp-soyuz
Revision history for this message
Celso Providelo (cprov) wrote :

Sorry, which "all 5" do you mean ?

Currently there is only 2, the source and the i386 binary.

{{{
queue info linux-source-2.6.17/2.6.17-7.20 -Q done
...
   90770 | S- | linux-source-2.6.17 | 2.6.17-7.20 | 14 hours
         | * linux-source-2.6.17/2.6.17-7.20 Component: main Section: devel
   90837 | -B | linux-source-2.6.17 | 2.6.17-7.20 | 7 hours 40 minutes
...
}}}

Why were they in NEW, btw ?

Changed in soyuz:
status: Unconfirmed → Needs Info
Revision history for this message
Adam Conrad (adconrad) wrote :

Oh, they were all in NEW because of a kernel ABI bump, producing new binaries. They've since all been processed, of course. Your example above still hilights the problem I'm referring to, however:

If I pick a random package that appears in all the binary uploads (say, linux-libc-dev), I get filter returns for all the binary uploads. If I filter on linux-source-2.6.17, I get the source package, and the one binary upload that produced a binary package by that name (I would expect to get all the binary uploads for the source package "linux-source-2.6.17")

Revision history for this message
Celso Providelo (cprov) wrote :

Uhm, I see what you mean...

No, I doesn't work like that, the name filter works on produced binarypackagenames when dealing with builds (QueueBuild).

 You get the i386 because it builds an arch-indep doc with this name.

Do think we should change ? It should not be difficult to joins over the Build>SPR>SPN, if you think it's worth.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Soyuz because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.