[04:42] I'm new to launchpad and bzr. I did a 'bzr branch ubuntu:tovid'. I aim to bring it up to date at least locally as it is not very current. I deleted some files with 'bzr remove' and finally did a 'bzr commit -m "blah blah". What happens if I push? Am I pushing to my launchpad project space or am I actually creating a branch on the official package repo? (ubunutu:tovid) [04:50] grepper: 'bzr push' will probably tell you it doesn't know where to push to. [04:50] Launchpad's model is rather different from sites like GitHub, though. [04:51] On GitHub everyone has their own fork, which is effectively their own project, and you propose merges between them. [04:51] wgrant: so what have I actually done at this point ? [04:52] when I do a bzr log I can see my branch along with the others already, which is a bit disturbing :P [04:52] But in Launchpad all the contributors can use the same project, just with their own branches. eg. if you look at https://code.launchpad.net/maas, you'll see the project's core developers and other open source contributors all listed together. [04:52] What do you mean? [04:52] bzr log doesn't list branches. It lists the revisions in your branch. [04:53] bzr log -n0 is what I did [04:53] Have you read through the first few pages of https://help.launchpad.net/Code? [04:53] Ah [04:53] That still just lists the revisions in your branch. -n0 just asks it to show merged revisions too. [04:53] Do you have experience with other DVCSes? [04:54] mainly svn (cvs before that). I just moved the project to GIthub so have had to learn git this last week. So I am thoroughly muddled. [04:55] so my revisions will show up for others already, even though I haven't pushed anything ? [04:55] The "Distributed" in "Distributed Version Control System" is the important bit. [04:56] All your commits are totally local until you push them. [04:56] great, that was what I was expecting from working with git [04:56] can I push to my own account on launchpad ? [04:59] Launchpad branches have an owner and a target, two separate attributes. Anyone can push a branch up targeting Ubuntu's tovid package, as long as they push it to a branch owned by themselves or one of their teams. [05:00] The form of a package branch URL is lp:~USER/DISTRIBUTION/SERIES/PACKAGE/BRANCH. So in your case you'll want 'bzr push lp:~your-launchpad-username/ubuntu/vivid/tovid/short-description-of-your-branch' [05:01] wgrant: okay, I'll give it a whirl, thanks [05:01] none of that is different than what I expected btw, I was just concerned I should check it out as I am new to this. [05:02] the actualy upstream project is mine, just wanted to contribute [05:02] actual* [05:03] The other thing to note is that most of the ubuntu:* branches (really lp:ubuntu/*) are auto-imported by a system that's kind of bitrotted. We hope to replace it soon with something git-based, but that isn't ready yet. In the meantime you will find that a number of those branches are broken or outdated; it's entirely reasonable to fall back to old-school and manipulate source packages directly, sending patches around and such. ... [05:03] ... pull-lp-source in the ubuntu-dev-tools package can help. [05:05] hm, just I guess I should be targeting vivid at this point, I was thinking maybe I'd do a ppa for the 14.04 LTS [05:05] okay [05:05] lp:ubuntu/tovid seems to be up to date with the last version from before it was removed from Ubuntu, but you won't necessarily find that for other packages. [05:05] its the only package I'm concerned with [05:05] If you want to revive the maintenance of that package, it'll need to be in the development release, although of course you're welcome to maintain a PPA. [05:05] (for that or for older releases) [05:06] my account right now is a ppa account, or I think that is what I registered for [05:06] Any Launchpad account can have PPAs. [05:06] do I need something else to push to a branch as you indicated? [05:06] ah, okay [05:06] Any Launchpad account can also have its own branches. [05:08] (when I say "if you want to revive the maintenance of that package", I mean in Ubuntu itself, which is the approach with greatest benefit although it also involves more up-front work, so you may well not want to start there right at first) [05:08] yeah, I don't see myself as a maintainer of a ubuntu package, I'm the sole maintainer, developer etc of the tovid project as it is. [05:09] just wanted to contribute. It was removed because of incompatibiities that have been resolved (libav etc). [05:09] Fair enough. You might well find somebody willing to pick it up now that it's on libav and such (thanks!). [05:09] I did post on the bug reports, but dunno if the old maintainer is still reading it or interested. [05:11] Maia Kozheva packaged it originally and was dealing with it for some time, but they aren't subscribed to the bug and I don't recall whether they're still around. [05:12] Err, apparently I mean Maia Everett now. Still at least a bit active on LP. [05:12] okay [05:14] at least I have it it working locally, creating a 0.35.0 deb and so on, so I may as well do a ppa [05:14] is there any kind of review process for ppa's ? [05:15] No. [05:17] okay, thanks for your help ! [05:18] I may be back tomorrow with questions ... [05:33] cjwatson: okay I did "bzr push lp:~grepper/ubuntu/trusty/tovid/tovid-0.35.0_branch" , does that look okay ? [05:34] how do I see it on a web interface, I don't see anything on my user login page [05:42] ah, http://bazaar.launchpad.net/~grepper/ubuntu/trusty/tovid/tovid-0.35.0_branch/changes [05:44] * grepper does a zombie walk off to bed [08:47] grepper: Sure, or https://code.launchpad.net/~grepper/ubuntu/trusty/tovid/tovid-0.35.0_branch [11:39] /b 5 [22:10] How do I reupload to my ppa? My first ppa upload sucessfully built, but I noticed a little while ago that libsox-fmt-all doesn't provide the 'sox' binary anymore, so needed to change this one depends to 'sox'. I tried a bzr bd -S and the tried to upload with dput, but received an upload failed message. I followed this guide to the error: https://help.launchpad.net/Packaging/UploadErrors, rebuilt with debuild -S and tried to [22:10] upload again. Same error. [22:13] did you get a specific error message from an upload tool or via email? [22:13] I somehow guess you did not change the version [22:14] yes, that is what I just realized [22:14] seems a bit harsh to have to change the version when I just uploaded the first, but I can understand the reasoning [22:14] sarnold: yes, it was an email [22:14] thanks for confirming mapreri [22:16] grepper: the reasoning is: "republishing the same version is just evil" [22:16] heh [22:17] no one has seen my 1st upload but God and the launchpad hardware/software :) [22:19] hm, so 0.35.0-0ubuntu0 --> 0.35.0-0ubuntu1 , or 0.35.0-1ubuntu0 ... or ..? [22:20] * grepper googles Ubuntu versioning [22:20] you also might want to use some other suffix, like ~ppaN or +ppaN, it depends. you can use whatever versioning you want, i guess quite nobody will care [22:20] or 0~grepper0 if you're making speculative builds.. [22:22] looks like ubuntu0 stays as there is no debian package version, so 0.35.0-0ubuntu1 is good enough. I may add another suffix though [22:23] er, sorry, 0ubuntu means no debian package is what I meant [22:24] means there isn't such a package in the debian archive [22:27] grepper: The rule is that if you change the package, you must change the version. [22:27] Which doesn't seem like a particularly unreasoanble restriction. [22:27] wgrant: yes, I have gathered that :) [22:28] damn, shouldn't run debuild in a bzr dir, it deletes the .pc/ directory [22:42] Upload went fine, thanks. Sorry for the noise, realized the obvious answer after I asked.