[00:17] <lifeless> yay I just got
[00:17] <lifeless>   File "/home/robertc/source/baz/bzr-test-fixes/bzrlib/transport/ssh.py", line 605, in recv
[00:17] <lifeless>     return os.read(self.proc.stdout.fileno(), count)
[00:17] <lifeless> OverflowError: signed integer is greater than maximum
[00:17] <lifeless> jml: ^ :(
[01:04] <jonnydee> hi, can anyone tell me how to configure ~/.bazaar/authentication.conf for a sftp account?
[01:04] <jonnydee> I've alread configured another location which just uses ftp -- and it works.
[01:05] <jonnydee> but with sftp I'm asked for the password even if I provide one in the config file...
[01:06] <lifeless> for sftp you should use your ~/.ssh/config file
[01:07] <jonnydee> and the same way like in the ftp case is not supported?
[01:07] <lifeless> right
[01:07] <lifeless> sftp authentication is done outside of bzr
[01:07] <lifeless> bzr has no access to the protocol
[01:08] <jonnydee> ah...ok, I see...
[01:08] <jonnydee> thanks again for your help, lifeless :)
[02:14] <markh> how do I update my checkout to an earlier revision of the branch?  I was surprised to find no '-r' option to 'bzr up' nor to bind.
[02:15] <beuno> markh, I don't think you can, since it's bound to the other branch
[02:15] <beuno> you could branch off of it at that revision
[02:15] <markh> so update the branch, then up the co?
[02:15] <pygi> markh, bzr pull --overwrite -r 8214
[02:15] <pygi> perhaps :p
[02:16] <pygi> markh, helped? :)
[02:16] <beuno> markh, you want both branches to be at that revno?  reverted?
[02:17] <markh> no, just experimenting.  I think I was missing I can still use "pull" on a checkout though - thanks
[02:17] <markh> ie, want to experiment with how the code behaves at an earlier revno
[02:17] <beuno> I think generally you'd branch -r off of it
[02:19] <markh> So what's the difference between "pull" (with no args) and "up" once you have a checkout?
[02:20] <markh> (I'm working with checkouts on a test machine, with the branches being on the main dev machine)
[02:20] <pygi> bzr pull is nicer in some cases :)
[02:21] <markh> heh :)  what's the conceptual difference?
[02:21] <pygi> well, anyway, they have different use-cases
[02:21] <pygi> bzr up will do a merge
[02:21] <pygi> bzr pull won't
[02:22] <markh> I think I need to experiment a little more with checkouts
[02:23] <pygi> :)
[02:24] <markh> I think some of the docs might need to tone down how checkouts are somwhat similar to working with svn :)
[02:27] <markh> So when I do a checkout, is a "branch" created locally?
[02:28] <LeoNerd> Yes, except if it's a "lightweight checkout"..
[02:30]  * fullermd blinks.
[02:30] <fullermd> Pull changes a branch.  Update updates a working copy.
[02:31] <fullermd> Using pull in a checkout to adjust your working copy is totally not what you want to do...
[02:53] <jonnydee> lifeless: sorry to ask again. I can login to my remote server using ssh public key authentication. now how does the authentication.conf have to look like for sftp access...? (btw I need to log in with another user name than I have locally, so would like to make bazaar use the one specified in the authentication.conf)
[02:55] <jonnydee> with other words: I would like to use "sftp://host/path/to/repo" and and bazaar should use "sftp://remoteuser@host/path/to/repo"
[03:17] <bob2> sftp happens after the ssh login has occured
[03:17] <bob2> configure .ssh/config to use the right username
[03:26] <bob2> (ie add a "Host yourhostname\nUser youruser" section to it)
[03:31] <jonnydee> ok, it seems like bazaar is not able to insert the username specified in the config into the url. So it's indeed only possible by doing your suggested approach... I see... Thanks a lot :)
[03:32] <markh> fullermd: right - thanks for the clarification
[03:32] <markh> so what is the best way to update my co to a specific revision of the branch it is checked out from?
[03:33] <fullermd> There isn't one.
[03:33] <fullermd> You can use revert to alter the tree state, but as far as your co is concerned it's still $OLD_HEAD, just with a crapload of changes waiting to be committed.
[03:34] <markh> right - that will probably do for my purposes.  But it seems an omission - is that by design/restriction, or a feature yet to be implemented?
[03:38] <jonnydee> markh: maybe you could first branch the requested revision and then do a switch to the newly created branch. but it's not that comfortable -- I know...
[03:42] <fullermd> bug 45719
[03:43] <jonnydee> I mean like  so "bzr branch -r REV PATH_OF_NEW_BRANCH" and then "bzr switch ﻿PATH_OF_NEW_BRANCH"
[03:44] <fullermd> According to that status, it's set for 0.13   :p
[03:44] <jonnydee> this should leave you with a branch of the required revision in the current directory... but I've not tried it yet
[03:49] <markh> jonnydee: yeah, that might work, thanks.  i just wanted to run a quick experiment with an earlier revno, so 'revert -r' worked for me in this case.
[03:52] <markh> fullermd: sad joke indeed :)
[03:55] <jonnydee> maybe we shoulg nominate this bug for bzr.dev? or 1.7?
[04:19] <markh> its not clear from the bug what the "quality issues" John referred to are, and launchpad is helpfully giving "Internal Server Error" trying to view a revision of the branch
[04:26] <fullermd> Unfortunately, it has to "update -r" to view the branch, see...
[04:28] <markh> heh :)
[04:34] <mwhudson> markh: what url?
[05:25] <markh> mwhudson: what url for what?
 its not clear from the bug what the "quality issues" John referred to are, and launchpad is helpfully giving "Internal Server Error" trying to view a revision of the branch
