[18:41] <jtaylor> hm requestsync does not work in precise
[18:41] <jtaylor> it just hands at please edit the report
[18:47] <jtaylor> ok no its just hanging on getting the changelog from the server
[18:49] <jtaylor> a very long time but finally it made it :) there should be some indication that its doing somethng
[19:21] <AmberJ_> Hello
[19:22] <AmberJ_> I just uploaded a source package to my PPA using 'dput'. Why did it uploaded the .deb file as well (created by 'debuild' on my system)?
[19:24] <jtaylor> probably because you built with default debuild options
[19:24] <jtaylor> you want -S for source only
[19:24] <jtaylor> add -sa if its a new upstream
[19:24] <jtaylor> those are options to dpkg-genchanges
[19:26] <AmberJ_> Ah right, I simply ran 'debuild'.
[19:26] <AmberJ_> Moreover, Launchpad PPA rejected my upload with error: "Unknown section 'unknown'". Time to get debian/control in shape...
[19:27] <AmberJ_> jtaylor, What does it do with .deb file that gets uploaded (if I use default 'debuild' options)?
[19:28] <jtaylor> launchpad will reject the upload
[19:28] <jtaylor> but its the default upload mode in debian
[19:28] <jtaylor> the deb will be published
[19:28] <jtaylor> not rebuilt
[19:28] <AmberJ_> ok
[19:43] <AmberJ_> Launchpad PPA rejected my upload with error: "Unknown section 'unknown'". So, I edited debian/control accordingly. Then I did 'debuild -nc'.
[19:43] <AmberJ_> Now when I dput source.changes, I get "Package has already been uploaded to ppa on ppa.launchpad.net"
[19:44] <AmberJ_> Nevermind. https://help.launchpad.net/Packaging/UploadErrors has the solution...
[19:51] <AmberJ_> How common (and normal) is it for a project to include a debian/ in upstream source/repo/tarball?
[19:52] <jtaylor> not common and not encouraged
[19:52] <jtaylor> if they do it should be in a branch or subfolder
[20:08] <AmberJ_> in a subfolder? Suppose I branch the project repo in directory 'xyz'... Do you mean that we should keep debian/ in xyz/subfolder/debian/ instead of xyz/debian/ ?
[20:08] <AmberJ_> +in case they really do it
[20:11] <jtaylor> for example
[20:11] <jtaylor> that makes simpler for debian packagers
[20:12] <jtaylor> as upstream debian/ folders can cause issues
[20:17] <AmberJ_> Ok, I'll communicate the message to the developers.
[20:17] <AmberJ_> Thanks!
[20:18] <jtaylor> I think its not so bad with the 3.0 format
[20:18] <jtaylor> it removes the debian folder before unpacking
[20:18] <jtaylor> but I think that still causes issues with VCS
[20:22] <AmberJ_> ok
[20:28] <AmberJ_> How do most debian/ubuntu developers automate debian/ creation then? Is this documented somewhere?
[20:29] <jtaylor> its no automatic process
[20:29] <jtaylor> you can use dh_make to get a starting template
[20:34] <AmberJ_> ok, that means for every new version of deb that you create, you start from dh_make and manually edit debian/control , debian/rules etc (?
[20:38] <jtaylor> yes
[20:41] <AmberJ_> ok
[21:16] <directhex> it's not so bad, starting with a blank slate means less "legacy" nonsense that only made sense in 2007