[00:09] <kfogel> vila: I think I have tried dvc before.
[00:10] <kfogel> vila: I dunno, I guess I just find the productivity gains not worth the effort of learning a new interface.  bzr in shell mode is already 95% of what I need, and it always Just Works.
[00:12] <mwhudson> dvc seems quite nice, but what you really need is for emacs to learn what a 'project' is, i think
[00:12] <mwhudson> or at least a branch
[00:12] <mwhudson> i hate having to C-x v all my buffers when i change branches
[00:14] <fullermd> Always works fine for me.  First, you fire up vim...
[00:43] <mthaddon> poolie: now a good time for me to switch on the "clean up the chroot" for bzr PQM?
[00:44] <poolie> yes please
[00:44] <mthaddon> cool
[00:50] <mthaddon> poolie: that's done - would be good if we were able to do a test commit
[00:51] <poolie> mthaddon: sure
[01:23] <mthaddon> poolie: any chance of that test commit so we can confirm the new PQM setup works?
[01:24] <poolie> mthaddon: yes, will send it soon...
[01:24] <mthaddon> cool, thx
[01:35] <jam> lifeless: I don't think I ever got around to factoring out the changes from my "hacks" branch, http://bzr.arbash-meinel.com/branches/brisbane/hack
[01:35] <jam> lifeless: but the specific changes are pretty small
[01:37] <lifeless> jelmer: ping
[01:37] <jelmer> lifeless: hello
[01:37] <lifeless> your InterBzrDirTransport
[01:37] <lifeless> is that in a patch for bzr.dev?
[01:37] <jelmer> BranchBzrDirInter?
[01:38] <lifeless> oh right
[01:38] <jelmer> that's in a branch here, but not submitted yet (since it lacks tests)
[01:38] <lifeless> uhh don't think that matches our needs - thanks
[01:44] <lifeless> poolie: spiv and I have just had a use case pass, which is "'bzr push bzr+ssh://foo' uses a smart verb to send the revision data in one stream"
[01:45] <lifeless> poolie: just don't ask what it does under the hood :P
[01:50] <poolie> igc, did you say you'll help OOo with their error? i'd like that.
[01:53] <igc> poolie: jelmer has replied to Heiner explaining that it's a bzr-svn bug and he's hoping to work on it this weekend
[01:53] <poolie> oh, great!
[01:54] <poolie> thanks
[01:54] <igc> poolie: also, I'm looking into a batch of fast-import bugs/patches today so that might help as well
[01:55] <lifeless> poolie: did you see my command hooks mail?
[01:57] <poolie> not yet
[02:15] <jelmer> lifeless, btw, I plan to submit a patch for InterBranch as well (for update_revisions/pull/push)
[02:16] <jelmer> lifeless, not really fit for your use case either, probably, but might change some of the same areas of code
[02:16] <jelmer> lifeless: also, would bug 272444 be appropriate for brisbane-core?
[02:34]  * igc lunch
[02:37] <lifeless> jelmer: patchesyadayadayada
[02:37] <lifeless> jelmer: I'm surprised we don't today
[02:40] <jelmer> lifeless, well, that one I don't actually care about :-) Was just wondering
[02:40] <jelmer> I might sent in one for the revision XML escaping
[02:40] <jelmer> having workarounds for that in bzr-git and bzr-svn is annoying
[02:40] <jelmer> and could potentially lead to corrupt revisions when roundtripping
[02:41] <jelmer> since there's no way to tell escaped characters apart
[02:41] <lifeless> I certainly think the core should be fixed
[02:41] <lifeless> bbc is purely focused on scaling-and-less-work-to-diff-two-inventories
[02:42] <mwhudson> verterok: ping
[02:43] <lifeless> if its not a scaling issue (size or performance), or a work-to-generate-diff issue, then its not going to get my attention at the moment, nor would I expect it to get John/Ian/Andrews (dataloss bugs and regressions are obvious exceptions to this rule of thumb)
[02:43] <lifeless> patches to the bbc development branch, to fix things that interest you would be cool
[02:44] <lifeless> jelmer: once the bbc focus is reached, obviously we can look for minor tweaks to do, but there is no reason to delay them if someone else is interested.
[02:46] <jelmer> lifeless, I should rephrase that; I meant it would be nice to get a new revision serializer in if we're going to be introducing a new repository format and rewriting revisions when upgrading to it.
[02:46] <jelmer> so not necessarily as part of bbc but rather of whatever format it will end up in
[02:46] <jelmer> (or is there no difference?)
[02:46] <lifeless> jelmer: there isn't a difference
[02:46] <jelmer> k
[02:46] <lifeless> lp:~bzr/bzr/brisbane-core
[02:46] <lifeless> development4* formats in there
[02:57] <poolie> mthaddon: if you're still here - i sent a trivial merge to pqm
[02:57] <mthaddon> poolie: yep, watching the logs
[02:58] <mthaddon> poolie: seems to be working nicely
[03:05] <lifeless> spiv: http://paste.ubuntu.com/116673/
[03:48] <lifeless> poolie: and we now have an acceptance test for pushing to a stacked branch using a streaming format
[03:49] <lifeless> poolie: passing
[04:44] <mthaddon> lifeless: bzr pqm seems to be hung on the sending the mail portion - should i just kill it, or is there any troubleshooting we can do?
[04:52] <lifeless> mthaddon: strace
[04:52] <lifeless> mthaddon: lsof
[04:52] <lifeless> mthaddon: etc etc etc
[04:52] <lifeless> (pqm doesn't do any magic here - if the 'mail' command is wedged, I'm not any more sure than you are whats causing it.
[04:53] <mthaddon> ok, nothing obvious there - thx
[04:54] <lifeless> what syscall is the program in?
[04:54] <lifeless> is the mail server itself wedged?
[04:55] <mthaddon> "read(0, " was all I got
[04:55] <mthaddon> mail server seems to be responding fine, though
[04:57] <lifeless> read(0 is in mail ?
[04:57] <lifeless> thats reading from stdin
[04:57] <lifeless> what syscall is pqm in?
[04:57] <lifeless> I have to go cathc a train
[04:57] <lifeless> can you brain dump all the info you have to a bug please
[04:58] <lifeless> get a python bt in pqm if possible
[04:58] <lifeless> and then kill it
[04:58] <lifeless> so people aren't blocked
[04:58] <mthaddon> was in "wait4(4294967295, "
[04:58] <mthaddon> have killed it - will keep an eye on it - have seem this every now and again before, just want to make sure it's not related to the config change I've just made
[05:32] <lifeless> mthaddon: thats a deadlock for sure, pqm is waiting, mail is wating
[05:32] <lifeless> mthaddon: so the question is, why is mail waiting
[05:33] <lifeless> spiv: so, turns out the Branch tests were running with real branches
[05:36] <spiv> lifeless: even when they were supposed to be parameterised not to?
[05:41] <lifeless> :P
[05:41] <lifeless> remember the bug we found where we got a real object back?
[05:41] <lifeless> thats why it expected a remote, because we fixed that bug
[05:42] <lifeless> the reason it only saw a real was... drum roll, because that was the server side one raising the event
[05:44] <lifeless> (RemoteBranch.set_revision_info doesn't invoke hooks)
[06:03] <poolie> lifeless: we've seen this before with pqm
[06:03] <poolie> congrats on your test passing btw
[06:04] <poolie> i suspect somebody relying on gc to close the pipe or something similar
[06:07] <lifeless> poolie: its in wait4(
[06:07] <lifeless> pqm is waiting for the response
[06:07] <lifeless> and mail is in read(0
[06:07] <lifeless> so its reading from stdin
[06:07] <poolie> yes exactly
[06:07] <lifeless> I can't remember what module pqm uses to send mail
[06:07] <poolie> pqm thinks mail should finish up but it hasn't actually closed the input pipe
[06:07] <poolie> i looked into this last time
[06:07] <lifeless> erm, 'which mail'
[06:07] <lifeless> so it might be bzr-mail
[06:08] <lifeless> or it might be the pqm success mail
[06:08] <lifeless> the backtrace should tell us
[06:08] <poolie> i think it runs it directly through subprocess
[06:08] <lifeless> there are two mail events
[06:08] <poolie> the command arguments to mail made it clear which it was
[06:08] <lifeless> ok
[06:08] <poolie> well, i'm assuming here that there are not two bugs with identical symptoms
[06:08] <lifeless> well, I started well before 9 :) and its >5, so really calling it a day
[06:10] <poolie> sure
[06:10] <poolie> unfortunately we must have discussed it only on irc
[06:12] <poolie> ah bug 242262
[06:12] <poolie> complete with suggested patch
[06:13] <lifeless> mthaddon: ^
[06:14] <mthaddon> aha
[06:14] <poolie> complete with suggested patch all tidied up by launchpad
[06:14] <poolie> getting rid of all that messy indenting :)
[07:05] <vila> hi all
[07:05]  * fullermd waves at vila.
[07:06] <vila> fullermd: hi !
[07:18] <vila> rats, Rejected:
[07:18] <vila> PPA uploads must be signed by an 'ubuntero'.
[07:18] <fullermd> A rare species of vole found only on Madagascar?
[07:25] <vila> fullermd: should be that yes :)
[07:26] <vila> poolie: I can't dput the same file anymore, which '1' should I change into a '2' in 1.12~rc1-1~bazaar1 ?
[07:26] <vila> rc1-2 ?
[07:26] <poolie> hm i guess so
[07:26] <poolie> if it was rejected i'm surprised it cares
[07:26] <poolie> did you sign the thing?
[07:27] <vila> yes
[07:28] <vila> argh, wait, there is a warning:
[07:28] <vila> gpg: WARNING: This key is not certified with a trusted signature!
[07:28] <vila> gpg:          There is no indication that the signature belongs to the owner.
[07:28] <vila> just fater saying:
[07:28] <vila> gpg: Signature made Wed 11 Feb 2009 07:43:03 AM CET using DSA key ID DEF6218F
[07:28] <vila> gpg: Good signature from "Vincent Ladeuil <v.ladeuil+lp@free.fr>"
[07:28] <vila> gpg:                 aka "Vincent Ladeuil <v.ladeuil@free.fr>"
[07:28] <vila> though...
[07:28] <poolie> wow
[07:28] <poolie> launchpad has translations into 272 human languages
[07:28] <poolie> or at least it thinks it does :)
[07:33] <vila> poolie: ok, I fixed that warning, I'm ready to try to dput again unless you have a better idea to check first
[07:35] <poolie> um
[07:36] <poolie> so i see you are an ubuntero now
[07:36] <poolie> let's go
[07:40] <vila> poolie: yeah, I did that and fix a glitch in my gpg config too
[07:40] <vila> dput done, no warning
[07:41] <poolie> ooh
[07:41] <vila> Package includes an .orig.tar.gz file although the debian revision suggests
[07:41] <vila> that it might not be required. Multiple uploads of the .orig.tar.gz may be
[07:41] <vila> rejected by the upload queue management software.
[07:41] <vila> is harmless I presume ?
[07:41] <poolie> you should be able to see in the web ui if it's building
[07:41] <poolie> yes, that's normal
[07:48] <vila> poolie: mail received, accepted, hurrah ?
[07:49] <poolie> https://edge.launchpad.net/~bzr-beta-ppa/+archive/ppa/+builds?build_text=&build_state=all
[07:53] <vila> Built successfully
[07:53] <vila> Purging chroot-autobuild/build/buildd/bzr-1.12~rc1
[07:53] <vila> is the relevant part ?
[07:53] <poolie> so Hassium, the element after which the machine that built your package is named
[07:54] <poolie> was not called that when i studied chemistry
[07:54] <vila> yet another joke flying high above my head ? :-)
[07:54] <poolie> no
[07:54] <poolie> it changed name in only 1997
[07:54] <poolie> http://en.wikipedia.org/wiki/Hassium | http://en.wikipedia.org/wiki/Element_naming_controversy
[07:55] <poolie> we have a machine for each element i think
[07:56]  * fullermd has sure never heard of 'hassium'...
[07:57] <vila> I always feel bad when scientists lose their energy on such disputes :-/ (Not only scientists for what it's worth...)
[07:58] <vila> How many builds should there be ?
[07:58] <fullermd> If it makes you feel better, I rarely lose my energy for arguing about things nobody else cares about   ;p
[07:58] <vila> fullermd: thanks, that helps :)
[07:58] <poolie> vila, about 3
[07:58]  * fullermd . o O (to most people's everlasting chagrin...)
[08:00] <vila> right, the three built successfully
[08:00] <vila> Is there a better way to check that than visual-grepping the 'Built succesfully' line ?
[08:01] <poolie> In https://edge.launchpad.net/~bzr-beta-ppa/+archive/ppa look at the 'build status'
[08:01]  * igc dinner
[08:01] <vila> Ha, of course, thanks :)
[08:02] <poolie> so that was only jaunty?
[08:02] <poolie> i think now you should send the others
[08:02] <vila> poolie: yup
[08:04] <vila> yet another glitch to fix first (reverting to checkouts my cautious change to branches)
[08:05] <vila> lol
[08:05] <vila> my bzr.dev doesn't include the fix for httlib broken readline so I can't bzr launchpad-login, the irony...
[08:05] <poolie> :/
[08:05] <poolie> it should
[08:05] <poolie> i thought john merged it
[08:06] <vila> Yeah, I should pull :)
[08:06] <vila> far better :)
[08:24] <poolie> ok that's enough
[08:24] <poolie> night all
[08:33] <vila> How long should I wait between a successful build and its occurrence in synaptic ?
[08:33] <mvo> vila: for the main ubuntu archive that can be easily 2h
[08:34] <vila> mvo: ok, thanks, nothing to worry about then ?
[08:35] <vila> err, should bzr-beta-ppa be considered the same as ubuntu archive in that respect ?
[08:36] <mvo> hm, no (I missed that it was about a PPA). but it does take a bit too nowdays
[08:37] <vila> mvo: ok, I'll just wait then
[08:37] <Lo-lan-do> mvo: The Ubuntu mirrors are refreshed every 2 hours?!
[08:40] <mvo> Lo-lan-do: the main archive, I can't speak about the mirrors. might be a bit more than 2h nowdays though
[08:41] <Lo-lan-do> Impressive.
[08:43] <mvo> yes, its pretty nice
[08:47] <vila> mvo: the user experience regarding uploading to ppa is really nice too, congrats
[08:48] <vila> mvo: showing up in synaptic ! That was fast too :)
[08:54] <mvo> nice :)
[08:54] <vila> poolie: ppa uploaded for dapper feisty gutsy hardy intrepid jaunty, build for jaunty and intrepid ok, others pending
[08:56] <lifeless> spiv: entertaining...
[08:56] <lifeless> [54/1114 in 17s] branch_implementations.test_branch.TestFormat.test_set_reference(RemoteBranchFormat-default)
[08:56] <lifeless> Command terminated
[10:28] <theAdib> hello, I did a 'bzr branch https://username/server/pathtorepository' from my svn server. now I did some changes and 'bzr commit' to apply locally but 'bzr push' says: 'bzr: ERROR: No push location known or specified.'
[10:28] <theAdib> so: How do I push my changes to the central svn repository?
[10:28] <Odd_Blok1> theAdib: "bzr push :parent" or "bzr push https://username/server/pathtorepository"
[10:29] <Odd_Blok1> The former is shorthand for the latter in more recent versions of bzr.
[10:30] <theAdib> :parent works smoothly :-) Thx.
[10:34] <shankhs> how to get the source code of bazaar ... bzr branch lp:amarok is giving me error( cannot pass through proxy) I think I should try to create a patch...
[10:34] <Odd_Blok1> shankhs: 'bzr branch lp:bzr' presumably won't help. ;)  Try 'bzr branch http://bazaar-vcs.org/bzr/bzr.dev/'.
[10:35] <shankhs> Odd_Bloke: thanx
[10:35]  * Lo-lan-do likes "apt-get source bzr"
[10:37] <Odd_Bloke> Lo-lan-do: Not necessarily the best way to get a bzr that's worth patching.
[10:37] <Odd_Bloke> If you're running unstable that gives you the source for bzr 1.5.
[10:39] <Odd_Bloke> shankhs: What do you get if you run 'bzr launchpad-login'?
[10:42] <shankhs> Odd_Bloke: No Launchpad user ID configured.
[10:42]  * awilkins thinks an lp: resolver that worked through SSH would be great
[10:43] <awilkins> I can't use the lp: convenience links, I have to work out the full SSH link because our proxy config is such a PITA
[10:45] <awilkins> bzr branch bzr+ssh//bazaar.launchpad.net/~bzr/bzr/trunk bzr.dev  # That should work, might have to add username, and of course, you need a public key registered on your LP account
[10:46] <Lo-lan-do> Missing :
[10:46] <awilkins> Darn
[10:47] <awilkins> Using lp: resolves the detail through some kind of HTTP-RPC which doesn't work through a bad proxy config even if SSH will work
[10:47] <lifeless> awilkins: yeah, bug in the python xml-rpc library, not trivial to work around
[10:47] <shankhs> so what should I do?
[10:48] <awilkins> shankhs: Register a public key on LP and use ssh, or if you can pull over plain http, use that
[10:48] <shankhs> I registered and got some SSH key now???
[10:52] <LarstiQ> shankhs: no, you need to generate an ssh key yourself, and then upload the public part
[10:53] <LarstiQ> shankhs: https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair
[10:54] <shankhs> ya I got it a very long string i registered starting ssh-rsa
[10:54] <shankhs> LarstiQ: How is that going to help me ?
[10:55] <LarstiQ> shankhs: it won't use http, so no http proxy
[10:56] <shankhs> LarstiQ: ok
[10:57] <shankhs> LarstiQ: can you please tell me the commands that I can use with ssh and bzr to download the source codes?
[10:58] <LarstiQ> shankhs: after you have followed that CreatingAnSSHKeyPair page, do `bzr launchpad-login <yourlogin>`, and then the `bzr branch lp:bzr` command
[11:00] <LarstiQ> although, maybe that only works for people in the bzr team, not sure
[11:00] <LarstiQ> shankhs: you tried `bzr branch http://bazaar-vcs.org/bzr/bzr.dev` and that didn't work?
[11:01] <shankhs> LarstiQ: bzr: ERROR: Unknown repository format: 'Bazaar RepositoryFormatKnitPack6 (bzr 1.9)\n'
[11:01] <shankhs> LarstiQ: when i tried bzr branch http://bazaar-vcs.org/bzr/bzr.dev
[11:02] <Odd_Bloke> shankhs: What version of bzr are you using?
[11:02] <Odd_Bloke> The latest is 1.11.
[11:02] <shankhs> Odd_Bloke: how to know that?
[11:02]  * LarstiQ leaves shankhs in Odd_Bloke's capable hands and goes afk
[11:02] <LarstiQ> shankhs: bzr --version
[11:03] <shankhs> Bazaar (bzr) 1.6.1   Python interpreter: /usr/bin/python 2.5.2   Python standard library: /usr/lib/python2.5   bzrlib: /usr/lib/python2.5/site-packages/bzrlib   Bazaar configuration: /home/shankhs/.bazaar   Bazaar log file: /home/shankhs/.bzr.log  Copyright 2005, 2006, 2007, 2008 Canonical Ltd. http://bazaar-vcs.org/  bzr comes with ABSOLUTELY NO WARRANTY.  bzr is free software, and you may use, modify and redistribute it und
[11:03] <Odd_Bloke> shankhs: Right, that's quite an old version.  What distribution/OS are you running?
[11:04] <shankhs> ubuntu 8.10
[11:04] <shankhs> updated an hour ago
[11:05] <shankhs> Odd_Bloke: by the way what is the <yourlogin> in bzr launchpad-login <yourlogin> is it the ssh key?
[11:06] <Odd_Bloke> shankhs: No, it's your Launchpad username.
[11:06] <shankhs> ok
[11:06] <Odd_Bloke> The SSH key is associated with the user account somewhere in the Launchpad UI.
[11:08] <Odd_Bloke> shankhs: I suggest you look at https://launchpad.net/~bzr/+archive/ppa
[11:08] <shankhs> i am getting ERROR: Connection error: while sending GET /%7Eshankhs/%2Bsshkeys: (111, 'Connection refused')
[11:08] <Odd_Bloke> It has more recent versions of bzr available.
[11:13] <shankhs> Odd_Bloke: what about the login problem I tried `bzr launchpad-login shankhs`
[11:19] <Odd_Bloke> shankhs: What login problem?
[11:20] <shankhs> am getting ERROR: Connection error: while sending GET /%7Eshankhs/%2Bsshkeys: (111, 'Connection refused')
[11:20] <shankhs> my login name is shankhs
[11:20] <shankhs> i tried my email id which i used to login
[11:21] <shankhs> every permutation still getting the same error
[11:22] <shankhs> I tried bzr launchpad-login <yourlogin>
[11:24] <awilkins> shankhs: You'll have the same problem because it uses the same XMLRPC mechanism
[11:24] <shankhs> I reinstalled bzr and the version is 1.11
[11:24] <shankhs> awilkins: oh!
[11:24] <awilkins> Do it with
[11:24] <awilkins> --no-check
[11:25] <shankhs> awilkins: thanx I got through
[11:25] <shankhs> awilkins: now how to log out
[11:25] <shankhs> and how to download stuffs
[11:26] <shankhs> is there any good tutorials
[11:27] <awilkins> All launchpad-login does is configure the username it uses for LP branches.
[11:27] <awilkins> Which OS are you using~?
[11:27] <shankhs> ubuntu
[11:28] <awilkins> Ok then, ssh-agent running?
[11:28] <shankhs> awilkins: how to check?
[11:28] <awilkins> Try   ps -e | grep ssh
[11:29] <shankhs> ya  `4771 ?        00:00:00 sshd `
[11:29] <awilkins> Ok, just an ssh server running
[11:29] <awilkins> Not sure if Ubuntu will automatically prompt you for a key password actually. Try.
[11:30] <awilkins> Is your new private key on your ubuntu keyring?
[11:30] <shankhs> I am a complete newbie...
[11:30] <shankhs> how to check them...please explain thankyou
[11:31] <awilkins> Ok, did you generate a keypair for Launchpad?
[11:31] <shankhs> awilkins: ya
[11:32] <awilkins> Ok, go to Accessories > Passwords and Encryption Keys
[11:34] <awilkins> Is there "Secure Shell Key" on your personal keys tab?
[11:34] <shankhs> ya I think i have SSH key and a GPG key
[11:35] <awilkins> Ok, so your key is already installed.
[11:35] <shankhs> awilkins: now?
[11:35] <awilkins> Try  bzr branch bzr+ssh://bazaar.launchpad.net/~bzr/bzr/trunk bzr.dev
[11:37] <shankhs> its running
[11:38] <awilkins> Big branch, may take a while :-)
[11:39] <shankhs> awilkins: ok :)
[11:39] <awilkins> I'm doing it too, just to slow you down some more
[11:39] <awilkins> (mostly to check I'm not talking out of my rear)
[11:40] <shankhs> ssh: connect to host bazaar.launchpad.net port 22: Connection timed out
[11:40] <shankhs> :(
[11:40] <shankhs> whats wrong now ? :(
[11:41] <shankhs> awilkins: bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required)
[11:41] <awilkins> Ah, so you didn't get the twirly baton and stuff
[11:42] <shankhs> awilkins: nope :(
[11:42] <awilkins> Sounds like your firewall policy doesn't allow outgoing connections on port 22
[11:42] <awilkins> You in a corporate office?
[11:42] <shankhs> awilkins: no in a college
[11:42] <awilkins> Only slightly better
[11:43] <shankhs> awilkins: we have squid proxy if this might help
[11:43] <awilkins> You know your proxy settings?
[11:43] <shankhs> ya
[11:43] <awilkins> (bzr.dev hit revision 4000, woohoo)
[11:44] <awilkins> Is your HTTP_PROXY env variabl eset?
[11:44] <shankhs> yes
[11:44] <awilkins> try
[11:45] <shankhs> trying again
[11:45] <Odd_Bloke> I got r4000. \o/
[11:46] <shankhs> awilkins: its not working and I am about to give up on bzr
[11:47] <shankhs> awilkins: hey wait look https://bugs.launchpad.net/bzr/+bug/241698
[11:47] <awilkins> Is that what you're getting?
[11:47] <awilkins> AFAIR that's a squid issue
[11:48] <shankhs> I tried using -Dhpss and I got HPSS calls: 1 <bzrlib.smart.medium.SmartSSHClientMedium object at 0xa29f3ac>
[11:49] <shankhs> svn commands are working fine... though
[11:50] <awilkins> svn has a simpler protocol for http I think
[11:50] <shankhs> I think so
[11:51] <awilkins> It's backed up by a more complex server
[11:51] <shankhs> anyways I got to go hope some simpler remedy comes
[11:51] <awilkins> Bazaar should work if you just serve the branch out of a dump http server
[11:51] <shankhs> awilkins: thanx for your precious time...
[11:52] <shankhs> awilkins: dump http server....!!!
[11:52] <awilkins> dumb
[11:52] <awilkins> sorry
[11:52] <shankhs> ohh
[11:52] <shankhs> ya i also think so
[11:52] <awilkins> noo... it does work
[11:52] <awilkins> svn has it's own WEBDAV server
[11:53] <awilkins> It integrates as an Apache module
[11:53] <shankhs> does that mean bzr wont work behind proxy servers?
[11:53] <shankhs> awilkins: I see
[11:53] <awilkins> It should work behind proxy servers ; but not all proxy servers are equal
[11:53] <shankhs> awilkins: i agree
[11:53] <awilkins> It didn't work out of IIS to start with either
[11:53] <shankhs> awilkins: have you ever tested on squid...?
[11:54] <awilkins> Because both IIS and Python ignore RFCs
[11:54] <awilkins> shankhs: I know there there is at least one protocol bug related to a bug in squid
[11:54] <shankhs> awilkins: I am login using SSH , how to log out?
[11:54] <awilkins> launchpad-login doesn't "log in" it just configures the username
[11:55] <shankhs> awilkins: ok
[11:55] <shankhs> awilkins: does bzr implements its own protocol or some existing one?
[11:56] <shankhs> awilkins: thanx once again for your help
[11:56] <awilkins> Bazaar will use ; direct file reads, FTP, SFTP, HTTP, bzr protocol (raw, over SSH, or HTTP)
[11:57] <awilkins> file/FTP/SFTP/bzr+http are writable
[11:57] <awilkins> plain HTTP is read only
[11:58] <awilkins> The smart protocol tries to reduce bandwidth consumption, the dumb ones all read indexes and read regions of files
[11:59] <awilkins> You can also send merge bundles as files and have them treated as first-class branches as long as you have access to the branch they are based on
[12:00] <awilkins> (well, for pulling/merging purposes)
[12:00] <awilkins> So email also works (this is generally how patches to Bazaar are accepted, by mailing a merge bundle to the mailing list)
[12:00] <awilkins> And i've been talking to myself....
[12:01]  * awilkins slaps head
[12:01] <Odd_Bloke> awilkins: I hadn't noticed. :p
[12:05] <AfC> awilkins: we're all very impressed, honest.
[12:08]  * awilkins hides under his comfort blankie
[12:27] <clemente> Hi; how can you resume an interrupted „branch“ command? I assume you can't easily, since there's bug #125607 open
[12:27] <vila> awilkins: welcome to http://bazaar-vcs.org/Quotes :)
[12:28] <clemente> mmm.... #125067
[12:28]  * vila watches the DOS failure in ubottu....
[12:28] <clemente> bug #125067 ?
[12:31] <Youssef> Hi all!
[12:31] <Odd_Bloke> Youssef: Hello.
[12:32] <Youssef> Odd_Bloke: can you help me please?
[12:32] <Youssef> im new to bazaar
[12:32] <Odd_Bloke> Youssef: I'm about to go for lunch, actually.
[12:33] <Odd_Bloke> awilkins might be around (PING!).
[12:33] <Youssef> hmmm... okay thank you very much!
[12:33] <awilkins> Ptthp
[12:33] <awilkins> Go on then
[12:33] <Youssef> awilkins I need you
[12:33] <Youssef> i have a problem with bazaar
[12:33] <awilkins> It's that or implement an XML/XSLT layer for a shell script
[12:34] <Youssef> awilkins?
[12:34] <awilkins> Ask
[12:34] <Youssef> hhaa okay
[12:35] <Youssef> so, i'm trying to push my project but it says =>This transport does not update the working tree of: bzr://localhost/. See 'bzr help working-trees' for more information.
[12:35] <Youssef> why?
[12:35] <Youssef> i checked it out
[12:35] <awilkins> Because it's pushing to a smart server - it concerns itself with getting the revision data across but it doesn't update the remote tree.
[12:36] <awilkins> If you want that tree updated, do `bzr up` in it
[12:36] <Youssef> in it?
[12:36] <awilkins> You also seem to be pushing to a branch on your own machine
[12:36] <Youssef> yeah thats it
[12:36] <awilkins> With a shell whos present working directory is inside the tree are pushing to
[12:37] <awilkins> It's not necessary to push to a server if you are pushing locally
[12:37] <awilkins> Just push to the actual filesystem folder and you get your tree update thrown in for free
[12:37] <Youssef> hhmmm just a second please
[12:39] <Youssef> i'll try trough my lan
[12:41] <Youssef> so i'm doing a : c:\pjTemp>bzr checkout bzr://192.168.0.35
[12:41] <Youssef> my LAN is a bit slow
[12:42] <awilkins> Right, so 192.168.0.35 is another machine?
[12:47] <Youssef> yes
[12:47] <Youssef> now
[12:48] <Youssef> check
[12:48] <awilkins_sandwic> The not-updating-remote-branch thing is by design
[12:48] <awilkins_sandwic> Are you just using the remote machine as a repository?
[12:49] <awilkins_sandwic> You don't need the working tree if you just want somewhere else to keep your revisions
[12:49] <Youssef> yes im using the server as repository
[12:50] <Youssef> check now
[12:50] <Youssef> http://rafb.net/p/C1I0Wf50.html
[12:51] <Youssef> you see
[12:51] <Youssef> if i understand what you said
[12:51] <Youssef> when I commit it saves automaticlly the modifications.?
[12:55] <Youssef> awilkins_sandwic?
[12:55] <awilkins_sandwic> Ok, the push is redudant because your local checkout is bound to the branch you are pushing to
[12:55] <awilkins_sandwic> sandwich
[12:55] <Youssef> so it's not usefull to do a push then?
[12:55] <awilkins> Not in that case, no
[12:56] <awilkins> A checkout will commit both locally and to the remote barnch it's bound tyo
[12:56] <Youssef> tyo?
[12:56] <awilkins> to
[12:56] <Youssef> really?
[12:56] <Youssef> hmm
[12:57] <awilkins> That's why it says "committing to bzr://192.168.0.35" and not c:\pjTemp\192.168.0.35
[12:57] <Youssef> so when i checkout the commit will commit locally and to the server
[12:57] <awilkins> And "no new revisions to push" (they are already there)
[12:58] <awilkins> Yes
[12:58] <Youssef> and making a push is useless
[13:00] <Youssef> and now when i want to export my projet to a finished projet i use bzr export
[13:00] <Youssef> but where in the server or directly localy?
[13:01] <awilkins> For an export, either is appropriate
[13:02] <Youssef> but without any push?
[13:04] <awilkins> push is only required when you want to put revisions where they are not already. They are already on the server because you are working with a bound checkout and not a standalone branch
[13:06] <Youssef> ooooh okay!
[13:06] <Youssef> thanks many thanks man
[13:07] <awilkins> You're welcome
[13:09] <Youssef> :D
[13:09] <Youssef> :DD
[13:11] <Youssef> ooh yeah I forgot
[13:11] <Youssef> see i reported a bug yesterday
[13:12] <Youssef> awilkins?
[13:14] <Youssef> https://bugs.launchpad.net/bzr/+bug/327558
[13:19] <Youssef> awilkins:
[13:19] <Youssef> now if i do a revert
[13:20] <Youssef> or an uncommit
[13:20] <Youssef> does it work like the commit or it work only locally?
[13:23] <hsn_> https://bugs.launchpad.net/bzr/+bug/305006 - can someone confirm that this bug is still not fixed in rc1? i would test it but i dont want to risk breaking my existing working bzr shelve instalation
[13:25] <mod_cure> is there a way to see the output as i grab a branch ?
[13:38] <hsn_> okay, i did testing on windows and bug 305006 is still not fixed in 1.12rc1 and it is marked as fix commited. is there way to reopen bug?
[13:52] <betus> hello
[13:54] <Odd_Bloke> hsn_: 'Fix committed' means that a patch has been submitted to the mailing list.
[13:54] <betus> i'm a newbie and i have installed bazaar on my host running CentOs, but I can't run the command svn on the ssh client
[13:55] <betus> can someone help me please?
[13:55] <Odd_Bloke> jam: This bug seems to be assigned to you.
[13:56] <Odd_Bloke> betus: What do you mean by "can't run the command svn on the ssh client"?
[13:56] <betus> I have to do this svn co http://svn.askeet.com/trunk
[13:56] <betus> I'm on putty
[13:57] <Odd_Bloke> betus: Are you trying to use bzr as a client for an SVN repository?
[13:57] <betus> yes is it worng?
[13:57] <betus> wrong?
[13:58] <betus> I read that I need a SVN client and on wikypedia I found that
[13:58] <betus> I supose that bzr was for that
[13:59] <Lo-lan-do> Only if you installed the bzr-svn plugin.
[13:59] <betus> sorry for my poor english
[13:59] <Odd_Bloke> betus: No, bzr can be used as a Subversion client.  However, Subversion does have its own client, which might be what you're looking for...
[14:00] <betus> ok, but I didn't found the plugin for CentOs
[14:00] <betus> and I don't know how to install it (this is the bad part)
[14:01] <Odd_Bloke> hsn_: The patch to fix the bug is being tracked at http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C497A0CD9.7030005%40arbash-meinel.com%3E
[14:01] <Tak> have you tried `bzr co svn+http://svn.askeet.com/trunk` ‽
[14:02] <betus> ok Odd_Bloke: what have I do install for subversion?
[14:03] <Odd_Bloke> betus: Probably 'subversion'.
[14:03] <betus> Tak: not i didn't try it
[14:04] <Youssef> Hi guys
[14:05] <betus> Odd_Bloke: and do you know a subversion client that can I run on putty?
[14:06] <Odd_Bloke> betus: Yes, the SVN client is command line based.
[14:06] <Odd_Bloke> poolie: You also seem to have approved that patch. :)
[14:07] <Youssef> okay I explain
[14:07] <Youssef> yesterday i've reported a bug okay
[14:07] <Youssef> https://bugs.launchpad.net/bzr/+bug/327558
[14:08] <Youssef> i noticed that is not only with checkout BUT with every command
[14:08] <betus> Tak: then do you think I don't need to install another svn client?
[14:08] <Youssef> hmm.
[14:08] <Youssef> ..
[14:10] <Odd_Bloke> Youssef: It's more valuable to add such information to the bug report than talk about it here, as it won't be seen when someone comes to help you.
[14:13] <betus> tak: when i do that command it say me that: bzr: ERROR: Unsupported protocol for url "svn+http://svn.askeet.com/trunk"
[14:14] <Odd_Bloke> betus: That means that you don't have bzr-svn installed.
[14:14] <betus> and how can I install it?
[14:15] <vila> Youssef: can you include a bit more of your log file in the bug report or at least mention which versions of bzr you are using for client and server ?
[14:15] <Odd_Bloke> betus: What version of bzr are you running?  (bzr version)
[14:16] <betus> the last I supose, i have installed with the instructions on yhe page yet
[14:16] <betus> i did it: su -c 'rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-2.noarch.rpm'
[14:16] <betus> 5.2 maybe
[14:17] <Youssef> done
[14:17] <awilkins> Youssef: Hah, I was just about to submit that as a bug
[14:17] <betus> and after this: c 'yum install bzr'
[14:17] <Youssef> huh what?
[14:18] <Youssef> hooo hehe
[14:18] <awilkins> The "connection reset by peer" error
[14:18] <awilkins> "Windows client diconnects rudely"
[14:18] <awilkins> It works fine with lunix client > windows server - no errors
[14:18] <Youssef> yeah okay than add a comment like this it will help
[14:18] <Youssef> really?
[14:19] <Youssef> maybe it's a problem of crlf character problem, no?
[14:21] <Youssef> everything works fine but that raise this error anyway
[14:25] <jdong> is it by design or bug that bzr pull shows much less progress info than bzr up?
[14:25] <betus> Odd_Bloke: I didn't find a subversion for CentOs
[14:25] <Lo-lan-do> jdong: They don't do the same thing.
[14:25] <Odd_Bloke> betus: How are you installing it?
[14:26] <Youssef> awilkins: are you writing a comment ?
[14:26] <jdong> well in the usecase of having a bzr-svn checkout, I've tried updating a bound-branch and pulling in an un-bound brand from the same location..
[14:27] <jdong> the bound branch displays things like "Determining Changes X/30000" ==> "Getting revision 1/30"
[14:27] <awilkins> Youssef: Yes
[14:27] <jdong> the unbound branch pull displays "Pull Phase 0/1"
[14:27] <jdong> the latter I find to be much less useful to a user who wants to see a progress bar :)
[14:28] <betus> Odd_Bloke: I'm install it throw SSH client
[14:29] <betus> Odd_Bloke:with putty
[14:31] <Odd_Bloke> betus: What command are you running?
[14:31] <betus> Odd_Bloke:ok i found a command that is installing subversion: yum install mod_dav_svn subversion
[14:32] <Odd_Bloke> betus: Yes, that's what you want.
[14:32] <betus> ok i'm happy thank you
[14:33] <betus> but 1 thing more: when i run this command line svn co http://svn.askeet.com/trunk
[14:33] <betus> what will be happen, where the files will be installed?
[14:34] <Odd_Bloke> betus: That's more of a Subversion question than a Bazaar question, so you should probably find a better channel to ask in.  However, I do know that that will create a directory called 'trunk' containing the files in the repository.
[14:35] <betus> I supose you all with this question will be lughing
[14:35] <jelmer> jdong, that should be a bit better in 1.12
[14:35] <jelmer> jdong, progress bars have been improved
[14:36] <Youssef> did awilkins let me a message?
[14:36] <jdong> jelmer: that's great to hear :)
[14:36] <Youssef> im back now
[14:36] <jdong> jelmer: and I haven't told you yet that recent bzr-svn using subvertpy is simply wonderful
[14:36] <Youssef> but
[14:37] <awilkins> Is subvertpy installer bundled with win32-python-installer?
[14:37] <Youssef> awilkins: like I said it is maybe a problem of CarriageReturn and LineFeed Charachters?
[14:37] <Youssef> I dunno
[14:37] <awilkins> Youssef: Not sure without either looking at the code or sniffing it
[14:37] <Youssef> hhmmm
[14:37]  * awilkins looks at the code
[14:37] <luke-jr> jdong: haven't been using it long? :þ
[14:38] <Youssef> thanks awilkins
[14:38] <awilkins> It's not a problem, it's been like that for aws long as I've been using it
[14:38] <jelmer> awilkins, jam was looking into that
[14:38] <Youssef> aws?
[14:38] <awilkins> as
[14:38] <Youssef> what is it?
[14:38] <Youssef> loooooooool
[14:38] <Youssef> okay
[14:38] <jelmer> awilkins, hopefully the 1.12 compiler will come bundled with subvertpy and bzr-svn 0.5.0
[14:38] <awilkins> Sorry, I was on a different keyboard yesterday
[14:38] <jam> awilkins: ATM, it does not, but I'm trying to get it working now
[14:39] <jam> I either need to get subvertpy bundled, or revert to bzr-svn 0.4.17
[14:39] <awilkins> jam: I've noticed that the setup has changed in that it seems to ignore your LIB and INCLUDE vars if you set them
[14:39] <luke-jr> jelmer: see that bzr log issue I reported?
[14:39] <awilkins> jam: Or that might just be because I installed Python 2.5.4 and broke a customized build environemnt
[14:39] <jam> awilkins: are you using "setup.py" or doing "make" ?
[14:40] <awilkins> jam: make
[14:40] <jam> k
[14:40] <awilkins> make + msvc
[14:41] <awilkins> The distutils stuff does it's own LIB/INCLUDE finagling
[14:41] <jam> so what are you trying that is failing, exactly?
[14:41] <awilkins> Compile extension ; can't find io.h
[14:41] <jam> io.h sure seems like it should be a system lib
[14:41] <awilkins> It's not passing INCLUDE as an include_dir
[14:42] <jam> which you shouldn't need to provide a custom INCLUDE for.
[14:42] <awilkins> jam: You'd think so, but I thikn you have to pass all the include dirs to the msvc compilers
[14:43] <awilkins> Which suited me fine because I was trying to stick to the 2003 vintage (because that's the Python vintage)
[14:43] <jam> well, for 2.4 and 2.5, you have to
[14:44] <awilkins> What was 2.6 built with?
[14:44] <jam> VS 2008, IIRC
[14:44] <jam> the fact that it is v9, and 2008 always confuses me
[14:44] <awilkins> It's not wonderful
[14:45] <awilkins> Why the damn compilers aren't backward compatible is a mystery
[14:45] <awilkins> (well, +more+ backward compatible)
[14:45] <jelmer> luke-jr, which one?
[14:46] <jam> yeah
[14:46] <jam> each has its own runtime
[14:46] <jam> I *think* you can use special flags to change which runtime they would use
[14:46] <jam> but at best it is hard
[14:47] <awilkins> jam: I recall projects that managed it (I think maybe an SVN project of some description)
[14:47] <luke-jr> jelmer: 'bzr log' being totally screwed up with revnos
[14:47] <awilkins> jam: I've royally fiddled with my registry to make distutils work with the MSVC2003 toolkit
[14:48] <bialix> awilikins: recently I'va managed to create valid SConstruct to build pyrex/c extensions
[14:48] <bialix> it may help in the case of MSVC2003 toolkit
[14:48] <bialix> but I did not have a chance to test it with
[14:48] <awilkins> bialix: I had it working at one point
[14:49] <awilkins> bialix: The distutils team made a mistake pandering to all the registry BS IMHO
[14:49] <bialix> with SConstruct I don't need to change the registry
[14:49] <awilkins> What does SConstructy do?
[14:49] <bialix> www.scons.org
[14:49] <bialix> it's a build system
[14:49]  * awilkins has ModelM fingers on a Cherry keybaord today
[14:50]  * bialix bbl
[14:51] <awilkins> Bah, it worked once.
[14:51] <jelmer> luke-jr, I don't think there is an open bugreport about that
[14:51] <jelmer> luke-jr, at least not afair
[14:51] <luke-jr> I do.
[14:52] <awilkins> I shall revert the tree and see if it works with a known revision, if it doesn't, I know it's some difference between Python2.5.2 and 2.5.4
[14:52] <luke-jr> https://bugs.launchpad.net/bzr/+bug/326278
[14:52] <jelmer> luke-jr, ah, I remember now - sorry
[14:52] <jelmer> luke-jr, I had it in mind as a svn-upgrade problem, but it obviously occurs in other situations as well
[14:54] <Youssef> guys
[14:54] <Youssef> what is scons?
[14:54] <Lo-lan-do> You don't want to know.  Really.
[14:54] <Youssef> what?
[14:55]  * Tak agree
[14:55] <Youssef> but yes I do lol
[14:55] <Youssef> what is it?
[14:55] <luke-jr> lol
[14:56] <jam> Youssef: it is a build tool, similar to "make"
[14:56] <shankhs> hi again
[14:57] <Odd_Bloke> shankhs: Hi. :)
[14:57] <shankhs> after 2 hrs of troubleshooting with Odd_Bloke and awilkins and 3 hours of googling did not help me to get bzr working through squid
[14:57] <Odd_Bloke> :(
[14:57] <jam> shankhs: old version of squid?
[14:58] <shankhs> i think so really old version
[14:58] <vila> jam: ping
[14:58] <shankhs> so i decided to review the source code myself but how to download the source code of bzr without bzr
[14:58] <awilkins> Tarball
[14:59] <jam> vila: pong
[14:59] <shankhs> from the bzr home site?
[14:59] <jam> shankhs: so, there is a known bug in squid that was fixed a while back
[14:59] <jam> which bzr triggers
[14:59] <jam> http://launchpad.net/bzr/1.11/1.11
[14:59] <jam> there will be a tarball there
[14:59] <jam> the fix is pretty easy
[14:59] <vila> shankhs: upgrading squid is the best option if what you're observing is bzr downloading whole files when it should download only part of them
[14:59] <jam> just a sec
[15:00] <vila> jam: I'm looking into doing ppas for bzrtools
[15:00] <shankhs> vila: I am not the net admin I am a student...
[15:01] <vila> I find mails between you and poolie dating back to 1.8, they seem to imply doing what is described in ppa.txt should mostly work, is that still true ?
[15:01] <vila> shankhs: You're a *user*, admins are here to server you :-) Ask for an upgrade !
[15:01] <vila> shankhs: You're a *user*, admins are here to serve you :-) Ask for an upgrade !
[15:01]  * vila hates when typos ruin jokes
[15:02] <vila> shankhs: the bug is squid will slow down bzr severely
[15:02] <vila> shankhs: the bug in squid will slow down bzr severely
[15:02] <vila> damn
[15:03] <shankhs> vila: I would do so...anyways do you know how to check the squid version ( from "user" terminal)
[15:04] <vila> shankhs: that's generally the hard part as squid is good as hiding itself (that's why it's called a *transparent* proxy...)
[15:04] <awilkins> Try pointing your browser at the squid server address
[15:05] <awilkins> Some proxies also return revealing pages when you try to browse to a 404
[15:05] <awilkins> Or a non-existent domain
[15:05] <awilkins> (but I'm not sure about squid)
[15:07] <shankhs> this is what I got http://www.mibbit.com/pb/cTLauf (i have the latest version of bzr)
[15:07] <jam> shankhs: http://paste.ubuntu.com/116853/
[15:07] <vila> jam: meh. I can find bzrtools-1.8.0 in bzr-beta-ppa and bzrtools-1.10 in bzr's ppa, where is bzrtools-1.11 ?
[15:08] <jam> vila: it was never built
[15:08] <jam> which is why poolie is trying to get you to do his work
[15:08] <vila> jam: ha great, I like it when I understand things :)
[15:08] <jam> shankhs: hmm... that looks more like lp: not working through a proxy
[15:08] <jam> which is a known issue
[15:09] <jam> what happens if you do "bzr branch http://bazaar.launchpad.net/~bzr/bzr/trunk"
[15:09] <vila> jam: But strangely enough lp:~bzr/bzrtools/packaging-dapper mentions
[15:09] <vila>    11 Martin Pool	2009-01-20
[15:09] <vila>       1.11.0 release
[15:09] <Odd_Bloke> shankhs: Try 'bzr branch http...' -- yeah, what jam said
[15:09] <jam> vila: maybe he built it, but didn't get it uploaded
[15:09] <vila> jam: I will work from that assumption then
[15:10] <jam> vila: 'bzr diff -c 11' might also give clues
[15:10] <shankhs> jam: Odd_Bloke : trying
[15:11] <shankhs> Hey its working...stuffs getting downloaded
[15:12] <shankhs> so I always have to download by getting the url of the trunk!!!!
[15:13] <shankhs> thanx guys
[15:13] <Odd_Bloke> shankhs: \o/
[15:13] <jam> shankhs: unfortunately "lp:" doesn't support proxies yet
[15:13] <shankhs> jam: :(
[15:14] <mod_cure> is there a way to see the output as i grab a branch ?
[15:14] <shankhs> hope someday it will
[15:14] <Odd_Bloke> mod_cure: What 'output'?
[15:15] <mod_cure> trying to grab a branch and it never completes
[15:15] <mod_cure> i was curious it there was a verbose option or something
[15:15] <Odd_Bloke> mod_cure: TIAS. ;)  Failing that, look at ~/.bzr.log.
[15:15] <Odd_Bloke> mod_cure: Also, what version of bzr are you using?
[15:16] <mod_cure> just installed bzr from yum
[15:16] <Odd_Bloke> mod_cure: 'bzr version' will tell you.
[15:16] <shankhs> bzr --version :)
[15:16] <mod_cure> Bazaar (bzr) 1.3.1
[15:17] <shankhs> mod_cure: I think you should update
[15:17] <mod_cure> how ?
[15:18] <shankhs> I dont know how to do this in fedora
[15:20] <mod_cure> thats the lastest version in the repos
[15:20] <Odd_Bloke> mod_cure: I don't know about a Fedora-specific way, but you can get the latest bzr by running 'bzr branch lp:bzr' or 'bzr branch http://bazaar.launchpad.net/~bzr/bzr/trunk'.
[15:20] <Odd_Bloke> And then you can use that.
[15:21] <mod_cure>  bzr branch lp:bzr
[15:21] <mod_cure> bzr: ERROR: Unknown branch format: 'Bazaar Branch Format 7 (needs bzr 1.6)\n'
[15:21] <Odd_Bloke> Oh, goodie.
[15:21] <shankhs> Odd_Bloke: How can I find the url address everytime we need to?
[15:21] <Odd_Bloke> mod_cure: Look at http://bazaar-vcs.org/Download
[15:22] <Odd_Bloke> shankhs: It's (bzr+ssh|http)://bazaar.launchpad.net/~<branch owner>/<project>/<branch name>
[15:23] <Odd_Bloke> You can get all of that information by finding the branch in the Launchpad web UI.
[15:24] <mod_cure> Package bzr - 1.3.1-1.el5.1.i386 is already installed.
[15:24] <mod_cure> 1.3.1 seems up to date
[15:26] <Odd_Bloke> mod_cure: Have you tried the EPEL-testing repo?
[15:26] <mod_cure> yep
[15:26] <Youssef> okay guys nice to meet you all i'll be back tomorow (if God want it)
[15:26] <Odd_Bloke> OK, in that case download a tarball.
[15:26] <Youssef> cya all++
[15:26] <Odd_Bloke> Youssef: Bye!
[15:27] <mod_cure> Odd_Bloke, which one as  i have 1.3.1
[15:27] <jam> jelmer: can you link your subvertpy patch again? I still haven't gotten an email on it
[15:27] <jelmer> jam: I never sent one :-)
[15:27] <Odd_Bloke> mod_cure: Download the latest bzr.
[15:27] <jelmer> jam: http://samba.org/~jelmer/tmp/setup.py-svn.diff
[15:27] <mod_cure> 1.1.1 ?
[15:27] <mod_cure> oic
[15:27] <mod_cure> tired, sorry
[15:30] <mod_cure> should i remove bzr then install the tarbar or just install the tarball ?
[15:31] <Odd_Bloke> mod_cure: I would suggest extracting the tarball somewhere in your home directory and running from there.
[15:31] <Odd_Bloke> Else you might run into problems when trying to install future bzr releases with your package management system.
[15:31] <mod_cure> ok
[16:07] <phinze> so is the general feeling here "there is no task too small for a task branch" ?
[16:08] <Odd_Bloke> phinze: It is for me.
[16:08] <Odd_Bloke> I'll sometimes have single revision task branches.
[16:08] <phinze> i'm still working on my workflow and while the personal task branch makes a lot of sense it's harder to see if it's actually unnecessary overhead for tiny issues
[16:08] <phinze> Odd_Bloke: so how do you keep your branches organized?  i'm just worried about having a billion task branches lying around
[16:10] <Lo-lan-do> I think I'll use more task branches when they are colocated, but so far I tend to avoid branching for trivial stuff (except when needed for separation of private and public stuff).
[16:11] <phinze> Lo-lan-do: "when they are colocated" refers to furture bzr functionality or a specific configuration you don't always use?
[16:11] <Odd_Bloke> phinze: Well, I get rid of them once they are merged.
[16:11] <Odd_Bloke> I know jam has bzr/<target version>/<branch name> to avoid too much clutter.
[16:11] <Lo-lan-do> phinze: Future (hence uncertain ;-) bzr functionality.
[16:12] <jam> phinze: I tend to have a "trivial-fixes" branch
[16:12] <jam> but otherwise everything is a separate feature branch
[16:12] <phinze> Odd_Bloke: so you differ from jam by deleting branches, right?
[16:12] <phinze> i.e. jam you never delete a branch?
[16:12] <jam> phinze: and you can see my "forest" here: http://bzr.arbash-meinel.com/branches/bzr
[16:12] <jam> phinze: correct
[16:13] <jam> all 450+ are there
[16:13] <phinze> jam: nice :)
[16:13] <Odd_Bloke> Actually, I don't tend to delete them.
[16:13] <nDuff> phinze, my workflow here is to create one branch per ticket
[16:13] <Odd_Bloke> But I have no objection to doing so.
[16:13] <jam> phinze: also, ISTR there being an "archive-branch" command written for you guys :)
[16:13] <nDuff> phinze, ...and to delete the branches after the tickets are closed.
[16:13] <jam> so you don't delete them, but move them into an archived location
[16:14] <phinze> jam: right, i'm probably going to be the one writing it ;)
[16:15] <jam> well, I wrote the first part, you just need to finish it for your final workflow
[16:15] <phinze> i figure it's a good idea to work out some workflow kinks for myself before imposing them on the group
[16:15] <phinze> honestly i haven't had the chance to look at what you wrote yet :\
[16:15] <phinze> your email fwd is still sitting in my inbox, heh
[16:16] <Odd_Bloke> Who's "you guys"?
[16:17] <jam> Odd_Bloke: a dev group. I used to work with one of the sys admins, so I convinced him to convince his group to switch to bzr
[16:17] <phinze> Odd_Bloke: my place of employment (small IT shop @ Uni of Iowa) where jam's got a buddy in one of my coworkers
[16:17] <phinze> there you go, two perspectives on the same fact :)
[16:18] <Odd_Bloke> Cool. :)
[16:18] <phinze> jam: so looking at your "forest", for a given version where are you mirroring and pushing and pulling?
[16:19] <jam> "mirroring pushing and pulling"?
[16:19] <jam> Generally, I have a treeless repo on my local machine
[16:19] <phinze> erm, still getting the terminology right
[16:19] <jam> with a couple lightweight working trees pointing at whatever branch
[16:19] <jam> my local repo matches the shape of the remote one
[16:19] <jam> so I can:
[16:19] <jam> bzr branch bzr.dev 1.12/feature-x
[16:19] <jam> cd work
[16:19] <jam> bzr switch ../1.12/feature-x
[16:19] <jam> bzr commit -m fix it
[16:19] <jam> bzr push
[16:20] <jam> And the "bzr push" will push it to $SERVER/1.12/feature-x
[16:20] <Lo-lan-do> Are there any documented workflows for using two machines (laptop+desktop)?
[16:21] <phinze> jam: okay, slowly getting that.  now when you'd merge there, you'd merge back into bzr.dev... which is 'tip'?
[16:22] <jam> phinze: well, I submit things to PQM, and it does the merging for me
[16:22] <jam> but if we didn't have that
[16:22] <jam> yes
[16:22] <phinze> ah yes
[16:22] <jam> bzr.dev would be a heavy-checkout of tip
[16:22] <jam> which is on another machine
[16:22] <phinze> and 'work' is...?
[16:23] <phinze> a lightweight checkout?
[16:24] <jam> phinze: correct
[16:25] <jam> (I technically have a 'work',  'alt_work', bzr.dev, and 'jam-integration' as checkouts, I don't think most people work on that many threads at once)
[16:26] <phinze> and the whole kit and kaboodle was started with bzr init-repo --no-trees
[16:27] <jam> phinze: correct
[16:27]  * phinze is learning!
[16:27] <jam> phinze: something like:http://paste.ubuntu.com/116911/
[16:27] <jam> I won't claim it is the *easiest* to set up
[16:28] <jam> but it works pretty darn well
[16:28] <jam> especially if you want *lots* of feature branches
[16:28] <phinze> i like it
[16:28] <jam> You'll also probably want lines like:
[16:29] <jam> [$PATH/local/bzr]
[16:29] <jam> push_location = $HOST/repo
[16:29] <jam> push_location:policy = appendpath
[16:29] <jam> That is what makes "bzr push"
[16:29] <jam> already know where to push
[16:29] <phinze> ah that's helpful indeed
[16:29] <jam> (in "~/bazaar/locations.conf")
[16:30] <phinze> i've definitely had to wrestle with the client pushing and pulling places i wasn't expecting
[16:30] <phinze> lots of furious ^Cs flying around :)
[16:30] <phinze> and subsequent 'bzr break-lock'ing and crying
[16:43] <vila> verterok: hi !
[16:43]  * verterok waves
[16:43] <vila> verterok: any progress on the OSX installers ?
[16:43] <verterok> hi vila
[16:44] <verterok> vila: no  :(
[16:44] <vila> You don't play with your new toy ??? I can't believe that :-)
[16:46] <verterok> vila: I'll try to get my ibook hooked up to the net today (need to have a lonk call phone with my parents in order to get it done :/ )
[16:46] <verterok> s/lonk/long/
[16:46] <jam> jelmer: what is the official branch for packaging bzr-svn for debian?
[16:47] <jam> bzrtools is here, right? http://bzr.debian.org/pkg-bazaar/bzrtools/unstable/
[16:50] <jelmer> jam: experimental rather than unstable at the moment (since Debian is in freeze)
[16:51] <jam> thanks
[16:51] <jam> I realized that when I saw bzrtools 1.6 there :)
[16:51] <jelmer> jam: I seem to've forgotten to upload again though
[16:51] <jelmer> doing that now
[16:52] <jam> you have 1.12 in experimental
[16:52] <jam> just 1.6 in unstable
[16:53] <jam> Of course, I read the range wrong, you have 1.11 in experimental
[16:53] <jam> (had)
[16:55] <verterok> vila: do you have the sources of the 10.5 installer? I could start with that one :)
[16:55] <vila> verterok: no :-(
[16:56] <jelmer> jam: pushed
[16:56] <verterok> vila: ok, I'll send a mail to phanatic about that, thx!
[16:56] <Lo-lan-do> You guys are aware of http://bzr.debian.org/loggerhead/pkg-bazaar/ right?
[16:57] <vila> verterok: ok, keep me informed
[16:57] <verterok> vila: sure thing
[17:36] <santagada> I asked yesterday, is there a way to trac a piece of code in a bzr branch? like a function that gets refactored to another file for exampl
[17:37] <santagada> this is the only feature of git that seems really interesting
[17:39] <Lo-lan-do> That, and revision squashing.
[17:40] <santagada> Lo-lan-do: what is that?
[17:40] <santagada> the way that git tracs changes using the whole project and not file by file is pretty interesting
[17:41] <Lo-lan-do> Merging successive revisions so that when you send your branch for inclusion it only has like 10 commits rather than 200.
[17:41] <santagada> Lo-lan-do: this seems cool also
[17:42] <Lo-lan-do> Maybe it'll happen in bzr-rebase sometime? :-)
[17:42] <santagada> but it is a cosmetic thing (a pretty interesting one), but looking at revision data as a whole project is very interesting
[17:43] <santagada> I don't know, maybe bzr is just like git....
[18:43] <elmo> why doesn't bzr assume push location is where I pulled from?
[18:52] <mwhudson> elmo: because reasonably often that's not what you want
[18:53] <mwhudson> you can say bzr push :pull
[18:53] <mwhudson> to push to where you pulled from without having to remember it
[18:53] <mwhudson> beuno, rockstar: loggerhead review ping!
[18:54] <elmo> mwhudson: it's what I want every time I've tried to use push, FWIW  and AFAICR :-P
[18:54] <elmo> maybe I'm just special
[18:54] <beuno> mwhudson, it's on my ToDo list, but now that you're up, I'll review now
[18:54] <rockstar> mwhudson, I don't really have the cycles to review it right now.
[18:55] <mwhudson> elmo: there was a long argumen^Wdiscussion on the mailing list on this
[18:55] <beuno> elmo, FWIW, I feel the same
[18:55] <mwhudson> rockstar: np
[18:55] <mwhudson> beuno: cool :)
[18:55] <elmo> mwhudson: the push :pull short hand is neat though, thanks
[18:55] <vila> elmo: and it will be remembered so you need it only once
[19:03] <beuno> mwhudson, done. Very small comment.
[19:04] <mwhudson> beuno: i think your comment is about a bzrlib api?
[19:04] <beuno> mwhudson, ah!  well, I guess you can ignore me then  :)
[19:05] <mwhudson> beuno: thanks :)
[19:50] <guest123> Hi all, I have just recently started using Bazaar (and in general VCSs). Would anyone kindly point me to the best place where I can ask some newbie questions?
[19:51] <NfNitLoop> guest123: ask away.
[19:52] <NfNitLoop> guest123: on IRC, it's generally best to avoid asking permission to ask a question.   You might wait a while for a response.
[19:52] <NfNitLoop> guest123: so just put it out there. :)
[19:56] <guest123> :) thanks. We have a small group of 4 developers inhouse, so all the projects are in the shared folder over network. I'm thinking of having some local bug tracking tool and was wandering if it be possible to integrate that with bzr
[20:08] <lifeless> elmo: you really need to start giving other projects patches then :)
[20:11] <lifeless> guest123: it certainly is possible to do that
[20:11] <lifeless> guest123:
[20:11] <lifeless> if you ru 'bzr help bugs' you will get the online docs about our bug tracking integration support
[20:13] <elmo> lifeless: pfft
[20:14] <guest123> I found how to integrate web-based bug support (bugzilla etc) but puttin url in the config file, but can it be used to call some other local application?
[20:22] <lifeless> elmo: (thats where our default makes sense - we're optimised for non-core contributors by default)
[20:22] <lifeless> elmo: and in fact, for core contributors working on non-trunk features too
[20:26] <kfogel> hunh
[20:26] <kfogel> I guess we're at revision 4000 now on trunk.
[20:26] <kfogel> At first I thought it was an error when my checkout stopped at that, because it was such a round number :-).
[20:44] <lifeless> abentley: have you seen 'bzr send' bring up a mail address prefixed with /// ?
[20:45] <abentley> lifeless: Yes.  There's an open bug about it.  xdg-email is broken in Intrepid.
[20:45] <lifeless> ah
[20:45] <lifeless> thanks
[20:45] <lifeless> bug 291847 ?
[20:46] <lifeless> abentley: would it be reasonable to not use xdg-email with intrepids version?
[20:47] <abentley> lifeless: You mean use the editor client on intrepid?
[20:48] <lifeless> I guess
[20:48] <lifeless> or do `which evolution`, `which thunderbird` ..
[20:48] <lifeless> I'll look at the xdg-open bug this weekend I hope
[20:49] <abentley> lifeless: If the user configures their client, everything's fine.  It's only the default that's broken.
[20:49] <lifeless> so the setting you refer to is an xdg-open setting?
[20:50] <abentley> lifeless: No, it's a bzr setting.
[20:50] <abentley> lifeless: the mail_client setting.
[20:50] <lifeless> ok
[20:50] <lifeless> so I'd like the default to work
[20:51] <lifeless> I just got bitten myself, a merge request I'd 'sent' was queued by evo because it doesn't understand /// is bogus, and thus the smtp daemon was rejecting
[20:51] <abentley> lifeless: Me too, but I was hoping someone on the distro would fix intrepid.
[20:51] <lifeless> indeed
[20:51] <lifeless> however, its new-unconfirmed which means noone has seen it
[20:51] <lifeless> I'll see what I can do about that
[20:52] <jelmer> I've seen it as well on Debian fwiw
[20:52] <lifeless> I was however, asking about other options, if its hard/tricky/whatever
[20:52] <lifeless> jelmer: probably upstream bug
[20:52] <lifeless> most things are :P
[20:54]  * jelmer tries to think of ways to describe a working tree without using the word WorkingTree to not break test_source.TestApiUsage.test_branch_WorkingTree
[20:59] <Lo-lan-do> jelmer: Sandbox?
[20:59] <lifeless> jelmer: why?
[20:59] <jelmer> I've added a "workingtree_updated" boolean to PullResult
[21:00] <jelmer> I guess I should probably move PullResult instead
[21:00] <lifeless> jelmer: or have a WorkingTreePullResult
[21:00] <abentley> lifeless: I don't think the difficulty is too high.  We already have code which tries one and falls back to another, so we can crib from that.
[21:00] <lifeless> which decorates BranchPullResult
[21:01] <jelmer> lifeless, hmm, yeah, that might be an idea as well
[21:06] <mwhudson> beuno: mmm, do you know if any of those "replace mootools with yui" for loggerhead we did at the epic were complete enough to use?
[21:07] <beuno> mwhudson, no. BUT, I'm planning on using lazr-js, so I should be able to actually do that in a day or two of work
[21:08] <beuno> I've been working on the stuff I need for this in lazr-js directly
[21:08] <beuno> so we all win  :)
[21:08] <mwhudson> ah, ok
[21:08] <mwhudson> when? :)
[21:08]  * beuno pretends that message never got across
[21:10] <lifeless> I have a layering problem
[21:10] <lifeless> Hopefully lazyirc will help me :)
[21:11] <lifeless> I want to change the TestResult instance used by 'bzr selftest', controlled via an option to 'bzr selftest' introduced by a plugin
[21:11] <lifeless> I'd rather not use global state
[21:11] <Lo-lan-do> beuno: Any chance of releasing a serve-branches-based loggerhead soonish?
[21:11] <beuno> Lo-lan-do, what do you mean exactly by that?
[21:12] <beuno> with configs n' stuff?
[21:12] <lifeless> I'd also rather not expose this as 'use this result class' at the UI, mainly because I don't want things like 'default' to be visible - I just want a single simple option
[21:12] <Lo-lan-do> beuno: Configs would be neat, but at least a working init script without local patching :-)
[21:14] <Lo-lan-do> I'd like to go forward with my FusionForge bzr plugin, which would require a branch browser.
[21:15] <beuno> Lo-lan-do, ah, that should easy I think. There are like 4 different patches that do that, including one that jelmer includes in the package
[21:15] <beuno> I don't really know which one to include though
[21:15] <beuno> jelmer, any ideas on that?
[21:15] <jelmer> beuno, if serve-branches is the way to go then Lo-lan-do's init script would be the way to go
[21:16] <Lo-lan-do> Also, the URL generation bug is rather nasty, if you allow me to bitch about that :-)
[21:16] <jelmer> beuno, that complies with common practices for init scripts
[21:17] <beuno> Lo-lan-do, file a merge proposal, I'll merge  :)
[21:17] <mwhudson> lifeless: i too have wanted to control which TestResult objects get used in tests
[21:18] <lifeless> jml: does your TeeTestResult or whatever it is called pass on all method calls and attribute access? or only the 'protocol'
[21:18] <lifeless> mwhudson: I think what I'm going to do is fix the lower layers, so I can have my plugin 'just do it'
[21:18] <lifeless> mwhudson: and then at the top probably just punt and set a global
[21:19] <Lo-lan-do> beuno: The branch is at http://bzr.debian.org/~lolando/bzr/loggerhead/daemonise/
[21:19] <Lo-lan-do> browsable at http://bzr.debian.org/loggerhead/users/lolando/loggerhead/daemonise/changes
[21:20] <beuno> Lo-lan-do, I'll try on get that merged in soon
[21:20] <Lo-lan-do> Yay :-)
[21:21] <Lo-lan-do> There's also the system-yui branch, but it's probably not interesting to you until yui 3 enters Debian.
[21:21] <beuno> Lo-lan-do, if I don't, please hunt me down and force me to  :)    I'm a bit over-committed this month
[21:21] <Lo-lan-do> Sure
[21:23] <lifeless> beuno: s/(.*)this month/\1/
[21:23] <beuno> lifeless, I'm taking it one month at a time  :)
[21:25] <lifeless> beuno: if only :)
[21:28] <jml> lifeless: ummmm... I can't remember.
[21:28] <jml> lifeless: probably only the protocol.
[21:31]  * kfogel is away: back on later
[21:33] <lifeless> jml: how would you feel about a more generic T adapter
[21:33] <lifeless> oo pycon downunder
[21:34] <jml> lifeless: as in a __getattr__ hack?
[21:36] <lifeless> jml: details, details :P
[21:36] <lifeless> jml: as in, I want to glue the new shiny subunit stuff
[21:36] <lifeless> and bzr's visual progress together
[21:37] <lifeless> subunit doesn't have bzr's additional protocol
[21:37] <lifeless> right now I'm finishing a patch to replace the runner altogether
[21:37] <lifeless> I'll see if that satisfies my itch; it may
[21:40] <mwhudson> beuno: is it possible to mix mootools and yui on the same page?
[21:40] <beuno> mwhudson, yeap, no problems with doing that
[21:41] <mwhudson> i still have this crazy plan for swapping between unified and side-by-side diffs using js
[21:41] <jml> go crazy
[21:41]  * jml bops to Prince
[21:41] <beuno> mwhudson, do that with ajax, and it's a triple win
[21:42] <beuno> fetch diffs with ajax, and make them interchangeable
[21:42] <mwhudson> oh right yes, that too i guess
[21:42] <beuno> the servers will *love* you
[21:42] <mwhudson> seems somewhat orthogonal
[21:42] <mwhudson> revision pages seem to be the main performance terrorizer right now
[21:43] <beuno> it is, it's just me trying to you sneak one of my ToDo's  ;)
[21:44] <mwhudson> :)
[21:44] <lifeless> what I really want is "the user made this selection, maybe a lower layer wants it, hand-off"
[21:57] <lifeless> mwhudson: jml: http://paste.ubuntu.com/117030/
[21:57] <lifeless> thats a sketch
[21:57] <lifeless> does it make baby jesus uncomfortable? I don't know
[21:58] <vila> lifeless: this has undeniably a perl taste :-)
[22:00] <poolie> hello
[22:00] <thumper> hi
[22:01] <jelmer> hi vila, poolie, thumper
[22:01] <igc> morning
[22:01] <vila> hey
[22:01] <beuno> hiya igc
[22:01] <mwhudson> lifeless: it's mildly odd, but not too horrific i guess
[22:01] <igc> hi beuno
[22:01] <mwhudson> morning all
[22:01] <igc> morning mwhudson
[22:02] <thumper> lifeless: pycon downunder different to nzpycon?
[22:02] <thumper> lifeless: is that the one in singapore next year?
[22:02] <lifeless> thumper: nzpycon
[22:03]  * thumper nods
[22:03] <thumper> lifeless: #nzpug
[22:03] <bob2> trying to exploit our good name
[22:03]  * mwhudson must try to not entirely miss the next planning meeting for that
[22:03] <thumper> lifeless: even if you aren't in nz right now
[22:03] <lifeless> bob2: 2/3rds of the region can't be wrong
[22:03] <thumper> poolie: are we standing up?
[22:03] <lifeless> bob2: North island
[22:03] <lifeless> bob2: South Island
[22:04] <lifeless> bob2: West Island
[22:04] <bob2> lol
[22:05] <poolie> vila: are you around? want to join our standup?
[22:05] <vila> poolie: yup
[22:43] <jml> Can I get a bzr dev to look at bug 328146 please?
[22:49] <thumper> jml: that is pushing a rich root branch stacked on a non-rich root branch :-|
[22:49] <jml> thumper: yeah, I got that far :)
[22:56] <spiv> jml: comment added, and opened it against bzr too
[22:57] <jml> spiv: I noticed! Launchpad trashed the comment I had just written :)
[22:57] <jml> spiv: I've marked it as invalid on launchpad-bazaar, because there really is no bug in what we're doing.
[23:08] <igc> poolie: calling back?
[23:09] <jam> poolie, igc: I'd like to finish, but I also need to go pick up my son
[23:09] <jam> Is there a lot left to discuss?
[23:09] <igc> jam: I'd like some rough idea of how much "core" engineering you think is left
[23:10] <igc> weeks still?
[23:10] <jam> igc: There is the "is it good enough for limited rollout" versus "it is what we really want to ask people to upgrade to"
[23:10] <jam> I know lifeless has mentioned wanting a really solid next repo format
[23:10] <jam> rather than continuing the "release early, release often" and have incremental improvements
[23:11] <jam> If we just want to get it to the point that we could merge it as a --dev format that exists in bzr.dev
[23:11] <jam> I would think we could do that in a week or so
[23:13] <phinze> okay so i have a completed task branch at tasks/1.2.3/cool_task
[23:13] <phinze> which is lightweight checked out at work/
[23:14] <phinze> when i'm running merge inside trunk/ is there any different between bzr merge ../work and bzr merge ../tasks/1.2.3/cool_task ...?
[23:14] <jam> phinze: no
[23:14] <poolie> igc, jam, lifeless, vila, spiv, i can't connect to skye
[23:14] <phinze> jam: happy days
[23:14] <phinze> thx
[23:14] <jam> poolie: do you want robert to call your house?
[23:21] <thumper> spiv: I have to head out to the dentist
[23:21] <thumper> spiv: shall we defer until tomorrow?
[23:21] <spiv> thumper: ok
[23:21] <poolie> it seems to be dentist week
[23:44] <lifeless> spiv: lets talk pairing in 15 minutes or so, I'm knackered
[23:45]  * igc breakfast
[23:47] <spiv> lifeless: agreed
[23:47] <mxpxpod> I shelved some changes and now I'm getting this error unshelving them: bzr: ERROR: No such file: None
[23:47] <lifeless> mxpxpod: thats a bug, fixed in bzr.dev
[23:48] <mxpxpod> lifeless: 1.12rc1?
[23:49] <lifeless> mxpxpod: that has the fix too, I believe
[23:50] <lifeless> https://bugs.edge.launchpad.net/bzr/+bug/319790
[23:53] <mxpxpod> lifeless: thanks... I just applied the patch from that bug
[23:53] <mxpxpod> works like a charm