private ppa page doesn't say what binaries are published therein

[Martin Pool]

example: https://launchpad.net/~canonical-ux/+archive/walled-garden?field.series_filter=

'apt-cache policy' from a client shows that this archive publishes the binary package ttf-ubuntu-font-family, but I cannot see that mentioned anywhere on the page, or anything linked from it. It only lists the sources.

[Martin Pool (mbp)]

This is pretty similar to bug 496862, and perhaps ought to be fixed together. But the specific difference I was talking about here is that for a public ppa I can click through to <https://launchpad.net/~bzr/+archive/daily/+packages> and eventually see what binaries it contains, whereas <https://launchpad.net/~canonical-ux/+archive/walled-garden/+packages> gives "Unauthorized" (and there's no link to it anyhow.) If I have access to the p3a is there any reason I shouldn't be able to see it's +packages?

[Julian Edwards (julian-edwards)]

Hi Martin

That's explicitly prevented because we don't want ordinary subscribers seeing all the build details. If you were an owner of a private PPA I'm pretty sure you wouldn't want your subscribers going in that page and finding old versions, build logs, etc. The +packages page is intended for developers and the +archive page for users.

We've not fixed bug 496862 yet because in the case of some packages, the list of installable binaries would be huge (the kernel for example) so we've procrastinated on that one while we come up with a decent way of presenting the data.

[Martin Pool (mbp)]

Fair enough.

Martin