[10:01] <jave> hello
[10:01] <jave> is there some way to verify a bzr installation?
[10:01] <bob2> what do you mean by verify
[10:01] <jave> I get baffling error messages like: bzr: WARNING: bzrlib version doesn't match the bzr program.
[10:01] <bob2> how did you install bzr and bzrlib
[10:02] <jave> so my installation seems broken somehow. I cant figure out how though
[10:02] <jave> as I remember, just "yum install bzr"
[10:02] <jave> on fedora 18
[10:03] <jave> but I have made various other bzr installs during the years, that I believed I have purged
[10:03] <bob2> file a bug on fedora I guess
[10:03] <jave> its a local issue
[13:13] <vila> jave: 'bzr version -v' and 'bzr plugins -v' should help you check which libraries and plugins are used
[15:00] <jave> vila: seems like theres a problem with the installation on the savannah.gnu.org rather than locally
[15:01] <vila> jave: well, then the diagnosis should be done there, there is little you can do from your side
[15:05] <jave> yes I didnt know at first where the problem was
[15:05] <jave> the error message made it look like it was my local problem
[18:02] <spundun> hi all... development-colo doesn't support merging branches!!
[18:03] <spundun> or I can't figure out how to do it
[18:03] <spundun> https://bugs.launchpad.net/bzr/+bug/1174445
[18:13] <SamB> spundun: huh, I'd never even heard of that flag before
[18:14] <spundun> --development-colo ?
[18:14] <SamB> yeah
[18:14] <spundun> I use it to keep only one working directory and switch branches within that to work on specifics
[18:15] <spundun> but I can't figure out if there is a way to merge those branches
[18:15] <spundun> SamB: https://lists.ubuntu.com/archives/bazaar/2012q1/074217.html
[18:30] <spundun> Found a workaround for it.
[18:30] <spundun> posted in https://bugs.launchpad.net/bzr/+bug/1174445
[18:31] <SamB> it sounds like the special format isn't needed anymore ...
[18:31] <spundun> I'm not sure what you mean
[18:31] <SamB> (or didn't 2.5 ever get released?)
[18:31] <fullermd_> I'm not aware that it has particularly thorough or meaningful support for colo.
[18:32] <fullermd_> It was kinda in progress when the wheels came off.
[18:32] <spundun> "it" being release 2.5?
[18:32] <fullermd_> Being in-core colo.
[18:33] <spundun> I'm not aware that it(=in-core colo) has particularly thorough or meaningful support for colo.
[18:33] <spundun> like that?
[18:34] <fullermd_> No, the first it was 2.5.  The second was colo.
[18:34] <spundun> ok :
[18:34] <fullermd_> 2.5 is out.  Really usable in-core colo isn't.  The formats in 2.5 (theoretically) support it, but the UI mostly isn't there.
[18:34] <spundun> I'm using lp:bzr
[18:35] <fullermd_> Situation isn't really different there.
[18:35] <spundun> yeah, it seems like
[18:40] <spundun> 2a format seems to work just as good without the --development-colo flag