[00:05] I think --xml is in a plugin [00:05] written for IDE integtation [00:22] hi everyone... has been there any progress on this? [00:22] https://blueprints.launchpad.net/bzr/+spec/tls-and-ssl-support [00:24] mnn: yeah, sounds highly advisable. the python 2.7 argument doesn't quite work for me... [00:24] it can always be conditional functionality [00:24] on the build or version of python installed [00:25] and what about gnutls along with python-gnutls? [00:25] that way python 2.7 won't be required [00:25] py2.7 seems like the more elegant way [00:25] but yeah, that's feasilbe [00:25] especially as a plugin [00:26] mnn: there way forward with this, as with most experimental/new technology in bzr, is a demonstration plugin [00:26] as proof-of-concept at the very least [01:54] Noldorin: I have little knowledge about ftp/ssl but I could try it... anyway I have more pressing concern: [01:54] https://bugs.launchpad.net/bzr/+bug/1027529 [01:54] Ubuntu bug 1027529 in Bazaar "Cannot push/operate on SFTP; no useful error message" [Undecided,New] [01:54] seems like old issues with SFTP transport are crawling back: [01:54] https://bugs.launchpad.net/bzr/+bug/681047 [01:54] Ubuntu bug 681047 in Bazaar "Random failures on SFTPTransport tests on windows" [Low,Fix released] [01:55] i haven't had any problems with sftp on windows or mac... [01:56] however, I believe the sftp server I'm using is not hosted on windows [01:57] most likely linux [03:07] is it possible to `bzr log` all revisions that aren't part of the branch anymore? [03:07] i.e. do not have revno anymore [03:38] seany: bzr heads [04:40] hello. Is it safe to remove some older /tmp/bzr-index-* files ? (2 wks+) [04:40] I'm trying to read about what they are but all I've gained is they are used for caching [04:41] i just have 440 3M files clogging up /tmp .. === iBasic is now known as BasicOSX === iBasic is now known as BasicOSX [05:20] (in case ls3 comes back): anything bzr leaves in /tmp is safe to remove, and probably also a bug (in the bzr-index plugin maybe?) [07:45] lifeless: thanks! [08:03] moin [08:24] morning [13:18] hi guys [13:19] Anyone around? [13:21] hi bzrnewb [13:21] hey jelmer [13:22] are you well acquainted with bzr hooks by any chance? [13:22] i require very specific assistance and google seems to be failing me today [13:23] bzrnewb: a bit [13:23] bzrnewb: please just ask your question - if there's somebody around who can help they'll hopefully speak up [13:23] sweet thanks [13:23] well [13:25] is it possible when pushing to run a post_push hook only if there are changes in a specified directory [13:25] ? [13:25] bzrnewb: inside of your hook you could check if there were any changes? === Guest49605 is now known as slank [13:27] ah that's not a bad idea. [13:27] bzrnewb: the hook params should contain the old and the new revid === slank is now known as Guest96367 [13:27] so it should be a matter of just checking that those are different [13:28] Would you do it file by file? [13:28] bzrnewb: what do you mean exactly by "changes in a specified directory" ? [13:28] excuse my ignorance here, I've only just started setting up a continuous integration environment at my new office [13:28] bzrnewb: committed changes that were pushed that weren't present remotely before the push? [13:28] yes [13:29] but only for one of the directories in the branch [13:30] bzrnewb: you could probably call Repository.revision_tree() for old-revid and new-revid, and then use new_tree.changes_from(old_tree) to get the list of files that have somehow changed [13:30] great stuff [13:30] I'll go investigate [13:30] Thanks jelmer === yofel_ is now known as yofel === deryck is now known as deryck[lunch] === frankoid_ is now known as frankoid === zyga is now known as zyga-afk === iBasic is now known as BasicOSX === bitglue_ is now known as bitglue === mbarnett` is now known as mbarnett === samkottler is now known as sparklepony === sparklepony is now known as samkottler