[01:16] Hi. Where can I find a good guide on creating a package from a git repository and uploading it to a PPA? [01:21] orion: http://packaging.ubuntu.com/html/ and https://help.launchpad.net/Packaging/PPA should tell you what you need to know. [01:23] I don't want to use Bazzar for source control. [01:24] I want to use git. [01:25] um... that packaging guide explains both... sorta. [01:25] orion: The bzr parts of that guide are limited. You can ignore them if you don't want to use bzr. [01:25] ^ that [01:26] https://wiki.debian.org/PackagingWithGit has some git-specific bits. [05:13] this page has a dead link: https://help.launchpad.net/Packaging/PPA/Copying ( https://launchpad.net/~ubuntu-mobile/+archive/ppa/+copy-packages ) [05:14] I wouldn't copy from the ubuntu-mobile PPA :-P [05:15] I was trying to figure out how you can have support for more than one ubuntu version for your ppa [05:15] how is that done? [05:16] for example the packages I have install on 14.04 -> vivid [05:16] (as vivid stands now) [05:22] ah, found a 'copy packages' link [05:24] thanks :) [05:46] I should probably move where my code lives after finding out this fact of the packages working on all these ubuntu releases. Right now its https://code.launchpad.net/~grepper/ubuntu/trusty/tovid/tovid-0.35.0_branch. Is that too problematic to bother with ? [05:56] grepper: Package branches are always associated with a particular release, so I'm not sure there's anywhere better to move it if you want a single branch for all of them. [05:57] okay, thanks [05:57] the ppa doesn't have 'trusty' in it so its not really going to cause confusion I don't think [05:58] grepper: What do you mean? [05:58] I see a package for trusty in your PPA. [06:00] wgrant: no, I mean there is no 'trusty' in the url as in the one I was concerned about. Its fine [06:00] both are fine with me , just wanted to ask if I was doing it the right way. [06:00] grepper: Right, a single PPA can provide packages for all Ubuntu releases. [06:00] It's very rare that you'd create a separate PPA for each release. [06:01] right [06:01] is it usual to have all the package names the same regardless of target release? [06:02] Yes, otherwise upgrades wouldn't work. [06:02] okay [06:03] If the same binaries work on each release (they'd mostly stop working due to library ABI breaks), it's OK to copy them up to newer series. [06:03] But if they need to be rebuilt (eg. because libav changed its soname), you'll need to upload multiple versions. [06:03] If the source doesn't need changes, you'd often just append eg. ~ubuntu14.04.1 to the trusty version. [06:05] okay [06:06] if I upload a new version, do I need to use the web interface to copy them to each release again ? [06:06] or is there a command line interface to that [06:06] You can use the copy-package tool from lp:ubuntu-archive-tools. [06:08] great, thanks [06:08] eg. copy-package --from=~grepper/ubuntu/ppa --from-suite=trusty --to-suite=utopic --include-binaries tovid [06:08] thanks for the example [06:09] (that's just a convenient CLI wrapper around the archive.copyPackages API) [09:33] grepper: I've fixed the dead link, thanks. === [HeOS] is now known as HeOS [19:41] np [19:42] p [19:45] Is there a way to sign a package without getting a prompt? I tried ~/.bazaar/authentication.conf [19:45] thanks for the p btw [19:45] nothing like a good p [19:46] it was a math joke [19:46] sign as in gpg? [19:46] yes [19:47] gnome-keyring has support to function as a gpg-agent, so if you've stored the passphrase in the keyring, and the keyring is unlocked, you shouldn't get a prompt; assuming debsign finds your key correctly [19:50] debsign must find it as it prompts for password and signs it [19:50] though I seem to have to enter it twice, maybe that is by design [19:51] probably signing two different things [19:52] ah [19:53] dunno why the gnome-keyring thing isn't working then, it has pam support enabled [19:55] don't know, it works fine here [22:33] fixed, had to jump through a few hoops