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