SPPH.getBuilds only returns builds in the same series

[Kees Cook]

The following packages show builds in the web interface, but not the LP API:

cloog-ppl
gcc-4.4
gcj-4.4
gcj-4.5
gcj-4.6
gmp
gmp4
mpclib
ppl

For example, https://launchpad.net/ubuntu/+source/gcc-4.4/4.4.6-2ubuntu1 shows the builds. Clicking on them shows them as having come from a PPA: https://launchpad.net/~ubuntu-toolchain-r/+archive/staging/+build/2451918

This is not visible in the LP API:

$ ./live-api
lp: <launchpadlib.launchpad.Launchpad object at 0x1ffde10>
ubuntu: https://api.launchpad.net/1.0/ubuntu
archive: https://api.launchpad.net/1.0/ubuntu/+archive/primary

series = ubuntu.getSeries(name_or_version='oneiric')
sources = archive.getPublishedSources(status='Published', distro_series=series, pocket='Release', exact_match=True, source_name='gcc-4.4')
print len(sources[0].getBuilds())
0

print len(sources[0].getPublishedBinaries())
93

[William Grant (wgrant)]

It's because it built in natty in the PPA, then was copied to oneiric. SPPH.getBuilds() only returns those with a matching series. This could possibly be regarded as a bug, but maybe not.

[Kees Cook (kees)]

On Mon, May 16, 2011 at 11:58:17PM -0000, William Grant wrote:
> It's because it built in natty in the PPA, then was copied to oneiric.
> SPPH.getBuilds() only returns those with a matching series. This could
> possibly be regarded as a bug, but maybe not.

Hm, what's the correct path to the builds via the API? (It shows up on the
web interface, so there must be logic somewhere...)

I would argue it's a bug given that the binaries are attached to the
record, just not the builds.

--
Kees Cook
Ubuntu Security Team

[William Grant (wgrant)]

There's no real correct path, unfortunately. The problem here is that getBuildsForSourceIds restricts the series... not sure why. I might delete the constraint and see which tests break.