[02:19] <exarkun> Why does this checkout take so long?  http://buildbot.twistedmatrix.com/builders/hardy32-py2.5-select/builds/795/steps/bzr/logs/stdio
[02:26] <lifeless> exarkun: this seems relevant Upgrade to svn 1.5 or higher for faster retrieving of revision properties.
[02:26] <lifeless> (it has the word 'faster' in it
[02:27] <lifeless> exarkun: also, what bzr version are you using?
[02:28] <exarkun> bzr 2.3.4
[02:29] <exarkun> It's sort of hard to get a newer version of svn on hardy, but I guess it's possible.  If someone can confirm that that will definitely speed it up, then it'll be worthwhile for me to pursue it.  I'd rather not chase any wild geese though.
[02:29] <lifeless> I am not sure when the 'copy all tags' behaviour came in
[02:29] <exarkun> It's not totally obvious to me that "faster retrieving of revision properties" translates to "don't issue a request to the svn server for every revision in the branch history"
[02:30] <lifeless> It may be relevant.
[02:31] <exarkun> Hmm
[02:31] <exarkun> Okay, there's a svn ppa, so I guess I should just try that.
[02:31] <jelmer> exarkun: with svn 1.5 it will indeed avoid a single request per revision
[02:31] <jelmer> per revision in the repository, that is
[02:31] <exarkun> jelmer: Thanks
[02:32] <jelmer> exarkun: you'll also need a new python-subvertpy that was built against the newer libsvn
[02:32] <exarkun> Hummmmmm
[02:33] <exarkun> python-subvertpy is in the bzr ppa, right?  I'm using that already.
[02:33] <exarkun> is that good enough?
[02:33] <jelmer> exarkun: yes, but the python-subvertpy in the bzr ppa for hardy was built against the hardy libsvn
[02:34] <jelmer> so even if you install a new libsvn, it'll only use the svn 1.4 API
[02:34] <exarkun> :(
[02:34] <exarkun> So I have to compile something.
[02:34] <jelmer> an alternative would be to get libsvn backported into the bzr ppa for hardy
[02:34] <jelmer> I'm not sure how hard/easy that would be
[02:35] <exarkun> For now I think it will be easiest for me to switch back to svn in this configuration.
[02:35] <jelmer> (fwiw, that checkout seems reasonably fast with svn 1.7, bzr 2.4, bzr-svn trunk)
[05:34] <Noldorin> jelmer, hi. let me know when youre around :-)
[06:00] <exarkun> How should I fast-export this project?  http://twistedmatrix.com/trac/browser/sandbox/exarkun/merit/
[06:02] <exarkun> I did mange to get trunk using `bzr fast-export-from-svn Twisted.repo/ --trunk-path=/sandbox/exarkun/merit/trunk --branches-path=/sandbox/exarkun/merit/branches merit`, but how do I get the branches?
[07:30] <Noldorin_> hey jelmer, you around yet?
[08:15] <Anteru> Hi
[14:43] <exarkun> How should I fast-export this project?  http://twistedmatrix.com/trac/browser/sandbox/exarkun/merit/
[14:43] <exarkun> I did manage to get trunk using `bzr fast-export-from-svn Twisted.repo/ --trunk-path=/sandbox/exarkun/merit/trunk --branches-path=/sandbox/exarkun/merit/branches merit`, but how do I get the branches?
[19:08] <Noldorin> hi jelmer
[19:09] <glyph> exarkun: "When a shared repository is created or found at the destination, branches are created inside it. In the simple case of a single branch (refs/heads/master) inside the input file, the branch is project.bzr/trunk."
[19:09] <glyph> http://doc.bazaar.canonical.com/plugins/en/fastimport-plugin.html
[19:10] <glyph> exarkun: I have obviously never tried this, but that sounds to me like you should have gotten a '.fi' file at some point
[19:10] <exarkun> too late
[19:10] <exarkun> jonathanj pointed out that the feature is unimplemented
[19:10] <exarkun> (but documented as though it is implemented)
[19:11] <glyph> man I'm glad we have a policy of never writing documentation for Twisted
[19:11] <glyph> that must be embarrassing
[19:11] <exarkun> I'm just going to use bzr branch and fix it up
[19:19] <glyph> exarkun: fix it up how?
[19:19] <exarkun> rebasing maybe?  or maybe that wasn't actually necessary, but I did it already anyway.
[19:25] <maxb> Generally I'd try to use bzr-svn whereever possible for bzr/svn conversions
[19:25] <maxb> It seems to be far more advanced than the rather naive fast-exporter code
[21:14] <jo-erlend> I have a project to translate some manuals and tutorials. I thought about using LibreOffice Writer for this, but would that work well with bzr? Would I be able to easily see diffs, etc?
[21:45] <nbjoerg> trying to use the fast-import plugin and get
[21:45] <nbjoerg> 23:03:28 WARNING: Cannot import multiple branches into a standalone branch
[21:45] <nbjoerg> 23:03:28 WARNING: Not creating branches for these head revisions:
[21:45] <nbjoerg> what is it trying to tell me?
[21:47] <exarkun> maybe you need to make a shared repository
[21:48] <exarkun> "When a shared repository is created or found at the destination, branches are created inside it. In the simple case of a single branch (refs/heads/master) inside the input file, the branch is project.bzr/trunk."
[21:48] <nbjoerg> I've started from "bzr init"
[21:49] <nbjoerg> all branches but trunk from the import seem to be on the list
[21:53] <exarkun> nbjoerg: shared repository is created with 'bzr init-repo'
[21:54] <exarkun> I don't really know though, just guessing
[21:54] <exarkun> I just gave up on fast-import a while ago in favor of bzr-svn.
[21:55] <lifeless> jo-erlend: you could write a bzr plugin to call out to the libre office diff utility
[21:55] <lifeless> jo-erlend: the raw diffs themselves are binary - libre office writes gzip compressed xml
[21:56] <jo-erlend> ah. Right. But there is a libreoffice diff utility? Where do I find it?
[22:03] <lifeless> somewhere
[22:17] <poolie> hi all
[23:01] <maxb> Yay for nice empty PPA build queues :-)
[23:04] <poolie> hi maxb
[23:04] <maxb> Evening