[04:00] <mwhudson> has anyone implemented du that works over a transport?
[04:58] <lifeless> mwhudson: repository info used to, I think. It was terrible.
[04:59] <mwhudson> ah yes, i think you're right
[04:59]  * mwhudson tries to remember why he asked
[07:16] <vila> hi all !
[07:19] <spm> heya vila!
[07:20] <vila> spm: hey there :)
[07:20] <spm> vila: nice shirt i noticed you wearing in some of the sprint photo's. something about google and to ask you instead. :-)
[07:20] <vila>  huh ? This got public ? OMG :-D
[07:20] <spm> hahaha
[07:21] <spm> I'll refrain from pointing out that you were walking around in public with that on....
[07:21] <vila> spm: for your enjoyment, you can try shuffling the words too, there are some interesting variations there :)
[07:21] <spm> quite possible
[07:21] <spm> possibly too even!
[09:08] <MAfifi> I've made a fatal mistake.
[09:09] <MAfifi> I've two projects on launchpad, namely listInstalledRPM and downloadRPM. I've, by mistake, pushed the trunk tree of the latter to the former.
[09:09] <MAfifi> Now I can't fall back.
[09:11] <poolie> MAfifi, did you do a push --overwrite?
[09:11] <poolie> or had you only pushed one of them
[09:12] <MAfifi> poolie: No it was just my first push to that project, so I normally used just push.
[09:22] <poolie> Mafifi ok so just push --overwrite what you do want to have there
[09:23] <MAfifi> poolie: Thank you, I used push --overwrite and it fortunately did exactly what I wanted.
[09:23] <poolie> great
[09:49] <jml> lifeless, I saw the bug report. ensaddening.
[09:52] <vila> jml, lifeless: who is 'he' ?
[09:57] <poolie> hi there vila
[09:58] <vila> poolie: hey
[09:58] <lifeless> vila: fuzzyman
[09:58] <poolie> how are you? what fabulous adventures will you have today?
[09:58] <poolie> lifeless,  this is your load_tests thing?
[09:58] <lifeless> yes
[09:59] <lifeless> he fairly casually, AFAICT, implemented a different protocol, breaking everyone using the bzr one.
[09:59] <poolie> ffs
[09:59] <james_w> rockstar: can you run the failing command again under "strace -o /tmp/strace.txt" and then send me that file?
[09:59] <spiv> yes, very ensaddening :(
[10:00] <rockstar> james_w, sure, one sec.
[10:00] <lifeless> I may be exaggeratig, I don't know the story behind the change.
[10:00] <lifeless> anyhooo
[10:01] <vila> on the -let-s-try-to-be-positive, 'pattern' can be said to be as arbitrary as 'module', in fact, I'm pretty sure both should be put in the loader letting any load_tests() function defines a new one for submodules if needed (or specialize whatever(
[10:01] <vila> s/(/)/
[10:01] <vila> hmm, not sure this sed command wont bring nasty comments...
[10:02] <rockstar> james_w, http://pastebin.ubuntu.com/466360/
[10:02] <Meths> vila: like "That isn't the sed command you're looking for..."?
[10:03] <vila> Meths: this comment is ok :-)
[10:04] <james_w> rockstar: and that run gave the same error?
[10:04] <rockstar> james_w, yup.
[10:04] <james_w> rockstar: it's very odd
[10:04] <rockstar> james_w, yes, yes it is.
[10:09] <vila> poolie: I'm setting up a maverick slave to help jam/barry
[10:09] <poolie> in babune, running 2.7?
[10:09] <poolie> that sounds useful
[10:10] <vila> yeah, first step is: running default python, then py2.7
[10:10] <james_w> rockstar: it's looking for /home/rockstar/Projects/repos/tarmac/tarmac_0.3.2.orig.tar.gz but I think you are running the command in /home/rockstar/Projects/tarmac/packaging ?
[10:10] <rockstar> james_w, oh man.  Yeah, I've got lightweight checkouts setup.
[10:10] <vila> long term, I think we want a dedicated job to track python-trunk, at least the 2.x series
[10:11] <james_w> rockstar: then you have found a bug sir
[10:11] <james_w> rockstar: please to be filing with details of your setup
[10:11] <rockstar> james_w, indeed, and you have found a workaround for me.
[10:11] <vila> that would have helped detect this load_tests() issue far sooner, may be even in time to yell when it broke testtools/bzr
[10:11] <rockstar> james_w, thanks.
[10:14] <vila> poolie: well, when I said first step, I should have said 'next' :-) There were many small steps before to setup the new VM but it went pretty smoothly. I'm not ready to automate that though :)
[10:15] <vila> poolie: the nice thing is that I seem to have fixed an old bug there where some vms were failing to connect to dhcp and led to spurious failures in babune, so even less maintenance for me :D
[10:20] <vila> jam, lifeless: first run on babune for maverick/py26: http://paste.ubuntu.com/466370/
[10:21] <vila> subunit faliing to parse a date ? Rings anyone bell ?
[10:33] <poolie> spiv, do you know anything about automatic changelog merging?
[10:34] <poolie> vila that looks like stderr and stdout are getting mixed together badly
[10:34] <poolie> or something similar
[10:34] <jml> jam, https://devpad.canonical.com/~jml/no-accel-tree.gz (also -2, -3)
[10:35] <vila> poolie: subunit and testtools were out-of-date, dunno exactly why... retrying
[10:36] <vila> meh, this laste paste is bogus, where are my EOL gone ??? :)
[10:54] <spiv> poolie: bzr-builddeb registers a hook that does that, it seems to work quite well
[10:54] <poolie> ok, thanks
[10:54] <poolie> so that's one thing fixed from scottk's list
[10:58] <knittl> hi. is there a way i can print bazaar repository files?
[10:58] <knittl> hg has debug*
[10:58] <knittl> git has cat-file and ls-tree
[10:59] <LeoNerd> bzr cat $URL  ?
[11:00] <knittl> url?
[11:00] <knittl> no, i mean local repository
[11:00] <knittl> showing raw changelogs, indices, trees, blobs
[11:00] <LeoNerd> Oh.. Poke at the internals? No...
[11:00] <LeoNerd> For that, see /bin/cat  ;)
[11:00] <knittl> yep, internals
[11:00] <knittl> human readable if possible
[11:00] <knittl> so, not really raw
[11:00] <poolie> cat-inventory
[11:00] <knittl> git ls-tree also uncompresses the files :P
[11:01] <poolie> cat-revision
[11:01] <poolie> sorry that's just 'inventory'
[11:01] <LeoNerd> The internals aren't really meant for people to go prodding at
[11:01] <poolie> or open a python shell and poke at it
[11:01] <knittl> LeoNerd: but i need to :P
[11:01] <knittl> poolie: ok, that may help
[11:01] <poolie> for curiousity?
[11:01] <knittl> gotta go now, lunch time
[11:01] <knittl> poolie: no, for my bachelor's degree
[11:01] <poolie> i would use python
[11:02] <poolie> easier to script examination of ti
[11:10] <vila> spiv: http://babune.ladeuil.net:24842/job/selftest-maverick/3/ any chance you can produce a maverick version of your paramiko package
[11:10] <vila> ?
[11:14] <spiv> vila: sure
[11:14] <vila> spiv: great ! I thought you were asleep :)
[11:14] <spiv> I wonder what happened to my merge proposal for getting that patch added to ubuntu
[11:14] <spiv> vila: will be soon, most likely :)
[11:15] <spiv> vila: https://code.edge.launchpad.net/~spiv/+recipe/paramiko-test/+build/340
[11:18] <vila> spiv: you rock !
[11:21] <spiv> vila: I just pressed a button :P
[11:22] <spiv> vila: hmm, build failed apparently.
[11:23] <spiv> In some obscure (to me) way.
[11:23] <spiv> Possibly it's just trying to tell me that the build-deps aren't right?
[11:24] <spiv> Hmm, I guess I am trying to build the lucid version on maverick with that recipe, so I suppose that's not so surprising.
[11:28] <vila> :-/
[11:30] <spiv> I'll make a new recipe tomorrow.  Hopefully I can figure out a way to use one recipe to apply the same patch to multiple distro series.
[11:31] <vila> spiv: ok, thanks
[15:24] <knittl> can i delete .bzr/obsolete_packs directory safely?
[15:24] <poolie> the contents of it
[15:24] <knittl> ok
[15:24] <knittl> thx
[15:24] <poolie> pack --delete-obsolete-packs does this
[15:25] <knittl> i don't want to repack again ^^
[15:26] <knittl> i only find a description of knit pack repositories
[15:26] <knittl> i know there exist several more formats
[15:26] <knittl> maybe not repo formats, but also branch formats
[15:26] <knittl> where can i find them?
[15:31] <knittl> and there is really no easy built-in way to have a look at bzr's internals?
[15:32] <poolie> use ipython
[15:32] <poolie> works very well
[15:38] <knittl> what is python?
[15:40] <knittl> just a python-shell?
[15:42] <lifeless> ipython
[15:42] <lifeless> its an interactive python shell with tab completion
[15:49] <knittl> docs.bazaar.canonical.com tells me to ask here :D
[15:49] <knittl> i don't want to write a lot of python …
[15:56] <jml> what's the constant for "null:"?
[15:56] <lifeless> revision.NULL_REVISION
[15:56] <lifeless> or something
[15:57] <lifeless> knittl: if you want to use bzr without writing python you can:
[15:57] <lifeless>  - use the xmlrpc server
[15:57] <jml> thanks.
[15:57] <lifeless>  - use java via jython or the xmlrpc server using bindings
[15:57] <knittl> i prefer not writing anything
[15:57] <lifeless>  - shell script it
[15:57] <lifeless> I don't know what you mean by that
[15:57] <knittl> the other dvcses all support some sort of debugprinting of repository structure
[15:58] <lifeless> there is a repositorydetails plugin
[15:58] <lifeless> or something-like-that
[15:58] <knittl> ok, i'll google it
[15:59] <knittl> hm no, statistics is not what i want
[16:00] <vila> knittl: there is no out-of-box solution for what you want, the plugin lifeless metioned will give you the best basis to write your own, which will be warmly welcomed
[16:00] <knittl> vila: ok, i'll have a look
[16:00] <knittl> although i'm _a little_ behind schedule :D
[16:00] <vila> knittl: giving a more precise explanation of what you want may help people help you find it
[16:01] <knittl> vila: i'm comparing different dvcs for university
[16:01] <knittl> and write about storage model, etc.
[16:01] <knittl> mercurial has debugindex and friends
[16:01] <knittl> git has cat-file commit, ls-tree and cat-file blob
[16:01] <knittl> bzr has nothing comparable. at least i could not find it easily
[16:02] <vila> knittl: great, you know hg and git, but here people knows bzr but not this level of detail about hg and git
[16:03] <knittl> ppl here know bzr, so i thought i'd ask
[16:03] <jelmer> knittl: I generally just use the Bazaar Python API
[16:03] <james_w> there's dump-btree, but not a complete suite of such tools I don't think
[16:03] <vila> so speaking about hg/git commands is not really enliHGtning
[16:03] <knittl> james_w: ok, that sounds better
[16:03] <knittl> although it segfaults here
[16:04] <knittl> vila: you asked what i wanted to do, and i told you what i did in git and hg to give a comparison of what i've already done and which worked
[16:04] <knittl> those were just examples. i want to view the storage model and write about it
[16:04] <knittl> types of objects, interactions, references, compression, etc.
[16:05] <vila> knittl: and I try to explain why you didn't get answers, if I failed, I'm sorry :)
[16:06] <knittl> vila: i can't really find good documentation on bzr's storage model
[16:06] <knittl> with google at least
[16:06] <knittl> reading source code seems like an endless adventure
[16:07] <knittl> but dump-btree suggests some form of binary tree
[16:07] <vila> knittl: *today* it's either reading the code or asking precise questions which requires some basic knowledge
[16:07] <vila> dum-btree will tell you which pack files are active for the repository
[16:08] <vila> repodetails will give you more entry points and how to access them
[16:08] <knittl> vila: i found my question rather precise
[16:08] <knittl> but i'll have a look at repodetails for that matter
[16:08] <poolie> knittl, ipytho
[16:08] <poolie> run ipython
[16:08] <knittl> before continuing complaining ^^
[16:08] <poolie> from bzrlilb.bzrdir import BzrDir
[16:08] <vila> knittl: my point is to explain why it wasn't precise enough to give you the answers you're after
[16:08] <poolie> bd = BzrDir.open('.')
[16:09] <poolie> then poke around in that object and follow links
[16:09] <poolie> repo= bd.open_repository()
[16:09] <knittl> vila: let's try this way: what objects uses bzr for storage of: commits, trees, files, tags, branches?
[16:10] <vila> knittl: start here: http://wiki.bazaar.canonical.com/MatthewFuller/SpotDocs/PiecesInBrief
[16:10] <knittl> ok. thanks
[16:10] <fullermd> Well, that's not gonna tell much about storage models  :p
[16:10] <vila> knittl: continue there: http://wiki.bazaar.canonical.com/MatthewFuller/SpotDocs/PiecesInLength
[16:10] <knittl> poolie: thanks to you too
[16:10] <vila> fullermd: it will give him the right words :)
[16:11] <vila> fullermd: and the entry points
[16:11] <vila> I'm not going to write the doc about the bzr data model right now and here :)
[16:11] <poolie> knittl, if you write docs and post them to the list we can correct them
[16:12] <vila> knittl: and keep in mind that bzr has used different formats with slight variations about the data model so you'd better focus on the last one: 2a
[16:12] <knittl> vila: yes, i know that there were different formats
[16:12] <knittl> but i can only find information on how to convert a repo, not about the exact differences between them
[16:13] <knittl> but now i'll read those wiki pages
[16:13] <knittl> thx
[16:13] <vila> I think jam blogged about the most important points in 2a
[16:14] <vila> knittl: chk maps and group compress
[16:14] <knittl> btw, are there any books about bzr?
[16:15] <knittl> the last time i looked i couldn't find a single one
[16:15] <jelmer> knittl: There are no books yet
[16:15] <knittl> jelmer: ok. bad for me :(
[16:21] <vila> jam: ping
[16:22] <jelmer> knittl: Yeah, we should fix that at some point :-(
[16:32] <jam> hi vila
[16:39] <vila> hey jam, I thought you mentioned a ppa with a python-2.7 from barry but I can't find it
[16:39] <vila> jam: I have a maverick slave setup on babune on the test suite ~passing there
[16:39] <jam> vila: ppa:doko/toolchain
[16:39] <jam> has maverick I believe
[16:39] <jam> and one of barry's starts making python2.7 as part of 'python-defaults'
[16:39] <jam> I don't really know the state
[16:40] <jam> so something like
[16:40] <jam>  sudo add-apt-repository ppa:doko/toolchain
[16:40] <jam> sudo apt-get update; sudo apt-get install python2.7
[16:41] <jam> vila: ^^
[16:41] <vila> jam: almost done
[16:42] <vila> I need python-2.7-dev too I presume
[16:43] <vila> jam: I fixed 2 of the 3 failures on maverick if you want to review the patch ;-)
[16:44] <vila> hmm, default python is still 2.6.5+ but python2.7 is in the path
[16:46] <jam> vila: right, python-defaults describes what pythons are *available* as well as which is default
[16:46] <jam> the goal for maverick is 2.7 available-but-not-default
[16:46] <jam> vila: already reviewed the http one
[16:46] <vila> sure, I wasn't sure what the ppa was doing
[16:46] <jam> 3 times
[16:47] <vila> jam: cool, argh, sry for the second one then :)
[16:51] <vila> jam: so, since I override BaseHTTPServer, I closely followed what was done there, specifically the atttributes are used only by this method so putting them far away... make them *less* discoverable
[16:55] <jam> vila: though it doesn't conform to *our* style guide, which makes it harder for me as a bzr-hacker
[16:55] <jam> (not positive what style says, but we do avoid local class members)
[16:56] <jam> certainly it can be a bit tricky to recognize the ident level
[16:56] <vila> jam: inherited design
[16:56] <vila> jam: since we don't define the base class it's hard to follow *our* rules
[16:57] <vila> I can *delete* them even if that's make you more happy
[16:57] <jam> vila: it is *our* code...
[16:57] <jam> vila: ultimately, I'll let you decide.
[16:57] <jam> I just saw that and noticed that I find that kind of code hard to read.
[16:58] <vila> jam: try the base class for fun :-/
[16:58] <vila> jam: the responses attribute is the last one defined in the class after all existing methods and attributes
[17:03] <vila> gee, lp is... capricious today
[17:15] <jam> vila: what's up for you?
[17:16] <vila> landing the fixes and running the test suite with py27
[17:16] <jam> vila: I mean what is going wrong with lp for you
[17:17] <vila> timeouts on mps
[17:17] <vila> but transient ones
[17:19] <vila> argh, no pyrex...
[17:19] <vila> jam: what's the status across bzr/testtools regarding unittest._WritelnDecorator ?
[17:27] <jam> vila: we dropped some timeouts in the lp code
[17:28] <jam> vila: lifeless mentions "can you please file a bug including the OOPS info"
[17:28] <jam> (from 17+s down to ~12s)
[17:29] <vila> I didn't get OOPS, only 'try again later'
[17:29] <jam> you're in the beta tester team, right? (edge urls not regular ones)
[17:29] <vila> yup
[17:29] <jam> vila: there should have been an "OOPS-XXX" string in the try-again-later page
[17:29] <jam> but if you missed it that is ok
[17:29] <jam> mentioning that mp's are timing out is still useful
[17:30] <vila> jam: the pages are long gone
[17:30] <jam> vila: sure. Robert is pushing hard on lp performance, and trying to get that into the culture
[17:30] <jam> so expect some teething
[17:30] <vila> I thought the OOPS were reported to devs anyway, I didn't think I should poke especially for transient ones
[17:30] <lifeless> vila: for future ref' please make sure there is a bug with the oops number in it.
[17:30] <jam> vila: they get 100s of oops per day
[17:30] <lifeless> robots cause oopses
[17:30] <jam> unfortunately
[17:30] <lifeless> but robots don't file bug
[17:30] <lifeless> s
[17:30] <vila> lifeless: ok
[17:31] <jam> having poked at the code recently
[17:31] <jam> there are quite a few bits that are doing big scans and pulling out only a row or two
[17:31] <jam> which after the data is in memory, aren't that bad
[17:31] <jam> which are hard to push hard on
[17:36] <jam> btw vila, thanks for giving me access to saw, it means I can test meliae on a 64-bit platform easily :)
[17:36] <vila> jam: keep in mind I'll shut it down Thursday
[17:37] <jam> vila: for good? or just for a while?
[17:37] <jam> anyway, probably heading out to dinner now. Have a good evening
[17:37] <vila> jam: just during my vacations :)
[17:37] <vila> jam: you too !
[18:23] <adiroiban> Hi, any idea why I get - "wpad://": No host component
[18:23] <adiroiban> this is on a bzr-svn branch
[18:23] <adiroiban> and yesterday I was able to work on that branch
[18:24] <jelmer> adiroiban: Hi
[18:25] <jelmer> adiroiban: That's odd - can you paste a traceback?
[18:25] <jelmer> adiroiban: is "wpad://" part of a URL you're working with?
[18:25] <adiroiban> no
[18:25] <adiroiban> the url is http://adi@svn.roiban.ro/project
[18:26] <Meths> On windows?
[18:26] <adiroiban> i tried bzr push http://adi@svn.roiban.ro/project
[18:26] <adiroiban> but same result
[18:26] <jelmer> adiroiban: a backtrace would be useful - if you don't get one on the command-line -Derror should help.
[18:28] <adiroiban> http://paste.ubuntu.com/466561/
[18:29] <adiroiban> I am now on Karmic with python 2.6 as default python version
[18:32] <jelmer> Any proxies involved?
[18:32] <lathiat> I am guessing that you have set a proxy in the Ubuntu settings
[18:33] <lathiat> which gets imported into the shell variables, go
[18:33] <lathiat> export -a |grep wpad
[18:33] <lathiat> sorry just
[18:33] <lathiat> export|grep wpad
[18:33] <adiroiban> jelmer: yep.
[18:33] <adiroiban> not sure who has defined that variable
[18:33] <lathiat> if you set it in ubuntu proxy settings theres something in the gnome session thing that sets it
[18:35] <adiroiban> thanks for the help. That was the problem. Web Proxy Autodiscovery Protocol was somehow set in gnome.
[18:37] <jelmer> makes for one hell of a confusing error though :-/
[18:37] <lifeless> hey jelmer, thanks for your note.
[18:37] <lifeless> are you back home ?
[18:37] <jelmer> hi lifeless
[18:38] <jelmer> lifeless: yep, got back late on Sunday
[18:38] <lifeless> cool
[18:38] <jelmer> are you still in Europe or just jetlagged ? :-)
[18:38] <lifeless> #launchpad-dev on this network might be worth adding to your joinlist
[18:38] <lifeless> in prague
[18:38] <jelmer> lifeless: I'm there actually, as rinze
[18:38] <lifeless> why not as jelmer ?
[18:39] <jelmer> I use two different IRC clients these days, in an attempt to keep work and private stuff separate
[18:39] <lifeless> ah
[18:39] <GaryvdM> Hi lifeless and jelmer
[18:39] <lifeless> hi GaryvdM
[18:39] <GaryvdM> How was the sprint?
[18:39] <jelmer> 'evening Gary
[18:39] <lifeless> GaryvdM: great
[18:40] <GaryvdM> lifeless: Good to hear.
[19:29] <GaryvdM> Hi mgz.
[19:32] <alkisg> Hi, can I tell bzr to ignore *.dcu but still clear them with bzr clean-tree?
[19:33] <GaryvdM> alkisg: Use bzr clean-tree --ignore ?
[19:33] <GaryvdM> sorry bzr clean
[19:33] <GaryvdM> sorry bzr clean-tree --ignored
[19:33] <alkisg> Thank you GaryvdM, that looks to be what I want.
[21:47] <mgz> hey GaryvdM if you're still up. I'll give your 2.2b4 installer a go.
[21:50] <stupenrose> Hi everyone.  I'm migrating some svn stuff to bzr using bzr-svn.  I'm running into a problem with a few of my svn branches.  Basically, I get an error like so:
[21:50] <stupenrose> stu@ruth:/home/stu# bzr branch http://my-svn-server.com/project-name/trunk
[21:50] <stupenrose> bzr: ERROR: The branch http://my-svn-server.com/project-name/trunk has no revision None
[21:51] <stupenrose> Anyway, I found some old bugs that seemed to match my symptoms, but they appear to have been fixed.  https://bugs.launchpad.net/bzr-svn/+bug/233964  https://bugs.launchpad.net/bzr-svn/+bug/295284 https://bugs.launchpad.net/bzr-svn/+bug/364416
[21:52] <stupenrose> running "bzr --version" gives:
[21:52] <stupenrose> Bazaar (bzr) 2.1.1
[21:52] <stupenrose>   Python interpreter: /usr/bin/python 2.6.5
[21:52] <stupenrose>   Python standard library: /usr/lib/python2.6
[21:52] <stupenrose>   Platform: Linux-2.6.33.5-rscloud-x86_64-with-Ubuntu-10.04-lucid
[21:52] <stupenrose>   bzrlib: /usr/lib/python2.6/dist-packages/bzrlib
[21:52] <stupenrose>   Bazaar configuration: /root/.bazaar
[21:52] <stupenrose>   Bazaar log file: /root/.bzr.log
[21:52] <stupenrose> Copyright 2005-2010 Canonical Ltd.
[21:52] <stupenrose> http://bazaar-vcs.org/
[21:52] <stupenrose> bzr comes with ABSOLUTELY NO WARRANTY.  bzr is free software, and
[21:52] <stupenrose> you may use, modify and redistribute it under the terms of the GNU
[21:52] <stupenrose> General Public License version 2 or later.
[21:52] <stupenrose> Bazaar is part of the GNU Project to produce a free operating system.
[21:53] <stupenrose> Anybody else run across this?
[21:56] <mgz> if noone who knows bzr-svn shows up shortly, file a bug with the full traceback from .bzr.log and a link to your svn server if it's public
[21:57] <stupenrose> ok.  I'm working through the 'file a bug' wizard now.
[22:08] <jelmer> stupenrose, hi
[22:08] <stupenrose> howdy!
[22:08] <jelmer> stupenrose: what version of bzr-svn?
[22:08] <stupenrose> lemme see...
[22:09] <stupenrose> according to 'bzr plugins': svn 1.0.2
[22:10] <knittl> how are revids in bzr calculated
[22:11] <jelmer> knittl: They're globally unique per revision
[22:12] <jelmer> knittl: How they're generated depends on the way the commit is created
[22:12] <jelmer> knittl: if they're native commits made by "bzr commit" they're pseudorandom (formed from email-address, timestamp and randomized string)
[22:13] <toabctl>  i downloaded a package with "bzr branch lp:ubuntu/xf86-input-wacom" , changed the package to a new upstream version and want to push th package now back to launchpad and send a merge request. how can i push the package to launchpad?
[22:13] <jelmer> knittl: commits imported from bzr-svn for example use the branch path, repository uuid and revision number
[22:13] <knittl> aha. ok
[22:14] <knittl> so no hashing?
[22:14] <knittl> like 'identical' commits will give the same revid
[22:14] <jelmer> knittl: Hashes for each revision are stored but they are not used to address the commit
[22:15] <jelmer> only for integrity checking
[22:15] <jelmer> (hashes are bound to a particular serialization of commits)
[22:15] <knittl> i see. thanks
[22:46] <stupenrose> mgz: you mentioned including the full traceback from ."bzr.log" ... I'm not seeing such a file.  In my case, it fails before the branch is fully created, so there isn't really a .bzr directory.  I do have an assosciated repo dir, but I don't see such a log there either.  What am I missing?
   Bazaar log file: /root/.bzr.log
