[12:04] ...the launchpad test suite seems deliberately designed to make it near-impossible to test on production systems [12:11] Merge to rocketfuel@canonical.com/launchpad--devel--0: new improved fascist. r=SteveA (for parts spiv wrote), [trivial] for the rest. (patch-2043: steve.alexander@canonical.com, andrew.bennetts@canonical.com) [12:12] jamesh: ping? === asgeirf [~asgeirf@203-206-229-169.dyn.iinet.net.au] has joined #launchpad [12:36] Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial] make the title input autofocus on the product filing page. (patch-2044: brad.bollenbach@canonical.com) [12:38] jblack: pong [12:39] ok. [12:39] I'm in a conversation atm (thats making a lot of sense to me). I'm almost done though [12:40] New Malone bug 1263 filed on product Malone by Brad Bollenbach: Bug ID links don't change colour after they've been visited [12:40] https://launchpad.ubuntu.com/malone/bugs/1263 [12:43] lifeless: ok. =) [12:48] New Malone bug 1264 filed on product Malone by Brad Bollenbach: Bug keyword search is overly-literal [12:48] https://launchpad.ubuntu.com/malone/bugs/1264 [12:50] New Malone bug 1265 filed on product Malone by Brad Bollenbach: Bug search seems to ignore matching on assignee [12:50] https://launchpad.ubuntu.com/malone/bugs/1265 [12:51] lifeless: your patches are in prod [12:51] and there has been a daily sync since the rollout [12:51] so now is good time to sanity check the result [12:51] lot of red... apparently cvs.gnome went down [01:13] ddaa: patch-370 cleans up tempdirs [01:14] I'm used up for today. Care to send me a mail? [01:14] sure [01:14] I learned the hard way not to make production admin when tired. [01:14] have you documented the process yet so I can do it ? [01:14] hu no... [01:17] it would be a bit lengthy to document all... my rollout process is a mix of personal best practises and the use of few scripts and the ssh/rsync setup [01:17] dude [01:34] lifeless: morning [01:41] Keybuk: hey there [01:41] there are a bunch of bugs on hct in lp - are they still valid? [01:42] yeah, they ones I filed to start off with [01:43] what do you think of matts apt-get wrapper suggestion ? [01:44] sounds reasonable [02:02] so I had a cunning plan [02:02] mdz has a list of packages that turn him on [02:02] Keybuk: what should I do for FTP data here : http://dl.openafs.org/dl/openafs/ [02:02] lets get mdz laid. [02:03] I think that will work [02:03] so I wrote a script to download them, stuff the appropriate soyuz data in for them, and am now running sourcerer over them on my laptop to figure out why the fuck it's broken [02:03] and I'll fix the problems [02:03] sweet [02:04] and then he'll have a list of things he knows will work [02:08] ...ok [02:08] that's quite fascinating [02:08] the list of packages comes out of launchpad backwards [02:12] Merge to rocketfuel@canonical.com/launchpad--devel--0: add better distrorelease translation pages, r=salgado (patch-2045: mark.shuttleworth@canonical.com) [02:13] Keybuk: can you eyeball that url for me ? [02:13] Keybuk: and suggest what I should do w.r.t. ftp series :| [02:16] no, because I'm debugging, go away [02:16] ;) [02:16] lifeless: Doesn't dyson do recursive? [02:17] jblack: I don't know. Bugalogs heres does, which is why I'm askin' him. [02:17] it does [02:17] just stick that http URL as the root [02:17] ok [02:17] Thats what ddaa tells me, anyways, so I'd go with http://dl.openafs.org/dl/openafs/ openafs-*src.tar.gz [02:18] Today I got about 30 setup. Then, ddaa and I talked for a couple hours, and I finally undersatnd this. :) [02:18] fantastic [02:18] yeah. if you merged, I'm the one that bombed ya. [02:18] holy christ openafs is big [02:18] WARNING: revisions left: 90486 [02:19] [02:19] its one of the bigger repos. [02:19] what's bugalogs? [02:19] typo [02:19] bugalugs is what I meant. You. [02:19] what's bugalugs? [02:20] Google tells me it's a "BUM THIEF" [02:20] I suspect Google doesn't know [02:20] jblack: in that case you probably want something like openafs-1.3.*-src.tar.gz because there are overlapping series [02:23] ddaa: they are all main I think [02:23] hmm [02:23] no they aren't [02:24] no releases from MAIN at all [02:24] they have branches for everything [02:24] yuck. [02:25] I sort of understood that when series have overlapping time spans we want to make them distinct productseries regardless because otherwise sourcerer may get new releases with the wrong release ancestry [02:25] ddaa: I don't quite understand how to do series that aren't directly related to main. [02:25] in that case, if lifeless is correct, that's like automake [02:25] thus wanting to use the "these look mainish to me" [02:25] (hammer) [02:26] Keybuk: bugalugs == that guy == hey you - at least how I intended it, humurous 3rd person reference [02:27] ah [02:27] I think I see now [02:27] I thought you had some mystic software [02:27] I am full of mystic software === jblack mumbles something about lp being vaguely archish. [02:29] nah, it's like an elephant [02:29] Heh. I'm referring to the thou-shalt-not-delete feel. [02:29] hehehe... I guess that's a missing feature :) [02:29] if god didn't intend you to delete records from databases, he wouldn't have given you DELETE FROM [02:30] god(stub) hasn't given you DELETE FROM [02:30] ddaa: What's a good example of an overlapping series you've done? I want to pick it apart while I'm thinking about it. [02:31] Never mind. I just looked at cyrus-imapd [02:31] when I say overlapping it's to mean that you can see it from the ftp, the best one is cyrus-imapd, but apparently that one you have is just like automake, so the overlapping bit is really second to the fact they are all living in branches. [02:31] Merge to thelove@canonical.com/dists--bazaar--1.5: new build (patch-32) [02:32] that's really a bit where you have to psyschic and get in the shoes of the packager [02:32] Merge to thelove@canonical.com/bazaar--devo--1.5: added --switch to build-config (patch-25: Matthieu.Moy@imag.fr) [02:33] So help me, if he introduced more tabs, then we're having the next conference in france just so that I can kick him in the balls. [02:33] ddaa: I'm gnomic, not psychic. :) [02:34] gnomes have big feet, so you can feel the packager shoes better :P === jblack checks his shoe size... [02:35] Ok. [02:37] mpt: around? [02:38] you know what they say about men with big feet? [02:40] I used to know somthing like that about women [02:40] But maybe they say the same for men on the other side. === stub [~stub@203-217-37-199.dyn.iinet.net.au] has joined #launchpad [02:51] heh [02:52] I appear to have severed sourcerer's dependency on launchpad [02:57] stub: hey dude [02:57] Morning [02:57] your name is mud [02:57] try "make -C database/schema" as a user called "launchpad" with super-user privegles [02:58] That would fail. You have to run that as a PostgreSQL superuser. [02:58] stub: how much effort is involved in fixing a bug like: https://launchpad.ubuntu.com/malone/bugs/1264 ? [02:58] yes, we made launchpad a postgresql superuser [02:58] then security.py took it away again [02:59] launchpad should not be a PostgreSQL superuser or your tests will be dodgy and not fail when they should. [02:59] right [02:59] so we relented and just ran it as postgres [02:59] bradb: It would involve dropping the full text search stuff and never using indexes for searches, which would be bad. [03:00] stub: surely there's gotta be some solution that doesn't suck here? [03:00] i can't be the first person to have ever considered that users make typoes when they search [03:01] (and to note the other benefits of partial matching, of course) [03:01] bradb: We would have to dump the text to some sort of external search engine like agrep or write stuff for PostgreSQL. [03:01] bradb: Spelling can be done by improving the stemmer I think. [03:02] bradb: You can integrate ispell into the mix, but I didn't have much success setting it up. [03:02] does a stemmer take a misspelled word and try to link it to one or more of the correct spellings? [03:03] bradb: It could. Checkout textsearching.txt for what the stemming currently does (mainly plural forms and some suffixes). [03:04] bradb: I don't know if the ispell integration does that though out of the box - I would need to get out of the box functioning fist (since the docs are sketchy) [03:04] jamesh: ping? [03:04] stub: https://launchpad.ubuntu.com/products/malone/+bugs?field.searchtext=listings&search=Search&advanced=&status=10&status=20&assignee=all [03:04] are the results being weighted properly here? [03:04] why is there a bug with a title that doesn't have "listings" in it above a bug with a title that does? [03:04] bradb: Nope. I only just got the ranking into the indexes. No code is using them yet. [03:05] ah [03:05] bradb: It complicates the queries substantially unfortunately [03:05] Keybuk: yeah? [03:05] but it will happen :) [03:05] stub: i'm willing to assume the complexity so that the user's life becomes easier [03:05] jamesh: so, I'm confused [03:06] you say that hct-enable got merged into rocketfuel [03:06] stub: can you give me an idea of when you plan to look into the typo fu? [03:06] except that none of the patch logs are in it [03:06] but when I try and merge, I get 82,000 conflicts [03:06] Keybuk: Mark had half of your branch merged into his launchpad--debbugs--0 branch [03:06] but none of the patch logs? [03:07] Keybuk: it seems that the other half of the revisions in your branch were keeping it up to date [03:07] Keybuk: base-0 -- patch-4 are in rocketfuel [03:08] oh, silly me [03:08] I think I just merged it into the production config [03:08] yes 5 thru 8 are all ketchup [03:08] Keybuk: I took a quick look through the conflicts, and they look like areas I got Mark to fix when I reviewed debbugs [03:10] right [03:10] so we can just forget about that [03:10] and remove it from PendingReviews [03:12] bradb: The basics is " select title from bug where fti @@ ftq('listings') order by rank_cd(fti, ftq('listings')); ". I havn't through through how to do it though when the indexes are in multiple tables. Probably something like 'order by rank_cd(bug.fti | bugmessage.fti, ftq('listings') === stub buggers off for 40 mins [03:13] friend has an emergency, I'll be popping out for a while [03:15] stub: sorry, i was referring to when you might have a chance to look at the ispell (or whatever) integration [03:34] bradb: yo [03:35] mpt: hey: what do you think of these suggested titles? https://launchpad.ubuntu.com/malone/bugs/1266/ [03:38] bradb: bug 936 is a bug in Malone, not a bug in Firefox [03:39] So if we chop out the "Malone: " from your suggested titles, the only difference between them and what we have currently is "Bug 1234 (edit)" vs. "Editing bug 1234" [03:40] or rather, "Bug 1234 in Mozilla Firefox (edit)" vs. "Editing bug 1234 in Mozilla Firefox" [03:40] mpt: the other difference is that the edit and view pages have that same "Editing..." title currently :) [03:40] mpt: do you see why that's a fairly important difference? [03:41] well, that's just a bug [03:41] So we have three distinct things here [03:42] in order of definiteness [03:42] (1) the view mode shouldn't say "Editing" [03:42] (2) the edit mode should be "... (edit)" rather than "Editing ..." [03:42] (3) all the titles should start with "Malone: " [03:43] correct? [03:43] (4) the bug and bug task titles should be consistent with one another [03:43] but yeah, that's basically it [03:44] (4) is something I did months ago and had to revert [03:44] in the way described by the bug report? [03:45] yes [03:45] you could have used that sentence as your first reponse when i asked what you thought of the titles suggested in that bug report :) [03:46] IOW, if i baz get that branch, i'll find a bugfix for precisely the bug i'm showing you? [03:46] If I had, you would have said "What's (4)?" :-) [03:47] If you baz get, you'll get a smelly fix for (4) [03:47] you won't get a fix for (1), (2), or (3) [03:47] and you won't be able to use the fix for (4) anyway, because that was the pre-LaunchpadTitles days. [03:48] you've lost me [03:49] We now have pagetitles.py for specifying titles of pages in Launchpad [03:49] how can it be that you fixed the titles in the way described by the bug report without addressing 1, 2 and 3? [03:49] I said, "(4) is something I did months ago and had to revert" [03:49] I didn't say "(1), (2), and (3) are things I did months ago and had to revert" [03:50] ok, i'm just going to make this fix :) [03:50] well, this is interesting [03:50] def bugtask_display(context, view): [03:50] return 'Bug #%s in %s: %s' % (context.bug.id, context.contextname, context.bug.title) [03:50] def bugtask_editform(context, view): [03:50] return 'Editing bug #%s in %s: %s' % (context.bug.id, context.contextname, context.bug.title) [03:51] bradb: So (1) shouldn't be happening. [03:51] it should [03:51] that only worked when they were two different pages, which they are becoming again now [03:52] Are you using bugtask_editform even for the view mode? [03:52] i've already submitted the merge to break it into two again [03:52] then i'm going to make another small change to hide the Save Changes button [03:52] (on the view form) [03:52] bradb: I don't think I'll have a chance to improve the text searching any more than it currently is before 1.0. It was on my list, but I don't see myself finding time for it. [03:52] then fix the titles [03:52] stub: ok, no worries. maybe we'll have a chance to discuss it in brazil. [03:53] well, if you're splitting it into two using the same template names as before, you won't need to touch the titles [03:53] they'll start Just Working [03:53] i called them bugtask-view.pt and bugtask-edit.pt [03:53] bradb: Yup. Be good to have some brains on it too. This is a whole big area of research that I've only dipped my toe into. [03:54] bradb: So all you'll need to do is fix the first and third of the four lines I pasted above [03:54] bradb: But it seems wrong to me that there should be completely different templates depending on whether you're editing something or looking at it [03:54] stub: i can imagine. it would be a real usability milestone for all of launchpad to improve the searches in that way. [03:54] that just encourages gratuitous inconsistency in layout [03:55] can lp titles even work if it's only one template? [03:55] erp - make that rank(fti, ftq('foo'), not rank_cd. Need to experiment with the two, but I expect the former will give us better results. [03:55] (also, the task view Just Looks Different that the view view) [03:56] bradb: I only put "Editing " in the title of the edit page *because* they were separate pages. I'd much rather they were just a single "Bug 123 in Mozilla Firefox" page with a single title. [03:56] New Malone bug 1267 filed on source package gqview by Vince: Doesn't remember window dimensions/location etc... [03:56] https://launchpad.ubuntu.com/malone/bugs/1267 [03:57] and that, in the future, you can click a little Edit icon next to an item to turn it into a text field or whatever [03:57] without having to go to a separate edit page [03:57] mpt: enter sabdfl, who has said he doesn't like having one superform that handles all possible scenarios, etc. [03:58] mpt: as well, like i say, they'll be different pages. [03:58] yeah [03:58] *sigh* [03:58] Launchpad has too many pages. [03:58] for example, kiko has proposed that maybe the watch information doesn't make sense on the view only page if there's no watch info set [03:59] A separate page for subscribing, a separate page for marking as duplicate, a separate page for editing title/description ... it's painful. [03:59] also, the view page could have, for example, and actions portlet that has an action to go to the edit page (like the bug page has for editing bug details). [04:00] mpt: we agree fully on that horror :) [04:00] the uncensored version of my opinion on that model is that it's PURE SHIT [04:00] but changing things will require a consensus that we haven't yet reached, i don't think [04:01] oh, now that's just kooky [04:02] the success *and* failure functions just got called for everything [04:02] Heisenbug! [04:02] bradb: I disagree with (3), however [04:03] and iirc kiko does too [04:03] mpt: you want to keep "Malone: " in there? [04:03] i'm happy to go either way, really [04:03] No, I want to keep it out of there [04:03] It's currently out of there [04:04] i'm happy to not put it in there too [04:05] i don't mind if we don't put (edit) in there either, to be honest [04:05] bradb: Bug 936 was a bad example for you to use in bug 1266, because bug 936 is a bug about Malone-the-product :-) [04:05] that's why it has "Malone" in its titles. [04:06] i'm going to change the description to make things clearer [04:07] New Malone bug 1268 filed on source package gqview by Vince: File browser doesn't use Gnome's widgets/icons [04:07] https://launchpad.ubuntu.com/malone/bugs/1268 [04:10] there [04:11] mpt: btw, did you notice: https://launchpad.ubuntu.com/malone/bugs/1263 ? [04:11] Malone seems to be a bit sporadic in sending out notifications today; not yet sure what's going on [04:11] bradb: yes, I saw when dilys mentioned it [04:12] ok [04:12] that's going to be ... fun [04:13] mpt: can we perhaps create two kinds of links, one for menus, and one for "content" links? [04:13] It's not that hard [04:13] the "content" kind of links could be underlined; the menu ones not, perhaps [04:14] telling menu links not to change color is either 10 or 20 more characters in launchpad.css [04:14] it's easy [04:14] 20, I think [04:14] i was wondering about that: is it bad for them to change colour? [04:15] well, why else did you want two different kinds? [04:15] oh, the underlining [04:15] right [04:15] well, ironically, the links in the bug listing sidebar shouldn't have been underlined, to match the portlets elsewhere [04:16] exactly, i screwed that up [04:16] no, that was my fault [04:16] or did you use something other than