[15:32] <chillysurfer> hello! yesterday i created a ppa on launchpad and then i subsequently pushed a .changes file to it. dput reported success, but looking this morning it doesn't seem like the package "went" to my ppa
[15:32] <chillysurfer> is there any way to troubleshoot this?
[16:36] <cjwatson> chillysurfer: Wasn't that the one we discussed yesterday, determined to have been a keyserver failure, and told you you should reupload?
[16:37] <cjwatson> chillysurfer: Or was this a subsequent failure?
[16:37] <chillysurfer> subsequent failure
[16:37] <chillysurfer> i tried again this morning (maybe 1 hour ago?)
[16:37] <cjwatson> chillysurfer: I see a couple of rejections that our logs say were emailed to you - check your spam folders and such?
[16:37] <chillysurfer> ahhhhhhh
[16:37] <chillysurfer> cjwatson: Source/binary (i.e. mixed) uploads are not allowed
[16:38] <cjwatson> Indeed
[16:38] <cjwatson> You need to use debuild -S or similar
[16:38] <chillysurfer> cjwatson: so the problem is rooted in that i tried to push a .deb _and_ a .orig.tar.gz?
[16:39] <cjwatson> Well, that you tried to push a .deb at all
[16:39] <chillysurfer> oh i see
[16:39] <cjwatson> Launchpad does not accept and will never accept binary uploads of .debs
[16:39] <cjwatson> Only source uploads
[16:40] <chillysurfer> cjwatson: so i should modify my .changes file to remove the deb from the Files list before signing it and dput'ing it?
[16:40] <chillysurfer> (sorry for the basic questions)
[16:40] <cjwatson> You should just use the -S option to the tool you're using to build it in the first place
[16:40] <cjwatson> It is possible to excise it from the .changes file by hand but I wouldn't recommend it
[16:41] <chillysurfer> cjwatson: ok cool. i'll figure that out. the cloud-init project has a wrapper script (packages/bddeb) that "does it all"
[16:41] <cjwatson> What tool are you using to build the upload?
[16:41] <cjwatson> Ah
[16:41] <cjwatson> That sounds like a script to do a local test build, not one intended for building uploads to PPAs
[16:41] <chillysurfer> cjwatson: yeah that sounds about right
[16:41] <chillysurfer> i'll just make a debuild call directly
[16:42] <cjwatson> DEBUILD_ARGS = ["-S", "-d"]
[16:42] <cjwatson> Hm, it does seem to at least be trying
[16:42] <chillysurfer> cjwatson: oh nice
[16:42] <chillysurfer> i'll give that a shot too
[16:42] <cjwatson> Ah, you have to pass -S to packages/bddeb
[16:42] <cjwatson> It accepts it and passes it through
[16:42] <chillysurfer> ahhhhhhhh
[16:43] <chillysurfer> cjwatson: nice!
[16:43]  * chillysurfer is trying that now
[16:43] <cjwatson> I don't know how much it's worth it, but if it fits your workflow, sure
[16:43] <cjwatson> Make sure you end up with a *_source.changes
[16:43] <chillysurfer> cjwatson: oh that's the .changes file to dput?
[16:43] <cjwatson> Yep
[16:43] <chillysurfer> cjwatson: i guess there's no benefit to using this wrapper script then instead just calling debuild though..
[16:46] <cjwatson> Not sure, I see it's doing some other stuff with preparing the tree and working out a version number and such
[16:46] <cjwatson> Haven't played human python interpreter for long enough to work out how much of it is a no-op :-)
[16:50] <Odd_Bloke> chillysurfer: We can take this conversation back to #cloud-init, but the TL;DR is that you will want to use bddeb because we only ship debian file _templates_ in upstream cloud-init; there isn't a debian/ directory for you to use the normal Debian tools on.
[16:51] <Odd_Bloke> (So bddeb constructs a temporary tree and build in there for you.)
[16:51] <Odd_Bloke> *builds
[16:51] <chillysurfer> Odd_Bloke: ahhh ok in that case i'll just pass -S to bddeb then!
[16:56] <chillysurfer> ahhh it's in my ppa!! what a great feeling. thanks so much cjwatson and Odd_Bloke!!
[16:56] <Odd_Bloke> :)
[16:59] <cjwatson> Excellent