'queue override' command scales at O(n^2) with the number of packages on the commandline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
William Grant |
Bug Description
When passing more than one package name to 'queue override' on the commandline, it appears that the override is executed on *all* packages, one time for *each* package listed in the command.
For instance, in the simple case of overriding two binary packages, the output looks like:
$ q -s dapper-security -Q new override -c main binary acpi-modules-
Initialising connection to queue new
Running: "override binary acpi-modules-
Overriding ubuntu/
-------
Overriding acpi-modules-
| * linux-source-
| N acpi-modules-
Overriding acpi-modules-
| * linux-source-
| N acpi-modules-
Overriding acpi-modules-
| * linux-source-
| N acpi-modules-
Overriding acpi-modules-
| * linux-source-
| N acpi-modules-
$
For packages such as the kernel which create literally hundreds of binary packages that need overrides when there's an ABI change, it of course makes it very inefficient to batch these up on a single commandline when this means a hundredfold speed penalty, whereas it would otherwise be quite nice to not have to spawn a separate subprocess (and db connection) for each package override...
Related branches
- Māris Fogels (community): Approve (code)
-
Diff: 82 lines (+16/-3)2 files modifiedlib/lp/soyuz/scripts/queue.py (+7/-2)
lib/lp/soyuz/scripts/tests/test_queue.py (+9/-1)
Changed in soyuz: | |
assignee: | nobody → William Grant (wgrant) |
status: | Triaged → In Progress |
Changed in soyuz: | |
status: | In Progress → Fix Committed |
milestone: | none → 10.08 |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
Steve, can you try the override web interface instead at /launchpad. net/ubuntu/ dapper/ +queue
https:/
It *may* be quicker until we fix this bug.
Thanks.