The builds portlet in the DSPR page does not appear for unembargoed packages

[Julian Edwards]

Compare
https://edge.launchpad.net/ubuntu/gutsy/+source/wireshark/0.99.6rel-3ubuntu0.1
to
https://edge.launchpad.net/ubuntu/gutsy/+source/wireshark/0.99.6rel-3ubuntu0.2

The builds portlet is missing on the latter.

[Kees Cook (kees)]

I'd like to see the priority of this bumped -- researching build logs after a security release has been published is not easy currently. :)

[Julian Edwards (julian-edwards)]

By your command :)

But seriously, when bug 276020 is done you won't really need this as much I guess?

[Celso Providelo (cprov)]

Even via the API, P3A security builds/publications will be not reachable by ordinary users. This bug is about this scenario:

"John has just installed wireshark from the intrepid-security and he is curious to know if there was any warning while building it"

"John" wants to read the wireshark buildlogs, but he can't access the ~ubuntu-security PPA (not via the UI neither via the API, fortunately). Although, since wireshark was unembargoed, anyone has permission to view it.

The only problem is that we don't list the builds in the UI. DSSPR (not DSPR) uses the SPR portlet-builds (based in SPR.builds), which filters out builds that happened in other archives than PRIMARY and PARTNER.

[Michael Nelson (michael.nelson)]

RF 8189. The solution required two queries: the first gets all builds that were built in the context of a main archive (this includes new/failed builds), the second ensures we include builds built in other archives that have subsequently had binaries published in a main archive, the union of the two being returned.