[15:40] <Robe> how long should a publish take after a build completed successfully?
[15:41] <Robe> currently waiting for https://launchpad.net/~robe/+archive/ubuntu/bareos/+packages
[15:42] <cjwatson> Robe: 10-15 minutes would be reasonably typical
[15:42] <cjwatson> There are a lot of PPAs :-)
[15:42] <Robe> oh, ok!
[15:42] <cjwatson> It doesn't seem stuck or anything.
[15:43] <Robe> the build queue was rather empty
[15:43] <cjwatson> The build queue's not relevant to publication time
[15:43] <Robe> *nods*
[15:43] <Robe> the publication worker doesn't have a public visible queue, does it?
[15:43] <cjwatson> And the build queue's usually empty now, but that just reflects having a lot of hardware on that end of things
[15:44] <cjwatson> No
[15:44] <Robe> heh
[15:44] <Robe> and now the publisher is backlogged till high heaven? :)
[15:44] <cjwatson> Not particularly worse than before, it's just not scalable so hasn't received the same treatment
[15:44] <Robe> and thanks to all the people maintaining ppa - helps me keep my sanity
[15:44] <cjwatson> You're welcome :)
[19:49] <smithy> I have a question for a private ppa (I have a commerical subscription) anyone on?
[19:49] <cjwatson> I have only limited access to such things, but I can try
[19:50] <smithy> I am trying to build my source code on launchpad and have sucessfully built but I'm not sure how to only show the debian while hiding the source code
[19:50] <smithy> is this possible?
[19:51] <cjwatson> You mean that you don't want even people with access to the private archive to be able to see the non-packaging parts of the source?
[19:52] <smithy> yes, we want to be able to have people download and install the binary (source can be built from launchpad) to test it out but we are still working out the policies for the source code
[19:52] <cjwatson> The only way to do that would be to compile the source outside of Launchpad and build a "source" package for upload to LP that contains only pre-built binaries.
[19:53] <smithy> hmmm, I was trying that but launchpad does not like only binaries being uploaded, would there be another command line than "debuild -S -sa"?
[19:54] <cjwatson> Or, I suppose, compile the source in one private PPA in Launchpad, download the resulting binaries, and reupload them to another private archive in fake source packages.
[19:54] <cjwatson> Alternatively you could build in a private PPA with very limited permissions and then manage the distribution yourself.
[19:54] <teward> smithy: correct me if i'm wrong, but if that error shows that's because you uploaded binary .deb files, not the source packages?
[19:54] <cjwatson> You can't upload .debs directly - you must use debuild -S or similar - but you can stuff binaries into a source package.
[19:54] <teward> i think what cjwatson suggests is a NEW source package containing the compiled binaries separately
[19:55] <cjwatson> And then have a trivial source package whose debian/rules just copies the binaries into the right places
[19:55] <teward> ^ that
[19:55] <dobey> smithy: is the source code not also hosted on launchpad?
[19:55] <teward> so, foo.exe is packaged into a source package, the debian/rules is trivial ad directs the install
[19:55] <teward> but the source package contains only the compiled final-product executables, NOT the actual source code
[19:56] <teward> and it is that source package that would be uploaded
[19:56] <cjwatson> It might be easier to manage the distribution independently, if you already have working real source packages.
[19:57] <cjwatson> Very-private PPA to do the actual build, and then you can slurp down the resulting binaries and put them on your own website.
[19:57] <smithy> Ah I see, that would probably be best for right now and the source code is hosted on launchpad (my company bought a subscription). Funny enough how I got it to work was to have the rules files use our build scripts and then copy the binaries into its respective place
[19:57] <smithy> but I just couldn't find the options to make private PPAs
[19:57] <smithy> but I will definitely try uploading only the binary files and see what happens, it's just tricky since there are quite a bit of shared objects that the binary depends on
[19:58] <smithy> yes I put the source code on launchpad.net/vipa
[19:58] <cjwatson> Yeah, that's why I'm suggesting independent distribution as probably a lot less work for you.
[19:58] <dobey> smithy: it seems weird to me that you'd want to not have the source debs have source in that case. the people who can access the ppa can already access the source if it's also hosted on launchpad.
[19:58] <dobey> but *shrug* :)
[19:58] <cjwatson> There is no way to do separate access control on source vs. binaries within the same PPA: you get either or both.
[19:58] <cjwatson> dobey: That's not necessarily true with a private PPA.
[19:59] <dobey> oh, right. i forgot the subscriptions were separate from teams.
[19:59] <smithy> how do you obtain a private ppa? I tried searching and the docs refer to contacting through #launchpad
[19:59] <smithy> is there a place to request one? I could not find the options
[20:00] <smithy> the only reason we host on launchpad is so we can build the deb files for people to download (I figured it's a security reason). We use git internally.
[20:00] <cjwatson> (Launchpad has git support now)
[20:01] <smithy> yeah I saw but we just want an easy way for people to download only our binaries for now until we work out the source code details
[20:01] <smithy> but it seems like a ppa with just the binary will suffice
[20:03] <cjwatson> Any PPA created for a private team will be private; for other cases, contact commercial@launchpad.net
[20:05] <smithy> I go to my profile and select "create a new ppa" and that will be private? I tried that and people can still add that repository, I could be missing something though
[20:05] <cjwatson> Make sure you've never published anything to the PPA you want to make private.
[20:05] <cjwatson> smithy: Your account is not a private team.
[20:05] <cjwatson> smithy: You probably fall into the "other cases" category above, so contact commercial@launchpad.net
[20:06] <smithy> will do. Thanks for the help!
[20:06] <cjwatson> No problem