[00:06] <OldAl> I see Patrick is still online - is that correct?  I am still in the bzr chat room.
[02:33] <Peng> Am I doing something dumb, or is BzrDir.create_branch_and_repo('foo') supposed to raise a KeyError?
[02:33] <Peng> (Seems the format argument is less than optional.)
[02:33] <lifeless> Peng: I imagine you're doing something unusual
[02:33] <lifeless> or its broken
[02:36] <Peng> D'oh. Of course it works now when I try to reproduce it. :|
[02:47]  * Peng watches get_parent_map try to figure out that the repo is empty.
[02:59] <Peng> I can't reproduce it now. :\
[02:59] <Peng> The target *may* have already had a .bzr directory in an odd state.
[03:00] <Peng> No, wait, that raises a different error.
[03:01] <Peng> Here's the traceback, FWIW: http://paste.pocoo.org/show/152176/
[03:04] <lifeless> untested code path I imagine
[03:05] <lifeless> file a bug please
[03:16] <Peng> lifeless: filed bug #486535, fwiw
[05:29] <OldAl> Anyone there?
[05:35] <OldAl> pidgin tells me there are 116 people in room, but there does not seem to be any activity, viz people coming or going, nor do I see my nick on the list...
[05:39] <mwhudson> it's usually pretty quiet on the weekend
[05:40] <lifeless> OldAl: it doesn't matter who is here or not
[05:41] <lifeless> OldAl: everyone might be here, and noone able to answer your question. Just Ask.
[05:41] <OldAl> ah, geat!
[05:42] <OldAl> I only want to ascertain that I have connected to #bzr chat room.
[05:42] <lifeless> pidgin is correct, you are connected ;)
[05:43] <OldAl> where are you from, lifeless?
[05:43] <OldAl> I am from Canberra
[05:44] <OldAl> May I put you down as a buddy?
[05:46] <lifeless> IRC isn't like IM networks
[05:46] <lifeless> there isn't the same social-network / buddies aspect
[05:46] <OldAl> Here is a question - when I connect, I get a message: (15:51:49) NickServ: (notice) OldAl is not a registered nickname.  So, should I a) ignore it b) register and if so where?
[05:47] <lifeless> http://freenode.net/
[05:47] <OldAl> But I have registered on freenode.net - else I would not be here, would I?
[05:48] <lifeless> what do you mean by upgrade :)
[05:48] <lifeless> sorry
[05:48] <lifeless> by registered
[05:49] <OldAl> Well, I did fill out some details and was able to connect under an OldAl nick, but it showed my real given name...
[05:50] <OldAl> so I suspect that it was not complete or something.
[05:50] <bob2> you register your nick by talking to nickserv using your irc client
[05:51] <bob2> pidgin is not a very useful irc client
[05:51] <lifeless> OldAl: so each time you connect you need to login
[05:51] <lifeless> and that message says you haven't actually registered a usercode
[05:52] <OldAl> OK, so what is the button to press to start registration?
[05:53] <lifeless> http://freenode.net/faq.shtml#nicksetup
[05:53] <OldAl> and, lifeless, did you have to type in "OldAl:" in your previous message?
[05:53] <lifeless> no
[05:54] <OldAl> so what is the smart way of getting that?
[05:54] <lifeless> getting what ?
[05:54] <bob2> irc clients tab complete nicks, so you type o<tab>
[05:55] <OldAl> lifeless: OK :
[05:55] <OldAl> lifeless: That's a great help.
[05:55] <OldAl> lifeless: Many thanks for that.
[05:56] <OldAl> lifeless: I do appreciate your help.  Will read up the FAQ on registration of a user name.
[05:56] <lifeless> so actually, I was answering 'did I need to have OldAl present at the start of the message' with 'no'.
[05:57] <lifeless> not how I went about putting it there :)\
[05:58] <OldAl> lifeless: You wrote parts of FAQ for pidgin?
[05:58] <lifeless> nope
[05:59] <OldAl> lifeless: Oh, I was at cross purposes there - I am now using the tab - great "invention".
[06:00] <OldAl> lifeless: Since my nick is apparently not registered. how can I talk to you?  Is it a temporary "registration"?
[06:01] <bob2> this isn't IM
[06:01] <bob2> registration just means that a) you're allowed in some channels that forbid unregistered users and b) you can kick off other people who use your nick
[06:02] <OldAl> lifeless: Well, I don't know IM.
[06:02] <lifeless> for a) bob2 meant 'not allowed in'...
[06:02] <lifeless> OldAl: imagine that this is a table in a restraunt
[06:02] <lifeless> when you are connected, you are at the table. And everyone here can hear everyone else.
[06:02] <OldAl> lifeless: yap
[06:02] <OldAl> fine
[06:03] <lifeless> *if* you get an 'official' name badge, then you can grab someone and talk to them privately, and sit at some tables that require people to have official names
[06:05] <OldAl> lifeless: But I have chatted with people already, in separate "table" (or room), as it were.
[06:51] <mneptok> lifeless: missed you at UDS :(
[06:52] <lifeless> mneptok: Swings and roundabouts
[06:53] <lifeless> had stuff going on I would have had to shove around, and no specific things I needed to be at UDS for this time
[06:53] <mneptok> and i thought we had something *special*
[06:54] <mneptok> *sniff*
[06:55] <lifeless> we do
[06:55] <lifeless> I hear you made an unrepeatable quote
[06:56] <lifeless> so bad only its existence hit the Quotes page
[06:56] <mneptok> it wasn't that bad.
[06:57] <mneptok> Keybuk likes to paint me as a greater rogue than i am. i think it's part of his rich fantasy life.
[06:57] <lifeless> it wasn't Keybuk :)
[06:58] <mneptok> hrmf. he said he had added it.
[06:58] <mneptok> trying to make himself more attractive to me, i s'pose.
[06:58] <lifeless> I think I'd need to go check I guess.
[06:59] <mneptok> not that his rugged good looks and commit rights don't make him attractive enough.
[07:02] <mwhudson> mneptok: i even clicked a link in your blog and didn't regret it too much!
[07:02] <mneptok> mwhudson: oh nice! you got that Thorazine scrip and lobotomy you were asking for!
[07:03] <mneptok> (or you're just insanely drunk)
[07:03] <mwhudson> c'mon, the police aren't that bad
[07:03] <mwhudson> (i am disturbingly hungover for 20:00 though :/)
[07:04] <lifeless> mwhudson: hungover or drunk ?
[07:04] <mwhudson> lifeless: hungover
[07:04] <lifeless> wow
[07:04] <mwhudson> i didn't even drink _that_ much last night :/
[07:04] <mwhudson> getting old, it's terrible
[07:05] <lifeless> sneaks up on ya
[07:05] <mneptok> i have t-shirts older than both of you.
[07:12] <chx_> hi. i was wondering whether it would be possible / feasible / desirable to integrate trac-bzr-loggerhead together.  I guess a post commit hook that posts to trac and an apache rewirte rule so that the commit linking to the bzr source viewer ties into loggerhead instead?
[07:13] <lifeless> chx_: I don't know what that means
[07:13] <lifeless> nor have any idea about whether it would be good or bad to do it.
[07:14] <chx_> well, currently we use svn and commit messages (re #1234) post followups to tickets
[07:14] <chx_> that's awesome
[07:14] <chx_> The other part of the svn integration in trac is the source code browser
[07:14] <chx_> that's what i was considering replacing with loggerhead.
[07:15] <lifeless> so loggerhead showing svn?
[07:15] <chx_> no, we are migrating to bzr
[07:15] <chx_> oh now we are talking... anyone from Canonical here ?
[07:17] <lifeless> yes
[07:17] <lifeless> loggerhead can show svn btw
[07:17] <lifeless> wonders of bzr-svn :)
[07:27] <chx_> lifeless: pm?
[07:28] <lifeless> I guess
[07:30] <mneptok> oh no! the *bad* Monty!
[07:30]  * mneptok hides
[07:32] <lifeless> mneptok: does that make you the Full one?
[07:33] <mneptok> lifeless: not if you can't be bothered to visit UDS.
[07:37] <lifeless> mneptok: Sif a matter of botherment.
[07:43] <kgoetz> stupid python, stop making bzr complain about my locale :(
[07:45] <lifeless> kgoetz: install the locale data for it :)
[07:47] <kgoetz> lifeless: I'm not aware of any en_AU.UTF-8 python packages ;)
[07:51] <lifeless> kgoetz: its generally just missing langpacks, if you're on Ubuntu
[07:51] <lifeless> or it can be a missing langpack on a server.
[07:56] <kgoetz> nothing leaps out at me from the debian stable repos, so I might just put up with it
[07:56] <lifeless> kgoetz: a ew questions
[07:56] <lifeless> is it local or when pushing/pulling?
[07:58] <kgoetz> its local. and the install is pretty minimal - its netinstall of debian+a handful of packages
[07:59] <lifeless> check your local is being created
[08:00] <lifeless> kgoetz: also please file a bug if this is happening with bzr installed from a package; we shouldn't behave wrong from a package
[08:01] <kgoetz> lifeless: I don't follow - 'your local is being created'?
[08:01] <kgoetz> oh, *smacks self*
[08:03] <lifeless> kgoetz: I'll be afk for a bit, but it sounds like you've found a cluebat?
[08:04] <kgoetz> lifeless: checking local setup atm.
[08:08] <kgoetz> dpkg-reconfigure locales to the rescue.
[08:11] <OldAl> Why is it so quiet here?
[08:12] <OldAl> nobody wants to chat about bzr?
[08:13] <kgoetz> OldAl: seems no one needs support ;) it is sunday...
[08:13] <OldAl> kgoetz: No, it is not support - just signs of life!
[08:14] <OldAl> kgoetz: and just tell me, is this the bzr chatroom? (I expect so, but just to be sure. yes/no will do :) )
[08:15] <kgoetz> OldAl: I'm looking at my screen+scrollback, and i see lots of conversation
[08:15] <OldAl> Well, it must be #bzr, I hope.
[08:16] <OldAl> kgoetz: Sunday or not, I've just completed registering my nick - or so I hope.
[08:16] <kgoetz> it would seem your identified, so yes, your registered
[08:17] <OldAl> kgoetz: Thanks for that.
[08:18] <kgoetz> *you're
[08:18] <kgoetz> np. /whois OldAl to see
[08:18] <OldAl> kgoetz: I will log off and leave you in peace!  Thanks for helping me to check what is going on
[08:18] <kgoetz> OldAl: catch you nex time :)
[13:08] <OldAl> me_too: Like your nick...
[13:09] <OldAl> me_too: Are you watching the screen of bzr?
[13:09] <OldAl> menesis: Hi there!
[13:10] <OldAl> Actually it is a bit late for me - down under Canberra, the time is past midnight
[13:19] <OldAl> Noldorin: Alex, where are you? (I am in Australia, Canberra)
[13:20] <OldAl> Noldorin: irc informs me that you are on bzr, so ...
[14:42] <matt_p> Hi, where is a downloadable version of the User Reference?
[14:43] <matt_p> It can be viewed as a HTML, but there is no PDF version...
[14:45] <GaryvdM> matt_p: http://doc.bazaar-vcs.org/bzr.2.0/downloads/
[14:45] <GaryvdM> or http://doc.bazaar-vcs.org/bzr.dev/downloads/
[14:45] <matt_p> GaryvdM: http://doc.bazaar-vcs.org/bzr.2.0/downloads/pdf-en/
[14:46] <matt_p> GaryvdM: There is only the Quick Ref.
[14:46] <matt_p> I need this: http://doc.bazaar-vcs.org/bzr.2.0/en/user-reference/index.html
[14:47] <GaryvdM> http://doc.bazaar-vcs.org/bzr.2.0/downloads/pdf-en/bzr-en-user-guide.pdf ?
[14:48] <matt_p> GaryvdM: It is User Guide, not User Reference
[14:48] <GaryvdM> matt_p: It's the same thing as far as I can tell.
[14:49] <matt_p> GaryvdM: So you mean that this http://doc.bazaar-vcs.org/bzr.2.0/en/user-guide/index.html and this http://doc.bazaar-vcs.org/bzr.2.0/en/user-reference/index.html are the same documents? :-)
[14:50] <GaryvdM> matt_p: Sorry - I'm wrong. It's not the same.
[14:51] <GaryvdM> matt_p: Sorry  - I don't know then.
[14:51] <GaryvdM> matt_p: igc will know. But he will probably be asleep now. He is in Austraila
[14:52] <matt_p> GaryvdM: OK, thanks.
[14:57] <matt_p> Oh, I have a second question... I use Bzr and I understand its concepts as a user. But what is the right relation between branches and repositories? (Shared) repo contains the revisons in their physical forms and the branches only point to the relevant revisions?
[14:58] <GaryvdM> matt_p: Yes. A branch has just a pointer to the latest revision, tags, and config
[14:58] <gioele> matt_p: yes, repositories holds all the information: file contents, deltas, other common info
[14:58] <GaryvdM> matt_p: A stand alone branch has a repository
[14:59] <GaryvdM> *has it's own repository
[14:59] <gioele> matt_p: http://bazaar-vcs.org/CategoryTerm
[14:59] <GaryvdM> gioele: Nice collaboration :-)
[14:59] <gioele> GaryvdM: :)
[15:00] <matt_p> GaryvdM, gioele: great, thank you.
[15:00] <gioele> matt_p: in particular the first sentence of http://bazaar-vcs.org/Branch
[15:09] <pitseleh> hi, i'm trying to host a bazaar server
[15:09] <pitseleh> so i start the server with bzr-2.6  server --directory=/mnt/md1/public/Glen/Repos
[15:09] <pitseleh> and i can branch from it fine
[15:09] <pitseleh> but when i try to push it tells me operation not possible: readonly transport
[15:10] <pitseleh> pushing to bzr://ip/myrepo
[15:10] <pitseleh> i'm obviously missing a step..
[15:10] <GaryvdM> pitseleh: you need bzr server --allow-writes
[15:10] <pitseleh> GaryvdM: ah, thanks for that :)
[15:11] <pitseleh> works perfectly :D, wonderful
[17:14] <Lo-lan-do> Hi jelmer :-)
[17:15] <jelmer> hey Lo-lan-do
[17:15] <Lo-lan-do> For some reason my changes don't work anymore.
[17:15] <Lo-lan-do> (Even given the stretched value of "work" I used)
[17:18] <jelmer> Lo-lan-do: it might be nice to have some tests for this code first and figure out the right approach
[17:20] <Lo-lan-do> Probably, yes.  Is there a tutorial on that, or should I just read the existing tests?
[17:21] <Lo-lan-do> Also, it might be a bit complex, since I'm trying to do git+ssh:// with a git client…
[17:33] <jelmer> Lo-lan-do: There isn't anything like that at the moment, in fact I don't think we have any tests for the server side
[17:34] <jelmer> you should be able to test with the git:// server though, since the protocol should be the same
[17:35] <jelmer> testing with ssh will be trickier
[17:36] <Lo-lan-do> I think maybe the "git proxy" configuration could help
[17:49] <Lo-lan-do> Actually, $GIT_SSH pointing at a custom script can do the trick :-)
[17:50] <jelmer> Lo-lan-do: isn't that kinda hard to set up in the tests though?
[17:58] <Lo-lan-do> I don't think so.  It's just an environment variable.
[17:59] <Lo-lan-do> And a 30-line shell script.
[18:03] <Lo-lan-do> http://pastebin.com/f1db8ac6c
[18:03] <Lo-lan-do> Stick that in a script, point $GIT_SSH at it, and there you go, git+ssh:// without ssh :-)
[18:04] <Lo-lan-do> I'm off to dinner, but I'll probably start doing unit tests afterwards.
[18:48] <eli_> hi, when you do 'bzr init' and then 'bzr add' it should add all subdirs. correct?
[18:49] <eli_> the part is that when i do 'bzr status' i get a good chunck of unknown objects
[18:50] <Lo-lan-do> Objects that were created later on?
[18:50] <eli_> even doing 'bzr add foldername' and then do 'bzr status' the foldername will still show up under unknown
[18:50] <eli_> nope, the objects are already there
[18:51] <eli_> it only adds two directories out of about 10
[18:52] <eli_> that is not how bzr normally acts. right?
[18:52] <beuno> eli_, that is not expected behavior, no
[18:53] <LarstiQ> it should either add or ignore, no unknowns
[18:53] <eli_> hmm
[18:53] <eli_> it even treats .bzrignore as an unknown
[18:53] <LarstiQ> that can happen
[18:53] <eli_> i'm using version 2.0.1
[18:54] <LarstiQ> if you manually create the file
[18:54] <LarstiQ> without using `bzr ignore`
[18:54] <LarstiQ> eli_: it's not perchance already versioned? (Different vcs maybe)
[18:55] <eli_> you mean having .svn in the subdirs?
[18:56] <LarstiQ> eli_: oh, that might explain it
[18:56] <LarstiQ> eli_: if you also have bzr-svn installed that is
[18:57] <eli_> LarstiQ, i think your suggestion may have hit it.
[18:57] <eli_> It was not .svn, there were .bzr in each subdir
[18:58] <LarstiQ> yeah
[18:58] <eli_> bingo, adding everything now :)
[18:58] <eli_> Thanks!
[18:58] <LarstiQ> that is indeed a case I forgot that will result in unknown dirs :)
[18:58] <LarstiQ> eli_: cheers!
[19:00] <eli_> is there a way to list just the unkowns in bzr?
[19:01] <LarstiQ> `bzr ls --unknowns`
[19:01] <LarstiQ> optionally with -R
[19:02] <eli_> excellent. bzr is already proving much more handy than hg and svn :)
[19:03] <LarstiQ> I'm glad to hear that :)
[19:03] <LarstiQ> though a bit surprised perhaps, how is hg lacking?
[19:12] <eli_> hg is creates larger histories than bzr. at least in my case
[19:19] <chx_> So yeah i was trying to research hg vs bzr vs git (not in speed) for recetn versions and ... hmm...
[19:21] <GaryvdM> chx_: and ?
[19:21] <chx_> empty/
[19:21] <chx_> i cant find anything
[19:22] <LarstiQ> chx_: http://bazaar-vcs.org/Benchmarks ?
[19:22] <chx_> as said, not in speed
[19:22] <chx_> we can simply take it granted they are all fast.
[19:22] <LarstiQ> chx_: no, this is disk space
[19:22] <GaryvdM> chx_: http://doc.bazaar-vcs.org/migration/en/why-switch-to-bazaar.html
[19:24] <GaryvdM> chx_: Both my url, and LarstiQ's are up to date documents.
[19:26] <chx_> oh
[19:26] <chx_> the latter is very nice
[19:26] <chx_> how come i couldnt find it this with google
[19:27] <LarstiQ> chx_: what did you google on?
[19:27] <GaryvdM> I found it with http://www.google.com/search?q=why+bzr , But I knew the name of the doc.
[19:27] <chx_> bzr git comparison
[19:27] <chx_> bzr vs git
[19:28] <chx_> I am reading this
[19:28] <chx_> and though i myself am using bzr since long, i find interesting pieces
[19:28] <chx_> how do i create a bound branch?
[19:28] <GaryvdM> chx_ bzr checkout
[19:29] <chx_> oh that
[19:29] <chx_> i see.
[19:29] <GaryvdM> chx_: or if you allready have a branch, bzr bind
[19:29] <chx_> nice
[19:30] <chx_> another question , hardlinks
[19:30] <chx_>   --hardlink            Hard-link working tree files where possible.
[19:30] <chx_> i see that
[19:30] <chx_> this hardlinks files inside .bzr i presume?
[19:31] <GaryvdM> I'm not sure
[19:31] <Peng> It explicitly says "working tree files", so probably not.
[19:31] <LarstiQ> 'working tree' suggest otherwise, but I don't know what it does
[19:31] <LarstiQ> hey Peng ;)
[19:31] <chx_> huh that would be nice but challenging what happens if someone edits one such file...?
[19:32] <Peng> chx_: Yeah. If your text editor doesn't break links, it won't work for you. That's why it's not the default.
[19:33] <chx_> Peng: and which editors breaks...?
[19:33] <Peng> chx_: No idea!
[19:33] <LarstiQ> vim breaks hardlinks, so that should work
[19:33] <LarstiQ> I'm sure emacs can too
[19:34] <chx_> it would need to save the file under a diff name , rm the oriiginal and mv back
[19:34] <chx_> i presume that's not hard.
[19:35] <Peng> It's a nice way of making the write a bit safer, too.
[19:39] <eli_> is there a way to have bzr to not create histories of binary files?
[19:39] <eli_> rather than an outright ignore?
[19:41] <eli_> for example, i have several subdirs with binaries and scripts
[19:41] <eli_> i would like to version control the scripts
[19:41] <eli_> but not the binaries.
[19:42] <eli_> but, if i do push or pull with bzr i'd like to have the binaries move between systems
[19:42] <eli_> probably sounds like a dream, but that would well for me
[19:42] <LarstiQ> nope, something is either versioned or not.
[19:42] <LarstiQ> (likewise, there is no 'precious' class of unknowns)
[19:43] <LarstiQ> eli_: you fear the binaries would take up a lot of space?
[19:43] <eli_> yep
[19:43] <eli_> tons
[19:43] <eli_> but i do need them synced between two computers
[19:44] <eli_> and keep version control on the scripts
[19:44] <LarstiQ> can the binaries be generated from something else?
[19:45] <eli_> nope, the binaries are data files. they are not dynamically generated
[19:45] <LarstiQ> ok
[19:45] <LarstiQ> could you maybe version them in a separate branch?
[19:45] <LarstiQ> and have symlinks in the original?
[19:46] <eli_> that would seperate out the binaries from the scripts
[19:47] <eli_> generating the symlinks would be the next complication. we're talking +10,000 binaries
[19:48] <LarstiQ> woha
[19:48] <eli_> yeah, lots
[19:48] <LarstiQ> not your typical usecase :)
[19:48] <eli_> nope ;)
[19:48] <eli_> would it be possible to do a layer of rsync with bzr?
[19:49] <eli_> rsync for the binaries
[19:49] <LarstiQ> you could maybe hack up a plugin (based push-and-update?) to do something like that
[19:49] <eli_> and bzr for version control
[19:49] <LarstiQ> eli_: yeah
[19:49] <eli_> even with the binaries in the same dirs as the scripts?
[19:49] <LarstiQ> yes
[19:49] <eli_> hmmm
[19:50] <eli_> that would work then
[19:50] <LarstiQ> it would be a plugin tailored to your workflow
[19:50] <LarstiQ> (or more general if you wish)
[19:50] <eli_> i know quite a few people in my field who would use such a workflow
[19:50] <eli_> ill write it up then
[19:51] <eli_> thanks for your help in brainstorming on this :)
[19:51] <eli_> adios!
[19:51] <LarstiQ> eli_: http://doc.bazaar-vcs.org/plugins/en/push_and_update-plugin.html is what I'd start with
[19:52] <eli_> Thanks
[19:52] <eli_> will looks into
[20:33] <maxb> I am not familiar with the bzr test system. Can anyone suggest what I should look into when a test 'fails'  because it starts thinking normal progress messages are errors?
[20:34] <maxb> errors:
[20:34] <maxb> 'All changes applied successfully.\nCommitting to: /tmp/testbzr-LDqLMO.tmp/bzrlib.plugins.rebase.test_blackbox.TestRebaseSimple.test_rebase_merge/work/main/feature/\nCommitted revision 3.\nAll changes applied successfully.\nCommitting to: /tmp/testbzr-LDqLMO.tmp/bzrlib.plugins.rebase.test_blackbox.TestRebaseSimple.test_rebase_merge/work/main/feature/\nCommitted revision 3.\nAll changes applied successfully.\nCommitting to: /tmp/testbzr-LDqLMO.tmp/bzrlib.plugins.re
[20:34] <maxb> base.test_blackbox.TestRebaseSimple.test_rebase_merge/work/main/feature/\nCommitted revision 4.\nAll changes applied successfully.\nCommitting to: /tmp/testbzr-LDqLMO.tmp/bzrlib.plugins.rebase.test_blackbox.TestRebaseSimple.test_rebase_merge/work/main/feature/\nCommitted revision 5.\n'
[20:35] <LarstiQ> that's a bit unreadable
[20:36] <LarstiQ> maxb: but blackbox tests especially look at the output the cli produces
[20:36] <LarstiQ> if that doesn't match with what the test expect, it flags
[20:38] <lifeless> maxb: ask 'is the new output what I want'?
[20:38] <lifeless> maxb: if yes, change the test. If no, change your code.
[20:38] <maxb> hmm. I wonder why I am getting stderr output when before there was none at all
[20:39] <maxb> All I've done is change rebase parent selection logic
[22:13] <igc> morning
[22:15] <OldAl> igc: good morning.
[22:15] <OldAl> poolie: top of the morning, to you too.
[22:15] <poolie> hello
[22:16] <OldAl> poolie: Strange, but have no questions to  ask right now...
[22:16] <igc> hi poolie
[22:16] <poolie> hi igc
[22:18] <poolie> spiv, hi?
[22:18] <igc> OldAl: so pull, merge and push are all in handled in the one qbzr module IIRC
[22:19] <igc> OldAl: bound branch or otherwise, pull is the way to update a local mirror
[22:19] <igc> so it's pretty useful
[22:21] <OldAl> igc: I am sure it is.
[22:22] <igc> OldAl: so starting on a small change to qpull is a good, safe way of beginning qbzr hacking
[22:22] <OldAl> Have 'they' (who?) used gtk or Qt for the GUI of qrun?
[22:22] <OldAl> I would prefer to put my hands into Qt rather than gtk
[22:23] <igc> OldAl: any command startng with 'q' is Qt based, not Gtk
[22:23] <OldAl> igc: Ah, great!
[22:23] <OldAl> igc: that puts my mind at ease on that score.
[22:24] <igc> OldAL: one more social thing: in open source, we value self-selection over central assignment
[22:24] <igc> so me assigning bits of work to people isn't the way to go
[22:24] <OldAl> igc: I know tha well.
[22:25] <OldAl> igc: Why not suggest stuff to start on - individually.  Nobody should mind suggestions...
[22:25] <igc> instead, I ask for volunteers, people enter changes in our bug/wishlist tracker and assign them to themselves instead
[22:25] <OldAl> igc: not if they want to work on it.
[22:25] <igc> OldAl: sure, individual suggestion for people keen to get started in excellent
[22:26] <igc> that's why I'm suggesting you working on qpul first :-)
[22:26] <igc> OldAl: I'll raise the minor bug I'm thnking of now
[22:26] <OldAl> igc: I gather that and am happy to look at.  But then there is a bigger question of how to get
[22:27] <OldAl> igc: things to speed up in the "documentation" group and I thought I would make a suggestion - to you :)
[22:28] <OldAl> igc: But I don't want to do it in public before I suss out if you would be agreable.
[22:28] <OldAl> igc: No conspiracies - but just that I don't want to be too big a PITA with suggesting something that my appear as extra work.
[22:30] <OldAl> igc: If you are satisfied with the response, that is fine: if not, then there is a suggestion that I want to make, if agreeable to YOU, as it would affect you if you accept it.
[22:32] <igc> OldAl: here's the bug you could work on: bug 486843
[22:32] <igc> OldAl: don't worry about public suggestions being a PITA
[22:33] <igc> OldAl: even if I don't agree, someone else may step up and do it or refine your idea
[22:34] <igc> OldAl: if in any doubt, favour open communication over private emails and IRC chats
[22:34] <OldAl> ubottu: Thanks for the bug 486843. "Being too verbose" is my problem, usually. I do feel that verbosity is superior to lack of clarity.
[22:35] <OldAl> ubottu: So who is the midget inside of you? (Reminds me of a chess playing "machine")
[22:37] <igc> OldAl: ubottu really is code, not a person
[22:38] <OldAl> igc: I am in agreement with "public" preference to "private".  Alas, some things, like disabilities, may want to be kept private.
[22:38] <igc> OldAl: very useful though - just say "bug xxx" and ubutto will display the bug summary
[22:38] <igc> OldAl: right. Personal stuff is best kept personal
[22:38] <igc> and private
[22:38] <OldAl> igc: xxx is the number?
[22:39] <igc> yep
[22:39] <igc> just #xxx might be enough as well
[22:39] <igc> iirc
[22:40] <OldAl> igc: Actually, I don't mind to talk about *my* disabilities, but what I do - or do not do - affect the disabilities of others and that I want to keep private.
[22:42] <OldAl> igc: also things like my experience and qualifications - it is rather a long list and requires explanation, but I feel it would be helpful to know for people that may try to get something useful done by me...
[22:43] <OldAl> igc: Basically, again I try not to be a PITA, seldom successfully.
[22:44] <OldAl> igc: Clarify: my tries at avoiding being a PITA are seldom successful.
[22:45] <igc> OldAl: so my suggestion is to create a Wiki page or blog with your experience and skills. See http://ianclatworthy.wordpress.com/about/ for an example
[22:50] <OldAl> igc: Just looked at your blog. Impressive! I guess for me it would be easiest to make something vaguely similar in my home page on PCUG and just pass on the open address, which, however, is not obvious to casual visitors (like there are no links to it in the face page.)
[22:54] <OldAl> igc: clarification: PCUG is the PC Users Group in Canberra, very supportive of ONE OS, though not from the bunch of people who run the Internet Service, the admins.  (The admins are very supportive of their independence of any elected bodies of PCUG :) )
[22:55] <OldAl> igc: My last  sentence is clear as mud...
[22:55] <igc> OldAl: sure. Or add http://bazaar-vcs.org/OldAl
[22:57] <OldAl> igc: OK, that is simpler!  Easier to see for anyone that may be interested in my experience and qualifications.  Will give it a good run!
[22:57] <OldAl> igc: Thanks - have a call from my real boss!
[23:04] <spiv> Good morning.
[23:08] <igc> hi spiv
[23:18] <poolie> hello spiv
[23:19] <poolie> spiv, enquiring minds want to know about the patch pilot project :)
[23:19] <lifeless> poolie: well I'm on this week
[23:19] <lifeless> in my personal time
[23:19] <poolie> i know
[23:20] <poolie> i am obliquely asking spiv to send a mail about how the first week went
[23:20] <spiv> poolie: composing mail about that :)
[23:20] <poolie> :)
[23:20] <poolie> thanks for doing it this week lifeless
[23:22] <lifeless> spiv: be sure to call for more folk
[23:22] <spiv> lifeless: good idea
[23:28] <jdub> what's the sanest way to get a recent bzr for RHEL? EPEL appears to have 1.3
[23:28] <jdub> somehow this system has 1.5, but i dunno where from
[23:29] <lifeless> jdub: wget the tar
[23:37] <mlh> jdub: IF you wanted an rpm ANd you were comfortablish with src.rpms, you could try the src.rpm for F12 (which is bzr 2.0.2)