[01:31] Is --fixes info displayed only in bzr qlog? Bzr log -v is not working. [01:35] and in lp [01:35] don't think the bzr ui itself exploses it [01:36] it should [01:36] imo [02:56] Is there a simple way to set the public branch from the command line? [02:56] I mean *parent* branch. [02:56] bzr pull --remember [09:11] hey all is there a way to make bzr ignore ownership and permission changes? [09:27] It does ignore ownership, and the only permission it tracks is the exec bit. But if you want to ignore that, I don't know how. [09:44] oh [09:44] hmm [09:44] it seem to go away after i reverted === kgoetz is now known as Kamping_Kaiser [12:05] does anyone know the cause of this - http://paste.ubuntu.com/296071/ - and if I can work around it? [12:06] I'm rather stuck otherwise :( === luks__ is now known as luks [12:22] mdke: does bzr check pass on that repository? [12:38] jelmer: running now [12:40] jelmer: it crashes too, with what looks like a similar error message [12:40] jelmer: I guess I could get the branch again without a repository, and then copy my changes across wholesale [12:41] mdke: yeah, that might work - it looks like corruption of some sort in the repository you're committing too [12:41] s/too/to [12:42] mdke: Please also file a bug report [12:42] jelmer: ok, noted thanks [12:54] jelmer: there seems to be a problem with the branch on Launchpad too, I can't branch it - http://paste.ubuntu.com/296099/ [15:23] is BzrBranch5 and old format? [15:24] I'm getting "bzr: ERROR: Tags not supported by BzrBranch5" when I bzr pull from a branch [15:25] what does 'bzr info' say? [15:25] about your branch directory [15:25] Repository tree (format: unnamed) [15:25] Hmm [15:26] ah, if I go up into the shared directory I get: [15:26] Shared repository with trees (format: pack-0.92) [15:26] yes, that is quite old. :) [15:27] is the ERROR about tags important? [15:27] not necessarily [15:27] for best results you want your local repository to be in the same format as the remote one though, I think [15:27] Yes, Branch5 is pre-tags. [15:28] The error is important if you care about missing the tags :p [15:28] yes. [15:28] (and Branch5 is ooold too; you surely don't really want it) [15:29] LaserJock: ideally, both the remote and the local repos would use the default format for bzr 2.0 [15:29] Certainly no reason to have it if your repo is in pack format; Branch6 is the default for pack-0.92. [15:29] well, it's not my repo [15:30] I just wondered if the tag error would cause problems [15:30] if you want to use tags, yes. [15:32] Generally, you'd only see that error on the target branch (since it's the only one that might be considered writable), so if you're getting it on pull, it's telling you _your_ branch is Branch5. [15:32] (and presumably the far side is Branch6+_ [15:33] LaserJock: one last check [15:33] LaserJock: what's "bzr info " say? (where is the address of the branch you are pulling from) [15:34] dash: Standalone branch (format: unnamed) [15:34] Heh [15:35] well that isn't very informative, is it. :) [15:35] Try -v. [15:35] oh i forgot about that [15:35] LaserJock: so yeah, maybe 'bzr info -v' will help [15:36] As fate would have it, 'central' branches are often going to be 'unnamed', since they often won't have WT's... [15:36] what am I looking for in there, it's got stats [15:36] specifically under 'repository' [15:36] The several lines of 'format's. [15:36] control: bzr remote bzrdir [15:37] branch: Remote BZR Branch [15:37] repository: bzr remote repository [15:37] Gruh. [15:37] I forgot about that. [15:38] Stuff a nosmart+ on the start of the URL. [15:38] LaserJock: I hardly know more about this than you, apparently :) [15:38] control: Meta directory format 1 [15:39] fullermd: oh cool, I didn't know about that [15:39] branch: Branch format 6 [15:39] repository: Packs containing knits without subtree support [15:39] there we go. [15:39] still old, but not as old. [15:39] Yeah, so that would be pack-0.92. [15:39] so I'm at Branch5 and remote is at Branch6? [15:39] Yah. [15:40] You should just move your local stuff to pack-0.92. [15:40] LaserJock: so doing "bzr upgrade --pack-0.92" will make that error go away [15:40] Actually, I'd move it to 1.9; going between those two is cheap&easy, and it'll be a bit smoother for you locally. [15:40] ah. [15:40] so that would be "bzr upgrade --1.9" [15:41] k, thanks === AnMaster_ is now known as AnMaster [17:32] hey people. Just a couple of things. [17:33] I think that you probably need to update the messages for upgrading stuff. I just tried to commit to a bound branch, and it seems I couldn't (because I needed to upgrade the repo on bazaar.lp.net) [17:33] also, with bzr-gtk - is the nautilus stuff meant to work ? cause I'm not seeing any embelems in nautilus [18:02] argh. The different formats of branches are a never ending source of problems :( [18:03] I checked out a branch which is 2a format, and I can't push it to launchpad as a new branch, because the "default stacking branch" is a different format [18:03] any ideas for working around that? [18:06] specifically the error message is http://paste.ubuntu.com/296256/ === Guest33124 is now known as sdboyer [19:31] Is there a Bazaar shell? [19:34] depends on what do you think by 'bazaar shell' [19:38] er, s/think/mean [19:40] luks: A shell you can run bzr commands from without the "bzr" prefix. [19:41] `bzr shell` from bzrtools [19:41] (the other alternative was something like git-shell, which is used for restricted ssh, and for which bzr has no equivalent) [19:42] luks: though it would be fairly trivial to make one, wouldn't it be? [19:42] luks: bzr shell was exactly what i wanted [19:42] I don't know, never needed it [19:45] * SamB_XP_ wonders why the configures for Cygwin's setup.exe are investigating fortran compilers ... === mwhudson_ is now known as mwhudson === khmarbaise_ is now known as khmarbaise [23:26] morning [23:26] hi lifeless [23:27] hi igc [23:39] hi igc, lifeless [23:40] hi jelmer [23:40] jelmer: thanks for the svn-fast-import stuff - I'll test it this morning [23:41] hi jelmer