[08:05] <jave_> hello
[08:06] <jave_> is ploblematic to use non-ascii in commiter name?
[08:10] <jave_> I'm experiencing the issue here:
[08:10] <jave_> https://github.com/felipec/git/issues/38
[12:24] <LarstiQ> jave_: nafaik
[12:25] <LarstiQ> jave_: I'd suspect it is git-remote-bzr where the problem is
[12:27] <jave_> LarstiQ: ok, I delved some more and there seems to be some unicode/ascii conversion issue with git-remote-bzr
[12:34]  * LarstiQ nods
[12:34] <LarstiQ> jave_: that sounds plausible
[22:46] <tuv> is this the official irc channel for bzr?
[22:47] <tuv> i pulled from a different branch, and now everytime i 'bzr update', i get 'bzr: ERROR: [Errno 1] Operation not permitted:...' for some (arbitrary, afaict) file. I rm the file, update again, and I get the same error for another file!
[22:47] <tuv> what could be causing this?
[22:48] <tuv> if I don't rm the file, and update again, I get the same error for the same last file
[22:48] <tuv> it's a huge repository, so if this goes on, it could take a while
[22:52] <tuv> reiserfs
[22:54] <fullermd> errno 1 is (on my system anyway, but that low is probably common) EPERM, which would fit.  But I can't think of any way on its own bzr could have put things in an EPERMish way.
[22:54] <fullermd> The files are writable by $YOU?
[22:56] <tuv> yes. i'm rm'ing them. i can revert them too
[22:56] <fullermd> rm'ing wouldn't prove it, since you don't need write on a file (or any perms, for that matter) to delete it.
[22:56] <fullermd> And revert would be the same, since it doesn't strictly speaking edit the file; it rm's it too.
[22:56] <tuv> i don't own them, but i belong to the files' group, and they have write access for group
[22:57] <fullermd> But doing an update would, so that's the salient difference...
[22:57] <tuv> ok.. trying to edit a file
[22:57] <fullermd> (rm'ing a file requires you have write perms to the directory the file is in; the files perms are irrelevant.  Hence why /tmp requires the sticky bit)
[22:58] <tuv> i can edit them
[22:59] <tuv> it seems all the problematic files have their permissions changed (-x)
[22:59] <fullermd> Mmm.  Well, bzr should be able to edit them on your behalf, then...
[22:59] <tuv> it's having difficulty chmod'ing them, it seems
[22:59] <fullermd> That could be.  Can't chmod a file you don't own.
[23:00] <tuv> ah
[23:02] <tuv> right. that seems to be it
[23:03] <tuv> i'm trying to manage the repository as a different user than the one using it
[23:03] <tuv> apparently it's not working
[23:04] <fullermd> Yeah.  Always tricky.
[23:04] <tuv> chown.. update completes without errors :)
[23:04] <fullermd> With BSD fs semantics (or SysV and use of g+s), you can usually manage to pull it off, but dark corners like that require manual work...
[23:11] <tuv> how do i make sure i have a certain revision id checked out in my working tree?
[23:12] <tuv> revno was giving the revision no. although the update to that rev was not complete
[23:12] <fullermd> revno tells you the revno of the head of the branch; revno --tree tells you what the working tree considers itself at.
[23:13] <tuv> and do i have to use another command to resolve the revno to revision id?
[23:15] <fullermd> There's a revision-info command that shows both (and it has a --tree as well)
[23:16] <tuv> nice. does it detect a dirty tree?
[23:17] <fullermd> Don't think it says anything about that.  version-info can.