[00:56] <ki7mt> Hello All, not sure if anyone is around as it's the wknd but, I want to create a BZR repo on LP where a 2 or 3 person admin team can merge to the trunk while others must provide merge proposals. Is this considered the "Decentralised with shared main line" and if so, how to I establish the trunk for the team ?
[00:59] <teward> ki7mt: i think you'd push the brand new branch to lp:~teamname/project/branchname but don't quote me on that
[01:00] <ki7mt> teward, Ok, thanks, that's what I thought after reading a bit on LP. Would this main branch be created in the Team, or the project owned by the team ?
[01:01] <wgrant> ki7mt: The team that owns the branch are the only people who can write to the branch.
[01:01] <teward> ^
[01:01] <wgrant> For a small project, that team often owns the project as a whole too.
[01:01] <teward> that too
[01:01] <wgrant> But they can be unrelated teams or people if you desire.
[01:02] <ki7mt> wgrant, Ok, thanks. As it stands now, it is a small team, only 5 or 6, but there's the main project, then the documentation project.
[01:02] <ki7mt> and oth have teams.
[01:02] <ki7mt> .. both ..
[01:03] <ki7mt> So if I wanted and bzr brans url of say: lp:<project-name>  .. I would init that on my local machine, make my commits, then push the initial brach up that way?
[01:04] <wgrant> Yep. You always create the branch locally, then push it to Launchpad -- it'll automatically create the remote branch if it doesn't already exist.
[01:05] <ki7mt> Ok, cool, now that won't include my ~username in the URL thought right?
[01:06] <ki7mt> That's the main thing Im trying to avoid, is having my ~ki7mt username in the url
[01:07] <ki7mt> Or any of the team members ~username for that matter.
[01:07] <teward> if you push to lp:~teamname instead of lp:~username it should be bound to that team
[01:07] <teward> but keep in mind commit logs
[01:07] <teward> (they will show who committed changes, iirc)
[01:07] <wgrant> A project branch always has a URL of the form lp:~owner/project/branch, but if it's the official project trunk it also gets the URL lp:project.
[01:08] <ki7mt> wgrant, Yes, that I am trying to establish at the moment, the official project trunk
[01:08] <wgrant> If you push directly to lp:project and it doesn't exist yet, it'll automatically be created as lp:~your-username/project/trunk, and only you can write to it. But you can then hit "Change details" on that page to change the owner to the team so they can all write to it.
[01:09] <teward> wgrant: if they push to lp:~teamname/project/branch that'll have the team name as ownership, right?
[01:10] <wgrant> Right, but then you'd have to set the default manually (using the "Configure project branch" link on the project's homepage)
[01:10] <teward> right
[01:10] <teward> i think the goal of ki7mt is to get the branch itself to be team owned, not lp:~your-username
[01:10] <wgrant> Sure
[01:10] <teward> so that manual step would be needed :)
[01:10] <wgrant> A manual step is needed either way.
[01:10] <teward> indeed.
[01:11] <ki7mt> Ok, so I psuch a branch:  lp:~teamname/project/branch .. then go to the home page, and Configure project branch and set it to the team ?
[01:11] <wgrant> Set it to ~teamname/project/branch
[01:12] <ki7mt> Ok I think I got this sorted out :-) ..
[01:13] <ki7mt> Now if I balls this up, how can I remove that branch ?
[01:13] <teward> wgrant: the Lucid series is 'closed' now on Launchpad for bugs, right?
[01:13] <ki7mt> 10.04 yeah, I got a lod of bug close message no long ago I know that
[01:13] <teward> ki7mt: yeah i did too for packages in my radar directly, but it's still a question out there :p
[01:13] <teward> just a prereq question for my next one xD
[01:14] <ki7mt> Anyways, Im gonna go try out this push to LP ..
[01:14] <teward> and whether there were any substantial API changes for mass searching for all bugs in a specific target series in the Ubuntu project and closing and commenting about EOL stuff :)
[01:15] <ki7mt> Thanks for all your help
[01:15] <wgrant> teward: Support for Ubuntu 10.04 LTS ended on April 30.
[01:15] <wgrant> Searching, closing and commenting has been doable on the API since about 2007.
[01:16] <teward> wgrant: i have a script i used... what, several months ago, I think... to mass close remaining Karmic bugs but meh
[01:17] <teward> my question is whether the api changed substantially or not
[01:17] <teward> lemme go dig it up, i think it's on a usb stick somewhere...
[01:19] <wgrant> No, that part of it is in 1.0 and hasn't changed at all.
[01:21] <teward> cool
[01:21] <teward> lol i found a karmic bug that's still alive XD
[01:22] <teward> and still a current issue xD
[01:28] <ki7mt> Another question, when I create my local branch first, does it take on the trunk, branches and tags like SVN or should the first branch name just be the app or manual name ?
[01:29] <ki7mt> Bascially I want to follow the ubuntu-manual setup: https://launchpad.net/ubuntu-manual
[01:29] <wgrant> ki7mt: Your initial branch would usually just be named trunk.
[01:29] <wgrant> Why do you want to follow that?
[01:30] <wgrant> ubuntu-manual has a fairly complex setup which isn't really warranted for a small project.
[01:30] <ki7mt> Ok :-) .. what would you recommend, Im very much open to options here :-)
[01:32] <wgrant> ki7mt: I don't know what your project is doing, so it's difficult to advise. https://help.launchpad.net/Projects/SeriesMilestonesReleases describes the model.
[01:32] <wgrant> ubuntu-manual has a series corresponding to each Ubuntu series, but that's only useful if you're maintaining multiple lines of stable releases.
[01:32] <wgrant> eg. releaseing 0.1.2 after 0.2 is out.
[01:33] <ki7mt> Yes, this will be doing that also, but it's following the LTS releases only.
[01:33] <ki7mt> The main project is a desktop integrate or a custom version of Mate / LXDE ..
[01:34] <ki7mt> Adn the Manual will follow those releases
[01:34] <wgrant> Ah.
[01:34] <ki7mt> releases beaing, 14.04, 16.04 and so on, with updates only on the point releases.
[01:34] <wgrant> So in that case you probably don't want a trunk series or branch at all -- you'll want to rename the existing trunk series to whatever the current series is called on the main project, and call the branch the same thing.
[01:36] <ki7mt> At the moment, we dont have anything in the repo, that's where Im at now, setting that portion up.
[01:37] <ki7mt> And the main project is called c4c-desktop ..
[01:39] <ki7mt> The guy that started it created a personal style branch in the c4c-project, that needs to be fixed, and it has user-name and a trunk
[01:39] <ki7mt> in the url .. which we dont really want that.
[01:40] <ki7mt> here's what he done so far: https://launchpad.net/c4c-desktop
[01:41] <wgrant> ki7mt: You can just push a new branch and make it team-owned, or you can get the existing branch owner to make that one team-owned.
[01:43] <ki7mt> Is there a way to remove the old branch once we have the new team owend branch setup ?
[01:43] <wgrant> Sure, the branch's owner can delete it.
[01:43] <ki7mt> Ok, cool as they added a ton of binary media in there and it's huge already :-)
[01:43] <wgrant> Heh, never a good start.
[01:43] <ki7mt> Huge as in, GB huge
[01:44] <ki7mt> Im fairly well verese in Git and SVN, but to be honest here, I've not done whole lot of team and project work on LP, so, appreciate your patients here.
[01:46] <ki7mt> In any case, I think I have a direction to head in, thanks for all the help wgrant and teward
[01:46] <wgrant> Great.
[02:27] <mwhudson> what is the expected time between a build finishing and me being able to upgrade to it these days?
[02:31] <mwhudson> (in a ppa)
[02:31] <wgrant> mwhudson: Within 20 minutes.
[02:31] <mwhudson> ok
[06:35] <ki7mt> Hello All, yet another question. I have another project that I imported code from a SF Git repo. On the code Tab of the project, there is a message that states a refresh will happen in about 5hrs or so. Is this a constant feature or does it stop at some point?
[06:39] <wgrant> ki7mt: Code imports refresh regularly as long as no errors occur.
[06:40] <ki7mt> wgrant, Ok, thanks.
[08:15] <alkisg> Is it possible to push to imported branches? If so, what happens then, changes get overwritten at the next sync?
[08:15] <alkisg> I tried with https://code.launchpad.net/~alkisg/ltsp/ltsp-debian-packaging and I got: "bzr: ERROR: Cannot lock LockDir(chroot-75159440:///~alkisg/ltsp/ltsp-debian-packaging/.bzr/branch/lock): Transport operation not possible: readonly transport "
[08:15] <alkisg> ...not sure if that's the expected result, or if I did something wrong...
[08:16] <wgrant> alkisg: No, you can't write to an imported branch.
[08:16] <alkisg> Thank you wgrant
[08:16] <wgrant> You can push the modified version up to a different branch, however.
[08:16] <alkisg> Gotcha, will do that
[09:56] <wgrant> Launchpad will be offline for a few moments in about five minutes for a database upgrade.
[13:50] <cjwatson> Launchpad qastaging/staging will be offline for about ten minutes shortly for hardware maintenance.
[14:21] <elfy> wgrant: re gmx.co.uk and launchpad - been in contact with them - last thing and seemingly the only thing that I will get from them contains this line "Please ask the admin of the domain to contact directly our postmaster so they can fix the issue: http://postmaster.gmx.com/en/ "
[14:49] <bdmurray> cjwatson: when might 17503 get rolled out?
[14:50] <cjwatson> bdmurray: It's being rolled out at the moment.
[14:51] <cjwatson> I was going to tell you when it was done :-)
[14:51] <bdmurray> cjwatson: Ah, thanks!
[15:37] <cjwatson> bdmurray: That's deployed now.
[15:39] <bdmurray> cjwatson: thanks
[15:50] <mpt> What is “paddev.net” and why is it showing up in Google search results?
[15:51] <mpt> Specifically, I just came across <https://bugs.dogfood.paddev.net/ubuntu/+source/system-image/+bug/1355093>
[15:54] <ki7mt> wow, I did not know that adding blueprints to a project would add so much Karma :-) .. mine is x4 up from yesterday :-)
[15:54] <cjwatson> mpt: The non-production instances of Launchpad are gradually moving there so that they can't get hold of production cookies and suchlike.
[15:54] <cjwatson> dogfood has been there for a year or two, and git.qastaging.paddev.net was created there.
[15:54] <mpt> Ah, ok
[15:55] <mpt> I wonder if there’s a way to NOINDEX the whole domain
[16:18] <ki7mt> I just saw a message about Launchpad and the use if Git rather than BZR .. is the available to the general public? If so, can someone post a link to the setup and usage docs?
[16:18] <ki7mt> .. is this available ..
[16:21] <ki7mt> NVM, I found it: https://help.launchpad.net/Code/Git
[18:56] <ki7mt> Hi another question. I pushed a Git repo up to my project that did not have a trunk focus previously. How to change the Development Focus to the Git Master branch rather than the bzr trunk series ?
[18:59] <dobey> if it's possible, i guess it would be obvious in the edit page for the trunk series on the project
[18:59] <cjwatson> ki7mt: The interaction between development focus and git repositories is someting we're still working out.
[18:59] <cjwatson> ki7mt: Which project is this?
[18:59] <dobey> so i guess it's not :)
[18:59] <cjwatson> dobey: Not that simple.
[19:00] <cjwatson> Development focus is actually an inapplicable concept because it's per-series ...
[19:00] <ki7mt> Project: https://launchpad.net/jtsdk
[19:00] <cjwatson> ki7mt: Right, so you've already done the correct thing per our model, which is to make that repository be the "default" repository for the project.
[19:01] <cjwatson> ki7mt: We'll be improving the UI soon to take account of that in more places, and to let you say that you prefer git for this project.
[19:01] <ki7mt> I thinkso, yes, I was folling the Code/Git LP instructions.
[19:02] <ki7mt> cjwatson, Im in no rush on this, as I'm pulling it from SF anyway, but thought I'd give it a shot.
[19:02] <cjwatson> ki7mt: So just leave that as it is and the UI should gradually get better for you. :-)
[19:02] <ki7mt> Ok thank you.
[19:04] <cjwatson> per-series> I phrased that badly, I mean that the development focus for a project *is* a project series, and a project series may have a default branch associated with it.  But that model doesn't quite work for git because you normally want to keep lots of branches in a single repository instead.
[19:06] <dobey> well, it works i think if you just consider each series to be a "fork" repository a-la github, right?
[19:06] <cjwatson> That works in theory but isn't actually what one generally wants to do.
[19:06] <cjwatson> So that's not how our model is constructed.
[19:06] <dobey> if i create some changes to merge into an upstream git project on LP, it's roughtly the same, no?
[19:06] <cjwatson> Forks are much more sensibly applied to a contributing user's fork of a project.
[19:07] <cjwatson> But series default branches are much more like branches within the project's default repository.
[19:08] <cjwatson> Project series are used for things like long-lived maintenance branches of a project (the canonical original example back in 2004 was Apache 1.3 vs. 2.0, IIRC), and if you look at say any GNOME repository on git.gnome.org people are not creating fork repositories for maintenance branches.
[19:08] <dobey> right
[19:09] <cjwatson> So we can do per-user forks, but they don't map to series.
[19:09] <dobey> well git.gnome.org is not managed as a gneeral code hosting thing where lots of people contribute to lots of random projects, either
[19:09] <cjwatson> Sure, but per-series fork repositories just *do not make sense*
[19:09] <cjwatson> So we're not doing them
[19:10] <cjwatson> You *can* do things that way but it isn't the natural git workflow
[19:10] <cjwatson> And the goal of hosting git on Launchpad does not include unnecessarily crowbarring it into bzr ways of thinking
[19:10] <dobey> well, it makes sense to create a fork where the default checked out branch is for the associated series branch for the default respository of the project
[19:11] <cjwatson> It might make sense for a series to be able to designate a particular branch in the project's default repository, yes
[19:11] <cjwatson> I don't know how useful that would be, and it's not in the model today
[19:11] <cjwatson> But it could be added
[19:11] <dobey> i think it makes sense for maintenance work and bug tracking
[19:11] <dobey> but *shrug* :)
[19:12] <cjwatson> You can still do that, it's just that LP wouldn't tell you which branch is the default, that's all
[21:57] <mgw> I'm having difficulty uploading to my PPA
[21:57] <mgw> I'm getting a failure email after uploading
[21:58] <wgrant> What does the failure email say?
[21:58] <mgw> "Unable to identify .... in launchpad"
[21:59] <mgw> where .. is "Me <me@my-laptop>"
[21:59] <wgrant> Your changelog is misformatted, I suspect.
[21:59] <ali1234> sounds like somehting to do with pgp keys
[21:59] <wgrant> No.
[21:59] <mgw> yes, it does sound like a gpg issue
[21:59] <mgw> but my key appears correctly with my email host when I list keys
[22:00] <wgrant> The end of the latest changelog entry in debian/changelog must contain a valid email address.
[22:00] <mgw> and I'm specifying that key with the -k option to backportpackage
[22:00] <wgrant> You can override the address that dch uses by default using the DEBMAIL environment variable.
[22:00] <mgw> ah, ok
[22:00] <mgw> thanks
[22:00] <mgw> that explains it
[22:02] <ali1234> doesn't it also have to match the pgp key though?
[22:02] <mgw> how long should it take to show up on LP after I upload?
[22:03] <mgw> I matched DEBEMAIL to my gpg key this time
[22:03] <ali1234> a few minutes to show up after you get a success email, and then a few hours before it actually builds
[22:04] <mgw> it's showing up now -- thanks!
[22:04] <wgrant> A few hours?
[22:04] <wgrant> Normally a minute or so, though at the moment perhaps 20 minutes.
[22:04] <ali1234> where a few = 2, in my experience
[22:04] <wgrant> When was that experience?
[22:05] <ali1234> 2014-12-12
[22:05] <wgrant> Ah, that was a long long time ago.
[22:05] <wgrant> The queue is more than ten minutes deep for about an hour a day now, and then it barely exceeds an hour.
[22:06] <mgw> looks like i just got a time machine
[22:06] <mgw> :-)
[22:07] <mgw> thanks again!