[00:00] <lifeless> AfC: thanks
[00:01] <lifeless> AfC: one possible cause
[00:01] <lifeless> AfC: they may have run send with strange parameters
[00:02] <lifeless> people do the oddest things
[00:02] <AfC> yeah
[00:05] <lifeless> jelmer: you're using git too much "bzr add .
[00:05] <lifeless> "
[00:05] <lifeless> whyforthedot!
[00:07] <jelmer> lifeless: :-)
[00:07] <jelmer> lifeless: btw, I've pushed an updated version of my split-subsegment branch for your reviewing pleasure.
[00:08] <lifeless> jelmer: I'll look at it now
[00:08] <lifeless> poolie: thanks for approving my branch; a small request - click on 'approved' at the top too, next time ;) - or 'merge: approved' if doing by mail
[00:16] <jelmer> lifeless: thanks for the review
[00:16] <poolie> lifeless, the dkim yak looks at me with big sad eyes
[00:18] <lifeless> poolie: lol
[00:18] <lifeless> poolie: it is whinging slightly
[00:19] <poolie> 'it'?
[00:19] <lifeless> the dkim yak
[00:20] <lifeless> its saying 'shave me', 'shave me'
[00:20] <poolie> ah yes
[00:20] <lifeless> to the music 'I need to break free', 'I need to be shaved'
[00:21] <lifeless> hmm, speaking of which, I should do that too
[00:21] <lifeless> poolie: igc's sphinx doc branch can't land until we get some deps on pqm sorted out
[00:22] <lifeless> I've queried him unsuccessfully about what they are
[00:22] <lifeless> perhaps you can do so with more luck and either let me know, or jsut file an RT directly about it.
[00:22] <poolie> we can't reproduce the failure?
[00:23] <lifeless> poolie: its just the sphinx toolchain missing
[00:23] <lifeless> I don't know what that consists of
[00:23] <poolie> lifeless, hm bzr-loom, at least as it is in lucid, seems a bit broken by the named branch changes
[00:23] <lifeless> poolie: we could/should SRU the trunk fixes for that
[00:24] <lifeless> hmm, actually, I know I fixed it for 2.x, I don't know if I fixed it for named branch foo.
[00:24] <poolie> hm
[00:24] <jelmer> lifeless: are you landing the split-subsegment branch?
[00:24] <poolie> https://bugs.edge.launchpad.net/bzr-loom/+bug/586602
[00:24] <ubot5> Launchpad bug 586602 in Loom "open() got an unexpected keyword argument 'name' running 'info -v' (affected: 1, heat: 0)" [Undecided,New]
[00:24] <lifeless> jelmer: I'm not sure, I did a feed-bzr run, so if it was pending to land, then yes :)
[00:25] <lifeless> poolie: looks like not fixed yet
[00:25] <poolie> lifeless, how would you feel about asking people to always tag bugs' regression'
[00:25] <poolie> then we can get some stats
[00:25] <lifeless> I'd be delighted to ask people to do that
[00:25] <poolie> or softly prioritize them
[00:25] <lifeless> please sire, may I have another?
[00:26] <lifeless> jelmer: does the bzr packaging in debian have pristine-tar info yet ?
[00:26] <lifeless> jelmer: and is it history-joined?
[00:27] <jelmer> lifeless: no, it's got manual merges
[00:28] <lifeless> jelmer: how would you feel about dumping the history and switching
[00:28] <lifeless> sorry
[00:28] <lifeless> was that 'not pristine tar'
[00:28] <jelmer> lifeless: yes, not pristine tar
[00:28] <lifeless> or 'not connected in history'
[00:28] <jelmer> it's connected with bzr.dev in history
[00:29] <jelmer> lifeless: I basically ran "bzr merge -rtag:bzr-2.1.2 lp:bzr/2.1; dch -v 2.1.2-1 New\ upstream\ release."
[00:29] <lifeless> jelmer: ok, so you should do 'bzr import-upstream --version=2.1.2 TARBALL branch-of-2.1 at rev -2'
[00:29] <jelmer> import upstream rather than merge upstream?
[00:29] <lifeless> right
[00:29] <lifeless> that will import 2.1.2's tarball
[00:30] <lifeless> e.g. bzr branch lp:bzr/2.1 -r -2 temp
[00:30] <lifeless> cd packaging
[00:30] <lifeless> bzr import-upstream --version=2.1.2 tarball ../temp
[00:30] <jelmer> bzr import-upstream really should support -r then :-)
[00:30] <lifeless> iterative development
[00:30] <lifeless> I don't know if james_w has merged it or not yet  even :)
[00:31] <jelmer> lifeless: Branching first makes my life more complex, I'll see if I can provide a patch.
[00:31] <lifeless> jelmer: you'll tear your eyes out.
[00:33] <poolie> lifeless, branching a loom from launchpad (with tip of the plugin) gives me a loom with no thraeds
[00:33] <poolie> is that a known problem?
[00:36] <lifeless> poolie: no, and very unexpected
[00:36] <lifeless> what does revert-loom do ?
[00:37] <lifeless> poolie: the most likely explanation btw, is that the loom on launchpad has never had 'record' called
[00:44] <poolie> ok probably
[00:44] <poolie> perhaps we should have an optional warning to do it
[00:49] <spiv> Good morning.
[00:50] <poolie> hi there spivvo
[00:50] <lifeless> poolie: I haven't done PPA uploads for the releases
[00:50] <lifeless> I was going to, but I think I'm going to be out of time.
[00:50] <lifeless> -sorry
[00:50] <poolie> np
[01:13] <jelmer> it looks like http://wiki.bazaar.canonical.com/SourceDownloads is out of date, should that perhaps just point at the launchpad download page?
[01:21] <poolie> yep
[01:22] <poolie> done
[01:24] <lifeless> abentley: the fix to the command stuff - to not raise - is at 96% in PQM
[01:24] <lifeless> abentley: so should land in a minute or two
[01:24] <lifeless> ciao
=== tchan1 is now known as tchan
=== _thumper_ is now known as thumper
[03:06] <spiv> lifeless: hello again.  Did you see the post to the list about the bad .sig for the 2.2b3 tarball (it seems to have the 2.1.2 sig by mistake)?
[03:07] <lifeless> no
[03:07] <lifeless> fark
[03:07] <lifeless> I should be able to fix now
[03:07] <lifeless> I should have just used my automated toolchain, but its not polished yet
[03:10] <lifeless> poolie: spiv just told me about the sig issue
[03:10] <lifeless> am fixing
[03:10] <poolie> ok
[03:10] <poolie> shouldn't you be flitting?
[03:10] <lifeless> yes, in the waiting area
[03:10] <lifeless> boring not boardin
[03:10] <lifeless> g
[03:13] <lifeless> spiv: should be fixed shortly - 4% uploaded
[03:19] <lifeless> spiv: ifxed
[03:21] <spiv> lifeless: thanks!
[03:21] <lifeless> de nada
[03:23] <lifeless> is there anything else? 500 seconds to go :P
[03:23] <spiv> lifeless: not that I know of
[03:27] <spiv> lifeless: have a good flight!
[03:27] <lifeless> thanks
=== poolie changed the topic of #bzr to: Bazaar version control | try https://answers.launchpad.net/bzr for more help | http://irclogs.ubuntu.com/ | Patch pilot: poolie | bzr 2.1.1 is out
[04:30] <humphreybc> hi
[04:30] <humphreybc> could someone please tell me why I'm getting this error when I try to download a fresh branch in a fresh project?
[04:30] <humphreybc> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~humphreybc/about-ubuntu/main/".
[04:30] <humphreybc> I'm trying to start work in this branch, https://code.launchpad.net/about-ubuntu
[04:31] <humphreybc> Do I need to do a push first?
[04:31] <poolie> hi humphreybc
[04:31] <poolie> yes, make a branch locally then push there
[04:31] <humphreybc> benjamin@benjamin-laptop:~/Projects/about-ubuntu/main$ bzr push lp:about-ubuntu
[04:31] <humphreybc> bzr: ERROR: Not a branch: "/home/benjamin/Projects/about-ubuntu/.bzr/branch/": location is a repository.
[04:32] <poolie> i guess you need to cd into your trunk directory
[04:32] <humphreybc> benjamin@benjamin-laptop:~/Projects/about-ubuntu$ bzr push lp:about-ubuntu
[04:32] <humphreybc> bzr: ERROR: Not a branch: "/home/benjamin/Projects/about-ubuntu/.bzr/branch/": location is a repository.
[04:32] <humphreybc> benjamin@benjamin-laptop:~/Project
[04:32] <humphreybc> is it because I've used ground control to pull the project first?
[04:33] <poolie> where did you pull it from?
[04:33] <humphreybc> what do you mean?
[04:33] <poolie> hm
[04:34] <poolie> i was asking what you did with ground control
[04:34] <poolie> but let me ask instead
[04:34] <poolie> so you're trying to start a new project called 'about-ubuntu'?
[04:34] <humphreybc> yepo
[04:34] <poolie> and there's no code for it anywhere yet?
[04:34] <humphreybc> nope
[04:34] <poolie> except maybe on your laptop?
[04:34] <humphreybc> none on my laptop yet
[04:34] <poolie> ok so what does 'bzr info' show?
[04:34] <humphreybc> bzr info where?
[04:35] <cody-somerville> lol
[04:35] <humphreybc> I got rid of my ground control folder
[04:35] <poolie> ok
[04:35] <humphreybc> and just started from scratch
[04:35] <poolie> so to get started you should do
[04:35] <poolie> "cd"
[04:35] <poolie> "bzr init-repo about-ubunut"
[04:35] <poolie> *ubuntu
[04:35] <poolie> "cd ubuntu"
[04:35] <poolie> "bzr init trunk"
[04:35] <poolie> "cd trunk"
[04:35] <poolie> "bzr push lp:about-ubuntu"
[04:35] <poolie> mm
[04:35] <humphreybc> oh really? I can't just pull down the branch?
[04:35] <poolie> perhaps before doing this you want to make an ~about-ubuntu-dev team?
[04:36] <humphreybc> and I'm doing all this inside ~/Projects/about-ubuntu
[04:36] <poolie> it sounds like there's no branch to pull yet
[04:36] <humphreybc> I'll probably be the only person developing for it at the moment
[04:36] <humphreybc> so can I push say a plain txt file to just initiate the branch?
[04:36] <poolie> sure, so let's change those instructions to
[04:37] <poolie> bzr init-repo ~/Projects/about-ubuntu; cd ~/Projects/about-ubuntu
[04:37] <poolie> bzr init trunk; cd trunk; gedit README; (type something):
[04:37] <poolie> bzr add; bzr commit; bzr push lp:about-ubuntu
[04:37] <poolie> that'd be a nice project btw
[04:37] <poolie> it's not a great window at the moment
[04:38] <humphreybc> yeah, it's part of the revitalization of the Ubuntu first use stuff
[04:39] <humphreybc> committed okay, but when I went to push, "bzr: ERROR: Target directory lp:about-ubuntu already exists, but does not have a .bzr directory. Supply --use-existing-dir to push there anyway."
[04:39] <poolie> i wonder how you got that
[04:39] <humphreybc> and Ground Control is kindly informing me it's a read only branch
[04:39] <poolie> anyhow, yes, add that option
[04:39] <humphreybc> so Ground Control can't initiate branches?
[04:40] <humphreybc> yay, that seemed to have worked
[04:40] <humphreybc> now I wonder if I can pull the project and branch using ground control
[04:41] <humphreybc> every time I try to use GC it never works, i'm so eager to actually use it!
[04:41] <poolie> sorry, i'm not expert with gc
[04:41] <humphreybc> so howcome the URL for the branch is "https://code.launchpad.net/~humphreybc/about-ubuntu/main" instead of "https://code.launchpad.net/about-ubuntu
[04:42] <thumper> humphreybc: any LP code questions I should be able to answer
[04:43] <humphreybc> thumper: Okay, i'll hassle you in the future then :)
[04:43] <humphreybc> thumper: Brendon sent that email out to everyone too
[04:43] <humphreybc> are you the only speaker on Monday?
[04:44] <humphreybc> great, ground control pulled down the branch fine now. thankyou for your help poolie
[04:45] <thumper> humphreybc: https://code.launchpad.net/about-ubuntu points to branches for the project
[04:45] <thumper> humphreybc: all branches have an owner and a name
[04:45] <thumper> humphreybc: they have short cuts, but they don't always translate to a branch location
[04:45] <thumper> humphreybc: although https://code.launchpad.net/+branch/about-ubuntu should redirect
[04:45] <humphreybc> okay, groovy
[04:46] <thumper> humphreybc: I saw the email, and I think we might convince ajmitch to talk about quickly
[04:46] <thumper> humphreybc: you can always join #nzpug :)
[04:46] <humphreybc> I'm hopeless at joining channels
[04:46] <humphreybc> I use Pidgin, you see :P
[04:47] <thumper> humphreybc: try /join #nzpug
[04:47] <humphreybc> oh yeah, I know how to join channels
[04:47] <thumper> to know and not to do is not to know
[04:47] <thumper> :)
[04:47] <humphreybc> but pidgin doesn't have an auto-join thing, so every time I start it up, I have to manually join them - hence why I'm only ever in one or two
[04:47] <thumper> well that sucks
[04:47] <humphreybc> pretty much
[04:49] <humphreybc> where should I go to talk about python/gtk/glade and all that?
[04:51] <poolie> humphreybc, hm #ubuntu-motu maybe?
[04:52] <poolie> humphreybc, i think it does have auto join
[04:52] <poolie> but i use xchat now
[04:52] <humphreybc> poolie: really? hmm. I've looked through all the settings and plugins but never found anything
[04:54] <mwhudson> does pidgin actually work well for irc?  i've always had a hard time imagining that
[04:54] <poolie> join the room, then right-click it in the buddy list and choose auto-join
[04:54] <humphreybc> how do you get rooms to show in the buddy list?
[04:54] <poolie> mwhudson, it's kind of ok but not great
[04:54] <humphreybc> ohh
[04:54] <humphreybc> I see!
[04:55] <poolie> mwhudson, i don't think it shows who's in the channel
[04:55] <poolie> you can't ignore joins/parts
[04:55] <poolie> oh and you can't ignore stupid freenode bots
[04:55] <humphreybc> yeah, the bots are annoying
[04:56] <poolie> so i went back to using empathy for xmpp and xchat for irc
[04:57] <mwhudson> yeah, i use xchat
[04:57] <mwhudson> i used to use erc, but i'm gradually getting over the "use emacs for everything" thing :-)
[04:59] <humphreybc> emacs = bad
[05:00] <humphreybc> What's that opportunistic developers channel?
[05:08] <mwhudson> pff
=== _thumper_ is now known as thumper
[08:08] <ara> hello!
[08:09] <ara> can anyone remind me what was the option in bzr commit to close a lp bug, please?
[08:09] <bialix> --fixes
[08:09] <bialix> but it does not close, just add mark
[08:09] <ara> bialix, ok, thanks!
[08:15] <poolie> ara, --fixes lp:00000
[08:16] <ara> poolie, yes, thanks :)
[08:16] <ara> poolie, how is it going? about to finish the week for you, isn't it?
[08:16] <poolie> hi ara, bialix
[08:16] <poolie> yes
[08:16] <poolie> just ask stephanie :)
[08:17] <bialix> hi poolie !
[09:02] <spiv> Ok, I have a rough implementation of 'bzr merge-into' that passes some blackbox tests and has a fairly clean core implementation.
[09:02] <spiv> Just in time for beer o'clock ;)
[09:03] <spiv> All that remains is decrufting...
[09:03] <spiv> Have a happy weekend everyone!
[09:08] <fullermd> Harumph.  All you smug people over there, chasing the Date Line...
[09:13] <poolie> nice one spiv, have a good weekend
[09:51] <awilkins> jelmer, I have some problems with bzr-svn finding tags on a particular repository ; it tries once for each new branch, fails, then doesn't try again. Would you like a stack trace?
[10:07] <jelmer> awilkins: please file a bug
[10:38] <awilkins> jelmer, Clearing out the metadata cache may have fixed it.. on another note, why are tags a per-branch thing and not shared in a shared repository?
[10:40] <awilkins> (not that this is a bzr-svn thing)
[10:40] <awilkins> Since tags are on revisions not branches, and revisions are fundamentally stored in a repository, should tags not also be stored in the repository?
[10:41] <jelmer> awilkins: tags are like a dictionary though
[10:41] <jelmer> awilkins: you can't have a tag set on more than one revision
[10:41] <jelmer> awilkins: unlike your normal web2.0-ish tags
[10:41] <jelmer> awilkins: so if you have multiple unrelated projects in a repo you might get conflicts
[10:43] <awilkins> Heh, it was just affecting me after this tag discovery thing because it only does it once the first time it pulls the branch - so the branches that were suffering from it don't have the older tags... repulling them fixes that though
[10:43] <awilkins> Just occured to me that if they were a repo-level thing I'd only have to do it once.
[10:45] <awilkins> I suppose you could use the same tag on multiple diverged branches and only run into trouble when you wanted to merge them
=== nlisgo_ is now known as nlisgo
[11:02] <millun> hi
[11:04] <millun> i've created a branch in /var/www/. but when i try to do anything to update the branch (bzr merge, right?) i get error that /var/www is not a branch
[11:21] <spiv> millun: how did you create the branch?  What does "bzr info -v" report?
=== nlisgo_ is now known as nlisgo
=== nlisgo_ is now known as nlisgo
=== nlisgo_ is now known as nlisgo
=== nailuj24_ is now known as nailuj24
[16:49] <ronny_> hi
[16:51] <jelmer> hey ronny_
[16:51] <ronny_> easy_install/pip install bzr=={2.0,2.1,2.1.1} fails for me - can anyone fix that?
[16:52] <ronny_> ok, wait, easy_install actually finds 2.1
=== IslandUsurper is now known as IslandUsurperAFK
[17:12] <iamlouis> Hello! I was wondering if anyone could help me - I'm trying to set up bzr to keep track of a uni project - I want to be able to work on it on my desktop and my netbook and keep a master repo on my desktop. My problem is that I can't figure out how to do it, despite googling for ages! Any suggestions?
[17:14] <nailuj24> iamlouis: do you want to also have a repo online?
[17:16] <iamlouis> nailuj24: not just now, I'd rather get it to work before putting it online, and as it's for my course I wouldn't be able to accept any code contributions anyway! I thought I'd set up ssh on my desktop and then log in every now and then and commit changes from my netbook
[17:16] <mgz> that's kinda too broad a question to be able to usefully answer.
[17:16] <nailuj24> that would work indeed
[17:17] <mgz> I take it you've read <http://doc.bazaar.canonical.com/bzr.2.1/en/tutorials/tutorial.html>
[17:17] <nailuj24> iamlouis: in general, there's no thing like "master repo". in bazaar, all branches are equal
[17:17] <nailuj24> yes, the tutorial is a very good place to start
[17:18] <mgz> once you have the basics working on one machine, all you need to do it be able to address the other machine (by ssh as you said, or just see the filesystem over the network)
[17:19] <mgz> and create a new branch from the main one, so you can pull/push between them
[17:19] <mgz> probably don't need to worry about merging as it's only you working on it
[17:23] <iamlouis> I've looked at the tutorial, but a lot of it went over my head, I haven't really used a version control system before which probably doesn't help! I added a new user, created a branch and have a bzr server running, but I can't seem to commit changes to it, I'll go away and read the tutorial again, then maybe come back when I get totally stuck/confused! :-D
[17:23] <nailuj24> iamlouis: you don't need a server with bazaar :)
[17:23] <nailuj24> iamlouis: that's the good thing about it
[17:23] <nailuj24> iamlouis: basically, you commit to a normal directory
[17:24] <iamlouis> nailuj24: so how would I sync commits on my netbook and my desktop?
[17:24] <iamlouis> (sorry for asking idiotic questions btw!)
[17:24] <nailuj24> no problem. in theory, you just have two directories and keep them in sync
[17:25] <nailuj24> i found this very helpful when i started with bzr http://doc.bazaar.canonical.com/bzr.dev/en/mini-tutorial/index.html
[17:26] <iamlouis> thanks :-)
[17:48] <vila> iamlouis: if you can connect to your desktop via ssh and bzr is in your path, you can 'bzr push bzr+ssh://iamlouis@desktop/~/uni_project'
[17:48] <vila> iamlouis: and be done
[17:49] <vila> iamlouis: do some tests to understand when you need to 'bzr update'
[17:50] <vila> iamlouis: later, you can also look at 'bzr bind :push' on your laptop and 'bzr bind' when your desktop is not reachable (aka you're not connected to internet)
[17:51] <iamlouis> vila: thanks, I think I'm slowly getting there - just trying to set up the ssh server now on my desktop. I've got the local repo on the desktop working nicely, that mini-tutorial is brilliant
[17:51] <iamlouis> vila: cool, I'll look at bind once I get the basics sorted, thanks
[17:51] <vila> iamlouis: oh, and after the first push you can just 'bzr push' (search for the --remember option)
[17:52] <iamlouis> vila: great, thanks
[17:52] <vila> iamlouis: start without bind, you'll use it better once you're a bit more familiar with push and update
[17:53] <iamlouis> vila: will do, thanks
=== beuno is now known as beuno-lunch
[17:55] <mgz> vila, your computer survived then?
[17:57] <vila> mgz: no
[17:57] <mgz> ack.
[17:58] <vila> mgz: but I think I've got all the needed services restored: web, mail, ssh and gpg auth
[17:59] <vila> mgz: the HD died and since it wasn't serviceable (I swear I tried, but I resigned at step 3 when the DIY had 20 steps + 20 backwards of course)
[18:00] <mgz> may it live happily in machine heaven.
[18:01] <vila> I had to find a repair store, the best I found will give me my mac back with a new HD next wednesday (yes, tuesday at best(
[18:01] <vila> You live and learn :)
[18:01] <vila> The hard part that I was also running my "main" host as a vm there... So I lost not one but two machines
[18:02] <vila> Most of the backups were already in place on the laptop, and I had a 95% backup of the dead HD, but getting the last 5%...
[18:03] <vila> Ever heard about putting an HD in the freeze to make it work just that more minute to get this file pretty please nothing else fullpath given no cd I swear ?
[18:04] <mgz> heh, yeah, that trick is famous, no idea how reliable it actually is
[18:04] <vila> Well, I couldn't use it because my freeze is too small or a 24", but yes, waiting even for 20 minutes that the HD cool down, even at room temp, helped
[18:04] <vila> s/or a 24/for a 24/
[18:05] <rockstar> vila, it worked for me, but not for long.
[18:05] <vila> But I used it on an old HD with good results some years ago
[18:05] <mgz> the only hdd I've had trouble with refuses to actually die, it just got less and less reliable until I got fed up with it making my computer hang
[18:05] <vila> rockstar: yeah, I'm not suprised
[18:05] <guijemont> vila: you mean you can't get your HD out?
[18:06] <vila> mgz: I stopped playing with that long ago, a dieing HD is worse than any other hardware failure I can think of (on the other hand bluetooth these days...)
[18:07] <vila> guijemont: 20 steps+20 backwards ^
[18:07] <guijemont> mac ?
[18:07] <mgz> it's a mac, guijemont
[18:07] <vila> guijemont: The HD is *behind* the LCD
[18:07] <mgz> they don't make it easy.
[18:07] <guijemont> ok :)
[18:07] <guijemont> that's soooo simple on a thinkpad
[18:08] <guijemont> 1/ remove one screw
[18:08] <guijemont> 2/ take the hard drive
[18:08] <vila> mgz: that's a bit exaggerated, but this model is reputedly the worse, in fact the DIY was for a 20" and some guy had left comments about... well has left a patch
[18:08] <guijemont> really cool when I had to send imne for repair for sucky usb ports
[18:08] <guijemont> they let me the choice to *not* send my hard drive with all my data
[18:09] <vila> guijemont: the LCD itself couldn't be bought at that time, trust me that was a bargain
[18:10] <vila> I've only seen HD died three times, but this last one was the most aggressive and devastating one
[18:11] <guijemont> makes me think I should back up my stuff more
[18:11] <vila> guijemont: Hehe, be honest, when was the last one ?
[18:11] <guijemont> so far I've been lucky with HDs, but I don't believe this is always gonna be the case
[18:12] <guijemont> vila: well, err, ...kinda
[18:12] <guijemont> I did that when I installed karmic on my laptop
[18:12] <guijemont> since I changed from reiserfs to ext4
[18:12] <ronny_> who do i need to bug to fix easy_installablilty of older bzr releases that may still be in the wild
[18:12] <guijemont> I copied all my stuff on an external HD, and didn't delete it from there afterwards
[18:12] <mgz> not me, easy_install is the devil.
[18:13] <vila> rockstar: wow, that's kinda vague... versions ? OSes ?
[18:13] <mgz> wrock r-tab?
[18:13] <mgz> *wrong.
[18:13] <mgz> dammit.
[18:13]  * rockstar looks up
[18:13] <vila> errr, sorry rockstar, that was for ronny_ bad xhat, no sugar
[18:13] <vila> ronny_: wow, that's kinda vague... versions ? OSes ?
[18:13] <ronny_> vila: anything older than 2.1.1 cant be installed with pip/easy_install
[18:14] <ronny_> vila: and well, i really could use that for my build process for the anyvc ci server
[18:15] <vila> rockstar: that leaves only 2.0.6 for which we will gladly accept patches I think :)
[18:16] <vila> ronny_: but we recommand 2.1 over 2.0 anyway, the former has received optimizations and bug fixes and there is no good reason to *not* upgrade
[18:21] <mgz> bah, so much for testing that.
[18:21] <mgz> bzr-git needs dulwich needs a C compiler.
[18:22] <ronny_> vila: well, this is just for having backward-compatibility tests in my ci
[18:22] <mgz> I'm not launching on upgrading this box from lenny right now, or deleting enough stuff to fit gcc on there
[18:24] <mgz> ...I guess I can always remove gcc after... okay then.
[18:24] <vila> ronny_: I don't get it, I'm all for automated tests, but backward comp of what with what ?
[18:25] <vila> mgz: You have a lenny setup ???
[18:25] <mgz> ...which... still failsm, errors in dulwich/_objects.c
[18:26] <mgz> ^yup, on my old box
[18:27] <mgz> 's a K6-III and not a big HDD.
[18:27] <vila> If you need a bigger HD and have a fridge I may make you an offer you could not resist in a couple of days...
[18:27] <mgz> ehehhe
=== IslandUsurperAFK is now known as IslandUsurper
=== beuno-lunch is now known as beuno
[18:30] <vila> mgz: oh, and I should have a fix for most of the thread leaks RSN, I'm sorry it took so long to get some progress on the indows32 stuff
[18:30] <ronny_> vila: bzr versions that are still in the wild?
[18:30] <mgz> it's not an easy fix, if you'd have done it in a day I'd have almost been offended :)
[18:30] <vila> mgz: The main source of thread is now SocketListener
[18:32] <vila> ronny_: if that's for automatic installs, can't you just 'bzr pull --overwrite -rtag:xxx ; make ' and run from source ?
[18:33] <vila> ronny_: I mean installs in the ci context (hudson ?)
[18:34] <vila> mgz: I'm around 50 tests leaking and most of them come from this single point
[18:34]  * vila off, may pass around later
[18:35] <mgzmini> ah, now I see, don't have Python headers on here for some reason
[18:35] <ronny_> vila: i'd have to script that, and only for bzr, wouldnt be worth it
[18:35] <mgzmini> later vila, good news on thread leaks, if not hard drives.
[18:41] <iamlouis> vila: cheers for your help earlier, got it working now, thanks!
[18:48] <ronny_> i wouldnt have any issues if the bzr guys would actually upload their releases to pypi :(
[18:50] <mgz> using setuptools is asking for issues.
[18:53] <ronny_> mgz: im using pip install, works fine, caches after the first install, and generates no issues
[18:53] <ronny_> mgz: however that needs the releases to be findable somehow
[18:54] <ronny_> and older bzr releases arent findable
[18:54] <mgz> scraping webpages for binary code isn't a great way of doing things.
[18:54] <ronny_> mgz: scraping the pypi index for source packages is reasonable enough
=== BasicPRO is now known as BasicOSX
[19:29] <bitdancer> I've got a simple quesiton whose answer I couldn't find in the docs: how do I get bzr to display its currently remembered locations?
[19:43] <exarkun> Can I expect "bzr revert; bzr update; bzr clean-tree --force --ignored --unknown --detritus" to give me a working tree that's exactly the same as one I'd get from a clean "bzr checkout"?
[19:58] <maxb> I would certainly think so. I can't see how there would be any difference left after that
[19:58] <maxb> bitdancer: bzr info
[19:58] <exarkun> Darn it, it turns out I want one difference to remain :/
[19:59] <bitdancer> maxb: ah, so simple.  Thank you.
[20:00] <bitdancer> maxb: except that it doesn't tell me what I want to know.
[20:00] <bitdancer> :(
[20:01] <maxb> Does it not? What did you want to know?
[20:11] <maxb> bitdancer: ?
[20:13] <bitdancer> maxb: I figured it out.  It said 'parent branch' and I was expecting 'pull branch' or something like that.
[20:14] <bitdancer> what I want is to know what branch is going to be used if I omit the branch on any given command.
[20:15] <bitdancer> so I'm still not sure what that will be in all cases, but I'm sure I'll learn soon enough.
[21:33] <rockstar> bitdancer, bzr info will give you that information on a branch
=== nlisgo_ is now known as nlisgo
=== Adys_ is now known as Adys