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