[05:11] <bigjools> does anyone have any idea how to make bzr builddeb export my local branch instead of using apt-source to get upstream tarball?
[05:11] <bigjools> I'm using --export-upstream and it completely ignores it
[05:22] <bigjools> looks like a bug, builddeb/cmds.py appends the upstream branch source after the apt source type so it never gets used ahead of that
[15:14] <ziksum> Hey! I would like to use bzr-svn on Windows with a serverless subversion repository (which I access using the file:// protocol). Is bzr-svn able to handle this case? I couldn't make it work and instead get "bzr: ERROR: Not a branch: ..." Can anybody help me? Thanks!
[15:14] <jelmer> ziksum: yes, it should be able to handle that case
[15:15] <ziksum> jelmer: How exactly do I specify the path for a checkout? As in "bzr co file:///p:/dir/to/svn-repo/project/trunk" ?
[15:26] <jelmer> ziksum: I'm not sure how you would on Windows actually
[15:26] <jelmer> ziksum: but yes, with /project/trunk (assuming that path exists in svn)
[15:28] <ziksum> jelmer: I found the problem... I am using a wrong version of bzr, which does not have bzr-svn installed... I'll check again when I fixed this. Thanks for now and the confirmation that it SHOULD work!
[15:29] <jelmer> ziksum: bzr-svn has issues with newer versions of svn (anything newer than 1.7)
[15:29] <ziksum> oh... I just updated TortoiseSVN, which we use to manage the SVN repositories...
[15:30] <jelmer> that might be related (if they use a shared svn instance)
[15:31] <ziksum> Thanks for now!
=== lalatenduM is now known as lala_afk
=== zyga__ is now known as zygha
=== zygha is now known as zyga2
=== zyga2 is now known as zyga
=== BasicMBP is now known as BasicOSX