[00:29] <ali1234> how do i get bzr to show the current revision of the working dir?
[00:29] <mwhudson> ali1234: bzr revno
[00:29] <vadi2> I updated to 0.100.0-2ubuntu2, wrote a really big commit log, it asked me whenever to commit with unknowns in the repo - I clicked yes, and the dialog froze. It's not accepting any clicks on yes or no buttons and is just sitting there.
[00:30] <vadi2> No errors in the terminal. Has anyone else experienced this?
[00:30] <vadi2> The only thing clickable is the X and it does nothing, the dialog doesn't go away.
[00:30] <ali1234> ok, given that i tried to bisect between 1363 and 1448, why is the working dir at 1455?
[00:30] <ali1234> (i am using bzr-bisect)
[00:31] <mwhudson> ah i guess bzr revno gives you the revno of the branch really
[00:31] <mwhudson> if you've used bzr revert or something that's just tree modifying, i don't know how you can find out which version corresponds to the current state
[00:31] <ali1234> well the current revision doesn't build so i need to move dorwards or backwards
[00:31] <ali1234> but i can't do that if i don't know the current revision
[00:32] <ali1234> and bzz bisect move needs an exact revision
[00:32] <ali1234> and yeah i gather it does use revert
[00:32] <mwhudson> i've not used bzr-bisect
[00:32] <mwhudson> you can probably use bzr revert -r $revno to move to a different revno though
[00:33] <ali1234> moving isn't the problem
[00:33] <ali1234> the problem is i need to move to $current_revno+1
[00:33] <ali1234> and i don't know $current_revno
[00:35] <ali1234> so how do you all usually do bisects?
[00:36] <ali1234> by hand?
[00:36] <fullermd> 'revno --tree' will tell you the base revno of the working tree.
[00:37] <fullermd> Of course, if you've flung things around with 'revert', you haven't changed the base revno, so that won't tell you anything.
[00:37] <ali1234> yeah, that also say 1455
[00:37] <fullermd> Yeah, I think bisect does that.  Annoying.  It really needs to be updated...
[00:39] <fullermd> Presumably the plugin stashes its current state somewhere; if you can dig that up, it should tell you.  You'd expect it to have a command for that too...
[00:44] <ali1234> it has bzr bisect log
[00:44] <ali1234> but that doesn't really tell you anything useful
[00:45] <ali1234> it prints <commiter>-<timestamp>-<hash> but not revno
[00:45] <ali1234> and only for the points you've already said yes or no to
[00:45] <fullermd> That's thre revid.
[00:46] <fullermd> You can look up the revno from that.
[00:46] <fullermd> First way that comes to mind is with log.  Various other probably more direct internally (if less simple/obvious interface-wise).
[00:47] <ali1234> but it doesn't tell me the current point anyway
[00:47] <ali1234> also "yes" and "no" are undefined
[00:47] <fullermd> (it's not really committer-timestamp-hash, it's opaque; just happens to be built that way.  And it's random data, not a hash anyway...)
[00:47] <ali1234> and if you get them the wrong way around it jumps to somewhere outside the range
[00:48] <ali1234> maybe i should just convert this to a git repository :)
[00:49] <fullermd> I've never touched the bisect plugin, so I don't know whether it stores its data in a particularly easy-to-read form.  Or where it is, for that matter.
[00:50] <fullermd> Probably either the root of the tree or somewhere under .bzr/.
[09:31] <MvG> jam: wrt https://code.launchpad.net/~gagern/bzr/bug483661-pull-bound-testcase/+merge/73147 : you quoted the relevant change yourself: I dropped the possible_transports kwarg. So what "actual changes" are you missing?
[14:50] <antivirtel> hello!
[14:51] <antivirtel> I'm using bzr-explorer on Ubuntu. How can I add a spell checker language? Which spell checking method is it using?
[15:02] <jelmer> antivirtel: hi
[15:02] <jelmer> antivirtel: I think it uses the Qt spell support
[15:03] <antivirtel> hmm, jelmer has it got a package?
[15:04] <jelmer> antivirtel: no idea, sorry. I haven't used it myself.
[15:06] <antivirtel> thanks, I google it
[23:40] <poolie> hi all
[23:46] <jelmer> g'morning poolie, did you have a good weekend?
[23:50] <poolie> great thanks
[23:50] <poolie> the superbike school was very fun
[23:50] <poolie> how are you?
[23:52] <jelmer> poolie: cool :) what's super about superbikes vs regular bikes?
[23:52] <poolie> :)
[23:53] <poolie> i think it's a bit of an anachronistic term
[23:53] <poolie> it means sporty production bikes as opposed to grand prix bikes
[23:53] <poolie> however, most people came on regular road-going bikes, as i did
[23:54] <jelmer> ah :)
[23:58] <poolie> this stuff http://www.superbikeschool.com/curriculum/the-levels.php