| [01:02] <ia> 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] <jfroy|work> quick question: how do I get the revno of the working-tree? | |
| [01:36] <jfroy|work> 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] <verterok> jfroy|work: revision-info? | |
| [01:49] <jfroy|work> That seems to give me the latest revno of the branch | |
| [01:49] <jfroy|work> e.g., gives me the revno of bzr log -r -1 | |
| [01:49] <jfroy|work> when a bzr st outputs a message stating my working tree is out of date | |
| [01:56] <verterok> jfroy|work: according to bzr help version-info, it shows revision info of the tree | |
| [01:56] <verterok> jfroy|work: you could do bzr update to get your tree up to date | |
| [01:56] <jfroy|work> indeed, thanks | |
| [01:57] <jfroy|work> 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] <n[ate]vw> I'm trying to install bzr 1.9 on my web host, but getting a build error due to missing Python.h | |
| [01:57] <n[ate]vw> How do I use this --allow-python-fallback that it recommends? | |
| [01:58] <n[ate]vw> or where do I find an older version? | |
| [01:58] <verterok> jfroy|work: maybe you can use lightweight checkouts to have different revisions of the tree around | |
| [01:59] <verterok> 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] <n[ate]vw> yeah, I'm assuming that's the problem, but the error diagnostic makes reference to this python fallback option | |
| [02:01] <verterok> 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] <n[ate]vw> but then I get "error: option --allow-python-fallback not recognized" | |
| [02:01] <n[ate]vw> it's a shared host, so no can do | |
| [02:02] <verterok> hmm, what version of python? | |
| [02:02] <n[ate]vw> 2.5.1 | |
| [02:02] <jfroy|work> verterok: version-info worked fine | |
| [02:02] <verterok> jfroy|work: great! :) | |
| [02:02] <jfroy|work> Although indeed, I am getting a bzr exception when trying to checkout if a tree already exits | |
| [02:02] <jfroy|work> I have to remove-tree, then co again, with a different revno | |
| [02:03] <verterok> jfroy|work: you could do the co in different dirs :) | |
| [02:03] <jfroy|work> I don't really care to keep multiple trees | |
| [02:03] <jfroy|work> I mean, I could, I suppose | |
| [02:04] <jfroy|work> But I'm playing a game of "is it this one?" | |
| [02:04] <verterok> hehe, ok. | |
| [02:04] <verterok> n[ate]vw: could you pastebin the error? | |
| [02:05] <verterok> and the command you are using? | |
| [02:06] <n[ate]vw> verterok: http://pastebin.com/d61571c59 | |
| [02:07] <n[ate]vw> (original command was 'python setup.py install --home ~/sw') | |
| [02:08] <verterok> n[ate]vw: you could simply drop the source there, and bzr should "just work" (mileage may vary) | |
| [02:09] <n[ate]vw> 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] <Leefmc> 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] <luks> it's not downloading the code at all (ie, the process has finished and no code was downloaded)? | |
| [12:45] <Leefmc> luks: Correct | |
| [12:45] <luks> that's weird | |
| [12:45] <luks> how do you check that? | |
| [12:46] <Leefmc> is "bzr branch http-addy-to-trunk" the correct command? | |
| [12:46] <Leefmc> erm, minus a space, heh | |
| [12:46] <Leefmc> luks: By looking in the directory and seeing zero code | |
| [12:46] <luks> in most cases, yes | |
| [12:46] <luks> Leefmc: what does `bzr info` say? | |
| [12:46] <Leefmc> lemm rebranch it, one sec | |
| [12:46] <luks> I think you just have a branch without a working tree | |
| [12:47] <Leefmc> ohh thats right | |
| [12:47] <luks> which `bzr checkout .` should fix | |
| [12:47] <Leefmc> i forgot, if theres no working tree bzr wont show you code | |
| [12:47] <Leefmc> that always trips me out. heh | |
| [12:47] <luks> hm, I wonder why? | |
| [12:48] <Leefmc> My minds all fluxxed from bzr-svn hybrids heh. | |
| [12:48] <luks> bzr doesn't show you the code, your shell does | |
| [12:48] <Leefmc> luks: Well, i ment that bzr physically hides the code, does it not? | |
| [12:48] <luks> Leefmc: no | |
| [12:48] <Leefmc> Oh well, maybe thats not the problem then.. lemme bzr info | |
| [12:49] <luks> all bzr is interested in is the .bzr directory (in most cases) | |
| [12:50] <luks> the working tree matters only if you try to e.g. commit | |
| [12:50] <Leefmc> 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] <Leefmc> but the branch, only has one directory in it, .bzr. The file system has zero code in it | |
| [12:50] <luks> try bzr checkout . | |
| [12:51] <luks> or bzr log | |
| [12:51] <luks> if bzr log list something, you just want to add the working tree | |
| [12:52] <Leefmc> luks: Ah, you confused me before (or rather 4am with no coffee, confused me, more than likely) | |
| [12:52] <Leefmc> luks: So bzr _does_ actually hide the code if you have no working tree | |
| [12:52] <luks> Leefmc: it doesn't hide it, it simply doesn't exist | |
| [12:52] <Leefmc> ie, without a working tree, code is not visable on the file system | |
| [12:52] <luks> Leefmc: you can't hide something that doesn't exist :) | |
| [12:53] <luks> well, that's obvious | |
| [12:53] <luks> but the working tree is not hidden | |
| [12:53] <Leefmc> luks: Well it must exist somewhere on it, because you can essentially download it from bzr when you checkout | |
| [12:53] <luks> Leefmc: no, bzr only knows the data to generate it | |
| [12:54] <luks> but it doesn't exist in the form of actual files | |
| [12:54] <Leefmc> luks: Ah, well imo it still exists within bzr then haha, but now were splitting hairs :) | |
| [12:54] <Leefmc> luks: Yea | |
| [12:54] <Leefmc> luks: Anyway, thanks | |
| [12:54] <Leefmc> luks: Have you delt with bzr-svn much? | |
| [12:54] <luks> I wonder how did you get into this situation, though | |
| [12:54] <Leefmc> luks: No working tree? | |
| [12:55] <luks> yes | |
| [12:55] <luks> it's not the default option | |
| [12:55] <luks> do you have a repository created with `bzr init-repo --no-trees` or something? | |
| [12:55] <Leefmc> 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] <luks> 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] <Leefmc> 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] <luks> or at least non-existance of the checkout would not confuse you | |
| [12:57] <luks> well, you _told_ it to do that | |
| [12:57] <Leefmc> Its been a couple months since i've used bzr, so it confused me ;) | |
| [12:57] <luks> so that should be the expected behavior | |
| [12:57] <Leefmc> well, 4am and no coffee too haha | |
| [12:57] <luks> ah :) | |
| [12:58] <Leefmc> 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] <Leefmc> So i told it "--no-trees" and i forgot i was telling it "--dont-give-me-any-visible-code" :o | |
| [12:59] <luks> heh | |
| [12:59] <Leefmc> anyway, i really do need coffee. Thank you for your patience. | |
| === cprov is now known as cprov-afk | |
| [13:52] <GaryvdM> Hi - Is there a way to suppress warnings in bzr. | |
| [13:53] <GaryvdM> 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] <GaryvdM> I would like to suppress these warning, as they are not a problem in this case. | |
| [14:10] <LarstiQ> GaryvdM: I'd file a bug on bzr-upload | |
| [14:18] <GaryvdM> Ok - It is a todo in their code. | |
| [14:20] <LarstiQ> or fix it yourself if it's not too much trouble :) | |
| [14:31] <gour> 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] <ubottu> Launchpad bug 232177 in bzr-fastimport "Better darcs support needed" [Undecided,New] | |
| [14:33] <gour> 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] <leefmc> 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] <LarstiQ> leefmc: `bzr remove-tree` | |
| [16:12] <leefmc> LarstiQ: Thank you. | |
| [16:12] <leefmc> Wasn't sure if any of those would harm my branch, etc. | |
| [21:16] <pygi> I know its saturday, but would anyone here be so kind to help me assemble a TOC? | |
| [21:52] <mkanat> kiko: NASA used PRACA for the first time, live, for the Endeavour shuttle launch yesterday. :-) | |
| [21:53] <mkanat> 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] <mkanat> At least, at Ames HCI. | |
| [21:54] <mkanat> 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] <kiko> mkanat, wow, no way! is that serious? | |
| [22:00] <mkanat> kiko: Yeah! :-) http://www.bugzilla.org/news/#praca | |
| [22:00] <mkanat> kiko: They started using it because I use it for ES projects. | |
| [22:00] <mkanat> 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] <kiko> you are the man | |
| [22:01] <kiko> that's a really cool story | |
| [22:01] <mkanat> Thanks! :-) | |
| [22:01] <kiko> let's try and get some news out on monday | |
| [22:01] <mkanat> kiko: Okay. Do you want me to put you in touch with the people at Ames who use bzr? | |
| [22:01] <kiko> yes, if you could forward an email to me I'll do the rest | |
| [22:01] <mkanat> kiko: Okay. | |
| [22:02] <kiko> nasa, how about that | |
| [22:03] <mkanat> :-) | |
| === fta_ is now known as fta | |
| [23:11] <lamalex> does anyone know who the loggerhead maintainer is? Does he/she hang out in here at all? | |
| [23:12] <lamalex> I submitted a bug with a patch a few nights about but there's been no activity on the bug | |
| [23:12] <lamalex> s/about/ago | |
| [23:14] <pygi> lamalex, I think its Michael Hudson | |
| [23:14] <pygi> not sure | |
| [23:46] <jelmer> lamalex, yeah, Michael Hudson (mwh) or Martin Albisetti (beuno) | |
| [23:46] <lamalex> jelmer: pygi: thanks | |