[00:06] oh, is it today? [00:07] ah, for you thumper it is :P [00:07] Ursinha: yes, you've got to remember I'm in the future :) [00:08] thumper, indeed :) [00:08] but, it is for spm as well :) [00:08] true [00:08] so, happy sysadmin day spm :) === matsubara-dinner is now known as matsubara [00:25] thanks thumper, Ursinha, mwhudson! [00:25] * spm adds priority flags to losa requests from those three.... [00:27] hahaha [00:29] ... errr for now. I may remove said flags at any moment and with no warning. I do have a bofhish reputation to maintain afterall! [00:43] jelmer: hai [00:43] lifeless: hey [00:44] lifeless: did you see my progress core review? [00:44] I landed it [00:44] did you see my progress-gtk branch? [00:44] I saw that there was a branch, but I haven't had time to try it yet [00:45] its pretty small if you could that would rock [00:46] I'll have a quick look [00:47] jelmer: hey, do you have perl subunit bindings for output ? [00:47] argh, the diff in lp is not against lp:subunit [00:47] resubmit it [00:47] it will make a new one [00:47] I'll do that now [00:49] I just did that, but now the diff is gone :-/ [00:49] * jelmer grumbles [00:49] give it a sec [00:53] there it goes [00:55] jelmer: ^ [00:56] already reading it from a locally generated diff [00:56] (I wasn't aware it took a while for the diff to appear, I figured there was just something broken) [00:56] heh [00:56] its async [00:56] it would be nice if it could say "Updating diff.." like it does when it doesn't know a branches history yet, but knows it has been pushed to. [01:04] let me file a bug on that. [01:05] done [01:08] what's the bug #? [01:08] (I also filed one a few seconds ago, would like to mark it as a dupe) [01:09] never mind, brute forcing bug #s worked :_) [01:09] bug 407176 and bug 407177 [01:10] Bug #407176: new reviews could say 'updating diff' [01:10] Bug #407177: indication that a diff is being generated on merge request page [01:11] reviews are very much at the forefront of my mind right now [01:11] heh heh heh [03:05] er [03:05] the bzr builder test run stopped because the appserver segfaulted! [03:08] ouch [03:09] Yes. [03:09] Oops. [03:15] thumper: FINALLY some progress on the cscvs bug!! [03:15] * mwhudson runs off for a haircut [03:15] \o/ === matsubara is now known as matsubara-afk [03:32] thumper, have a moment to review a simple fix to the JS test suite driver? https://pastebin.canonical.com/20637/ [03:32] * thumper takes a look [03:34] mars: r=me [03:34] cool, thank you [03:57] * thumper is going to get the girls [04:26] * mwhudson is back [04:33] mwhudson: Have you lost your CVS grokking ability with your hair? [04:34] wgrant: well, i wouldn't be as cocky as to say that i grok CVS [04:37] mwhudson, ever set up a build slave image? [04:37] mars: not from scratch, but i've updated them [04:38] hmm [04:38] ah, I would need a new one, from scratch, for the JS CI build stream [04:38] thanks anyway [04:38] well, i wouldn't say 'from scratch' [04:38] start from the existing AMI [04:39] you'll need to fuck about on the master a lot too [04:39] well, no, probably based off of the devel image [04:39] mars: probably best to do this with gary, he's in your tz after all :) [04:39] and yes, I would need to configure something in the master [04:39] heh [04:40] darnit, I am really close to getting JS continuous integration running [04:41] I just need to generate the image, and configure the buildbot system [04:42] How will that work? Run the browsers into xvfb? [04:42] yep: xvfb-run -s '-screen 0 1024x768x24' make jscheck [04:42] Useful. [04:42] oh yes :) [04:43] and 'make jscheck' in turn runs the entire LP windmill test suite [04:43] mars: making the image will take a few hours at least [04:43] yeah :( [04:43] mars: and it will be easier if you get some sleep, i promise :) [04:43] mars: (it's nearly midnight for you?) [04:44] yes, it is :)] [04:46] firefox just crashed, taking 20 tabs with it [04:46] I think it was trying to tell me something [04:47] seen, even your computer wants you to stop working [04:47] I would start playing nethack, but it would just nag me too [04:47] ok, good night :) [04:48] night mars [05:57] thumper: i think i have a fix for the cscvs bug! [06:01] mwhudson: yay [08:30] good morning [08:31] Morning adeuring [08:31] hi noodles775! [09:01] rockstar, you here? [09:07] jtv: Are translation commits meant to be done by codehost@crowberry? [09:07] That seems a bit ugly. [09:08] wgrant: could you file a bug about that under rosetta please? [09:08] jtv: Sure. [09:08] thanks [09:21] abentley, you here? [09:35] Howdy [09:36] hi mrevell! [10:43] BjornT: I can handle Bug #407288 if you can confirm I can throw the data away. [10:43] Bug #407288: BugNotificationRecipient needs pruning [10:48] stub: sounds good. i've commented on the bug. [11:00] Morning. === noodles775 is now known as noodles-afk === noodles-afk is now known as noodles775 === salgado-afk is now known as salgado === matsubara-afk is now known as matsubara === mrevell is now known as mrevell-lunch [14:10] jtv: I'm here now. [14:10] abentley: hi! I ran into the fact that IBranchCollection.ownedBy doesn't return branches that the person in question is an _indirect_ user of. [14:11] abentley: i.e, branches owned by teams that the user is in. [14:11] jtv: I guess that makes sense. I'm not sure how to get the list of branches you have write access to. [14:11] I wanted your opinion on whether that is the right thing for it to do (in which case I should work around it e.g. by adding a method that casts a wider net), or if it should also include those branches (in which case it's basically not my problem any more :-) [14:12] jtv: I opine that both lists are useful, so we need two methods. [14:13] jtv: For example, I'd expect ownedBy is used on code.launchpad.net/~abentley [14:14] abentley: ah yes, that page goes through all teams you're in. We had those timeouts with that this week. [14:14] It counted branches owned by each of the teams you're in. [14:15] jtv: In the main display, it only lists branches you personally own. [14:16] abentley: maybe the best way to do this is to add an optional parameter for "indirect ownership too"? [14:18] That might be the most discoverable for cases like yours. === mrevell-lunch is now known as mrevell [14:44] yess! launchpad is finally working :D [14:44] well, ... make schema is working at lest [15:27] JamalFanaian, woo, awesome [15:28] JamalFanaian, want some bugs to try and work on fixing now? [15:30] jtv: I was trying to figure out how to use http://blog.launchpad.net/general/exporting-translations-to-a-bazaar-branch with source package translations, but can't seem to see how to turn it on there. Is this supported for source packages yet, or only for projects? [15:30] cjwatson: only projects for now, sorry [15:30] ah, drat [15:31] should I file a bug about it? I didn't see one [15:41] kiko: uhh well sure! i don't know python *that* well yet.. so i was hoping to be able to get into playing with the project [15:41] i can try to fix bugs but i don't know if i'm going to be too useful just yet [15:44] matsubara, can you help find one or two trivials for JamalFanaian to work on? [15:45] sure thing. once we finish the call I'll look for some [15:46] JamalFanaian, are you interested in any specific are of Launchpad? Bug tracking, code hosting, translations, etc [15:46] matsubara: not particularly, i wouldn't mind working on any part of the project :) [15:49] jtv, hi. [15:57] JamalFanaian, bug 126509 is very very trivial. just a text change in one of the templates and perhaps a test update. [15:57] Bug #126509: "Most Frequently Reported Bugs" is incorrect capitalization [15:57] JamalFanaian, would you like something more difficult? [15:59] matsubara, it's a good first test :-) [16:03] herb, you here? [16:03] jtv: yes sir [16:04] great :) I wanted to ask for two things: [16:04] herb: 1, is there any way I can see the output from the export-to-branch script? It's not showing up on error-reports. I'd like to see how the timing holds up. [16:05] 2, there's something I'd like to test on staging later that'd involve a patch and a few script runs. [16:06] herb: ah nm, tom just came back and gave me the info [16:07] jtv: ok. I'll nevermind then. :) [16:07] sorry to bother you. 2 remains open though :) [16:07] oh. ok. [16:07] yeah. just let me know what you need for 2 [16:07] I'm around for hours. [16:07] (with a break for lunch in there) [16:08] matsubara: sorry i was gone for a few minutes.. no i'm fine with that.. it will help me figure out how TAL works and where templates are stored in launchpad [16:09] kiko: heh, it is a good first test :) [16:10] JamalFanaian, all right. let me know if you need some help finding your way around the tree [16:11] sinzui: did you send me the person page mockup? [16:11] matsubara: thanks :) i will.. let me start playing with this, hehe [16:11] can sb help me? [16:11] * sinzui does now [16:11] i try to follow https://dev.launchpad.net/Getting [16:11] but i get an error at ./utilities/launchpad-database-setup $USER [16:12] it's : -bash: ./ultilites/launchpad-database-setup: No such file or directory [16:12] JamalFanaian, sure. I'll leave for lunch in a bit. if you have any questions ask here and I'll help you out when I get back (or someone else might be able to answer) [16:12] mrkid, it looks like you're either not in the right directory, or you've actually mistype utilities. [16:13] i'm in the 'devel' directory [16:13] and i make a copy of this line into my terminal [16:16] mrkid, try `ls utilities` [16:16] matsubara: alright thx :) [16:16] And pastebin that output, please. [16:19] rockstar:chat? [16:20] abentley, I was just about to propose that. [16:21] rockstar: ring me when ready. === matsubara is now known as matsubara-lunch [16:21] rockstar, would you like to do a UI review? [16:21] beuno, ABSOLUTELY! [16:23] rockstar, I'll assign [16:25] rockstar, i tried but i got: administrator@ToshibaServer:~/launchpad/lp-branches/devel$ ls utilites [16:25] ls: cannot access utilites: No such file or directory [16:26] oh gosh, i feel dumb.. i'm pretty lost.. is there any document that explains the directory structure of launchpad? [16:28] * JamalFanaian thinks he is getting somewhere [16:29] JamalFanaian, grep is your friend. [16:30] rockstar: heh, well i don't know what to grep for just yet [16:30] but i found lib/lp which is what i was looking for [16:32] JamalFanaian, I suspect you want lib/lp/bugs/templates [16:34] rockstar: for this its lib/lp/code/templates [16:34] merge proposals are in the code section [16:34] and the issue seems to be in the merge proposal template [16:34] JamalFanaian, which bug are you working on again? [16:35] assuming i picked up the right bug [16:35] #407347 [16:35] Bug #407347: Failure detecting membership in the targeted review team - "(community)" label incorrectly showed [16:35] and i didn't [16:35] i have no clue where i got that bug number from [16:35] went back through the look and saw that i was actually pointed to #126509 [16:35] Bug #126509: "Most Frequently Reported Bugs" is incorrect capitalization [16:36] oh gosh, that's a lot easier.. i was having a hard time figuring out how to replicate #407347 [16:36] Bug #407347: Failure detecting membership in the targeted review team - "(community)" label incorrectly showed [16:36] rockstar: i apologize for the misunderstanding, you are right :) [16:37] jml, thanks for the feedback [16:41] why would the "Most Frequently Reported Bugs" section not show up in my local environment? :\ === mrkid is now known as kedatinh [16:50] hello every body, i need some help [16:50] when i try './rocketfuel-setup' [16:51] i got error: Logging bzr into Launchpad (it's okay if this errors)... [16:51] bzr: ERROR: The user name administrator is not registered on Launchpad. [16:51] You can ignore any error above about not registering an SSH key [16:51] with Launchpad. Registering an SSH key is only important if you [16:51] are writing data to Launchpad, or trying to access private data. [16:51] make: *** No rule to make target `install'. Stop. [16:51] ERROR: Unable to install apache config appropriately [16:51] so what can i do? [16:53] kedatinh: it sounds like your bzr configuration has your launchpad_username as 'administrator'? [16:53] (check ~/.bazaar/bazaar.conf) [16:54] ok i have commited my changes and pushed them to launchpad, https://code.edge.launchpad.net/~jamalfanaian/launchpad/bug-126509 [16:54] do i just push a merge proposal for it now? [16:56] JamalFanaian, submit a merge proposal, but find a reviewer as well. [16:57] do i just ask for a reviewer here? === noodles775_ is now known as noodles775-afk [17:11] maxb: time to help me with the wiki again? [17:11] maxb: I got some sysadmin help this time. :-) [17:12] mrevell: can you log out and back into the dev wiki please? [17:13] sinzui, from our discussion about the context/menu TALES formatter expensiveness, I seem to remember that the biggest issue seems to be with items that may hit the DB for permission checking. is that right? [17:15] salgado: the biggest issue is that the list is recreated with each call, which causes duplicate db calls and permission checks. Once we start rendering a page, the state the the menu links can never change, so we should cache each call [17:16] JamalFanaian, you go to #launchpad-reviews for reviews. [17:17] joey done [17:17] mrevell: ok. make sure you can edit [17:17] mrevell: maybe remove the "####" comment in the header [17:17] sinzui, right, but if we had an easy way of caching the permission checks, thus avoiding the DB calls, recreating the lists wouldn't be a big deal, I think [17:18] deryck: thanks [17:18] np [17:18] joey: yup, no probs [17:18] mrevell: super. Community devs can now edit the front page [17:18] joey: Ah, superb :) [17:19] mrevell: kfogel - afaict, the front page is the only ACL locked page on the dev wiki [17:19] I see you point, but I do not understand why we think the link states will change from one call to the next. We know if they did change, there is a bug. The links cannot ever change once we call them the first time [17:19] herb: a different request than expected... could you "GRANT SELECT ON POFileTranslator TO translationstobranch" on the production db? I've written up a branch that does the same for the long run. [17:20] mrevell: kfogel - so, we should be good there. Matt, you'll want to make a decision about the ACls on the help wiki [17:20] joey: Looks like you're sorted, but I'm around now. [17:20] mrevell: if you do want to make a change, it appears we need to make a config change to enable the new team, plus the new acl [17:20] maxb: super thanks. If you can log out and back into the dev wiki, you should be able to edit the front page now [17:20] sinzui, right, I agree that it makes no sense to regenerate the list of links in a given request, but it might be easier to cache the permission checks than the list of links [17:21] yes, I have an edit link now! :-) === deryck is now known as deryck[lunch] [17:25] jtv: done [17:25] herb: thanks [17:25] welcome [17:34] hi sinzui -- have you pushed that announcements branch yet? === salgado is now known as salgado-lunch [17:38] bac: I can push the branch. I had trouble extracting it from my other branch === matsubara-lunch is now known as matsubara [17:39] sinzui: ok, i can wait. untangling them would probably be best [17:39] bac: and this branch will depend upon a branch that I am testing before I submit to PQM [17:40] sinzui: thanks for the comments on those bugs. i think i found all that can be handled during this effort. [17:40] * bac -> lunch === beuno is now known as beuno-lunch [17:49] good weekend, everyone! [17:56] herb: did you do that grant on all slave DBs too? [17:56] mthaddon: I did [17:56] sweet [18:02] have a great weekend all [18:11] bac: you can merge lp:~sinzui/launchpad/announcement-edits, to get the navigationmenu changes === deryck[lunch] is now known as deryck === rockstar` is now known as rockstar [18:40] sinzui: thanks [18:42] I think I have found my first example of a browser test that is not testing what it claims. [18:42] * sinzui considers changing it to a view test. === salgado-lunch is now known as salgado [18:44] matsubara rockstar: well it only took me 2 hours to finish that bug! -- is there another bug that you would want me to work on? [18:45] JamalFanaian, I'm sure I could find you some things... :) [18:45] matsubara may be able to help you more unbiased than I though. :) [18:45] rockstar: o.O lol [18:50] JamalFanaian, I think you can search launchpad projects for the tag "trivial" and find some simple fixes. [18:51] deryck: alright i will do that, thanks [18:51] JamalFanaian, np. Thanks you for taking on some bugs! :) [18:51] * maxb wonders if anyone has any thoughts on how to debug a twistd process that doesn't exit when you Ctrl-C out of "make run" [18:52] JamalFanaian, how 'bout bug 337582 [18:52] Bug #337582: Branch sort fields say "by registrant name", but they mean "by owner name" [18:52] JamalFanaian, https://edge.launchpad.net/launchpad-project/+bugs?field.tag=trivial is a good start [18:53] JamalFanaian, also, when you start working on a bug, assign it to yourself and set the status to in progress [18:54] JamalFanaian, I just did that for you for bug 126509 [18:54] Bug #126509: "Most Frequently Reported Bugs" is incorrect capitalization [18:55] JamalFanaian, and link the branch to the bug report [18:56] matsubara: ah ok understood [18:56] that makes sesne [18:56] s/sesne/sense [18:59] beuno-lunch: ping [18:59] * rockstar fetches a foods [19:01] how do you guys usually deal when working on something else? do you revert your source back to the trunk? [19:03] JamalFanaian, we do a branch for every bug or feature we work on. [19:07] deryck: oh ok, i see there's a rocketfuel-branch script, let me try with that [19:08] JamalFanaian, yeah, that's typically how we do it. I think it just runs bzr branch and then links sourcecode deps from trunk. [19:08] deryck: alright, thanks [19:08] JamalFanaian, as your branches get more complicated, you want to keep them around even after review because you may have to come back to the problem, reference your work again, etc. === EdwinGrubbs is now known as EdwinGrubbs-lunc === EdwinGrubbs-lunc is now known as Edwin-lunch [19:10] deryck: that makes sense, i will do that [19:15] it's funny how much i learned from changing 3 characters on my last bug lol [19:21] JamalFanaian: We usually assign new hackers trivial bugs during their first week because most of his time will be spent learning how to make the change. [19:21] sinzui: yeah, it's actually a really great idea :) [19:22] i mean, just from that i learned about running launchpad, where templates are stored and how launchpad is layed out, and how to run / modify page tests [19:23] right. your experience is the same for most of us. We are 100% distributed. We usually do not meeting someone for two weeks. At which time, we have lots of questions about why something does not work on our machines. [19:50] JamalFanaian, only mark a bug as fix committed when the branch has landed on lp:launchpad/devel [19:51] matsubara: sorry i will revert that then [19:52] JamalFanaian, only mark a bug as fix committed when the branch has landed on lp:launchpad/devel [19:55] I'm having "An error occured when trying to install bzr 1.17" (full log: https://pastebin.canonical.com/20664/) when running make schema. Anyone got something similar and know how to fix it? [19:56] I'm running bzr 1.18dev [19:58] I probably can't help anyway - but as that pastebin's not community-accessible I definitely can't help! [19:59] matsubara, read carefully: [19:59] bzrlib/_chk_map_pyx.c:31:18: error: zlib.h: No such file or directory [19:59] matsubara, it basically says you're not on the diskless system. :) [20:00] should I remove my laptop's hard drive? [20:11] gary_poster, ping, have a pre-imq question for you [20:11] mars: what's up [20:12] hi gary_poster. I'm trying to get the 'test-all-windmills.py' script to have the lp dev paths configured [20:12] and that means either a) pulling the script contents into the existing bin/lpwindmill [20:12] or b) create a new script in bin/, bin/test_all_windmills.py [20:12] neither feels like a great solution [20:13] gary_poster, I was wondering what your opinion was [20:13] mars: lp dev paths: do you mean like ppa.* and code.*? [20:13] gary_poster, I need eggs/windmill, eggs/mozrunner, etc. [20:14] oh! [20:16] mars: if I understand correctly, I would do what I think is your (b): I would move the script to bin, and have it generated by the buildout stuff. You could do that using the setuptools approach or using that buildout-templates directory that is processed with z3c.recipe.filetemplate . Do you not like (b) because it hides the script away in bin? [20:17] (I must admit, I think it is more discoverable in bin in the abstract: it is a standard convention, and then you only have executables in there to dig through) [20:19] gary_poster, it is in utilities/ right now, and now I don't think that is right place for it, since it is an alternative test driver. [20:19] so bin/test-all-windmills.py sounds good [20:20] what is the buildout-templates approach? setuptools is a bit much for now, as it is a single shell script that needs wrapping. [20:20] mars, agree with utilities being odd [20:22] mars: it's pretty easy. You put templates (*.in) in buildout-templates, in a mirror of the dir you want (so buildout-templates/bin in this case). When buildout processes the files, it substitutes in buildout bits and bobs. There are plenty of examples in there. Here are the docs: http://pypi.python.org/pypi/z3c.recipe.filetemplate [20:23] mars: check out test.in, for instance [20:23] It only does some processing at the top, and it is probably the exact same variables you want [20:27] mars, actually we are using a slightly newer version; I think we are waiting on a review; need to check into that. The newest docs are in eggs/z3c.recipe.filetemplate-2.1dev_gary_r101903-py2.4.egg/z3c/recipe/filetemplate/README.txt . If this is bash shell script then you might want those features (ability to escape the {} syntax) [20:32] gary_poster, ok, thanks. Should this go on the dev wiki, or is it a moving target? [20:32] mas, you mean the fact that we use it? [20:33] just the process for adding something to bin/ [20:33] mars: oh...let me make sure I didn't describe it in the buildout doc. Do you think it ought to go there? [20:34] mars: and, no, I don't think this is a moving target [20:34] well, for buildout, there are two sources of information: how buildout works, and how to do things in our setup using it [20:35] "how buildout works" is on the PyPI page [20:35] "how do to things in our own setup", like an FAQ, is not around, afaik? [20:36] mars: we have doc/buildout.txt for that purpose so far [20:37] ok [20:37] mars, see the "Add a script" part of that doc [20:38] mars, and "Add a File Modified by Buildout" beneath it [20:39] It is described there as much as I thought was appropriate. Looks ok to me. [20:39] But I wrote it :-) [20:41] gary_poster, I think I'll make a tweak or two to the second paragraph, to explain the directory structure [20:41] mars, awesome thank you [20:42] gary_poster, what does "In the Launchpad configuration, this is used in the ``[filetemplates]`` section" mean? [20:42] I don't understand how that sentence relates to using filetemplate [20:43] mars: the [filetemplates] section of our buildout.cfg [20:44] (the section could be named anything; we call it [filetemplates] instead of [yogurt] or [sillyputty]) [20:44] ok, is that sentence necessary? Or is it self-explanatory, by knowing how buildout works, and seeing the [filetemplates] recipe section in the .cfg? [20:46] mars. mm, the way I see it, this is all a compromise. Everything is easier to understand zc.buildout, and the more you understand, the less you need any document like this one. This is supposed to be a guide. ...if you don't think it is helpful, I don't have any attachment to it. ;-) OTOH, I was *trying* to be helpful when I wrote it. ;-) [20:46] in other words, there is only one way to configure and activate a recipe, so saying "we use z3c.recipe.foo" doesn't need explanation as to how it is configured. [20:47] ok [20:47] mars: to a hypothetical robot, agree 100%. Less sure about a human. [20:47] heh [21:20] So I am looking at this bug, https://bugs.edge.launchpad.net/launchpad-foundations/+bug/127489 [21:20] Bug #127489: Answers column is in the wrong order in person's "Most active in" table [21:20] and I've found that the view just sorts the categories alphabetically... [21:21] now the issue is that i can't really figure out how i could set the proper sorting to go along with the application tabs without hard-coding that in :\ [21:30] JamalFanaian, it's possible to get the order of the tabs programmatically, but there's no way to map them back to the categories other than maintaining a hard-coded mapping [21:32] rockstar: skype? [21:32] I think the most reasonable thing to do is to hard-code the order in which the categories are returned, in PersonView.contributed_categories (which seems to be what's used in that page) [21:33] salgado: yeah, that makes sense. i'm going about figuring out a proper way of doing that :) [21:33] i'm fairly new to python and all, so it will take me a bit heh [21:33] it's fun though [21:36] and it will be lots of fun even after you become a python guru. :) [21:39] salgado: hehe i hope so, so far i'm liking it a lot better than php [21:40] abentley, hi [21:40] Ursinha: [21:40] Ursinha: Hi. [21:41] abentley, I see you fixed bug 394800, but people reported bug 407347 [21:41] Bug #394800: Members of review team shown as (community) [21:41] Bug #407347: Failure detecting membership in the targeted review team - "(community)" label incorrectly showed [21:42] Ursinha: Yeah, I've looked at that briefly, but it doesn't make sense. It looks like some kind of fundamental flaw in the way we determine team membership. [21:43] rockstar, just saw the branch test run by in the windmill continuous integration suite - very nice work! [21:44] abentley, so bug 394800 wasn't actually fixed? [21:44] Bug #394800: Members of review team shown as (community) [21:44] mars, ? [21:44] Ursinha: Matter of interpretation. The rule is right now. The things it depends on don't behave properly. [21:45] rockstar, first time I've run the code windmill test suite :) [21:45] abentley, hm... right. could you triage the latter then, please? [21:52] cprov, hi [21:52] Ursinha: hi [21:53] cprov, hi, just saw bug 378178 [21:53] Bug #378178: Lauchpad tells me: "There is no package in Debian named "pidgin-plugin-pack". If it should be here, report this as a bug." - Though there is one! [21:53] is that some kind of data corruption? [21:54] Seeing as I have never used postgresql, is there a cli tool such as mysql that i can use to browse the db? [21:54] nvm, found the answer myself [21:54] postgresql-client :) [21:55] Ursinha: well, this package exists in debian -> https://edge.launchpad.net/debian/+source/purple-plugin-pack [21:56] mars, sorry, I guess I'm confused what I did that was out of the ordinary. [21:56] I just thought the popup dialogs looked nice - I like inline editing [21:57] the Bugs and Registry teams are doing great work too [22:01] Ah, so what you're saying is that you've never noticed my hard work before? :) [22:01] I have, but I haven't used all of the features yet [22:01] running the full suite lets you see everything on the site in one go [22:02] there are quite a few JS interactions now! [22:02] really impressive [22:03] mars, yeah, I'm trying to get some more through right now. Could you possibly do a code review for me? [22:03] rockstar, I would, but I really want to finish as much of the continuous integration as possible before going on leave [22:05] mars, alright. [22:06] cprov, it seems the user is trying to open a bug to pidgin-plugin-pack, what isn't a valid package, it seems [22:06] Ursinha: that's not what the form tells me. [22:07] Ursinha: but that's probably because he has already filled an empty Debian task :( [22:08] Ursinha: anyway, someone from the bugs team can provide you a better feedback, I'm not familiar with the code involved in this form. === matsubara is now known as matsubara-afk [22:14] sinzui: is there an existing template converted to main_side? yui-g and yui-u aren't working as expected. [22:15] EdwinGrubbs: no [22:15] I have one that works, [22:18] EdwinGrubbs: This is a draft of a template that does layout correctly with the classes: https://pastebin.canonical.com/20672/ [22:19] EdwinGrubbs: not that I have seen that "yui-u portlet" must be on the same div to work...and this is a problem with using the first because the portlet should demand to be first. [22:33] sinzui: so you have to use two-column-list with
elements? Is there a wiki page? I was looking at your email from last week. [22:57] hello, I have downloaded and installed the llaunchpad source code in a ubuntu 8.04 vm on a ubuntu 9.04 host. I want to view the web pages in a web browser on the host, how can I forward everything from the vm to the host so it would work? [22:58] EdwinGrubbs: yes, you do to get some presentations to work...namely term and value. [23:11] sinzui: is there a wiki page? [23:12] No [23:12] The rules changed a few hours ago. [23:13] EdwinGrubbs: I will right a wiki page now that I think I know enough rules to give guidance [23:14] EdwinGrubbs: For example. I think we will have *more* NavigationMenus instead of ripping them out because they are needed for a lot of pages