=== gnomefreak76 is now known as gnomefreak [01:20] Hey [01:20] I have a branch on launchpad that is stacked on a branch that was moved which means I can't branch or check it out anymore. [01:20] How can I fix this? [01:29] cody-somerville: hi [01:29] cody-somerville: I don't think there is an easy way to do that, Launchpad shouldn't have allowed you to move the branch on which your branch was stacked in the first place. [01:30] Is there perhaps some way you can create the base branch again? [01:30] ah, live-helper was renamed to live-build ? [01:33] jelmer, aye [02:30] cody-somerville: also, I believe you can sftp in to your branch and edit the stacked on setting [02:30] aye [02:30] thats what I've done [02:30] excellent [02:31] although I agree with jelmer that you should have been prevented :) [02:32] anybody around know how to go back through and edit revisions in a branch - in this case, someone has committed without setting bzr whoami and I'd like to fix it - but I don't want to replay the whole revision history just to do it. [07:14] mtaylor: replay [07:14] mtaylor: + my patch to permit changing the committer which still has no home [07:14] mtaylor: sorry, rebase + my patch [07:15] lifeless: do you mean rewrite + your patch (hasn't it been renamed again?) [07:16] the rewrite plugin [07:16] the rebase command [07:16] + my patch [11:32] nebuPookins2: you're bouncing [17:22] anyone around? [17:23] anyone have time/interest in helping me with bazaar and plugins? [17:24] josh, hi [17:25] hello [17:25] let me try to explain what i've figured out and hopefully then my question will seem clear [17:26] we have these configuration files that are notoriously difficult with regards to syntax... so we have a perl script that checks them for syntax errors [17:26] we'd like to have this script run on every perl script before committing and fail the commit if there are syntax errors [17:26] i've been able to do this with the pre_commit_check hook [17:27] however, that would require us to make sure everyone has this plugin installed locally... this isn't difficult as a "one-time" thing, but it's a bit more difficult to make sure that newcomers get this installed [17:28] so, is there any way to do this on the server? [17:28] sorry for the novel [17:29] i have attempted to recreate the logic on the server using a pre_change_branch_tip but I'm not quite sure how to get access to the actual file (i.e. the perl script needs to be able to open the file and process it) [17:33] Well, bzr has the text available. Maybe it could run over stdin? [17:34] hmm, interesting [17:36] 'course, it could as easily write out a temp file somewhere and yada yada, but using stdin would save you from all the cleanups and corner cases and race conditions that entails. [17:37] ok, so am I on the right path with making sure the pre_change_branch_tip is where I want this to run? [17:37] Probably, though I'm hardly an expert. [18:50] Hello, i need some pointers on to use to use bazaar for newbies [18:50] how to use* [18:51] are there any toturials? [18:51] (for the GUI) [23:29] lifeless: Hi [23:29] hiya [23:30] lifeless: So, I've spent some time on Bazaar this weekend, mostly trying to get all of the tests to run without failing - including running tests against foreign branches. [23:30] \o/ [23:30] I'm down to 170 failures across the tests of all plugins I have installed, which I think is pretty good. [23:30] thats awesome [23:32] I ran into some tests that can obviously never run properly against foreign formats, since they make assumptions that are very much tied to Bazaar's formats (such as .bzr existing, or .bzr/checkout/merge-hashes). I've filed bugs for those. [23:32] coolo [23:33] What I wanted to ask at UDS and the GHM about this was basically to check with you that I'm doing the right thing by moving those tests (and those tests alone) to a per_bzr_bzrdir or something directory. [23:33] yeah [23:34] That reminds me, we really should rename that class to ControlDir.. [23:34] o/ [23:35] also, you'll find I filed some testrepository bugs [23:35] "testr run --failing" is awesome when fixing a large number of test failures [23:36] \o/