[22:48] <stupenrose> ah, I see.  thanks.
[22:48] <mgz> if you don't have write access to that location, set BZR_HOME to somewhere you do, and run the attempt again
[22:48] <mgz> though, jelmer is the right person to talk to if you can get his attention again
[22:48] <stupenrose> roger that.
[22:49] <stupenrose> jelmer: should I file a bug for this one?
[22:49] <jelmer> stupenrose, does your repository contain any revisions created by bzr-svn?
[22:51] <stupenrose> I believe so.  If you're asking whether I've pushed commits out to svn using bzr: yes.
[22:53] <stupenrose> If you're asking whether my /bzr/ repository hosts bzr-svn branches, the answer is also yes.  Though, as far as that goes, I've tried branching these problem branches without using my bzr repo, and the result is the same.
[22:54] <jelmer> stupenrose: please file a bug
[22:54] <stupenrose> ok.  will do.  thank you for your help.
[22:54] <jelmer> stupenrose: it would be useful to have the full backtrace though, that might require commenting out some code in bzrlib/builtins.py
[22:55] <stupenrose> does this look like it is full enough?:
[22:55] <stupenrose> Tue 2010-07-20 16:29:03 -0400
[22:55] <stupenrose> 0.038  bazaar version: 2.1.1
[22:55] <stupenrose> 0.038  bzr arguments: [u'branch', u'http://svn.cmaxdev.com/fortress/trunk', u'test1234']
[22:55] <stupenrose> 0.044  looking for plugins in /root/.bazaar/plugins
[22:55] <stupenrose> 0.044  looking for plugins in /usr/lib/python2.6/dist-packages/bzrlib/plugins
[22:55] <stupenrose> 0.133  encoding stdout as sys.stdout encoding 'UTF-8'
[22:55] <stupenrose> 0.168  bzr-svn: using Subversion 1.6.6 ()
[22:55] <stupenrose> 1.808  Traceback (most recent call last):
[22:55] <stupenrose>   File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 853, in exception_to_return_code
[22:55] <stupenrose>     return the_callable(*args, **kwargs)
[22:55] <stupenrose>   File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 1055, in run_bzr
[22:55] <stupenrose>     ret = run(*run_argv)
[22:55] <stupenrose>   File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 661, in run_argv_aliases
[22:55] <jelmer> stupenrose: please don't paste lots of lines of text but use pastebin instead next time :-)
[22:56] <stupenrose> sorry: I be IRC newbie.
[22:56] <jelmer> stupenrose: In particular the full error message - the actual revision id rather than "None"
[22:56] <stupenrose> (it all comes through on one line with jabber)
[23:00] <stupenrose> I've got builtins.py up in vim: any hints as to what needs to be commented-out?
[23:01] <jelmer> in the cmd_branch class, there should be a place where we catch NoSuchRevision
[23:01] <jelmer> and instead we raise a different revision (BzrCommandError I think)
[23:01] <jelmer> just re-raise the original exception
[23:01] <stupenrose> ok
[23:01] <jelmer> s/different revision/different exception/
[23:10] <stupenrose> ok.  I think I did it right.  this look better? http://pastebin.com/hNuLCDDi
[23:10] <LeoNerd> Anyone happen to know if bzr-git supports 'bzr branch URL' from any branch other than the head?
[23:11] <LeoNerd> I'm finding docs rather thin on the ground, also
[23:12] <jelmer> stupenrose, yep, thanks
[23:12] <stupenrose> cool. okey doke, I'll include that with the bug.  thanks again!
[23:12] <jelmer> LeoNerd: It does, but bzr doesn't have a UI for addressing such branches yet
[23:12] <LeoNerd> Ooh... hmmm.. I thought I'd try   bzr branch http://.../foo.git/branchname   but that didn't work
[23:13] <LeoNerd> Any way to abuse it into doing so, or am I ought of luck here?
[23:13] <jelmer> LeoNerd: http://.../foo.git,branchname should work in the future (bzr 2.3 hopefully)
[23:13] <LeoNerd> Ahhh
[23:20] <stupenrose> FYI, bug entered: https://bugs.launchpad.net/bzr-svn/+bug/607986