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