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