Queue tool requires direct DB access

[Colin Watson]

scripts/ftpmaster-tools/queue is one of the tools Ubuntu archive administrators use most often, yet it still requires an ssh login to a privileged account on ftpmaster. There is a UI, DistroSeries:+queue, but there are many situations where scripting is helpful to us. For example, when we run an auto-sync from Debian we want to go through shortly afterwards and accept all the new packages we chose to sync (since our auto-sync tool prompts us for each new source package, i.e. those not previously in Ubuntu, presenting all the relevant information not covered by Ubuntu's general trust of Debian's hygiene in accepting new packages). This can be done by hand using the web UI if we must, but it is clearly amenable to better automation.

Some of queue's capabilities are not currently exposed in the web UI, in particular overriding individual binaries in an upload. Julian has said that he considers this a bug in its own right (bug 828649), but that's a case where it would probably be easier to expose an API in the short term than to do yet another UI redesign; and, again, that's something I can imagine automated use cases for (e.g. syncing over the overrides for all of linux's zillion binary packages each time there's a new kernel API in the development release).

In general, I believe we make use of just about all the facilities provided by the queue tool in one way or another. I think the most straightforward approach here is just to provide a like-for-like replacement. We don't need the new API to have any particular stability guarantees, since the main consumers of it will be in ubuntu-archive-tools which isn't packaged and is just run out of a bzr branch whose users tend to keep it current, so exporting it only on devel with no plans to release it more formally should be fine. It also isn't necessary for the new API to follow the exact shape of the current data model, which I gather is considered problematic in various ways and best not exposed directly.

[Launchpad QA Bot (lpqabot)]

r15331 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15331) is part of this bug's fix.

[Colin Watson (cjwatson)]

My client is still distinctly rough, but it was enough to successfully reject and then accept a package in oneiric-proposed on qastaging.

[Launchpad QA Bot (lpqabot)]

r15537 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15537) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

r15545 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15545) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

r15555 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15555) is part of this bug's fix.

[Colin Watson (cjwatson)]

The read-only bits are mostly fine. The one thing I spotted is that there's no way to get an "info"-type summary of the custom files contained in an upload; but that's not a regression.

[Launchpad QA Bot (lpqabot)]

r15568 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15568) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

r15571 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15571) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

r15575 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15575) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

r15607 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15607) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

r15608 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15608) is part of this bug's fix.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r16052 (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/16052) by a commit, but not testable.