[02:01] huh, `ag` can find zope templates with --plone [02:07] wgrant: thank you for the review (imagine that took some time!) [02:07] blr: Yup, mostly tiny things. [02:10] wgrant: do we want the target ref to default to heads/master? [02:10] context +register-merge ref picker [02:11] blr: It should default to the target repo's HEAD ref, which is GitRepository.default_branch as of yesterday. [02:12] ah cool, handy [02:13] I'm not completely sure how it should all work at this stage. I think we eventually want a two-stage picker that selects a repo and then a ref within it. [02:13] yep, would make sense to be within the same control [02:13] We can't have the target ref input prepopulated with the default_branch, because the user could change the selected repo and invalidate the branch. [02:14] So I think we for now have to go with a picker that asks for a vocab on the selected repo, but for the normal case accept that an empty ref input means a server-side fallback to default_branch. [02:14] would be easy enough to reset it if the content of the target repository input changes [02:14] Right, but reset to what? :) [02:14] It'd have to be empty. [02:14] well, it would have to be empty yes [02:15] unless we could make an api call [02:15] I think blank == HEAD makes sense in general. [02:15] Like, if you clone a repo, you get HEAD. [02:15] HEAD is a sensible thing for a null branch name to mean. [02:15] ok, perhaps we just need to add a note in that case that HEAD is assumed unless otherwise specified [02:15] I don't think it's worth improving on that until we can have the unified picker. [02:15] Yep [02:32] wgrant, blr: just curious, have you thought at all about getting go get launchpad.net/foo to work if the foo project uses git? [02:35] mwhudson: I'm afraid I'm not that familiar with golang, but that certainly sounds like a useful feature given our increasing use of the language... [02:36] yeah, there is support in the go tool for urls like that, but it assumes bzr [02:36] would be nice to fix it somehow [02:36] i'm not sure about all the intricacies of how go get works [02:39] welp, apparently there's a carshare service in melbourne called GoGet. Thanks google. [02:40] i think one approach would be to put tags on the launchpad.net/project page [02:40] presumably the go source is on github somewhere [02:40] (and delete the special casing for launchpad in the go tool) [02:41] blr: docs here https://golang.org/cmd/go/#hdr-Remote_import_paths [02:41] source is here https://github.com/golang/go/blob/master/src/cmd/go/discovery.go [02:42] (and get.go, vcs.go) [02:42] mwhudson: thanks, will have a look this evening [02:42] have been meaning to spend some time with golang at any rate. [02:42] blr: would it be useful to file a bug about this? [02:42] mwhudson: absolutely yes, please tag it 'git' [02:42] if you do the lp bits, i'll do the go bits :-) [02:45] Yep, that definitely makes sense. [02:45] Inasmuch as go get itself does :) [02:45] https://bugs.launchpad.net/launchpad/+bug/1465467 [02:45] Bug #1465467: put tags on project, series pages [02:45] well yeah [02:46] i guess testing this against launchpad.dev will actually be easier than testing it against launchpad.net, unless you hack your own build tool [02:46] er [02:46] *go tool [02:49] thanks mwhudson, at a glance it seems easy enough [02:49] blr: yeah, seems like it should be fairly easy [02:50] blr: go 1.5 will be released in august, would be nice to be able to get the relevant change into that [02:51] not completely sure i want to set up a launchpad dev environment just for this, but i guess i could... [02:51] mwhudson: could you mock it locally somehow and point me at your golang fork on gh perhaps? [02:54] blr: sorry, i don't really understand [02:54] mwhudson: I'm not certain you're going to be able to avoid setting up LP heh, although it is reasonably painless these days [02:55] blr: depends on whether i can con one of you guys into doing it first [03:00] mwhudson: I can have a poke at it at codecraft this evening [03:00] blr: awesome [03:00] i've put it on my todo list [03:00] but not at the top :-) [06:54] Can someone help me? how to init series? [06:55] maozhou_: Um, what are you trying to do exactly? [06:56] Project series don't require initialisation, and initialising a distribution series on launchpad.net is something we'd expect to have had prior notice of. [07:02] i set up launchpad server on local, then i add a series.but when i init it ,it dosen't work [07:04] maozhou_: This is not even slightly easy to get going, but https://wiki.ubuntu.com/NewReleaseCycleProcess may provide some clues. [07:09] cjwatson: i do it by this way.(https://dev.launchpad.net/LEP/DerivativeDistributions),but when i init it ,it dosen't work. [07:11] You'll probably need to run 'cronscripts/process-job-source.py IInitializeDistroSeriesJobSource' [07:11] But on a local instance you're mostly on your own, or at least will have to dig through log files yourself and generally provide more useful problem reports than "it doesn't work" :-) [07:12] I suspect derived distributions will be pretty complex to get going on a local instance, as you'd have had to import some other distribution to derive from. [07:13] You could in principle import Ubuntu using scripts/gina.py or something, but there'd be a lot of details for you to work out for yourself. [07:24] cjwatson: my workmate said that he once init the "DerivativeDistributions" succeed by run some script, but he can't remember which script he run. may be i need try to run 'cronscripts/process-job-source.py IInitializeDistroSeriesJobSource' [07:27] cjwatson: thanks for your help, Let me try by your way. [07:27] maozhou_: Oh, are you working on the kylinos.com.cn Launchpad instance that was spamming people a few months back? [07:30] ... and have you deleted sampledata yet? :-) [07:33] wgrant: yes, may be. I am sorry about that. but how to stop it spamming people? [07:36] maozhou_: As far as we could tell, you took a normal Launchpad development instance, including all the development sample data, enabled outbound email, and started using it. The sample data includes some real email addresses, and is generally a terrible basis for a production deployment. [07:36] I don't know what your goal for your Launchpad instance is, but starting with sampledata is almost certainly the wrong way to go. [07:38] Also may well have security holes of various kinds since the sample data includes people with e-mail addresses you don't control in privileged teams. [07:41] The development sample data is meant to make it easier to experiment with changes to Launchpad itself locally, by giving you a bit of test data so that important pages will render something at least a little bit useful. But it should never be included in production deployments. [07:42] I don't know if there's a sensible way to excise it from an already-running instance; it would probably involve non-trivial database surgery, and might well be easier to start again from scratch. [07:54] ok, i will tell my workmate to check it . may be we need to modification datebase. [07:59] if i alter datebase about mailaddress,is it effectivity? [08:04] You really ought to delete the predefined non-team accounts, and there will be various other junk in e.g. your list of registered projects, your bug/branch/specification tables, etc. that you probably want to get rid of. [08:07] A fresh bootstrapped database would be a much better idea. [08:14] there are many data already in datebase ,if do a fresh bootstrapped database, all the data will be losed , may be we can't do that. [08:26] we will check it to stop it spamming people. [09:14] cjwatson:when i run 'cronscripts/process-job-source.py IInitializeDistroSeriesJobSource' , it's error . the error log is “Running (ID 2) in status Waiting” [09:14] Job resulted in OOPS: OOPS-ea5bde41e13487cb6437263a6b26b44d [09:14] 1 InitializeDistroSeriesJob jobs did not complete. [09:15] what is “OOPS: OOPS-ea5bde41e13487cb6437263a6b26b44d” ？ [09:15] You'll need to find the actual text of that OOPS. [09:15] It should have been dumped out somewhere, but exactly where depends on your configuration. [09:16] The error_reports lazr config section should have an error_dir key, which might be a place to start. [09:17] ok，i know .thank you. === anthonyf is now known as Guest89967 [14:33] wgrant: Would you mind having another quick look over https://code.launchpad.net/~cjwatson/launchpad/git-repository-ui-edit-target/+merge/261232 ? I know you already gave an Approve vote, but I made some fairly extensive changes to cope with the changes related to target_default. === anthonyf is now known as Guest41199 [20:55] morning [21:38] hmm would be nice to have the option to delete a comment within x minutes of creation for people that haven't had enough coffee. [21:56] i think there is a bug with a very small number about that :-) [21:57] mwhudson: made a start on your request last night, have the import meta rendering on Product+index, will try to sort out the bzr meta and ProductSeries tag before eow [21:57] blr: i just noticed, cool :-) [21:58] i'll get set up to be able to test it [21:58] is launchpad still running on precise? [21:59] mwhudson: yep [22:00] okidoke === anthonyf is now known as Guest21341 [23:09] mwhudson: have another branch (which allows a project to have an associated 'default' vcs, amoungst other things) which needs to land before this branch. Not far away however [23:09] will govern whether a bzr or git meta tag is rendered [23:20] blr: ah yes, that seems relevant :-)