Unauthorize to access to source publishing history in archive from a private build

Bug #1518275 reported by Łukasz Zemczak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

It's hard to find a good summary for this issue. The issue is: whenever a package has been built in some private PPA, LP API will not be able to get the latest source publication from that build. This is a bit troublesome as we're using getLatestSourcePublication() to get the binary -> source binding. Log from #launchpad-dev :

16:45 < sil2100> b = archive.getPublishedBinaries(binary_name='ca-certificates', version='20141019ubuntu0.15.04.1', exact_match=True)
16:45 < sil2100> b[0].build.getLatestSourcePublication()
16:45 < sil2100> I get a 401 - unauthorized
16:45 < sil2100> I just want to get the source package of a published binary - how can I be unauthorized?
16:49 < cjwatson> sil2100: so, that's a bit awkward - the build was actually off in the security PPA, and you're unauthorized because you can't see the source package publishing history *there*
16:50 < cjwatson> sil2100: can you file a bug about this? there are a couple of different plausible solutions and I want to consult with wgrant when he reappears

William Grant (wgrant)
tags: added: public-private-builds
Revision history for this message
Colin Watson (cjwatson) wrote :

https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/376459 solves a related problem and makes it possible to at least identify the source package version.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.