=== r0bby is now known as robbyoconnor [09:29] morning all [10:24] mgz: oh, I missed that, hey ! [10:25] hey vila! [10:26] hm, I need to fix my builddeb test a little, looking at it again this morning [10:27] jelmer: no need for a DictStore, we already have everything we need ;) Running a full test suite before pushing my changes to lp:~bzr/bzr/commit-uses-config-stacks but there are still issues to be addressed (more in my review comment) :-/ [10:30] jelmer: done [10:30] jelmer: all these minors bugs are the most painful part of the option migration :-/ [10:31] the bugs were introduced by children? [10:31] jelmer: ha crap, I didn't notice you pushed additional revisions :-/ [10:31] ? [10:32] * mgz is just teasing about a misplaced 's' :) [10:32] ha ha [10:32] :) [10:35] mgz: by the way, is http://paste.ubuntu.com/769900/ clearer ? [10:35] mgz: i.e. the added comma [10:39] :) [10:46] ...I still can't parse that I'm afraid [10:46] you need to just flip the clauses [10:47] "The ``SectionMatcher`` objects are for defining which." for eg. [10:54] mgz: thanks, fixed [11:18] okay, nearly caught up with life. [11:18] just need to write news and land things... [11:28] mgz: yeah for news ! :) If you had a look at what's new for 2.5 too that would also be truly great :-p [11:39] mgz: found that bug back: #659763 [11:39] bug #659763 you helpful bot [11:39] Launchpad bug 659763 in bzr (Ubuntu Natty) "bzr smart server can't handle UTF-8 user names, gives UnknownErrorFromSmartServer" [High,Fix released] https://launchpad.net/bugs/659763 [11:46] hi there! how does one change an existing branch hosted in launchpad to set append_revisions_only? [11:47] is it enough to change .bzr/branch/branch.conf and push? [11:47] vila: hey, another path for doing a similar thing, what fun [11:48] sidnei: with recent enough bzr versions you can do `bzr config append_revisions_only=True -d lp:...` [11:49] thanks mgz! [11:53] I wonder whether this diff/merge is bad because the file contains conflict markers for test examples... [11:56] vila, mgz: Could I persuade either of you to take a look at https://code.launchpad.net/~jelmer/bzr/hpss-no-vfs/+merge/85153 ? It's one of the prerequisites for hpss-get-inventories [11:57] on it [12:10] jelmer: done [12:11] vila: merci bien :) [12:11] hehe [12:11] lunch time for me [12:21] bzr info is too slow. [12:24] mgz: -v you mean? [12:25] just plain, it takes as long as st on hot cache and shouldn't need to do as much work [12:25] -v is just silly. [12:25] takes 6 seconds herre. [12:26] 400ms was what I was talking about with "too slow" [12:26] it's long enough that there's a noticable pause [12:28] it looks at the full branch history to see what the revid of the first revision is, so it can figure out its date [12:29] yup, at least the other output comes out before it goes off and does that. [12:51] hmm, is there a particular reason we always open a branch for a working tree? [12:51] it seems like some operations should be able to get away with not opening the branch (especially if it is remote) [12:56] probably similar to reasons we reopen repos and branches way too much [13:00] * jelmer lunches too [13:21] vila: have you decided what you want to do with lp:~jelmer/bzr-upload/fix-2.4-compat yet? [13:22] It's fine with me if you reject it, but it would be nice to see it disappear of my activereviews queue :) [13:35] * jelmer stumbles onto mumble [13:37] ha, well spotted on bug 317778 jelmer [13:37] Launchpad bug 317778 in Bazaar "Switching to a local sibling with non-ascii name causes error" [Low,Fix released] https://launchpad.net/bugs/317778 [13:39] * jelmer was browsing switch bugs anyway... :) [13:40] *crickets* [13:41] I think I borked by audio setup someone [13:41] oh, nope, just being an idiot === yofel_ is now known as yofel [13:52] jelmer: what I don't get is why you uploaded a new version when none has been released >-/ [13:54] vila: I had to earlier, because bzr-upload was broken with bzr 2.5 [13:55] that's fine, 2.5 is still beta, but then, why trying to ensure compat with 2.4 ? [13:56] vila: I'd rather not maintain two copies of bzr-upload in debian [13:57] meh, the point of splitting into series is to have *less* maintenance to do indeed, can't they be used in debian ? [13:58] vila: it means I have to do twice as many uploads to debian [13:59] vila: anyway, the current situation is fine for me, let's just reject the MP [14:00] ok, but be aware that I intend to track 2.5 far more than 2.4 so the series will diverge [14:00] sure [14:00] 2.4 will stop being relevant in Debian too at some point [14:01] right [14:03] jelmer: by the way, did you start to CC me when replying to reviews ? I got duplicate mails in the last days... [14:04] vila: https://code.launchpad.net/~jelmer/bzr/hpss-_get-checkout-format/+merge/85652 [14:04] ha no, not this thime [14:04] s/vila/mgz/ [14:04] vila: sometimes I have to resend email if I forget to use GPG/MIME [14:05] jelmer: sry, misread your re-submission, I *got* 3 copies last time you CC'ed me, [14:05] vila: as launchpad seems to refuse GPG signatures from thunderbird that don't use GPG/MIME [14:05] the (small but annoying) issue is that some of them are filtered in the wrong mailbox [14:10] lunch lunch [14:11] meh, can't '+reply' on comments from previous versions of a proposal o_O [14:12] jelmer: you really think BZR_EMAIL is used for cases where it is *also* defined in bazaar.conf and/or branch.conf ? [14:12] vila: yes [14:12] * vila shudders [14:13] launchpad uses it in its test suite for example, but I also imagine things like cron scripts rely on it [14:14] -Oemail=.. seems like a reasonable alternative, but IFF we want to change the behaviour I think we should deprecate BZR_EMAIL first and start warning existing users [14:15] yeah, but -Oemail may not work for crontab or scripts since it needs to be passed to bzr itself [14:17] vila: right [14:18] email_from_store may do the trick (ugly but doesn't require another confusing parameter to Option), let's try [14:30] vila: are you looking into implementing that or should I? [14:30] jelmer: ok, that fixes the issue with BZR_EMAIL, now looking into post_commit deprecation warnings [14:32] vila: I already added one to the definition of post_commit in BranchConfig [14:32] yeah, but the test suite is complaining now :) [14:33] vila: ah, ok [14:33] vila: if you need me to do a review, you know where to find me >-)( [14:34] hehe [14:34] BZR_EMAIL=me@example.com ./bzr config -Oemail=you@xxx.com email [14:34] gives the expected result :) [14:34] \o/ [14:34] well, for some compat-nutty value of expected [14:37] * jelmer is compat-nutty and proud of it :P [14:41] jelmer: hehe, about compat, tried the loom test suite recently ? [14:41] * vila dodges [14:49] jelmer: oh, forgot to reply: yes, post_commit predates our hook system (by far) [14:50] jelmer: dunno if it's casher but I approved your part of the common branch ;) [14:55] lambed up. [14:56] vila: on the config branch, BZR_EDITOR has a similar issue [14:56] of overriding any option setting ? [14:57] order is currently BZR_EDITOR, get('editor'), EDITOR, VISUAL... other fallbacks [14:57] same era probably [14:59] vila: makes sense to deprecate it then, IMO [15:00] jelmer: BZR_EDITOR ? BZR_EMAIL ? both ? [15:00] I would rather deprecate all of them in one go if only for users to handle them all at once [15:01] no ? [15:02] vila: post_commit [15:02] vila: I think we should keep BZR_EMAIL and BZR_EDITOR [15:03] jelmer: ha, but, yes, we agree that post_commit should be deprecated, you did it (I just fixed the test fallouts) [15:03] ha, sorry, mixed conversations, you were replying to my late reply here, [15:04] so, yes, post_commit is old, has been replaced by a better mechanism, never formally deprecated [15:04] the later is now done [15:04] great [15:05] officiously deprecated since 0.15 if you look at the comment I left [15:05] s/left/updated/ [15:11] vila: thanks! [15:11] I'll approve your work then, and land :) [15:11] hehe [15:12] * jelmer adds vila to the NEWS entry as well [16:20] jelmer: brain dumped my thoughts on your feature-flags proposal, about to leave for an appointment, should be back later [16:23] jelmer: oh, thanks for your review on config-explained, just one question: [16:24] I addd 'for modifcation' because I thought the parameters was a bit lost and obscure, would 'Where modifcations go' be clearer ? [16:24] or may be you know already too much about stacks to need these comments ;) [16:26] hmm, yeah, I added the comment first and the docstring later, now that I re-read the two, the comment is redundant [16:26] vila: before you notice independently, yes, I added release notes in the wrong section ;_; [16:27] hehe ! Progress ! [16:45] vila: thanks! [17:32] ...and the reaper kills mumble [17:33] hmm [17:33] dark-cloaked bastard. [17:39] hmm, what a language, missing context I assume I wasn't the target ;) [17:40] vila: unless you're the person going around killing random processes on mgz's laptop when it runs OOM, no. :-) [17:40] oops, busted :) === lamal666 is now known as lamalex === Vorpal_ is now known as Vorpal === deryck is now known as deryck[lunch] === nyuszika7h is now known as Makays === Makays is now known as nyuszika7h === mwhudson_ is now known as mwhudson [20:37] is it possible to fetch just a directory of a bzr branch? [20:37] so say I want just the debian dir of lp:~ubuntu-desktop/libindicator/ubuntu === deryck[lunch] is now known as deryck [21:30] lamalex: No, the data structures / protocols used just don't work that way [23:32] hey poolie [23:53] hi Noldorin, all