Can't upload a source package with the same name and version of a binary package

[Steve Kowalik]

While uploading linux-restricted-modules-lpia 2.6.27-3.3, it was rejected for an odd reason. Investigating led us to checking that a linux-restricted-modules-lpia 2.6.27-3.3 binary package has existed, which confuses Soyuz. This shouldn't affect an upload of a source package.

[Celso Providelo (cprov)]

Existing binaries https://edge.launchpad.net/ubuntu/intrepid/lpia/linux-restricted-modules-lpia/ and the confusion when looking up the intrepid queue, https://edge.launchpad.net/ubuntu/intrepid/+queue?queue_state=3&queue_text=linux-restricted-modules-lpia

[Celso Providelo (cprov)]

As far as I can tell, there shouldn't be any problem in accepting sources with name & version matching existing binaries. However, if the source produces conflicting binaries they will fail to upload.

IMHO, they are clearly distinct problems, in this case, the right thing to do is to fix the queue lookup (IDistroSeries.getQueueItem) to allow the callsites to select source-only / binary-only scope.

[Colin Watson (cjwatson)]

Definitely a Soyuz bug - there are no client-side problems with having source and binary packages with the same name and version.

[Celso Providelo (cprov)]

RF 7351