[01:02] hello, everybody. could someone, please, give me link to good manual for setting up bzr server to work with it via bzr:/-protocol? === mw is now known as mw|out [01:36] quick question: how do I get the revno of the working-tree? [01:36] I'm trying to find a regression by checking out old revisions of a branch, and I want to confirm the revno of the current working tree [01:45] jfroy|work: revision-info? [01:49] That seems to give me the latest revno of the branch [01:49] e.g., gives me the revno of bzr log -r -1 [01:49] when a bzr st outputs a message stating my working tree is out of date [01:56] jfroy|work: according to bzr help version-info, it shows revision info of the tree [01:56] jfroy|work: you could do bzr update to get your tree up to date [01:56] indeed, thanks [01:57] no that's just the thing, I'm doing a regression analysis, and I wanted to make sure my tree was out of date (at a specific revision) [01:57] I'm trying to install bzr 1.9 on my web host, but getting a build error due to missing Python.h [01:57] How do I use this --allow-python-fallback that it recommends? [01:58] or where do I find an older version? [01:58] jfroy|work: maybe you can use lightweight checkouts to have different revisions of the tree around [01:59] n[ate]vw: I not an expert, but it looks like your server don't have the development files of python (headers, etc) [02:00] yeah, I'm assuming that's the problem, but the error diagnostic makes reference to this python fallback option [02:01] n[ate]vw: if it's a debian based distro, I'n sure a simple: apt-get install python-dev should solve the problem [02:01] but then I get "error: option --allow-python-fallback not recognized" [02:01] it's a shared host, so no can do [02:02] hmm, what version of python? [02:02] 2.5.1 [02:02] verterok: version-info worked fine [02:02] jfroy|work: great! :) [02:02] Although indeed, I am getting a bzr exception when trying to checkout if a tree already exits [02:02] I have to remove-tree, then co again, with a different revno [02:03] jfroy|work: you could do the co in different dirs :) [02:03] I don't really care to keep multiple trees [02:03] I mean, I could, I suppose [02:04] But I'm playing a game of "is it this one?" [02:04] hehe, ok. [02:04] n[ate]vw: could you pastebin the error? [02:05] and the command you are using? [02:06] verterok: http://pastebin.com/d61571c59 [02:07] (original command was 'python setup.py install --home ~/sw') [02:08] n[ate]vw: you could simply drop the source there, and bzr should "just work" (mileage may vary) [02:09] that's true, forgot about that option [02:12] * verterok bbiab === verterok is now known as verterok_ === jszakmeister|awa is now known as jszakmeister === jszakmeister is now known as jszakmeister|awa [12:42] Question: I am attempting to branch a googlecode project via bzr-svn, and although bzr-svn is downloading the branch information (such as commit logs), it is not actually downloading any code.. Any thoughts as to why? [12:44] it's not downloading the code at all (ie, the process has finished and no code was downloaded)? [12:45] luks: Correct [12:45] that's weird [12:45] how do you check that? [12:46] is "bzr branch http-addy-to-trunk" the correct command? [12:46] erm, minus a space, heh [12:46] luks: By looking in the directory and seeing zero code [12:46] in most cases, yes [12:46] Leefmc: what does `bzr info` say? [12:46] lemm rebranch it, one sec [12:46] I think you just have a branch without a working tree [12:47] ohh thats right [12:47] which `bzr checkout .` should fix [12:47] i forgot, if theres no working tree bzr wont show you code [12:47] that always trips me out. heh [12:47] hm, I wonder why? [12:48] My minds all fluxxed from bzr-svn hybrids heh. [12:48] bzr doesn't show you the code, your shell does [12:48] luks: Well, i ment that bzr physically hides the code, does it not? [12:48] Leefmc: no [12:48] Oh well, maybe thats not the problem then.. lemme bzr info [12:49] all bzr is interested in is the .bzr directory (in most cases) [12:50] the working tree matters only if you try to e.g. commit [12:50] i dont wanna paste it all, so what are you looking for specifically? there is a shared repository, a repository branch, and a parent related branch [12:50] but the branch, only has one directory in it, .bzr. The file system has zero code in it [12:50] try bzr checkout . [12:51] or bzr log [12:51] if bzr log list something, you just want to add the working tree [12:52] luks: Ah, you confused me before (or rather 4am with no coffee, confused me, more than likely) [12:52] luks: So bzr _does_ actually hide the code if you have no working tree [12:52] Leefmc: it doesn't hide it, it simply doesn't exist [12:52] ie, without a working tree, code is not visable on the file system [12:52] Leefmc: you can't hide something that doesn't exist :) [12:53] well, that's obvious [12:53] but the working tree is not hidden [12:53] luks: Well it must exist somewhere on it, because you can essentially download it from bzr when you checkout [12:53] Leefmc: no, bzr only knows the data to generate it [12:54] but it doesn't exist in the form of actual files [12:54] luks: Ah, well imo it still exists within bzr then haha, but now were splitting hairs :) [12:54] luks: Yea [12:54] luks: Anyway, thanks [12:54] luks: Have you delt with bzr-svn much? [12:54] I wonder how did you get into this situation, though [12:54] luks: No working tree? [12:55] yes [12:55] it's not the default option [12:55] do you have a repository created with `bzr init-repo --no-trees` or something? [12:55] luks: Its my workflow of choice, coming from git (gawd, i really do need coffee). I prefer to have many test branches, and one working one on the file system so i never jump around in my IDE. So i have --no-trees defined in my shared repo [12:56] Leefmc: that's what surprises me, if you know enough to use the --no-trees option, I would have expected you know how to create a checkout :) [12:57] luks: I do, i just forgot that bzr hid (or rather, didnt make visable, however you wish to lookat it :o) the code within [12:57] or at least non-existance of the checkout would not confuse you [12:57] well, you _told_ it to do that [12:57] Its been a couple months since i've used bzr, so it confused me ;) [12:57] so that should be the expected behavior [12:57] well, 4am and no coffee too haha [12:57] ah :) [12:58] luks: Actually i told it "--no-trees", and really i had forgotten why i used it, aside from the fact that it allowed me to achieve my desired workflow. [12:59] So i told it "--no-trees" and i forgot i was telling it "--dont-give-me-any-visible-code" :o [12:59] heh [12:59] anyway, i really do need coffee. Thank you for your patience. === cprov is now known as cprov-afk [13:52] Hi - Is there a way to suppress warnings in bzr. [13:53] My client is using bzr-upload. It tries to set chmod's, but my client is using a IIS server for her site, so we get a warning for each file that it can't set the chmod. [13:54] I would like to suppress these warning, as they are not a problem in this case. [14:10] GaryvdM: I'd file a bug on bzr-upload [14:18] Ok - It is a todo in their code. [14:20] or fix it yourself if it's not too much trouble :) [14:31] hi, anyone interested for some benchmark results (doing bzr's vs. gits' fast-import from darcs), take a look at https://bugs.launchpad.net/bzr-fastimport/+bug/232177 [14:31] Launchpad bug 232177 in bzr-fastimport "Better darcs support needed" [Undecided,New] [14:33] and i'm bit disappointed that bzr couldn't finish task in more than 5hrs which git did in 20mins :-( === pmezard is now known as pmezard|afk [16:04] Question: I accidentally made a checkout into a no-tree branch. How can i remove the checkout from that directory without harming the branch? [16:11] leefmc: `bzr remove-tree` [16:12] LarstiQ: Thank you. [16:12] Wasn't sure if any of those would harm my branch, etc. [21:16] I know its saturday, but would anyone here be so kind to help me assemble a TOC? [21:52] kiko: NASA used PRACA for the first time, live, for the Endeavour shuttle launch yesterday. :-) [21:53] kiko: They use bzr for that, too. I think they use bzr as much as they can for their internal projects, now, actually. [21:53] At least, at Ames HCI. [21:54] kiko (and poolie, etc.): I have a little news article that's going to go live about PRACA on bugzilla.org. Maybe you could get them to make a little statement about bzr, too. They're pretty fond of it. :-) [21:59] mkanat, wow, no way! is that serious? [22:00] kiko: Yeah! :-) http://www.bugzilla.org/news/#praca [22:00] kiko: They started using it because I use it for ES projects. [22:00] kiko: But bzr is super-convenient for them because there's SO much merging involved in what they do, and there's also a LOT of branching. [22:01] you are the man [22:01] that's a really cool story [22:01] Thanks! :-) [22:01] let's try and get some news out on monday [22:01] kiko: Okay. Do you want me to put you in touch with the people at Ames who use bzr? [22:01] yes, if you could forward an email to me I'll do the rest [22:01] kiko: Okay. [22:02] nasa, how about that [22:03] :-) === fta_ is now known as fta [23:11] does anyone know who the loggerhead maintainer is? Does he/she hang out in here at all? [23:12] I submitted a bug with a patch a few nights about but there's been no activity on the bug [23:12] s/about/ago [23:14] lamalex, I think its Michael Hudson [23:14] not sure [23:46] lamalex, yeah, Michael Hudson (mwh) or Martin Albisetti (beuno) [23:46] jelmer: pygi: thanks