[00:00] done [00:00] lifeless: Thanks. [00:01] I like packaging branches :) [00:01] just need to get some tuits and fix the namespace issues [00:04] fullermd: \o/ freebsd just got libtool 2 :) [00:29] if i have a few classes in an index that i have to indent 2 spaces, in 1.x this would be a rather large change, but with 2.x that would be very trivial, correct? [00:31] meoblast001: just do the change [00:32] ok, i tend to freak out about things [00:32] you know, going concern [00:35] I'd be more worried about what it would do to annotate [00:35] annotate? [00:35] the output from annotate [00:35] you know, as in "bzr annotate"? [00:35] haven't used that feature yet [00:35] SamB_XP_: there will be an ignore whitespace flag at some point [00:36] one of the developers on my project rewrote a lot of it about a month ago, i tried to go through it and fix the formatting, but every now and then i pick up on things i missed [00:36] I would just do it [00:36] maybe you should get some automated nitpickers [00:37] bzr exists to support you:) [00:37] automated nitpickers? [00:37] but yeah, just do it, as long as you aren't actually substantial changes in that commit [00:37] where by substantial changes, I mean changes to the substance of the code [00:38] yeah [00:38] thanks for the info [00:38] what's wrong with rc1? [00:38] i know in this very project i used to have ZIPs in it [00:38] and by automated nitpickers, I mean tools that check your code style somewhat [00:38] once i figured out those aren't good with version control, i extracted them all and removed the ZIP files [00:39] well, it might be fairly reasonable if you didn't make the zp and don't expect anything in the zip to change ever ;-) [00:39] s/zp/zip/ [00:39] well, the thing was that i was unsure [00:40] it didn't change much, but i wasn't sure if it would in the future [00:40] and if i still had it, yes, it would have changed [00:40] our file format specification changed, and the contents of the files in the ZIP would have needed to be changed [00:40] yeah [00:41] what irks me is that the ZIP file is actually in there forever, even if it's not in the tree [00:41] idnar: brown paper bag bug [00:41] idnar: incorrect conversion of data; do not use. [00:41] idnar: it will usually completely fail to convert data, but if it doesn't fail its probably done the wrong thing [00:42] and just in case this question sounds crazy, i asked the MyBB developers what happens when i hit 4294967296 posts [00:42] lifeless: what does "brown paper bag bug" mean? [00:42] meoblast001: what's MyBB? [00:42] SamB_XP_: very bad, shouldn't have released, 'oops', 'bah', etc [00:42] SamB_XP_: a forum software [00:43] lifeless: well, I was wondering why those words mean that also ;-) [00:43] what does that have to do with brown paper bags? [00:43] lifeless: ah, nasty [00:43] SamB_XP_: http://www.catb.org/jargon/html/B/brown-paper-bag-bug.html [00:44] idnar: yup; we pulled tarballs etc the day after releasing it or so [00:45] lifeless: oh! [00:45] lifeless: you don't look like you're wearing a brown paper bag! [00:49] SamB_XP_: it was a few weeks back :P [00:50] lifeless: ah [00:50] well, I don't remember seeing you with one back then, either [00:56] jelmer: around? [01:40] lifeless: A while back, actually... it was a week or two after we talked about it. [01:41] fullermd: my bug just got closed [01:41] Ah. I thought about checking on that after I saw the commit go through, but laziness won. [02:17] I changed TortoiseBZR's shell extension code. [02:20] Could anyone kick buildbot for windows installer? [03:27] lifeless: you still here? [05:03] how do you set breakpoints in plugin code? [05:03] pdb tells me the file is not on sys.path when i try [05:07] breakpoint bzr itself I guess and add the breakpoint after the plugin is loaded? [05:37] thanks, lifeless. it seems to work if i use the full path to the plugin source file as the argument to `b` === r0bby|arr is now known as r0bby [07:37] So... um, I just googled "bzr ppa" and came up with https://launchpad.net/~bzr/+archive/ppa ... at which there is no bzr 2.0rc2. [07:37] What conceptual tidbit am I missing? [07:39] (or should I just be using the 1.18 in karmic?) [07:46] its in the beta ppa [07:47] http://bazaar-vcs.org/Download [07:47] lifeless: er, ok. I see. [07:47] Hm. I guess I thought that's what the "normal" ppa was for. [07:48] so what's the difference between {what is in karmic now, what is in ppa, and what is in beta-ppa}? [07:48] [and, when should I stop using beta-ppa for ppa for karmic]? [07:49] normal ppa has releases [07:49] beta ppa has betas [07:50] whats in karmic is what the debian/ubuntu packaging team select and put in there [07:50] lifeless: ah [07:50] right [07:50] what should you use is : if you want stable releases, use your distro and optionally our ppa [07:50] if you want newer-than your distro, use the ppa [07:50] lifeless: so bzr ppa will have 2.0 in it for the next year or so, and bzr beta-ppa will have 2.odd.x in it? [07:51] if you want to help us by beta testing, or want a beta for timely access to some feature, use the beta ppa [07:51] lifeless: ok, so given that I'm not a usual PEBKAC here, what should I be using? [07:51] Its not clear what will happen with 2.1b* and the ppas; Some of our users may want them to propogate to the normal ppa:- expect list traffic on it ~ 2.1b1's release :) [07:52] yeah [07:52] anyway, I was using 2.0rc1, so I presume I should act to get that [back] on board [07:52] I think you'd be fine with the beta ppa; it has a few days of roughness once a month or so [07:52] you definitely want to get rc2, given rc1's brown paper bag status [07:52] but I'm wondering if I should revert to normal ppa Real Soon Now™ :) [07:53] lifeless: yeah, but it's what the distro I had had shipped until they found out about that. [07:53] anyway [07:53] so as I say, I think the beta ppa would be generally fine for you [07:53] ok [07:53] its not that rough a ride :) [07:53] lifeless: I assume that once it's out [07:54] lifeless: I can be running 2.0 or > 2.0 on the server an not screw over 2.0 stable users? [07:54] [that seems to be a format question, not a software version one, now that I think of it] [07:55] lifeless: [ie, I have to balance me wanting to be close as possible to the code you're working on to actually see fixes & features [07:55] against [07:55] lifeless: hosting public branches of certain projects] [07:55] our servers are pretty robust [07:55] you can upgrade the server, or stick to 2.0 indefinitely [07:56] in terms of formats, yes, when you upgrade, you force other users to meet that minimum version [07:58] sure [07:59] I'm going to do that shortly. There aren't _that_ many of them; once Gentoo ~ and Ubuntu K support 2a [or whatever] I'll upgrade the repos. [08:01] * AfC wishes keyserver.ubuntu.com would answer [08:04] oh, that's not actually required. [08:06] lifeless: Robert, does one still have to do that "run Python program once as root" thing to get the .pyc files built? [08:06] lifeless: [c.f. Hobart, me on loaner laptop, you doing bzr timing tests to find out that was my bug] [08:24] AfC: you should not have had to do that then; something had gone wrong. [08:24] AfC: if bzr is slow, and strace shows errors openning the pyc files for write, then you have the symptoms again [08:25] lifeless: no, it's not slow now [08:25] lifeless: [not that I've done much] [08:25] lifeless: I was just wondering if it was a standard known thing everyone had to do [08:25] thanks [08:51] Is there a terse form for reverse-merging / backing out a single revision, or do I want merge -r N..N-1 ? [08:51] you want that [08:51] unless you want uncommit [08:52] Maybe bzr should borrow -c -revno from svn :-) [08:53] we have it [08:53] it means N-1..N === doko__ is now known as doko [09:17] Note the minus sign before revno [09:17] Nono, see. MINUS c means N-1..N, so for N..N-1 you obviously want PLUS c 8-} [09:20] maxb: bzr merge -c 5 will merge 4..5 [09:21] maxb: bzr merge -c -5 will merge -6..-5 [09:21] oh. [09:21] gah, right [11:04] hmm, got an error just now trying to clean up my bzrrepo [11:05] here's the output http://www.pastebin.org/18987 [11:06] and now every command i use throws something like it. [11:07] http://www.pastebin.org/18988 [11:09] NETabuse: hmm, that's bad. [11:09] arrg,, that's not what i was hoping to hear... [11:10] NETabuse: I think you have an ignore pattern that is causing that error [11:10] spiv, phew,, that did it. [11:10] NETabuse: please file a bug on bzr [11:11] i'd been messing iwth ignore patterns trying to ignore all images in the image upload data dir [11:11] NETabuse: I just skimmed the NEWS file, and it doesn't appear to have been fixed since the version you are using. [11:11] we should be prettier in that case [11:12] so i'd done bzr ignore path/to/uploads/*.[jpg|gif|png] and it just put in a line in .bzrignore path/to/uploads/*.[jpg and that was it. [11:18] there https://bugs.launchpad.net/bzr/+bug/433437 [11:18] Launchpad bug 433437 in bzr "bzr ignore paths including [ character throws "sre_constants.error: bad character range"" [Undecided,New] [11:18] i'll update it with more details soon. [11:18] thanks for spotting that it was ignore patterns. [11:24] hmm, how do i push my code up from my laptop to my server, server has bzr on it. [11:24] bzr push bzr+shh://server/abs/path/here [11:25] bzr: ERROR: unknown command 'serve' [11:25] the server must have a _very very very_ old version of bzr [11:26] what does 'ssh server bzr --version' [11:26] report? [11:26] yeh, bzr 0.8.2 [11:26] that is so old it doesn't support being a server [11:26] you could use sftp, or preferrably upgrade the bzr on the server [11:27] well, it's dapper. [11:27] so how do i update it to newer bzr? [11:27] we have dapper builds in the bzr ppa [11:28] see http://bazaar-vcs.org/Download [11:32] that's awsome, thanks, got the new bzr in and no serve command error [11:33] right, i'm off for some family time. [11:33] thanks for the help today. [11:35] np, ciao [11:50] Wow, 0.8.2 in the wild? [11:50] Scary... [12:09] hello, i'm working with an online repository, i've received the contents with bzr checkout sftp://... [12:10] how do i 'checkin'? [12:10] bzr commit [12:10] http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html [12:11] bob2: the problem is, i haven't set up an ssh key, so i'd expect a password prompt every time i update or commit [12:11] which happens on another pc i'm using [12:11] probably [12:11] but on this one.. it seems like it's not connecting to the server either during update or commit :/ [12:12] pitseleh: Sure you didn't do 'bzr branch' rather than 'bzr checkout'? [12:12] wgrant: ! that may be it lol, sorry about that [12:13] i'll try again :) [12:13] thank you [13:31] beuno: Oh! So my tshirt didn't get stolen by Customs or something? [15:10] jelmer: I don't suppose there's been any progress in getting bzr to use .gitignore and so on? [15:10] hmm, this one looks so simple, I'm tempted to just make .bzrignore a symlink to it ... === pwolanin is now known as pwolanin|afk [17:23] Woah, 2.0rc2. Congrats! [18:15] hey guys.. i pushed a copy of my branch up to a web server,, [18:17] how do i use it to deploy the code to the live site directories. [18:17] ? [18:47] Um, I'm currently fighting with multiple svn --reintegrate issues, if bzr is free of such problems then it should be one of its selling points, guys. [20:06] hi. i'm brand new to bzr. i've co'd a tree (e.g., bzr branch lp:pressflow pressflow-6). now i want to replace a dir within that tree with a backup of my files, and subsequently be able to merge updates to that tree (bzr merge lp:pressflow). atm, i've clearly made a mistake by simply copying in my backed up files, as @ update/sync i get -> http://pastebin.com/d6d8fa07c. [20:06] reading the docs, i'm guessing i'm misusing workflow, and may need a "--local" flag somewhere ... but unclear to me atm. [20:06] any hints? [20:25] pg1054: bzr and launchpad need to know who you are so they can communicate properly. you need to do bzr launchpad-login davidstrauss [20:26] Meths: hi. aha. even for 'anonymous' checkout, where i am NOT contributing back to the upstream trees? [20:27] try pull instead of merge [20:30] or I'm talking rubbish, the message is a warning not an error, it's doing what you are asking but telling you you haven't logged in as well [20:30] pg1054: lines 3 and 6 are the actual responses to what you are doing, everything else is message [20:31] Meths ok. got it, i think. thanks. [21:13] https://bugs.launchpad.net/bugs/433648 - there seems to be some problem with bzr push [21:13] Launchpad bug 433648 in bzr "bazaar crashes during push after adding tag" [Undecided,New] [21:14] i can repeat it every time === JaredWigmore is now known as JaredW [22:23] hello all ! What is it that makes a 2.0in the next release? [22:25] morning [23:35] hi igc [23:35] hi