'queue override' command scales at O(n^2) with the number of packages on the commandline

[Steve Langasek]

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-2.6.15-52-386-di acpi-modules-2.6.15-52-amd64-generic-di
Initialising connection to queue new
Running: "override binary acpi-modules-2.6.15-52-386-di acpi-modules-2.6.15-52-amd64-generic-di"
Overriding ubuntu/dapper-security (NEW) 2/3
---------------------------------------------------------------------------
Overriding acpi-modules-2.6.15-52-amd64-generic-di_2.6.15-52.67 (main/debian-installer/EXTRA)
         | * linux-source-2.6.15/2.6.15-52.67 Component: main Section: devel
         | N acpi-modules-2.6.15-52-amd64-generic-di/2.6.15-52.67/amd64 Component: main Section: debian-installer Priority: EXTRA
Overriding acpi-modules-2.6.15-52-386-di_2.6.15-52.67 (main/debian-installer/EXTRA)
         | * linux-source-2.6.15/2.6.15-52.67 Component: main Section: devel
         | N acpi-modules-2.6.15-52-386-di/2.6.15-52.67/i386 Component: main Section: debian-installer Priority: EXTRA
Overriding acpi-modules-2.6.15-52-amd64-generic-di_2.6.15-52.67 (main/debian-installer/EXTRA)
         | * linux-source-2.6.15/2.6.15-52.67 Component: main Section: devel
         | N acpi-modules-2.6.15-52-amd64-generic-di/2.6.15-52.67/amd64 Component: main Section: debian-installer Priority: EXTRA
Overriding acpi-modules-2.6.15-52-386-di_2.6.15-52.67 (main/debian-installer/EXTRA)
         | * linux-source-2.6.15/2.6.15-52.67 Component: main Section: devel
         | N acpi-modules-2.6.15-52-386-di/2.6.15-52.67/i386 Component: main Section: debian-installer Priority: EXTRA
$

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...