[08:59] <w7z> sort of morning
[15:38] <euphogeeza> Hi All. I have bzr installed on a windows box and trying to get post-commit emails working. I think I have everything in place but no mails are being sent.
[15:39] <euphogeeza> I thought I'd look in the trace (log?) but can't find it.
[15:39] <euphogeeza> If I do a "bzr help commands" at the command prompt I am getting "failed to open trace file [Errno: 13] Permission denied".
[15:39] <euphogeeza> Is this trace file == the log file?
[15:40] <euphogeeza> ...and where should it be?
[15:40] <euphogeeza> If I don't know where to look I can't check the permissions :-(
[15:41] <euphogeeza> I set the BZR_LOG environment variable (with "SET BZR_LOG=<path>") and now get "failed to open trace file [Errno: 22] Invalid argument".
[16:00] <LarstiQ> euphogeeza: `bzr version` will tell you where the log file resides
[16:01] <LarstiQ> euphogeeza: look for the 'Bazaar log file' line
[16:05] <euphogeeza> LarstiQ: OK Thanks. I'll go look...
[16:08] <euphogeeza> LarstiQ: OK I see the path "D:\Server Data\BZR" is listed...
[16:08] <LarstiQ> euphogeeza: that's a slightly weird path for the log
[16:09] <LarstiQ> euphogeeza: is BZR_HOME set?
[16:09] <LarstiQ> because that might influence the path
[16:11] <euphogeeza> LarstiQ: yes and BZR_LOG. I tried to force bzr to write to a location which I knew.
[16:11] <euphogeeza> LarstiQ: both set to "D:\Server Data\BZR"
[16:12] <euphogeeza> LarstiQ: ...no log file created though.
[16:12] <LarstiQ> euphogeeza: so if you're setting BZR_LOG, try "D:\Server Data\BZR\.bzr.log"
[16:14] <euphogeeza> LarstiQ: trying it now...
[16:19] <euphogeeza> LarstiQ: :-( still no log file created. Where is the default location that the log file, if BZR_LOG is not set?
[16:23] <LarstiQ> euphogeeza: home = osutils._get_home_dir(); return os.path.join(home, '.bzr.log')
[16:23] <LarstiQ> which on windows is *looks up*
[16:24] <LarstiQ> pff
[16:25] <LarstiQ> euphogeeza: quite a bit of code
[16:25] <LarstiQ> euphogeeza: if you unset BZR_LOG and BZR_HOME, what does it show?
[16:28] <jml> we wrote this – http://paste.ubuntu.com/1372760/ – to figure out the timestamp of the first commit made in a branch that then got merged into trunk.
[16:28] <jml> is there a faster way of doing it?
[16:30] <euphogeeza> LarstiQ: I unset BZR_LOG only, then bzr version => "D:\Server Data\"\.bzr.log ???
[16:31] <euphogeeza> I unset BZR_HOME also, and bzr version now returns: d:\local_data\<username>My Documents\.bzr.log
[16:31] <LarstiQ> euphogeeza: aha to the latter
[16:31] <LarstiQ> euphogeeza: to the former, wait, are the " included?
[16:31] <LarstiQ> euphogeeza: that would be problematic
[16:32] <euphogeeza> LarstiQ: yes. I have now found the .bzr.log. Yey!
[16:32] <LarstiQ> euphogeeza: good :)
[16:33] <euphogeeza> LarstiQ: I now have something to look at while trying to find the reason for post commit emails not being sent. Some thing for tomorrow. Many thanks for your help.
[16:33] <LarstiQ> euphogeeza: np
[16:45] <jml> http://paste.ubuntu.com/1372793/ <- two versions of getting the timestamp of the first revno of a branch
[16:46] <jml> I wonder which is faster / better
[16:46] <jml> james_w: ^^
[16:47] <jml> it cheats
[16:54] <james_w> jml, cunning
[16:54] <james_w> no idea which is better
[16:58] <jml> I wonder if any of the experts in bzr internals monitor this channel any more.
[17:01] <LarstiQ> they do, but not as intensively as in the past
[17:05] <LarstiQ> jml: Graph.find_lca?
[17:07] <jml> LarstiQ: I want the non-leftmost revision immediately after the lca, I think
[17:07]  * LarstiQ nods
[17:07] <jml> Ideally, if there were some way of retrieving when 'bzr branch' were run, that would be even better.
[17:08] <LarstiQ> jml: something with a pre_command hook?
[17:09] <jml> LarstiQ: yeah, maybe that might be a good thing to do in future.
[17:16] <LarstiQ> jml: I'm too exhausted to come up with a better response, sorry :/
[17:16] <jml> LarstiQ: no worries
[17:16] <jml> LarstiQ: thanks for the help
[20:23] <aquarius> I have a repo on a server I own which I push to via ssh. What's the easiest way that I can, on that server, when a new rev is pushed to trunk, automatically export trunk to a folder? (for deployment) I don't need jenkins or other super-complex stuff like that just yet :)