[00:18] <teknopaul> wgrant: thanks,  I added ssh and gpg keys and re-uploaded, this time I got an email.
[00:26] <teknopaul> I think I'm missing something here.  I followed the uploading source tutorial to the end. The code is build with  ./configure && make  but I did not specify that anywhere?   Also there is a script to create a .deb and that presumably needs to be specified somewhere?  Is launchpad presuming I follow some set of build standards?
[00:28] <wgrant> teknopaul: Launchpad just uses debuild, which is the standard program that builds all Debian packages. That internally uses debian/rules to construct the package. http://packaging.ubuntu.com/html/debian-dir-overview.html#the-rules-file may be of interest.
[00:29] <wgrant> debhelper handles many common build systems without any manual code in debian/rules, but if your build system is custom it may require some overrides.
[00:47] <teknopaul> wgrant: OK I'll take a look a this debbuild thing,  any way to find out what tools are installed in launchpad?  e.g standard stuff like gcc and bash?  file
[00:55] <wgrant> teknopaul: You must list in Build-Depends anything that isn't installed by build-essential.
[01:27] <teknopaul> My first upload failed, it took a few tweaks to get debuild working, so I deleted the failed package but It will not let me upload the same version to try again? Do we have to increase the minor version for all build failures?
[01:30] <wgrant> teknopaul: You can't upload the same version twice. But you should generally be test building locally using eg. https://wiki.ubuntu.com/SimpleSbuild, since that makes it much faster to iterate.
[01:39] <teknopaul> OK thats harsh, you can't tell if a version number will be valid until after PPA accepts it, that breaks my build pipeline, gonna need to rethink a few things.   Thanks for you help.  I'll be back :)
[01:39] <wgrant> teknopaul: Hmm, what's the issue with incrementing the package's version number?
[01:43] <wgrant> teknopaul: The version number of a package isn't just the version of the software; for software that exists outside Debian or Ubuntu, the package version is the upstream version plus a suffix starting with a hyphen. http://www.fifi.org/doc/debian-policy/policy.html/ch-versions.html describes the version syntax.
[01:43] <wgrant> Though for PPA packages you'll often start with eg. 1.2.3-0ppa1 rather than 1.2.3-1, to indicate it's not actually from Debian or Ubuntu.
[01:43] <wgrant> So if you need to upload a new version of the packaging, you end up with 1.2.3-0ppa2.
=== maclin1 is now known as maclin
=== signed8bit is now known as signed8bit_Zzz
=== signed8bit_Zzz is now known as signed8bit
=== rmk` is now known as rmk
=== Peng__ is now known as Peng
[22:33] <wxl> is there any way for me to get someone's signed CoC?
[22:53] <gsilvapt> Hello all. A friend is trying to update his Wiki page but he didn't accept the Wiki since 2014. All pages show as immutable. Any thoughts on how to fix this?
[22:56] <wxl> not an LP issue. the help pages say they need to be in wiki-editors or something of the sort
[22:56] <wxl> https://wiki.ubuntu.com/HelpContents
[22:56] <wxl> wiki-editors-team
[22:58] <gsilvapt> Hum, I don't remember joining that. Thanks for helping, wxl and apologies for posting the question in the wrong place
[22:58] <gsilvapt> And in fact I never joined that team in LP
[23:02] <teknopaul> Hi all do I need completely different control files for packaging a binary and packaging source code for PPA?
=== signed8bit is now known as signed8bit_Zzz