=== davidstrauss_ is now known as davidstrauss [01:33] * venia greets everyone. [02:01] is there a good way to do a side by side diff? (example: tkdiff, vimdiff) [02:03] eyda|mon: you can use 'bzr diff --using=gvimdiff' [02:04] There are also plugins to extend bzr diff in various ways. [02:04] http://bazaar-vcs.org/BzrPlugins [02:05] Also, the bzr-gtk and qbzr plugins provide that sort of functionality too. [02:46] * igc lunch [03:44] back [04:17] Hmm, lunch. That's a good idea. [07:12] bzr: ERROR: exceptions.AssertionError: second push failed to complete a fetch set([('inventories', 'brian@gaz-20091012224641-gjo56i190y8c98xg'), ('inventories', 'brian@gaz-20091012172541-ta8k2ejioknnexab')]). [07:12] that's not fun [07:21] mtaylor: huh [07:21] spiv: repeatable for me at the moment [07:21] mtaylor: ooh, good. [07:21] spiv: I have a copy of that branch on another machine, so I could re-push - but I thought I'd leave it there for you guys :) [07:21] mtaylor: I think there's an unsolved bug about that at the moment, IIRC it's stalled due to not being able to reproduce [07:22] spiv: yay! maybe I'll be helpful then :) [07:22] https://bugs.edge.launchpad.net/bzr/+bug/437626 [07:22] Launchpad bug 437626 in bzr "exceptions.AssertionError: second push failed to complete a fetch set" [Undecided,New] [07:22] hey look at that [07:23] mtaylor: if you can provide something along the lines of tarballs and a recipe to reproduce with them I will be very grateful! [07:24] spiv: you want me to tar up my local repo .bzr ? lemme try to see if that does it [07:24] mtaylor: yeah, please do [07:24] Somebody should mark the new bug as a dupe, then, no? [07:24] Peng_: yeah... I can do that [07:24] Peng_: probably, I haven't seen it yet.. [07:25] Actually, [07:25] Well, I guess it's probably the same bug, but it's not certain. [07:26] But I note that mtaylors' bug report only involves inventory records, which *might* mean it's a different issue. I guess it's easy to unmark it as a dupe later if necessary. [07:27] spiv: shit. sorry. I have altered my local repo already [07:28] mtaylor: that's ok [07:28] mtaylor: can you still reproduce? [07:28] spiv: I branched a different branch, which I'm guessing filled in something [07:28] spiv: nope [07:28] mtaylor: if not, a tarbll will still be handy [07:28] k. well, I can give you that [07:28] mtaylor: along with the details of the last change you made to it. [07:29] Chances are I can take out the most recent pack file with some simple surgery and get it back to the problematic state. [07:29] spiv: last thing I did was "bzr branch lp:drizzle/build fix-include-issues" [07:29] which is the only repo operation I did on it since the problem was reproducable [07:29] But it's also interesting to know that it's so easy to lose the state that triggers the bug. [07:32] hi all [08:29] hi, how do I branch a specific revision? For instance when I bzr branch lp:django-modeltranslation I always get the latest stable branch rather than the trunk. [09:01] hi, I got Format for file:///home/aron/main/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance when checkout a branch, what's this mean? [09:02] happyaron: Exactly what it says. [09:03] happyaron: /home/aron/main/ is using an old, slow, inefficient repository format. Upgrading will make things faster and use less disk space. [09:03] Peng_: so run "bzr upgrade"? but this will only effect in my local copy I think [09:04] happyaron: What version of bzr are you on? [09:04] Peng_: I have 1.13.1 installed [09:05] * happyaron on my box [09:06] Ah. Uh. Err. If you were on 2.0, by default "bzr upgrade" would upgrade to a format that you can't downgrade back to RepositoryFormatKnit1 from, but that's not the case in 1.13.1. [09:07] So, sure, upgrade, if you don't need your repo to be compatible with really old (<0.92) bzr versions. Take a backup first, of course, and run "bzr check". [09:08] And yes, it would only upgrade your local copy. Perhaps the remote copy already has been upgraded. If not, you can go and upgrade it too. [09:08] Peng_: how to upgrade the remote one? [09:08] Also.. 1.13.1 is rather old. You might want to upgrade to a newer version. That'll offer even faster and more disk-efficient formats, too. [09:08] Peng_: the branch is hosted on launchpad [09:09] happyaron: "bzr upgrade bzr+ssh://..." [09:09] happyaron: It won't be very fast, but it'll work fine. [09:09] oh [09:09] I know, I will first upgrade my bzr package, then run check, and finally upgrade the format [09:09] Peng_: thanks [09:10] happyaron: Sounds good. Like I said, though, if you upgrade to 2.0, by default "bzr upgrade" will switch to a format that you can't downgrade back to RepositoryFormatKnit1 from. [09:10] Not that there's anything wrong with that, unless you have a really ancient bzr install somewhere. [09:11] See http://doc.bazaar-vcs.org/latest/en/upgrade-guide/index.html about that. [09:11] Peng_: so if I upgrade the one using a 2.0 version, will it accessable for those who still run like 1.13? [09:12] happyaron: By default, 2.0 uses the 2a disk format, which was only added in, uhh, 1.17, IIRC. Maybe 1.18. [09:12] happyaron: You could use an older format if you need to, such as 1.9. [09:12] Peng_: oh [09:12] It'd still be much better than the one you're currently on. Just not as awesome as 2a. [09:13] Peng_: thanks [09:17] FWIW, even if you do upgrade to 2a, you can downgrade it back down to 1.9-rich-root (added in 1.9) or rich-root-pack (added in 1.0). [09:18] oh [09:27] I suck at explaining things. Upgrading to a rich-root format like 2a is a bit inconvenient (particularly if a lot of other people have copies of your branches), but not a big deal. The upgrade guide I linked to goes into more detail. [09:28] (FYI, rich-root formats contain a bit more meta data. Specifically, the root directory of the branch gets a file ID like all other directories do. It's not that important for most uses, but once you upgrade to a rich format, you can't just downgrade to a non-rich format again, throwing out that information.) [09:29] Peng_: I am now upgrading it to the 2a format since this branch wasn't used by more than 5 persions, I will notify them (we were blaming the low speed, hope this can help) [09:29] happyaron: It will. 2a rocks! [09:30] freeflying: :) [09:33] * Peng_ goes /away [09:56] * igc dinner [09:57] hello all [10:42] join : after you join a subtree, can you continue to pull revisions from it's original branch... particularly, I'm thinking of trees derived from SVN branches [10:42] * awilkins is about to try this anyway [10:46] Neato, that works really well [10:47] I'm guessing that pushing it to the SVN repo would be a bit of a disaster though [11:42] hmm [12:16] Hi there, I'm an engineering student and I'm starting a computing project with two other people. We could do with a some sort of (very basic) distributed revision control. Is Bazaar more or less what I'm looking for? [12:16] igc: I've pushed the updated subvertpy [12:16] igc: (including bin/subvertpy-fast-export.py) [12:18] tmartin: Those aren't very complicated requirements, so many DVCSes would work, including Bazaar. [12:18] tmartin: Bazaar has the advantage of working over plain old SFTP or (god forbid) FTP, though. [12:19] Peng_: cool. The reason I'm keen on Bazaar is that the other two people I'm working with aren't familiar with version control, so it's useful that the clients are the same across platforms so I can talk them through it [12:20] Well, hg has that advantage too. [12:20] hg? [12:20] ah, mercury [12:20] Well, the VCS is called "Mercurial", but yes. [12:23] Erm. I am a bzr proponent, but it's not the only good VCS, and which one you like best is a personal thing. [12:23] me sucks at advertising. :P [12:23] tmartin: bzr has very good giu [12:23] gui [12:23] bzr-explorer [12:23] if it matters [12:24] My main issue is with hosting. I can't host myself because I'm behind a NAT that I can't forward ports through (we're just using the leftover Internet in our flat from the last tenants until the new line rental comes through) so I need some project hosting. Using the Bazaar hosting for a small university project wouldn't be considered abuse of the service, would it? [12:25] ...Is it a software project? [12:26] s/a/a free/ [12:28] it's definitely a software project. It's of dubious use to anyone but us. Basically it models the performance of a Rover 826 accelerating to 100 kph subject to various conditions [12:29] but is it free software? [12:29] At the moment it's as-is, but yeah, I can BSD it if I need to [12:32] tmartin: you can use `bzr send` command to send new revisions via e-mail. in this case you won't need separate hosting [12:32] although it can be a bit tedious [12:32] bialix: Perfect! [12:32] no, it won't be [12:32] It's such a ridiculously small project [12:33] tmartin: then you need to have one reference branch and one working branch and create bundle to send against reference branch [12:33] bialix: you've lost me a bit there, hang on, i'm looking it up in the manual [12:33] there is nothing in manual [12:34] `bzr send` require reference branch to produce valid output [12:34] your reference branch should be equal to other people unupdated branch [12:35] bialix: okay, i think that's clear [12:36] `bzr send` automatically determines then what revision missing based on the info from reference branch [12:36] that's why it can be tedious [12:37] maybe using Launchpad.net will be much simpler solution [12:37] just set free licenseon your code [12:37] like the MIT one [12:37] or Apache 2 [12:37] it's nicer than BSD because you don't have any blanks to fill in, I believe [12:38] new BSD does not require any blanks, IMO but IANAL [12:38] MIT is still shorter. [12:38] * bialix nods [12:39] Besides, we all know MIT is cooler than Berkeley. :P [12:41] this tiny details is out of understanding of non-US guy like me [12:43] I'm not sure MIT really is ;-P === tonyyarusso is now known as Guest93713 [12:43] I was just kidding anyway. [12:43] I suppose it may depend on where your allegience lies: Lisp, or *nix [12:44] are you in the "worse is better" camp, or the "oops we never got around to adding syntax" camp? [12:45] ... though I guess MIT did make X, but then again that might just be a reason to hate them ;-P [12:46] Well, MIT has Clocky, the alarm clock that rolls away from you, and Berkeley has, what, LSD? [12:46] * bialix wonders why fullermd does not say anything yet [12:46] is that because MIT is so demanding you would oversleep without a clock that evades you? [12:47] But Berkeley is so demanding you need drugs. :D [12:50] Hmmwhat? Sorry, I was off doing LSD... [12:52] I long ago developed remarkable agility while asleep. I don't think it would be very easy for an alarm clock to evade me... [12:53] The only thing I can do while asleep is drool. :( [12:54] hmm. I can sleep [12:54] and have strange dreams [12:54] I had an alarm clock in college that I measured at around 145dB/1 meter. [12:55] It worked, in a roundable way. It woke up my whole hall, who then got the RA to open my door and woke me up. [12:55] That causes hearing damage! [12:55] Once, famously, by picking me up, carrying me out of the dorm, down the hill, and throwing me in the lake. [12:55] fullermd: roundabout, you mean [12:55] I woke up about the time I hit the water. I guess I was kinda tired or something. [12:56] that's an understatement ... [12:56] You're lucky you woke up instead of drowning. :\ [12:56] I hope you didn't have any 7:00 classes [12:56] Oh, I'm a good swimmer. I can probably do that in my sleep too :p [12:56] Anyway, it was college; if you're not exhausted, you're doing it wrong, right? [12:56] 7:00 classes are easy. You just stay up late for 'em. [12:57] I once slept through a fire alarm (no fire; it was broken), but I have no problems with my quiet alarm clock. [12:58] fullermd: I meant 7:00 AM [12:58] SamB_XP: So did I :p [12:58] oh [12:58] what if you have OTHER classes that day? [12:59] Well, I went a couple months sleeping 4 hours a night, on Tue and Fri... I made it to all my classes, though it's possible I might not have been entirely lucid on occasion. [13:00] (but then, it's _me_. I'm not sure you could tell the difference anyway.) [13:02] meaning you're never sane ? [13:03] Sanity is for the unimaginative. [13:03] yeah, it does seem overrated ;-P [13:06] Anyway, back to only vaguely off-topic, the MIT license and the 2-claues BSD license are isomorphic, so that's a matter of taste. 3-clause BSD is slightly more restrictive. [13:06] ... and the main reason to choose a 4-clause is to tick rms off :p [13:08] sadly it will also tick a lot of others off if they for some reason end up wanting to combine your software with something that's under the GPL ... [13:08] Their own fault for picking such a B&D license :p [13:08] they might not have written that part [13:08] ...ISC! :D [13:10] We should write an Escher license, granting all rights to users in a 4-dimensional space. [13:11] or on a mobius strip? [13:12] The ISC license is nice. It's equivalent to 2-clause BSD, but shorter. http://en.wikipedia.org/wiki/ISC_license [13:14] ...from the Internet Systems Consortium, or NAMBLA... === menesis1 is now known as menesis [13:33] is the right syntax for a password for svn:// repo just scheme=svn ? [13:34] if i put my credentials for this svn repo in authentication.conf and try to push, bzr-svn dies with TypeError: password should be string [13:34] it works if i just let it prompt me for it [13:35] if the svn command line tool caches it, I belive bzr-svn will pick that up [13:35] Torne: Sounds like a bug in bzr-svn [13:35] bob2: i've never touched this one with actual svn, so i don't have it stored there :) [13:35] Torne: please file a bug and include the backtrace [13:36] with a bit of luck we should be able to fix it for the 1.0.1 release [13:36] jelmer: ok [13:40] jelmer: submitted, https://bugs.launchpad.net/bzr-svn/+bug/452121 [13:40] Launchpad bug 452121 in bzr-svn "Putting svn password in authentication.conf doesn't work" [Undecided,New] [13:40] Torne: thanks [13:40] I *nearly* copypasted my password into the report. :) [13:41] heh [13:42] while i'm here: bzr-svn is fantastic other than that :) [13:42] i've just never had to actually push before ;) [13:44] cool, great to hear :-) [13:44] anyway, bye for now ;) [13:49] spiv is here? [13:53] spiv: when you'll back here: please comment somehow on bug #430382 [13:53] Launchpad bug 430382 in qbzr "qcommit crashes during Cancel" [High,Confirmed] https://launchpad.net/bugs/430382 === mrevell-lunch is now known as mrevell [14:17] jam: If you have time, any chance you could have a quick look at my lp:~jelmer/bzr/foreign-tests1 branch and see if the way the tests are set up is ood? [14:21] Ood? http://tardis.wikia.com/wiki/File:Ood.jpg (joke) [14:21] *good [14:22] awilkins: :-) [14:30] Peng_: the thing I find stupid about all of those licenses is that the DISCLAIMER OF WARRANTY WHICH IS IN ALL CAPS FOR SOME BIZARRE REASON is longer than the actual license [14:37] Well, that's easily solved, just make the actual license part 10 or 15 pages long. Then it's shorter :p === tchan1 is now known as tchan [14:46] n/win 3 [14:51] howdy === jblount is now known as jblount-bot === jblount-bot is now known as jblount [15:12] Hi [15:13] Probably one for the FAQ, but I cannot find it: How do I remove a local branch? Just deleting the folder works -- I wonder whether there are any ill effects of that? [15:14] i.e. I have /trunk, /feature-branch locally, and I merged /feature-branch back into trunk, so I don't need it [15:44] Anteru: No ill effects, if you merged it the revisions are all somewhere else. If it's in a shared repo, the revisions don't evaporate, the branch is a pointer. [15:45] ok, cool, thanks! [15:47] fullermd: ping? === e-jat is now known as norly === mfer is now known as mfer-lunch [16:29] jelmer: I'll try to get to the review. Sorry about the delay [16:29] /cry, wordpress doesn't auto-save your document, and it crashed while trying to insert and move an image... [16:29] back to blogger for me.... [16:30] I liked parts of the interface better, but crashing w/ no autosave is just out [16:31] heck, this post may never be written now... [16:32] jam: blogger has feature to send post via e-mail [16:33] I was writing up a fairly involved post about what it took to release 2.0.1 and 2.1.0b1 [16:33] but I'm unable to send images with my post [16:33] I got things mostly written, was inserting an image, tried to move it.... [16:33] and then firefox hung with 100% cpu [16:33] bad [16:33] I like your posts [16:34] w/ blogger, at least it would have saved for me [16:34] do you have twitter account? [16:34] perhaps WP has a ^S [16:34] I do not have twitter [16:34] np [16:34] seems... silly to me so far [16:36] wp has autosave, at least my installation saves every 5 minutes or so [17:11] where's my bzr-backed wiki [17:12] it's almost 2010 and I have no flying cars, no hoverboards, no pony and no bazaar-backed wiki [17:12] trac? [17:12] jml, you mean ikiwiki? [17:12] beuno, maybe I do. [17:13] http://ikiwiki.info/ [17:13] I think it's in perl though [17:26] I know people have worked on a bzr back end [17:27] james_w (and myself very minimally) [17:27] of course, it has a svn and git backend, so.. [17:27] Was there a plugin that pushes the revisions AND the current working tree to another machine? [17:28] jml: there is als Hatta, which is hg backed [17:30] awilkins: push-and-update? [17:30] I can't remember now if the bzr backend for ikiwiki was merged [17:30] james_w: Not quite, I have uncommitted state that I want to end up in the target [17:30] awilkins: rsync ? [17:31] jam: I was just using a tree-comparision client :) [17:31] pushing uncommitted changes isn't something that is likely to be supported 'out-of-the-box' for us [17:31] if you want them pushed, why not commit and push ? [17:32] (why is it important that they not be committed ?) === beuno is now known as beuno-lunch [17:34] LarstiQ, yeah, I saw a talk about Hatta at EuroPython, you probably did too [17:36] jml: yup [17:36] * LarstiQ forgot there was lightning talk about it [17:37] jam: Just my inner voice saying "no, don't push incomplete changes!" [17:37] jam: Or commit them, rather [17:37] awilkins: yet you want to deploy them? [17:38] LarstiQ: It's not deployment, it's moving workstation [17:38] I suppose what I really want is shelve-and-move-to-another-machine [17:39] awilkins: ah, yes [17:39] awilkins: or just diff, rsync, apply [17:39] Shelves are basically orphaned revisions (as I understand them now) [17:39] awilkins: I don't think they are put into the repo, but otherwise, yeah [17:50] so you know those archive inconsistencies I keep getting [17:50] theory: they're ghost revisions [17:50] ie. where I've overwritten one head with another [17:50] awilkins: bzr commit; bzr push; bzr uncommit... [17:51] jam: More ghost revisions :-) [17:51] awilkins: those aren't ghosts [17:51] ghosts are ancestors we don't have [17:51] jam: what are those? [17:51] those are just heads that aren't in a branch [17:51] bzr commit; bzr push; bzr uncommit; bzr commit; bzr push --overwrite [17:51] Ah, loose heads [17:52] Keybuk: A ghost is a revision in the branch's history, except we don't actually have a copy of that revision. [17:52] Or something! [17:52] hmm, actually I'm not sure that's right [17:52] Peng_: something spookier I believe :) [17:52] so I have the following error on push now [17:52] not sure how... [17:52] inconsistent details in skipped record: ('scott@netsplit.com-20091014154035-x6fdt088smfxy63j',) ('518 291 0 266', ((('scott@netsplit.com-20091014154020-3j2udgsm15lbdfm4',),),)) ('93400 238 0 266', ([('scott@netsplit.com-20091014154020-3j2udgsm15lbdfm4',)],)) [17:52] but the revision ids on each side *do* match [17:53] what's more interesting is that each of the revisions were made *after* I upgraded to bzr 2.0 [17:53] Keybuk: the warning there is saying that we have revision ids which claim to match, but *content* which claims to differ [17:53] jam: isn't that bad? [17:53] Keybuk: potentially, though abentley claims that there were ways of getting into this situation that weren't terribly [17:53] terrible [17:53] I'm getting into this situation with ordinary use of bzr [17:53] hence why he made it a warning when it used to be an error [17:54] I'm really worried that bzr 2.0 has some *serious* data corruption issues now [17:54] the way of triggering it that he knew of [17:54] was that launchpad had bad history [17:54] and different people had different *amounts* of bad history [17:54] this is on *new* revisions [17:54] Keybuk: right, but if you base a commit off of X, and someone else sees that as X' [17:54] the new commits can disagree [17:54] but that hasn't happened here [17:54] this is just an archive [17:55] one is the LP push of the other [17:55] and bzr is throwing up all sorts of errors with it [17:55] Keybuk: so to start with, try to get a tarball snapshot of the state, so that one of us can take a look at it [17:55] jam: it's on LP [17:55] I can't login to that and give you a tarball [17:55] I suspect you can [17:55] Keybuk: I don't have access to your branches [17:56] you can use "lftp" to mirror the remote to local [17:56] and then tarball that [17:56] afaict it's the LP-hosted branch that has the issues [17:56] Keybuk: right, and I can only see the "LP-mirror" of your branch [17:56] got an example lftp incantation? === dorins_ is now known as dorins [17:57] Keybuk: I think "lftp -c mirror sftp://bazaar.launchpad.net/~keybuk/... local" [17:57] is what you can use to get an exact copy of the launchpad branches [17:57] ok, grabbing that down [17:59] reconcile on this fails [18:00] http://people.canonical.com/~scott/ubuntu-core-dev--upstart--ubuntu.tar.gz [18:00] there you go [18:00] that's the .bzr [18:02] Keybuk: it says it is stacked on "~scott/upstart/trunk" can I get a copy of that as well? [18:02] yup [18:02] that one happens to fail reconcile too iirc [18:03] verterok: ping [18:03] (this is somewhat larger, so give me a few minutes for it :p) [18:04] jfroy|work: pong [18:04] I just made a few fixes to my packaging branch [18:04] including a critical fix for an issue I just found in the current distribution / build.py script [18:05] that would replace /usr/local/share/man/man1 with the bzr man page (instead of installing it into that directory) [18:05] fortunately, Installer is smart enough to move man1 to "man1 1", so I also added a pre-install script to the distro to fix up that mess. [18:05] Anyways, I merged your branch into mine, made the fixes and pushed to LP. [18:06] Trying to find how to send you a merge request... [18:06] Keybuk: so it is possible, that the above warning is bogus. I have to dig into it, but I'm noticing that one side says: [18:06] (((revid,),),) [18:06] and the other side says [18:06] ([(revid,)],) [18:06] (one side has a tuple, the other has a list) [18:06] jam: why does reconcile fail on that branch? [18:07] it is possible that it is comparing the objects and failing. [18:07] jfroy|work: oh, nice! [18:07] Keybuk: I haven't gotten that far yet. And certainly there is a bug if [] vs () was triggering a warning [18:07] jfroy|work: as there is no project we can't do merge proposals [18:07] jam: the branch it's stacked on seems to not fail reconcile fwiw [18:07] verterok: ahhh, that explains a lot :p [18:07] just uploading for you atm [18:07] i just installed Bazaar 2.0.0.2 on a Vista 64-bit machine. Running bzr st in an existing bzr repo gives this: "No module named commands" and "Unable to load plugin u'explorer' from u'C:/Program Files/ .. etc'. Bazaar Explorer doesn't seem to be working either. Any ideas? [18:07] thx [18:07] just merge lp:~jeanfrancois.roy/+junk/SnowLeopard-package then [18:08] stianhj: you might try "bzr -Derror status" [18:08] it sounds like it is unable to load bzrlib [18:08] which is fairly serious [18:08] I'm wondering about a permissions issue [18:08] I was going to submit Bazaar-2.0.0-5 [18:08] do you have any other copies of bazaar? [18:08] but with 2.0.1 around then corner, I guess we could wait for that. [18:09] jfroy|work: 2.0.1 has 'gone gold' [18:09] jam: my point exactly [18:09] so feel free to package Bazaar-2.0.1-1 [18:09] verterok: want to do it? [18:09] the tarballs should be uploaded, etc. [18:09] also, packaging Bazaar-2.1.0b1-1.pkg would be nice [18:09] jfroy|work: the merge or the build? :) [18:10] both :p [18:10] jfroy|work: :) [18:10] well you *need* to merge [18:10] trashing man1 is *bad* [18:10] jam: http://pastebin.org/46041 [18:10] Oh, the distro version is in config.py [18:10] (I added it) [18:10] jfroy|work: I'll merge it in my next boot into OS X, proably to build 10.5 installer ;) [18:10] I guess I can build the 10.6 one [18:11] so, let's see [18:11] how would I get the 2.0.1 sources? [18:11] jam: bzrlib seems to be the problem I guess [18:11] erm, I mean, w/r to your auto-fetch thing [18:11] jfroy|work: please, I don't have 10.6 and I'm not sure if it will work if I build it against non system python [18:11] verterok: it won't [18:11] stianhj: so it would look like 'bzr' itself is working, but that explorer is failing to find something [18:12] jfroy|work: PYTHONPATH=. python tools/fecth-external.py -p [18:12] specifically, it is looking for: from bzrlib.plugins.qbzr.lib.commands import ( [18:12] verterok: oh, I moved fetch-external.py out of tools :p [18:12] so it is *qbzr* which it isn't finding [18:12] jfroy|work: heh, ok [18:12] jfroy|work: so, python fecth-external.py -p :) [18:12] yeah basically [18:12] *fetch-external.py -p [18:12] stianhj: can you try just doing "bzr qbrowse" ? [18:13] or "bzr qlog" ? [18:13] I just tweaked config.py to get 2.0.1 [18:13] jfroy|work: and you can get the docs too, I don't remember the switch [18:13] I'll check the plug-ins and update them as well [18:13] I don't bundle the docs in the core package [18:13] jfroy|work: right, I missed that...update config, run the script [18:13] but I saw the o[tion [18:13] *option [18:13] jfroy|work: ok [18:14] jam: yes, bzr seems to be working. qbrowse seems to be working, as well as qdiff, qcommit, etc [18:15] qlog as well [18:15] stianhj: and I assume that doing "bzr explorer ." is failing? [18:15] no wait, qlog doesn't work [18:16] jam: i get a bunch of errors on the console about drawDisplay, and my commit messages aren't showing [18:16] oh well, the tar.gz isn't up yet :p [18:16] or the URL is wrong, lol [18:16] jfroy|work: you need to update the url in the config too [18:16] Keybuk: so I don't know why 'reconcile' is failing, but it does look like the warning is triggering because of () != []. I don't quite understand how we are getting a list there, though. As we generally always use tuples. [18:16] jam: the commit messages in the list that is. clicking on items gives me all the info at the bottom of the screen [18:16] verterok: I did, with a wrong one ;p [18:16] So bug #1 is that the comparison is giving you a bogus warning. [18:16] https://bugs.launchpad.net/ubuntu/+bug/1 (Timeout) [18:17] jfroy|work: heh [18:17] worked fine with the actual URL. [18:17] stianhj: do you know if you have another copy of 'qbzr' installed? Say in your $APPDATA folder? [18:17]