[01:51] <mwhudson> sooo... recipe builds build the source package with dpkg-source -I which means .a files get excluded
[01:51] <mwhudson> is there any work around for that?
[07:56] <wgrant> mwhudson: That seems like a feature :)
[08:51] <mwhudson> wgrant: it was mightily confusing is what it was
[08:51] <mwhudson> wgrant: the .a file was input data for atest
[08:52] <wgrant> Ah, heh.
[08:52] <wgrant> Hmm
[16:36] <Saviq> wgrant: #1754404 #1754405 #1754406
[16:36] <Saviq> no mup? ;P
[16:37] <wgrant> Saviq: I tried them all a while ago :)
[16:37] <wgrant> Thanks.
[16:37] <wgrant> s/tried/triaged/
[16:37] <Saviq> d'uh... I only just filed them, man :P
[16:37] <wgrant> I'm behind you :)
[16:38]  * Saviq doesn't even turn back
[16:45] <jonathon> i'm testing out a Private Project on qastaging.launchpad.net; how do i add a PPA to a private project? link to "P3As" is a 404 on https://help.launchpad.net/Teams/CreatingAndRunning#Private_.28proprietary.29_teams
[16:47] <cjwatson> Projects and PPAs aren't associated things
[16:47] <cjwatson> PPAs (private or otherwise) are associated with people or teams, not with projects
[16:49] <cjwatson> I've removed the dead link
[16:49] <cjwatson> wait, no I haven't.  done now
[16:50] <jonathon> ah, ok, so i've got a Team, and that Team has a PPA - and now I've made the team Private i can't see it when not logged in. Nice, thank you.
[16:50] <cjwatson> right, that's the general idea
[16:50] <jonathon> is it possible to add authentication to a private team's PPA?
[16:52] <jonathon> and does a private team require a commercial subscription?
[16:52] <jonathon> (sorry for all the questions - if i should email commercial@launchpad just say)
[16:54] <cjwatson> jonathon: what sort of authentication do you mean?
[16:54] <jonathon> i remember some years ago some commercial software was made available via PPAs which required a username/password
[16:54] <jonathon> (that might be authorisation rather than authentication)
[16:55] <cjwatson> jonathon: Yes, you should see "Manage access" on the private PPA's web UI for that
[16:56] <jonathon> (looking...)
[16:57] <cjwatson> jonathon: And yes, making a team private requires either admin permissions or a commercial subscription
[16:57] <cjwatson> That's true of Launchpad's privacy features in general
[16:57] <jonathon> ah, i have to create the PPA _after_ making the project private, then the "Manage access" option appears
[16:57] <jonathon> that's great thank you
[16:57] <jonathon> :)
[16:58] <cjwatson> It's also possible for an admin to make an existing PPA private provided that it's never had anything published to it, but yes
[16:59] <cjwatson> Usually easier to just create it under a private team to start with
[17:00] <jonathon> yup yup
[17:03] <jonathon> OK, cool, I think this should work. Thanks cjwatson :)
[17:03] <cjwatson> cool
[21:15] <ipmb> Any workarounds for GPG key imports timing out? https://bugs.launchpad.net/launchpad/+bug/1753019
[21:15] <ubot5`> Ubuntu bug 1753019 in Launchpad itself "Cannot import gpg key - Timeout" [Undecided,New]