[05:26] <mwhudson> markh: ^ that one
[05:26] <markh> oh - internal error?  any of the recent revisions shown at https://code.launchpad.net/~jameinel/bzr/update-r
[05:27] <mwhudson> huh
[05:27] <markh> eg, http://bazaar.launchpad.net/~jameinel/bzr/update-r/revision/2012
[05:27] <pickscrape> mwhudson: FYI I pushed up a new version of the breadcrumbs branch today. Added to other pages, moved the code to a shared location etc
[05:28] <mwhudson> markh: wow, that branch is sure confusing loggerhead
[05:30] <mwhudson> $ curl http://bazaar.launchpad.net/~jameinel/bzr/update-r/.bzr/branch/last-revision
[05:30] <mwhudson> 0 null:
[05:30] <mwhudson> errr
[05:31] <markh> he
[05:31] <mwhudson> i _guess_ the branch was mirroring ok
[05:31] <mwhudson> jam updated all his branches to packs
[05:32] <mwhudson> and the remirroring failed
[05:32] <mwhudson> still, loggerhead shouldn't explode so violently
[05:32] <mwhudson> ah yeah
[05:32] <mwhudson> http://bazaar.launchpad.net/~jameinel/bzr/update-r/changes
[05:32] <mwhudson> ^ ok
[05:32] <mwhudson> http://bazaar.launchpad.net/~jameinel/bzr/update-r/files
[05:32] <mwhudson> ^ not ok
[05:32]  * mwhudson files a bug
[05:42] <markh> bzr tells me the branch is empty
[05:43] <mwhudson> it is, yes
[05:43] <mwhudson> we really need to implement useful stacking for mirrored branches to save jam's adsl some abuse :)
[05:44] <markh> right - its empty as the remirroring failed
[06:30] <chandlerc> hrm...
[06:30] <chandlerc> thoughts on this bzr-svn error:
[06:30] <chandlerc> SubversionException: ("PROPFIND of '/svn/!svn/bc/136/parser/trunk': SSL negotiation failed: SSL error: parse tlsext (https://inc.googlecode.com)", 175002)
[06:33] <mwhudson> googlecode being a bit random maybe?
[06:35] <chandlerc> always
[06:35] <chandlerc> just wondering what this in particular oddity is
[06:35] <chandlerc> i'm moderately stuck with google code for several projects.
[06:37] <tacone> chandlerc: I did export from google code.
[06:37] <chandlerc> this is on a branch
[06:37] <chandlerc> into a shared repo
[06:39] <mwhudson> well, if it's a read-only thing
[06:39] <mwhudson> you can at least do it over http:// and avoid ssl randomness
[06:39] <chandlerc> nah, trying to do an https branch for future writes
[06:39] <mwhudson> um
[06:39] <chandlerc> =/
[06:39] <chandlerc> yea
[06:39] <mwhudson> you can do the pull over http
[06:40] <mwhudson> and push over https
[06:40] <chandlerc> true
[06:40] <chandlerc> will try that
[07:06] <chandlerc> oh fun
[07:06] <chandlerc> % bzr push svn+https://inc.googlecode.com/svn/parser/trunk
[07:06] <chandlerc> The svn+ syntax is deprecated, use https://inc.googlecode.com/svn/parser/trunk instead.
[07:06] <chandlerc> zsh: segmentation fault  bzr push svn+https://inc.googlecode.com/svn/parser/trunk
[07:09] <percious> anyone home?
[07:10] <percious> looking for a bzr-svn expert if there is one
[07:12] <percious> evening
[07:12] <chandlerc> join the crowd, i'm battling it as wel
[07:34] <mwhudson> chandlerc: oo
[07:38] <percious> ehem
[07:38] <percious> chadmiller: battleing bzr-svn ???
[07:38] <percious> :q
[07:43] <percious> chandlerc:  also having issues with bzr-svn?
[07:43]  * percious compiles svn 1.6....
[07:48] <tacone> percious: I had
[07:49] <percious> tacone: mac os leopard?
[07:49] <tacone> percious: ubuntu hardy.
[07:49] <percious> maybe this is just a version thing
[07:49] <tacone> plugin and bzr versions, right ?
[07:49] <percious> yeah
[07:49] <percious> svn = 1.6
[07:50] <percious> bzr = 1.6r3
[07:50] <percious> *rc3
[07:50] <tacone> I didnt' tried 1.6, but I was somewhere in the middle, and had to downgrade to use bzr-svn
[07:50] <tacone> it was a month ago, though, so I guess svn version could work.
[07:51] <percious> SubversionException: ("Unrecognized URL scheme
[07:51] <percious> owns me
[07:52] <percious> downgrade svn?
[07:52] <percious> i have tried 1.5.1 (universal installer) and 1.5.1 from svn repo
[07:52] <tacone> percious: no, I just used another version from the repositories
[07:52] <percious> what version of svn are you using?
[07:52] <tacone> uhm
[07:52] <tacone> let me check
[07:52] <percious> svn --version
[07:52] <percious> bzr --version
[07:53] <tacone> wait
[07:53] <percious> yep
[07:53] <tacone> svn, version 1.4.6 (r28521)
[07:54] <percious> wow, that is specific
[07:54] <percious> thanks :)
[07:54] <tacone> Bazaar (bzr) 1.3.1
[07:54] <tacone> bzr-svn version: 0.4.9-1
[07:54] <percious> you the man
[07:55] <percious> let me try those
[07:55] <tacone> uhm, yes. keep in mind bzr 1.3.1 is *old* so you are likely to use that only for exporting your branch to bzr.
[07:56] <percious> exporting my branch?
[08:00] <percious> wait, 1.3.1?
[08:18] <percious> Installed Subversion version does not have updated Python bindings. See the bzr-svn README for details
[08:18] <tacone> percious: yes
[08:18] <percious> ug
[08:18] <percious> the universal for svn sucks...
[08:19] <percious> building from source...
[08:19] <tacone> lol
[08:20] <tacone> percious: this is the readme for that version of bzr-svn http://paste.pocoo.org/show/82441/
[08:20] <tacone> percious: you need the python bindings, more than svn itself
[08:21] <percious> yeah
[08:21] <percious> im working on it
[08:21] <tacone> lol ok
[08:21] <percious> i had it going for svn 1.5
[08:21] <tacone> percious: is you have an ubuntu hardy vm it could work out of the box.
[08:21] <percious> right, on my mac
[08:21] <percious> im in love with mac os
[08:22] <percious> so linux is not happening
[08:22] <tacone> a virtual machine I mean.
[08:22] <mwhudson> um
[08:22] <mwhudson> if you're using a version of bzr-svn that needs the subversion python bindings
[08:22] <percious> yay :) http://svn.collab.net/repos/svn/tags/1.4.6/
[08:22] <mwhudson> get a newer bzr-svn
[08:22] <tacone> mwhudson: he had problems with the recent versions, so he tried to downgrade.
[08:22] <mwhudson> tacone: oh
[08:22] <percious> ive tried like 100 different versions at this point :)
[08:22] <percious> im going with what tacone has
[08:23] <tacone> mwhudson: I pointed him to the standard hardy versions, that worked for me.
[08:23] <mwhudson> well, you're pretty unlikely to have _fewer_ problems with older version
[08:23] <mwhudson> especially building on os x...
[08:23] <percious> agreed
[08:23] <percious> but I need to find a baseline to work from
[08:23] <tacone> mwhudson: I had problem on hardy using bzr repository and bzr-svn because of versions conflicts
[08:23] <percious> ls
[08:23] <mwhudson> building the subversion python bindings on os x is seriously hard
[08:24] <mwhudson> i managed it once a few years ago
[08:24] <mwhudson> on ppc
[08:24] <tacone> mwhudson: :(
[08:24] <percious> intel here
[08:24] <mwhudson> and had to install a specific micro-version of swig, install a different libtool, etc
[08:25] <percious> following directions here: http://bazaar-vcs.org/BzrForeignBranches/Subversion
[08:25] <mwhudson> percious: what problems did you have with the newest versions of bzr-svn and bzr ?
[08:25] <percious> um
[08:25] <percious> somethign about it not understanding http in the url
[08:26] <percious> SubversionException: ("Unrecognized URL scheme for 'http: ... pwns me
[08:26] <mwhudson> (i had it sort of working today, it broke, but because of problems in the remote repo, not in the software)
[08:26] <percious> compiling svn for the 10th time :)
[08:26] <mwhudson> argh!
[08:26] <percious> at least I am getting paid
[08:27] <mwhudson> hm, not seen that exception before
[08:27] <percious> there is a ticket for it
[08:27] <percious> i put a comment in
[08:27] <percious> i am evaluating this for my client
[08:27] <percious> we have some weird development practices
[08:28] <percious> want to make things better using distributed versioing
[08:28] <percious> but keep the svn repo
[08:28] <percious> bzr seems a perfect fit
[08:29] <percious> i might look at svn-git as well
[08:29] <mwhudson> mm
[08:29] <percious> but the commands aren't as nice
[08:29] <mwhudson> which is the bug?
[08:29] <percious> hang on, ill look it up for you
[08:29] <mwhudson> git-svn is a bit different aiui
[08:30] <percious> https://bugs.launchpad.net/bzr-svn/+bug/80553
[08:31] <mwhudson> um, that doesn't look very similar to me
[08:31] <percious> hang on
[08:32] <percious> thats not it
[08:32] <percious> https://bugs.launchpad.net/bzr-svn/+bug/211683
[08:34] <mwhudson> percious: oh, you have a checkout?
[08:34] <mwhudson> i'm not sure bzr-svn supports them
[08:34] <percious> check out?
[08:34] <percious> what do you jmean?
[08:35] <mwhudson> percious: alternative (and probably better) phrasing is a 'bound branch'
[08:35] <percious> hmm
[08:35] <percious> i did an svn copy trunk branches/my_new_branch
[08:35] <mwhudson> a branch where changes you commit go to the central repository
[08:35] <percious> and then i did a bunch of work in there
[08:36] <percious> and i cannot commit, because the internet is down
[08:36] <percious> so i thought... bzr to the rescue
[08:36] <mwhudson> well
[08:36] <percious> local commits...
[08:36] <mwhudson> right
[08:36] <percious> then push to the server when all happiness
[08:36] <percious> :)
[08:36] <percious> bad assumptions?
[08:36] <mwhudson> that command line shows that you are not doing a local commit though
[08:36] <percious> :-/
[08:36] <percious> what should I be typing?
[08:37] <mwhudson> well, i think
[08:37] <percious> bzr ci doesnt do a local commit?
[08:37] <mwhudson> oh hang on
[08:37] <mwhudson> you're running this in a svn checkout?
[08:37] <percious> yeah
[08:37] <mwhudson> aaah
[08:37] <percious> so, shouldnt bzr-svn do a local commit?
[08:38] <mwhudson> i don't think you can do a local commit in this situation
[08:38] <percious> oh :(
[08:38] <mwhudson> you need to get a bazaar branch before you can do that
[08:38] <percious> i am confused then
[08:38] <percious> ok
[08:38] <mwhudson> so bzr get http://svn/url
[08:38] <percious> which probably requires me to get at the server, which is inaccessable
[08:38] <percious> yeah
[08:38] <mwhudson> yeah :/
[08:38] <percious> im SOL
[08:38] <percious> but!
[08:38] <percious> in the future I can bzr everything and be all happy
[08:39] <mwhudson> roughly speaking, bzr doesn't have anywhere to store the new commit
[08:39] <mwhudson> in a svn tree
[08:39] <percious> (like, tomorrow) when the internet is working at the office 600 miles away
[08:39] <mwhudson> yes, if you had somehow prepared for the internet going down...
[08:39] <percious> why doesnt bzr just make their own place?
[08:39] <percious> big storm in denver this weekend
[08:39] <percious> affected ABQ too i guess (where my client resides)
[08:40] <mwhudson> i'm not totally sure
[08:40] <percious> they only have a dish for the internet :-/
[08:40] <mwhudson> it may also be the case that bzr needs to have access to the history of the svn repo to be able to commit
[08:40] <percious> isnt that in the .svn files though?
[08:40] <mwhudson> jelmer would be the man who would know
[08:41] <mwhudson> but i guess he's very firmly asleep
[08:41] <percious> well, im evaluating this technology anyway...
[08:41] <percious> which will take place tomorrow in the rain as well
[08:41] <mwhudson> percious: no, the .svn directories only contain data about the current state of the tree, there's no history there
[08:41] <percious> ok 1.4.6 is in
[08:41] <percious> and bzr 1.3.1
[08:41] <percious> and bzr-svn 0.4.9
[08:42] <mwhudson> very retro :)
[08:42] <tacone> percious: I fear that those versions could not solve your problem. I didn't tried commit, I just converted my repo to bzr and goodbye svn
[08:43] <percious> ah
[08:43] <tacone> mwhudson: that's the current hardy default repositories versions :-(
[08:43] <percious> wow, fun errors now
[08:43] <mwhudson> tacone: yeah
[08:43] <tacone> percious: very sorry, I guess I misunderstood your problem, very sorry. I thought you just wanted to convert your repositories.
[08:43] <percious> no worries
[08:44] <percious> i just want to be able to work remotely
[08:44] <mwhudson> percious: that you get such incomprehensible errors would count as a bug
[08:44] <percious> i guess...
[08:44] <percious> i dunno
[08:44] <percious> i think user error
[08:44] <percious> im basically a bzr ignoramous, despite wearing a bazaar t-shirt for the last 2 years
[08:44] <percious> (not continuously)
[08:44] <mwhudson> :)
[08:44] <tacone> mwhudson: that could be (old)bzr-svn rather (old)bzr errors. I don't think anyone is going to fix those versions.
[08:45] <percious> so what versions of things do you recommend
[08:45] <percious> ?
[08:45] <percious> so when I get things working tomorrow on the internet side i can actually achieve what I want
[08:45] <mwhudson> tacone: https://bugs.edge.launchpad.net/bzr-svn/+bug/211683/comments/5 isn't
[08:45] <mwhudson> percious: probably the newest of everything
[08:45] <tacone> percious: when the bzr tshirt gets dirty just run bzr pull lp:bzr-tshirt
[08:45] <percious> indeed
[08:46] <percious> ide like a new t-shirt
[08:46] <mwhudson> percious: maybe a released version of svn would be a good idea
[08:46] <percious> and wing is supposed to send me one too...
[08:46] <percious> well, there are lots of released versions
[08:46] <percious> 1.5.1 is already checked out on my machine....
[08:46] <tacone> mwhudson: I guess I misunderstood again :). I thought you were referring to 1.3.1.
[08:46] <percious> (and compiled)
[08:46] <percious> im a bad-ass at compiling svn now
[08:47] <mwhudson> percious: that should be good then
[08:47] <mwhudson> percious: my commiserations :)
[08:47] <percious> lemme go get that installed
[08:47] <percious> ima have to look that word up
[08:47] <percious> anything over 10 letters is a bit much for me at 2am
[08:48] <mwhudson> heh
[08:48]  * mwhudson goes to cook dinner
[08:49]  * percious might need sleep soon
[08:50]  * tacone dives into python (and needs sleep too)
[08:51] <percious> 1.5.1 is hating me
[08:54] <percious> ok, where does svn install it's binary
[08:54] <tacone> "which svn" could work.
[08:54] <percious> i knwo
[08:54] <tacone> I don't know macosx though.
[08:54] <tacone> oh
[08:54] <percious> but there are like 3 svns all over the place now
[08:55] <percious> and they are seemingly pointing to each other in various ways
[08:55] <percious> (a tangled web we weave)
[09:00] <percious> hmm, now I get a different error
[09:01] <percious> UnsupportedFormatError
[09:06] <percious> UnsupportedFormatError: This client is too old to work with working copy '/Users/percious/clients/clearwired/mvpdev/src/mvp2_root/branches/coop_resource_ass'; please get a newer Subversion client
[09:07] <percious> it'd be nice if we knew which version would work
[09:08] <tacone> percious: is that the path of a repository or a checkout ?
[09:08] <percious> path of a co
[09:08] <percious> weirdness though
[09:08] <tacone> I'd try to checkout again with the version of subversion you have installed now
[09:09] <percious> yeah, that'd be a great option
[09:09] <percious> if the network wasn't down
[09:09] <tacone> oh.
[09:09] <percious> im somehow thinking bazaar is using the wrong version of svn
[09:09] <percious> ;-)
[09:10] <percious> i think i need sleep to function tomorrow.
[09:10] <percious> this was a fun learning experience though
[09:10] <tacone> :) see you again
[09:10] <percious> i have one patch to submit
[09:10] <tacone> oh, well, I am not a bzr dev, so..
[09:11] <percious> no worries mate
[09:11] <percious> that is what launchpad is for :)
[09:11] <tacone> yes, launchpad's nice.
[09:11] <percious> ide like to see TG on there
[09:11] <tacone> tg = ?
[09:11] <percious> Turbogears
[09:12]  * percious is a TG dev
[09:12] <tacone> oh
[09:12] <tacone> you'd like to make tg hosted on launchpad ?
[09:13] <percious> ide like to see it happen
[09:13] <percious> we use SVN/moinmoin/trac
[09:13] <percious> recently, we started using sphinx for docs
[09:13] <tacone> launchpad doesn't have a wiki on it's own yet. I filed a bug for that. they're considering.
[09:13] <percious> but there is no feedback...
[09:13] <percious> (no feedback on sphinx)
[09:14] <tacone> lp is great for all the rest. and bzr rocks big time.
[09:14] <tacone> I love it.
[09:14] <percious> sphinx is nice for semi-automated api docs: http://showmedo.com/videos/video?name=2910020&fromSeriesID=291
[09:15] <percious> i want to put a wsgi wrapper on it to create a commenting system
[09:15] <percious> then it will really work well
[09:15] <tacone> I am new to python development. I don't know sphinx
[09:15] <tacone> lol, it's you ?
[09:15] <percious> :)
[09:15] <tacone> I saw the username on the terminal :)
[09:15] <percious> my agile series
[09:16] <percious> in the back there is longs peak
[09:16] <percious> ;-)
[09:16]  * tacone is making his first steps with python unit testing.
[09:17] <percious> have fun with it
[09:17] <percious> certainly makes programming less stressful
[09:17] <percious> nose rocks
[09:17] <tacone> nose = ?
[09:18] <percious> check out the video :)
[09:18] <percious> test discovery
[09:18] <percious> and more
[09:18] <tacone> I watching it already
[09:18] <percious> anyway, i gotta knock off before I wake up with keyboard-face
[09:18] <percious> see you tomorrow prolly
[09:19] <tacone> ok, bye
[09:19] <tacone> see you
[15:50] <robtaylor> Ok, Say i have a project that's grown large and I want to split in into seperate repos. How would i go about that in bzr?
[15:54] <radix> robtaylor: one way to do it is to create two branches, and remove one set of files from one branch and the other set of files from the other
[15:57] <robtaylor> radix: hmm, sounds sensible :)
[15:58] <radix> of course, that means both branches have all the history of the shared development
[15:58] <robtaylor> thats really what you want though, isn't it ?
[15:58] <radix> which, sometimes, isn't what you want (like if you're splitting a chunk off of a proprietary project for release as open source, or if you're trying to prevent the history from growing too large)
[15:59] <robtaylor> oh ugh yeah
[15:59] <radix> I guess it's what you want :)
[15:59] <robtaylor> that's definitly history-rewriting time
[16:01] <Pieter> or if the other part is really large and you want to keep both repositories of sensible size
[16:14] <robtaylor> Pieter: is it possible to have a repo that just points to another repo for history before a certain point?
[16:16] <LarstiQ> robtaylor: s/repo/branch/ and the answer is yes with 1.6
[16:18] <LarstiQ> but that provides what you want I guess, you didn't actually mean revision garbage collection on repositories?
[16:24] <Jc2k> robtaylor: 'stacked branches' -> http://jam-bazaar.blogspot.com/2008/05/this-week-in-bazaar_29.html
[16:48] <robtaylor> Jc2k, LarstiQ: ah, yeah thats what i'm thinking of
[16:48] <robtaylor> thanks
[19:49] <luks> hmm
[19:49] <luks> blackbox.test_check.ChrootedCheckTests.test_check_missing_branch is either way too slow or hangs on my machine
[19:53] <luks> and blackbox.test_non_ascii diff tests fail :(
[19:55] <luks> actually, ALL blackbox diff tests fail
[19:56] <luks> oh
[19:56] <luks> it doesn't like my pager plugin, never mind
[22:37] <lifeless> beuno: / mwhudson: does loggerhead 1.6 need bzr 1.6?
[22:40] <thumper> lifeless: that's what it says (but I doubt it)
[22:42] <lifeless> thumper: it says 'for 1.6' not 'needs 1.6'
[22:43] <lifeless> could be either :/
[22:44] <beuno> lifeless, nope, I added the code for backwards compatibility
[22:44] <beuno> should work fine with 1.5, maybe even 1.4
[22:44] <beuno> not sure older than that
[22:47] <lifeless> did you test 1.4?
[22:48] <beuno> I was on 1.3.1 for quite a while, and, while I did get deprecation warnings, it still worked
[22:48] <lifeless> ;P
[22:48] <lifeless> ok
[22:48] <beuno> but no, I didn't test with anything other than 1.5 and 1.6  :)
[22:48] <lifeless> so, did you see my rendering issue yesterday?
[22:48] <beuno> rendering issue?  no.  The server at my office decided to go to sleep, so I lost my backlog
[22:49] <lifeless> diff - can't see the edge of lines
[22:50] <beuno> edge if lines?
[22:51] <lifeless> foo bar baz quux | foo baz bar quux
[22:51] <lifeless> but I see up to q
[22:51] <lifeless> unless I zoom/resize my browser window
[22:51] <lifeless> theres no scroll bar
[22:51] <beuno> huh, interesting
[22:52] <lifeless> http://bazaar.launchpad.net/~jml/subunit/split-right/revision/51
[22:53] <beuno> do you have font size set to something different than default?
[22:53] <lifeless> line 218
[22:53] <lifeless> no
[22:53] <lifeless> I see 'spli' as the last letters of the left hand size
[22:54] <lifeless> *side*
[22:54] <beuno> ah, yes. I can reproduce if I enlarge the font
[22:54] <sohail> hi, how can I undelete a directory in bzr?
[22:55] <lifeless> revert -r rev directoryname
[22:55] <sohail> I deleted it in revision 595
[22:55] <sohail> that didn't work
[22:55] <lifeless> oh
[22:55] <sohail> oh I should have done 594 shouldn't I
[22:55] <lifeless> yes
[22:55] <sohail> ok that worked :-)
[22:55] <sohail> thanks!
[22:55] <beuno> lifeless, I'll file a bug, thanks
[22:56] <lifeless> thanks
[22:58] <lifeless> the README doesn't talk about paste.deploy when behind apache
[22:58] <lifeless> is that no longer needed?
[22:58] <beuno> I'm not sure, that's mwhudson's terf really
[22:58] <lifeless> mwhudson: ping
[22:58] <lifeless> thumper: unless you know this one
[23:00] <mwhudson> lifeless: no, you still want paste deploy if you run behind apache
[23:00]  * mwhudson is not really here today
[23:00] <lifeless> mwhudson: ok
[23:00] <lifeless> mwhudson: FWIW the readme says what to do, but doesn't mention that
[23:01] <mwhudson> lifeless: serve-branches dtrt if paste deploy is importable
[23:01] <mwhudson> but yes, i guess documentation would be a good thing :)
[23:09] <percious> is it possible for bzr/svn installs to mess up my setuptools?
[23:15] <percious> ls
[23:17] <percious> ok, it is if anyone is wondering
[23:17] <percious> svn 1.5 breaks setuptools
[23:18] <percious> here is a thread on the subject: http://www.gossamer-threads.com/lists/trac/users/37446?page=last
[23:40] <meteoroid> percious: are you serious? that's a problem with svn?
[23:40] <percious> crazy, huh
[23:40] <percious> i guess the trunk of setuptools works
[23:40] <meteoroid> yah i'm having this problem with zc.buildout on a suse box
[23:40] <meteoroid> lol
[23:40] <meteoroid> interesting, maybe i can dev-egg it
[23:40] <percious> but installing the trunk of setuptools doesnt work until you revert to svn 1.4.6
[23:41] <meteoroid> lol
[23:58] <percious> of course our svn server is down, so I am SOL anyway...