=== wgrant_ is now known as wgrant [12:23] hello [12:24] is "public location for branch XXX" a synonym for "public branch for branch XXX"? [12:26] gioele: context? [12:27] LarstiQ: lp-open [12:27] gioele: yeah [12:39] can we say that in general "{push,pull,public,parent,bound} location" and "xxx branch" have the same meaning? [12:47] gioele: branches are usually addressed by their location/url. The two aren't exactly the same things (in bzrlib one is a str, the other a Branch) [12:47] gioele: but that's semantic nitpicking [12:48] gioele: for the bzr cli, yeah, that should be the case [12:49] gioele: location of the {push,pull,public,parent,bound} branch [13:36] what is the purpose of the 'submit location'. What is the submit branch used for? [13:48] I jot down my findings at http://bazaar-vcs.org/Locations Thoughts? === `6og is now known as Kamping_Kaiser === mark1 is now known as markh === chandlerc_ is now known as chandlerc === mwhudson_ is now known as mwhudson === Pilky_ is now known as Pilky [20:30] BasicOSX: replied to your mail [20:40] ok [20:44] * LarstiQ goes to bed [20:45] haven't gotten your email :-) === pygi is now known as pygi_kid [20:46] BasicOSX: basically, the failure is harmless, don't let it block 1.13 [20:47] ok [20:47] BasicOSX: ok, good luck :) [21:16] BasicOSX: no I didn't do the cherrypicks, I was offline - sorry [21:17] I got it, good lesson to learn, wasn't sure how PQM worked, but figured it out, just putting the finishing touches announcements [21:18] BasicOSX: cool [21:19] IRC op please update the /topic to 1.13 release 15 Mar [21:19] Thank you === lifeless changed the topic of #bzr to: Bazaar version control system | 1.13 released 15 Mar | http://bazaar-vcs.org | http://irclogs.ubuntu.com/ | http://planet.bazaar-vcs.org/ [21:28] Is it possible to selectively revert revisions? [21:29] ex. revert changes that occurred revision #3 [21:30] oh bloody hell, my nose is bleeding again. brb. [21:41] BasicOSX: thanks for the release! [21:41] I aim to please [21:41] I also jabber to please [22:07] yay bzr 1.13 [22:22] spiv: shall the two musketeers ride today? [22:23] lifeless: sure. Alright if I head down to Epping? [22:23] sounds great [22:29] yay! [23:01] I'm sure I'm missing something... How do I install bzr (from source) to /usr/local/bin instead of /usr/bin ? [23:01] pretty much anywhere you want it installed [23:01] Just need to make sure bzr is in your path [23:02] I put it into /usr/local/share/ and symlink /usr/local/bin to /usr/local/share/ [23:02] meaning I symlink /usr/local/bin/bzr to /usr/local/share/bzr.dev/bzr [23:02] How do I tell it where to go though? By default it goes into /usr/bin [23:03] From tarball? [23:04] From the bzr repo. [23:04] how are you getting it from the repo? [23:05] don't understand if you don't have bzr installed how are you getting bzr from a repo? [23:05] I pulled http://bazaar-vcs.org/bzr/bzr.dev/ and update it once in a while with bzr pull. [23:06] Just mv the bzr.dev to where you want it to live [23:08] cammoblammo: are you running setup.py ? [23:09] Yes. [23:10] cammoblammo: setup.py install --home=/usr/local [23:11] cammoblammo: BasicOSX is talking about an alternative where you don't really install it; just run 'make' and then symlink $(src)/bzr into your path somewhere [23:11] yes, I am, sorry [23:11] I use --prefix, not --home. :O [23:11] Ah. I thought it'd be something like that. There isn't somewhere I can set it permanently? [23:12] Peng_: either is fine, I think. [23:12] cammoblammo: not as far as I know [23:13] Oh well, I can live with it. Thanks for your help folks! [23:14] Hmm. Is there a setup.py uninstall command? [23:18] No ><. setup.py is a poor replacement for packaging [there are packages of bzr for most platforms..] [23:21] Yeah, Debian took too long to give me something recent. I can use the --record option on install and use that to delete what doesn't need to be there. [23:27] I'm reading my notes from last week [23:27] and I've got one that says "Gotchas w/ progress reporting in bzr 1.13" [23:27] does anyone have a clue what I meant? :) [23:30] yes, I do [23:31] bzr 1.13 does much less ('no') progress reporting during large fetches, instead the network activity reporting is the whole thing [23:34] lifeless: but it still does fairly granular activity reporting, right? [23:35] jml: I don't know what you mean [23:35] so perhaps I can phrase it differently [23:36] a local-disk new clone operation will output perhaps 1 seconds worth of progress bar stuff right at the start, then nothing until the tree building at the end [23:37] a over the network new clone will output perhaps 1 seconds worth of progress bar stuff at the start, and then the network activity when data is being read/written to the network, then the tree building progress bar at the end [23:37] fin [23:39] does anyone know who yoboy is? [23:40] BasicOSX and everyone else: Congrats on the release. :) [23:54] igc: you can move bugs by clicking on the status, and then typing in a new product in the box [23:56] lifeless: sure [23:57] igc: :P - perhaps I was wrong to move that bug to qbzr that you'd closed? [23:57] lifeless: And you're reminding me because? [23:57] igc: because I thought you closed something that was better moved [23:58] lifeless: I closed it because the person raising it wasn't sure how to close it [23:58] erm syntax, because you closed something I thought was better moved [23:58] ah [23:58] my bad [23:58] lifeless: ah - ok [23:59] * lifeless is a little twitchy on bugs today, after an unknown marked four unrelated surface-related-unicode bugs as dups