[12:05] <ddaa> hello lifeless
[12:05] <ddaa> lifeless: I have a good news for you
[12:05] <sabdfl> ddaa: share!
[12:05] <ddaa> lifeless: I do not have anything VCS related to ask you about before going to bed today ;)
[12:06] <ddaa> sabdfl: just teasing rob :)
[12:07] <sabdfl> awwww :-/
[12:07] <sabdfl> the branch stuff is looking good
[12:07] <sabdfl> can you get kinnison and celso to show you the lp build control system during the distro sprint?
[12:07] <sabdfl> i'd like to blow away buildbot and make it all native
[12:07] <ddaa> thank you, I played a bit with the allbranches listing this afternoon and noticed there are quite a few non-import branches there
[12:08] <ddaa> maybe we could use an green/orange/red light icon to quickly see which branches are bogus or broken (according to the branch puller)
[12:09] <ddaa> sabdfl: you do not have to push me for that
[12:09] <ddaa> SteveA is arranging for me to meet Kinnison and celso on sunday June 25th.
[12:09] <sabdfl> we need to make that listing a touch more compact
[12:10] <sabdfl> ok cool
[12:10] <ddaa> We'll look for overlap between buildbot-ng and buildd-ng
[12:11] <sabdfl> right
[12:11] <ddaa> I think the listing is nice
[12:11] <ddaa> any more compact would be hard to read
[12:12] <ddaa> maybe it should exclude the vcs-imports branches
[12:13] <ddaa> sabdfl: btw, it would be nice to be able to delete some branches sometimes
[12:13] <ddaa> https://launchpad.net/people/vos-team/+branch/vos/main
[12:16] <lifeless> bradb: what do you think of the idea in bug 43893
[12:16] <Ubugtu> Malone bug 43893 in launchpad "Should be able to link to a wiki page with bug filing guidelines per source package." [Wishlist,Unconfirmed]  http://launchpad.net/bugs/43893
[12:18] <sabdfl> +1 but only medium priority (and you want a spec not a bug), lifeless
[12:21] <lifeless> sabdfl: yes, going to do a spec too
[12:21] <lifeless> sabdfl: was in the middle of a meeting - wanted a real fast 'write it down now'
[12:24] <lifeless> night ddaa 
[12:29] <sabdfl> lifeless: one paragraph braindump and register it in the spec tracker, hmmk?
[12:29] <lifeless> sabdfl: just done that :)
[12:29] <lifeless> https://launchpad.net/products/launchpad/+spec/custom-bug-filing-instructions
[12:31] <sabdfl> v cool idea that
[12:31] <sabdfl> could even make them aggregate
[12:32] <lifeless> thanks :)
[12:32] <sabdfl> when filing on a package in ubuntu, show the custom message for ubuntu AND for that package-in-ubuntu
[12:32] <sabdfl> or product and project
[12:32] <lifeless> yes, that sounds nice
[12:32] <sabdfl> so Gnome can have one set of "this is how we do it" links, and GnomeBaker another
[12:32] <sabdfl> so, two paragraphs then
[12:33] <lifeless> on a conf call right now, will add that to the summary in a bit
[12:35] <sivang> lifeless: some packages have those instructions (noteably, GNOME) in the package itself. not sure if they follow a naming convention, if we got them to , LP could automatically extract this info from the source :)
[01:02] <lifeless> sivang: I'm inclined to walk before running here
[01:03] <lifeless> sivang: this isn't something that changes radically all the time, so providing a manual means to document it will improve the process immediately.
[01:03] <sivang> lifeless: 100%, was just a wild thought ;)
[01:42] <lalo> hey, quickie.  I registered a project; but the products I was thinking about are already auto-registered by vcs-import.  What's the procedure for requesting these to be transferred to the project?  I want to encourage the other upstream devs to use launchpad
[01:42] <lalo> or more generally... what's the procedure for admin requests?  Do I file a bug?  :-)
[01:53] <sivang> lalo: is it plone btw? :)
[01:53] <lalo> no, crossfire
[01:54] <lalo> I don't really contribute to plone anymore.  Or even use it.  But I haven't gained a new freenode cloak yet, so until some plone admin remembers to remove mine, I guess I'm keeping it :-P
[01:55] <lalo> it seems freenode has a bigger admin overhead for removing a cloak than for adding one
[01:55] <sivang> lalo: lol
[01:57] <sivang> lalo: crossfire as in online multi player game?
[01:57] <lalo> yes
[02:00] <sivang> lalo: anywas, you need one of the admins to do that for you, or you could probably open a bug about it and assign it to the registry admins, wait I'm trying to find you the team's name in LP.
[02:00] <lalo> crossfire :-P
[02:00] <lalo> both team and project are named crossfire
[02:00] <lalo> there are three products, crossfire, crossfire-client and crossfire-maps
[02:01] <lalo> there's a fourth, but this one wasn't registered yet, so I just registered it manually with the right ownership
[02:02] <sivang> lalo: this is team you need to assign the bug to, https://launchpad.net/people/registry
[02:02] <lalo> ok
[02:03] <lalo> ah, you meant the registry team, I thought you were referring to "my" team :-)
[02:03] <lalo> I open a bug on... where?  the launchpad product?
[02:04] <sivang> lalo: on the one you want to be merged in to the other
[02:04] <lalo> ok
[02:04] <sivang> lalo: and ask in the bug for it to be merged
[02:04] <lalo> not merged, just change ownership
[02:04] <sivang> lalo: sure, sorry, I am doing some other things in parallel ;-)
[02:05] <lalo> sigh
[02:05] <sivang> lalo: so change ownership of the one to be managed with the ownership of the auto imported one, then?
[02:05] <lalo> "       Crossfire does not use Malone as its bug tracker."
[02:06] <sivang> lalo: care to toss me the url?
[02:06] <lalo> ah, the product name is actually crossfire-server rather than crossfire
[02:06] <lalo> https://launchpad.net/products/crossfire-server
[02:09] <sivang> lalo: see if you can get this page https://launchpad.net/products/hubackup/+launchpad
[02:09] <sivang> lalo: for your product
[02:09] <sivang> lalo: then you can indicate of you guys are using rosetta and/or malone officically
[02:09] <sivang> lalo: then it will get updated IIRC
[02:10] <lalo> no :-) "Not allowed here"
[02:10] <lalo> obviously, only a maintainer can change launchpad usage
[02:11] <sivang> lalo: well, either the registrant of the product or, maintainer as named it , yes.
[02:11] <lalo> yeah.  And the registrant and maintainer are both the registry team :-)
[02:12] <sivang> lalo: okay, so then we go back to the bug report assigned to them :)
[02:12] <lalo> yes :-)
[02:12] <sivang> anyway, it's bedtime here for several hours already. night all.
[02:13] <lalo> I'll file it on launchpad
[02:14] <sivang> lalo: sub the registry team nonetheless, even if not assigning directly to them.
[02:15] <lalo> yes
[02:15] <lalo> I'll do either... if lp allows me to :-)
[02:15] <lalo> if not I'll just bug ddaa personally on irc, later :-P
[02:16] <sivang> lalo: it should :) night.
[02:18] <lalo> night
[02:18] <lalo> hmm, actually, looking at the list of support tickets for lp, it seems there _is_ a procedure for that after all... just file a support ticket at lp
[02:46] <hypatia> Hey launchpad folk (if any of you are awake).
[02:46] <hypatia> News from spiv: he's been excused from jury duty for the long (10 week) trial. He is going up for selection for a short trial.
[02:47] <hypatia> So even if he gets selected, he will be off for max 2 weeks.
[02:54] <sivang> hypatia: jury duty is in .AU as well? :)
[02:54] <hypatia> Yes, we have trial by jury.
[02:54] <sivang> cool :)
[02:55] <hypatia> spiv was summoned for a trial and we were very worried about it because it was meant to be 10 weeks long.
[02:55] <hypatia> But apparently he has been allowed to move to selection for a shorter trial.
[02:56] <sivang> good to know
[03:17] <sabdfl> morning mpt__
[03:17] <sabdfl> hypatia: that's good news. spiv will be a good juror
[03:18] <hypatia> sabdfl: He hasn't made it to that stage yet, he's still at selection. I don't mind him being a good juror as long as it's not 10 weeks!
[03:19] <sabdfl> hypatia: agreed :-)
[03:19] <sabdfl> night all
[04:40] <lifeless> good news
[04:40] <lifeless> spiv got a get out free card
[04:41] <stub> Too many people turned up, or they decided he was an unreliable juror?
[04:41] <lifeless> not sure
[04:41] <stub> I told him that claiming to be pregnant would work
[04:44] <jbailey> 0.8 uploaded to DApper
[04:46] <mpt> Must have been the ponytail
[04:46] <stub> jamesh, lifeless: Can I get a trivial review? https://chinstrap.ubuntu.com/~dsilvers/paste/filetLjlVl.html
[04:49] <lifeless> if team.id == self.id: - is 'team is self' or 'team == self' equivalent ? they would be clearer I think
[04:51] <lifeless> do we have a consensus on the abuse of class attributes to provide defaults ?
[04:51] <lifeless> +    # XXX: This cache should no longer be needed once CrowdControl lands,
[04:51] <lifeless> +    # as apparently it will also cache this information.
[04:51] <lifeless> +    _inTeam_cache = None
[04:51] <lifeless> +
[04:51] <lifeless> that really should in in __init__ imo
[04:51] <jamesh> stub: for correctness, would you need to clear entries from the cache in _cleanTeamParticipation()?
[04:52] <stub> I couldn't remember if SQLObject instances had standard __init__ methods you can mess with
[04:52] <jamesh> or maybe _removeParticipationFromTeamAndSuperTeams() would be the place to do it
[04:53] <stub> Where is this _cleanTeamParticipation?
[04:55] <stub> Ahh... I see.
[04:56] <stub> That will not be necessary - TeamParticipation is only messed with by the Person instances, so we can keep it nicely encapsulated and clear the caches in the same class that populates it.
[04:57] <stub> Clearing the cache is likely not even necessary - I just did it to guarantee no tests would break.
[05:01] <jbailey> mpool: I've sent the email.
[05:01] <jbailey> mpool: If there's more you want to add in, that would be lovely.
[05:02] <jamesh> stub: don't we call TeamMembership.setStatus() in the team management pages?
[05:02] <jbailey> Whups, ECHAN
[05:02] <jamesh> and changing the membership status can result in TeamParticipation records being deleted
[05:03] <dilys> Merge to devel/launchpad/: [trivial]  forgot to bzr add the pagetest for bug 39011 (Add distro packaging form needs input validation) (r3544: Diogo Matsubara)
[05:03] <Ubugtu> Malone bug 39011 in launchpad "Add distro packaging form needs input validation" [Major,Fix committed]  http://launchpad.net/bugs/39011
[05:07] <stub> jamesh: The worst that can happen in that case is an admin remains a member of a team that they just removed themselves from for the remainder of the transaction.
[05:07] <stub> I might clear it there too for laughs anyway though.
[05:08] <jamesh> stub: so inTeam is only used for auth checks against the current user?
[05:08] <stub> we only ever do auth checks for the current user
[05:09] <jamesh> but is inTeam() used for things other than auth checks?
[05:09] <stub> Nope
[05:10] <stub> We ask teams for lists of members, which is different (and not cached)
[05:10] <stub> But don't ask random people if they are members of particular teams
[05:10] <stub> I've added the clear at that point anyway, and a test too now I've realized I can test this a bit.
[05:11] <jamesh> fair enough
[05:11] <stub> Bah - need to unwrap the person to poke at their internals :-(
[05:12] <jamesh> or get participation.person
[05:12] <jamesh> which won't be security wrapped
[05:15] <stub> jamesh: https://chinstrap.ubuntu.com/~dsilvers/paste/fileqn1eli.html
[05:20] <jamesh> stub: looks good
[05:20] <stub> r=jamesh ?
[05:21] <jamesh> yeah
[05:28] <lifeless> stub: I'd still prefer the _inTeam_cache be declared in __init__
[05:29] <stub> Do we have other code overriding SQLObject __init__ methods?
[05:29] <lifeless> ah, if we dont then thats fine as is
[05:29] <lifeless> I'll discuss it with spiv as a general issue later
[05:31] <stub> We don't seem to have any - I'm not sure if it can be done or if it involves magic.
[06:38] <mpt> jamesh, got five minutes spare to answer some silly questions of mine?
[06:38] <jamesh> sure
[06:39] <mpt> jamesh, I'm trying to run a CGI on localhost, to test the new menus stuff
[06:39] <mpt> and I thought oh, that'll be easy, I have Apache installed already for LP development
[06:39] <mpt> then I discovered that I didn't
[06:40] <mpt> and nor do I appear to have Zope installed
[06:40] <jamesh> "sudo aptitude install apache2" should give you a basic apache install to play with
[06:41] <mpt> and launchpad-dependencies' dependencies don't include anything that looks like a server
[06:41] <jamesh> I don't really know much about getting Zope running outside of the LP tree
[06:41] <mpt> so, I'm missing one or two obvious things
[06:41] <jamesh> the server you start when you do "make run" in your LP tree is a Python web server
[06:42] <mpt> ahhh, and Zope doesn't show up as being installed because it's just part of the Launchpad codebase?
[06:42] <jamesh> yep
[06:43] <mpt> ok, thanks
[07:20] <stub> Weee.... new bzr
[07:55] <robitaille> what's the best way to request a comment to be removed from a Malone bug report?  The last comment in bug 34490 is some sort of spam
[07:55] <Ubugtu> Malone bug 34490 in imagezoom "Postinst and postrm fail to complete leaving dpkg in a broken state" [Major,Confirmed]  http://launchpad.net/bugs/34490
[08:00] <jamesh> robitaille: we don't have a mechanism to remove comments
[08:01] <robitaille> jamesh:  so we stuck with that junk comment forever?
[08:02] <jamesh> I guess so
[08:34] <stub> robitaille: We will get the feature at some point
[08:34] <stub> robitaille: They can be removed - I just have to do it manually
[08:35] <robitaille> stub: ok.  thanks
[09:27] <carlos> morning
[09:53] <mpt> SteveA, ping
[09:55] <carlos> lifeless: latest bzr from dapper removes bzrtools, is that normal?
[09:56] <SteveA> mpt: on phone...
[09:58] <lifeless> carlos: just means bzrtools wasn't uploaded at the same time
[09:58] <carlos> ok
[10:10] <SteveA> mpt: ping
[10:11] <SteveA> lifeless: what do i need to do to get "tickcounter" into sourcecode? 
[10:11] <lifeless> SteveA: put it in a bzr branch
[10:11] <lifeless> give it a Makefile with a 'build' and 'check' target
[10:11] <lifeless> they can be stubs if there is nothing to do 
[10:11] <lifeless> email me
[10:12] <SteveA> ok, cool
[10:12] <SteveA> thanks
[10:17] <mpt> lifeless, how do I get apache2 to treat a CGI as a CGI?
[10:17] <jamesh> SteveA: given the "make clean" problems with pygettextpo, it might be worth putting the extension module in a package
[10:18] <lifeless> mpt: script-alias usually
[10:18] <jamesh> SteveA: so that "make clean" in the sourcecode directory doesn't result in a dangling symlink in lib/
[10:18] <mpt> lifeless, /etc/apache2/sites-available/default has "+ExecCGI" for a parent directory of the directory containing the .cgi
[10:18] <mpt> but it still gets treated as plain text
[10:18] <SteveA> jamesh: you mean in a subdirectory with an __init__.py ?
[10:18] <jamesh> SteveA: yeah
[10:18] <SteveA> jamesh: ok
[10:18] <lifeless> SteveA: better yet, if its going to be mostly static an unchanging, put it in a deb, open source it, and stash it in ubuntu
[10:19] <SteveA> lifeless: yes, that would be nice.  however, i am not going to do that
[10:19] <SteveA> i'm am quite happy for someone else to do so
[10:19] <jamesh> SteveA: you can probably steal the Makefile from pygpgme almost unchanged too
[10:19] <SteveA> my only goal is to have this available for QA work on launchpad
[10:20] <lifeless> SteveA: if thats a preferrable option, we can package it up quickly.
[10:20] <SteveA> lifeless or jamesh: are either of you interested in packaging it?
[10:21] <lifeless> happy to do so, packaging a python module is quite easy :)
[10:21] <SteveA> in the next day or two?
[10:21] <jamesh> I haven't gotten round to learning debian packaging yet
[10:21] <sivang> re all
[10:21] <jamesh> I probably should at some point
[10:21] <lifeless> SteveA: I could do it tomorrow I think
[10:22] <SteveA> lifeless: okay.  thanks.  i'll make changes from jamesh's code review today, and put a bzr branch up somewhere and mail you
[10:23] <lifeless> mpt: I'm not sure that a bug reporting template matches what I am proposing
[10:23] <lifeless> mpt: see the spec https://launchpad.net/products/launchpad/+spec/custom-bug-filing-instructions for an expanded summary
[10:25] <jamesh> mpt: try creating a file /etc/apache2/conf.d/dotcgi containing the line "AddHandler cgi-script .cgi"
[10:25] <jamesh> mpt: restarting apache afterwards
[10:30] <SteveA> mpt: i'd like to have that skype call now.  i have other things to do in 30 mins.
[10:37] <Znarl> We are preforming network testing in the data centre for the next hour.  This may result in a small amount of connectivity problems to the data centre.
[11:07] <Znarl> Network testing has finished.  
[11:07] <lifeless> mpt: ping
[11:09] <mpt> lifeless, pong
[11:09] <lifeless> 18:23 < lifeless> mpt: I'm not sure that a bug reporting template matches what I am proposing
[11:09] <lifeless> 18:23 < lifeless> mpt: see the spec https://launchpad.net/products/launchpad/+spec/custom-bug-filing-instructions for an expanded summary
[11:10] <lifeless> I think you've inappropriately turned my bug into a duplicate
[11:10] <lifeless> they are certainly related.
[11:10] <lifeless> but I disagree about being the same.
[11:10] <mpt> lifeless, that pretty much matches what I thought the original was about
[11:11] <mpt> hmmm
[11:11] <mpt> though the cascading is a bit more complicated
[11:11] <lifeless> the way I read the template concept its about giving a customised malone input screen
[11:11] <lifeless> with things to tab between, space to attach multiple files etc
[11:12] <mpt> They're the same underlying problem, right?
[11:12] <mpt> I mean, we wouldn't have the template solution and the custom instructions solution simultaneously
[11:12] <lifeless> what I'm talking about is much lower tech, its about bringing in documentation from the project's web page, as a link. And the cascade *may* be cuteness, or may be essential, dont know yet.
[11:13] <lifeless> for instance, you might want the user to *read* the documentation, *then* follow a guided input form.
[11:13] <lifeless> the guided input form is what I think your templates are about
[11:14] <mpt> ok
[11:14] <lifeless> does this make sense? Do you agree they are separate things? Or should I leave it as a dup ?
[11:15] <mpt> I'm just un-dupping them
[11:15] <lifeless> thanks
[11:15] <mpt> and I'll move the paragraph I added to 3383 to 43893 instead
[11:16] <mpt> I like the idea of including product-/package-/prorject-/distro-specific instructions
[11:17] <mpt> but I think linking to an external page would be a waste of time - people won't read it
[11:22] <SteveA> mpt: you're back!
[11:22] <mpt> SteveA, yes, had to reset the router, then send my mail to guido
[11:40] <BjornT> SteveA, stub: re bug 39393, it seems to fail since we import * from zope.app.testing.functional in canonical.functional. what's the reason for importing * instead of importing everything we need explicitly?
[11:40] <Ubugtu> Malone bug 39393 in launchpad "Import fascist disabled" [Normal,Unconfirmed]  http://launchpad.net/bugs/39393
[12:13] <sabdfl> SteveA: call?
[12:14] <sabdfl> 1pm today?
[12:14] <SteveA> sabdfl: i've got a call scheduled with you for 1h45 from now
[12:14] <SteveA> conf call with kiko
[12:14] <sabdfl> ok great
[12:15] <aa_> hi :)
[12:15] <aa_> is the email interface the only remote procedural way I can do bug reports to launchpad?
[12:15] <aa_> I have just moved from trac, and I need to update my applications bug reporting tool
[12:15] <SteveA> aa_: hello
[12:16] <SteveA> right now, yes
[12:16] <SteveA> we'll be doing an xmlrpc interface in the near future
[12:16] <aa_> I love Malone, by the way. I was actually writing my own tracker, until I found it
[12:16] <SteveA> but it won't be ready for a little while
[12:16] <SteveA> cool, thanks for the feedback
[12:16] <aa_> need a hand? or all in-house stuff?
[12:16] <SteveA> please do file bugs on malone when you find things you'd like to be improved
[12:17] <SteveA> it's in-house, although if you want to be involved in writing clients for it, we should talk sometime
[12:17] <aa_> ok, will do, I would love it to have a wiki, not in Malone per se, but as part of the launchpad mega-app
[12:17] <SteveA> yeah, me too
[12:17] <SteveA> sorry -- got a phone call to have now
[12:17] <aa_> SteveA: I have to write a client for it before y next release, I have no choice :)
[12:17] <aa_> ok, thanks for helps
[12:21] <aa_> oh woo, I guess would it be allowed if I wrote a script that accepts http POST requests and files them as bugs by email?
[12:21] <aa_> I just can't force my users to register a GPG key with launchpad
[12:42] <SteveA> aa_: what do you want to do?
[12:42] <SteveA> are you talking about importing your data into launchpad?
[12:46] <dilys> Merge to devel/launchpad/: [r=SteveA]  Fix bug 36866 (Searching for bugs after selecting a certain status from the Right-Hand-Menu resets the search) (r3545: Brad Bollenbach)
[12:46] <Ubugtu> Malone bug 36866 in malone "Searching for bugs after selecting a certain status from the Right-Hand-Menu resets the search" [Major,In progress]  http://launchpad.net/bugs/36866
[12:53] <fabbione> hey guys
[12:53] <fabbione> SteveA: this is for you too :)
[12:53] <fabbione> so i am trying to get an idea on how many bugs our X has
[12:53] <fabbione> and this is getting kind of hard
[12:53] <fabbione> the "Package Reports" has no summary
[12:54] <fabbione> the "Subscribed" includes packages that are not X related
[12:54] <fabbione> there is no way to exclude bugs that have been fixed in Ubuntu or do not apply to ubuntu (like the ones imported from Debian)
[12:55] <fabbione> i will pretty much like to have an idea of what is the status of what i maintain
[12:56] <fabbione> what can i do other than start summing up manually the numbers from "Package Reports"?
[12:56] <SteveA> hi fabbione 
[12:57] <SteveA> so, i want to know a bit more about X
[12:57] <SteveA> i guess there are several X packages
[12:57] <fabbione> SteveA: tons yes
[12:57] <SteveA> and you want to know about them as a group, all together
[12:57] <SteveA> is this what you're asking about?
[12:57] <SteveA> (at least in part)
[12:58] <fabbione> i am team foo and i maintain N pkgs.. 
[12:58] <fabbione> i want to know how many bugs i have in total
[12:58] <fabbione> i can see the summary per package already
[12:58] <SteveA> okay, so i can see all the X related packages, because one particular team is the maintainer for just these packages
[12:59] <SteveA> (sorry that i'm being slow.  i don't have much experience in exactly how the distro team use malone at this level)
[01:00] <fabbione> SteveA: no problem..
[01:00] <fabbione> https://launchpad.net/people/ubuntu-x-swat/+packagebugs
[01:00] <fabbione> here
[01:00] <fabbione> this is the page i am talking about
[01:00] <fabbione> this page only shows ubuntu bugs
[01:00] <fabbione> but no summary
[01:00] <fabbione> so i can't say for example that in warty i had 150 bugs and in dapper with have 250
[01:01] <fabbione> because there is no summary
[01:01] <fabbione> so i can't track the progress
[01:01] <SteveA> are you asking for a summary for each table column?
[01:01] <fabbione> yes
[01:02] <fabbione> but how can i do it on they fly now without waiting a rollout in 3 months?
[01:03] <SteveA> if you want the sum of the numbers for each table column on that page, that's easy to do
[01:03] <SteveA> and i can get that into production quite fast
[01:04] <fabbione> ok thanks
[01:04] <SteveA> anything other than adding that "totals" row?
[01:05] <fabbione> well i would like to be able to exclude bugs in other distros from the advanced search
[01:06] <SteveA> fabbione: for advanced bug search, talk with kiko/brad later today
[01:06] <fabbione> SteveA: i won't be around later.. do you think you can proxy my request?
[01:06] <fabbione> it's my wife bday
[01:06] <fabbione> and i will be dragged all over
[01:06] <SteveA> i'll pass on what you just said
[01:07] <fabbione> thanks
[01:07] <fabbione> i don't mind if you copy/paste from here...
[01:07] <SteveA> but i also need to know
[01:07] <fabbione> or whatever
[01:07] <SteveA> what is the reason this feature is important to you right now?
[01:08] <SteveA> you explained why you need the "totals" part on the package bugs page
[01:08] <fabbione> because i know for a fact that i had ~100 bugs in X warty, 150 in hoary and 200 in breezy
[01:08] <fabbione> i want to know how the progression goes
[01:09] <fabbione> compared to our approx user base
[01:09] <SteveA> so, are you talking about wanting to select not just the distro but the distrorelease
[01:09] <fabbione> that gives me an idea if we are doing bad or good
[01:09] <SteveA> in the advanced search form?
[01:09] <fabbione> no no.. this is just for the totals
[01:09] <fabbione> i can keep track manually of that number
[01:09] <fabbione> for the advanced search it's enough i can filter by distro
[01:09] <fabbione> because when i go bug hunting i don't care to see baltix or Debian problems
[01:10] <fabbione> i want to see what affects ubuntu only
[01:10] <SteveA> i see
[01:10] <SteveA> okay, that's clear
[01:10] <SteveA> i'll talk with kiko later
[01:10] <fabbione> when i open the bug then i can see if it affects debian or baltix too
[01:10] <fabbione> for example
[01:10] <SteveA> yep
[01:10] <fabbione> thanks SteveA 
[01:10] <SteveA> enjoy the bday
[01:19] <aa_> oh shoot
[01:19] <aa_> SteveA: I want to submit bug reports to malone over http
[01:19] <aa_> more importantly, anonymous bug reports I guess
[01:22] <lifeless> aa_: what differentiates anonymous bug reports from spam ?
[01:23] <aa_> well, the plan is to send the annonymous ones to me, and I would sign them and send them as email
[01:23] <aa_> and well, maybe a spammer would work out the weird rpc I use, but I doubt they would bother
[01:24] <aa_> I don't get it, do spammers often submit bug reports?
[01:24] <aa_> I have seen wiki pages mutilated, but bug reports?
[01:25] <lifeless> debian had huge bug spam problems
[01:25] <lifeless> before it got its cross assassin etc shit all together
[01:25] <aa_> so um, basically providing a way for my users to submit anonymous bug reports is um utterly no no
[01:26] <lifeless> well
[01:26] <lifeless> its something that should be done with due care and caution
[01:26] <lifeless> who are your users ?
[01:27] <aa_> a gui application
[01:27] <aa_> um, developers I guess, it is an IDE
[01:27] <lifeless> do you think they are unlikely to create accounts on launchpad ?
[01:27] <lifeless> developers seem clueful enough to do it to me
[01:27] <aa_> not at all, I am actually sure most would
[01:28] <lifeless> so why do you need anonymous bug reports ?
[01:28] <aa_> but it is the few that wouldn't even know what it all was
[01:28] <aa_> if anythiong, those are the ones who need it most
[01:28] <aa_> but yes, you are right
[01:33] <aa_> unfortunately, the issue blocks my next release. Would it be reasonable to submit a bug against launchpad so that there can be some discussion about anonymous reports, or has it already been discussed?
[01:33] <lifeless> it has come up a lot
[01:33] <lifeless> I'm not sure if there is an informational spec about it or not
[01:34] <aa_> I will, just get them sent to myself
[01:34] <aa_> and then pass them on to launchpad after ensuing they are not spam
[01:34] <aa_> yeah, I suspected it had been discussed a lot :)
[01:36] <aa_> in an ideal world, I would make users have a gpgp key etc and email them in, but well, that ain't ever going to happen
[01:36] <`6og> hi sivang
[01:37] <aa_> that would save the whole "save password" stuff
[01:45] <sivang> hey kgoetz :) what's up?
[01:46] <kgoetz> :) just going through my bug email, and trying to get stuff done so i can start learning python and c (again...)
[01:47] <kgoetz> sivang: what's been happening mate?
[01:48] <sivang> aa_: I'd say you better try and educate them to open accounts on LP, might be more worthwhile then setting up all this juggelry. You could attached documentation inside your IDE for how to do so. /me notes this could be a good use for a client app style GNOME launchpad. (proposed as SoC project)
[01:48] <kgoetz> i just looked for my external usb hdd to test an hubackup bug (or comment on). cant find the bugger :S
[01:49] <sivang> kgoetz: let's take this to #u-devel okay?
[01:49] <kgoetz> sivang: sure
[01:49] <sivang> kgoetz: other then that everything's fine, but reports continue to flow in :)
[01:49] <aa_> sivang: right, I wish I was a student, and I only have a few days to write it, not all summer, but yes it will be a pygtk launchpad client of sorts
[01:50] <sivang> aa_: There's a proposal for that sort of app, we'll see how to progresses :)
[01:50] <aa_> oh excellent, you don't happen to have a url do you please?
[01:51] <aa_> one of my developers was wanting to do this, he is a student, and well, he actually wanted to write a front-end for all bug trackers, but he might be interested in this
[01:55] <cprov> good morning, hackers
[01:57] <sivang> aa_: lemme see if I can find it
[01:58] <sivang> aa_: actually, application were already due.
[01:58] <ploum> hello
[01:58] <ploum> sivang: are you a MOTU today ?
[01:58] <sivang> aa_: https://wiki.ubuntu.com/GoogleSoC2006#head-c63d73c3e2785fdb9f52077630b50dcac426b2ad
[01:59] <sivang> ploum: I am :-)
[01:59] <ploum> cool :-)
[01:59] <ploum> congratulations
[01:59] <ploum> I just see you were talking about a Gnome frontend to launchpad
[02:00] <ploum> any news from the SoC about this ?
[02:01] <salgado> stub, around?
[02:01] <sivang> ploum: let's continue on -motu
[02:10] <aa_> sivang: any idea how they were planning on doing "It must have an automated launchpad account registration.
[02:14] <sivang> aa_: no idea, this is still in the idea phase IMHO.
[02:14] <aa_> oh, fair enough
[02:15] <aa_> would be nice if it was more generic, that could be used in other applications other than ubuntu
[02:15] <aa_> and someone has drafted a proposal, he says he needs a mentor
[02:15] <aa_> https://launchpad.net/distros/ubuntu/+spec/smart-bugreporting-tool
[02:17] <aa_> oh well, meeting time. Thanks for the helps
[02:17] <sivang> aa_: np, apologies for not being to help furhter.
[02:18] <aa_> never hire an open source programmer, he hacks on his own stuff in lunch! muahah
[02:24] <sivang> aa_: you just need to make his stuff your stuff, and you're set :)
[02:29] <sabdfl> SteveA, kiko-zzz: now ok?
[02:29] <lifeless> night all
[02:29] <sabdfl> night lifeless
[02:29] <SteveA> sabdfl: sure.  i'll dial in
[02:30] <SteveA> kiko will be here shortly
[02:33] <matsubara> carlos: ping
[02:33] <carlos> matsubara: pong
[02:33] <matsubara> carlos: have you seen OOPS-129D14?
[02:33] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/129D14
[02:35] <carlos> sure
[02:35] <matsubara> carlos: is there a bug open on it?
[02:37] <carlos> matsubara: the bug there is that we are not showing a 404 error, you know that, right?
[02:37] <carlos> and no, I don't think we have a bug for it
[02:37] <matsubara> carlos: right, I'll report it then.
[02:38] <carlos> matsubara: ok, thanks
[02:38] <matsubara> carlos: assign it to you?
[02:38] <carlos> matsubara: yes, please
[04:17] <kiko-zzz> hello hello
[04:26] <SteveA> kiko: i have two feature requests from fabionne i said i'd mention to you
[04:26] <kiko> oh?
[04:26] <SteveA> 1. https://launchpad.net/people/ubuntu-x-swat/+packagebugs
[04:27] <SteveA> he'd like totals for each column added to that page
[04:27] <kiko> okay
[04:27] <SteveA> so he can see how many bugs that team has open on ubuntu altogether
[04:27] <SteveA> 2. he wants to be able to find bugs that have ubuntu bugtasks from the advanced search page
[04:28] <SteveA> because right now, he is concerned only with ubuntu bugs
[04:28] <SteveA> not bugs with upstream or other distro tasks
[04:28] <kiko> I am confused by request #2
 for the advanced search it's enough i can filter by distro
 because when i go bug hunting i don't care to see baltix or Debian problems
 i want to see what affects ubuntu only
[04:28] <kiko> that's what /distros/ubuntu/+bugs is
[04:29] <kiko> I don't quite see... oh
[04:29] <kiko> is he talking about the +packagebugs assigned view?
 well i would like to be able to exclude bugs in other distros from the advanced search
[04:29] <SteveA> 
[04:30] <kiko> well /which/ advanced search?
[04:30] <SteveA> you'll have to ask the padrino
[04:30] <SteveA> he's away this afternoon though
[04:30] <kiko> heh
[04:30] <kiko> ok
[04:31] <SteveA> btw, http://en.wikipedia.org/wiki/Tuva_or_Bust
[05:01] <kiko> heh
[05:15] <kiko> uhm
[05:15] <kiko> carlos?
[05:15] <carlos> kiko: yes?
[05:16] <kiko> carlos, should we go over the rosetta import statistics for a bit?
[05:16] <kiko> how are they looking?
[05:17] <carlos> well, is not a good moment atm, I'm finishing the extra testing for PoMsgSet that BjornT asked and I was planning to take a look to all missing entries, we could do it after my review
[05:17] <kiko> that's great.
[05:17] <kiko> okay.
[05:27] <aa_> surely not async kiko!
[05:27] <kiko> aa_, the one and only!
[05:28] <aa_> heh, I am ali, a kiwi user :)
[05:28] <kiko> well I knew that already :)
[05:28] <aa_> :P
[05:29] <aa_> kiko: you guys wrote launchpad?
[05:29] <aa_> oh ignbore me I am on crack
[05:29] <kiko> well, we work on part of it.
[05:30] <aa_> nice one, I just discovered it, but am desperate to get a gtk reporting tool going
[05:31] <kiko> tell me about your problems
[05:31] <aa_> well, it all started when I was a child...
[05:31] <aa_> maybe even before then
[05:32] <kiko> let's fast-forward a bit
[05:32] <aa_> ok ok, well I can't decide whether to use email or https or wait for the XMLRPC
[05:32] <aa_> strikes me all have pros and cons
[05:32] <kiko> email is nice because it is store-and-forward
[05:32] <kiko> but it's async
[05:32] <kiko> https is very easy
[05:33] <aa_> and needs gpg signing
[05:33] <kiko> to file new bugs? mmmm
[05:33] <aa_> yeah
[05:33] <kiko> okay let me be quiet as I may just have gotten myself in trouble there :)
[05:33] <aa_> yikes, best not to do that
[05:33] <kiko> general XMLRPC is on its way; we could add a bug-filing API pretty easily
[05:34] <aa_> well SteveA mentioned it is on the cards
[05:34] <kiko> using https is in the short term effective and very easy
[05:34] <aa_> well, people still need a launchpad account
[05:34] <aa_> but yes I agree, https
[05:35] <aa_> and an excuse to learn how to programmatically sign emails
[05:36] <aa_> oh and https adds a dependency
[05:37] <aa_> and signup still needs email
[05:38] <kiko> aa_, a dependency? httplib?
[05:39] <aa_> pyopenssl
[05:39] <aa_> I am just guessing
[05:40] <aa_> (not a biggie, except I get mercilessly flamed by my users for each new dependency)
[05:40] <aa_> you should have seen the day I switched to Kiwi :P
[05:41] <aa_> zakame: ping?
[05:42] <kiko> aa_, no, urllib/httplib do https.
[05:42] <aa_> oh good one, thanks
[05:42] <aa_> zakame: I saw your proposal for the bug reporting client, I am interested in helping and discussing with you, please /msg me any time, thanks
[05:42] <kiko> >>> import urllib
[05:42] <kiko> >>> urllib.urlopen("https://launchpad.net")
[05:42] <kiko> <addinfourl at 806357432 whose fp = <httplib.SSLFile instance at 0x301009e0>>
[05:42] <kiko> aa_, enjoy
[05:43] <aa_> :) thanks
[05:45] <aa_> I *love* screen scraping
[05:45] <aa_> is there a sandbox pproject on launchpad that I can use for testing things?
[05:46] <ddaa> staging.launchpad.net
[05:46] <aa_> wow, thanks
[05:46] <kiko> you can use anything on staging, it's blown away nightly
[05:46] <ddaa> it runs the latest crack of the minute code too
[05:46] <aa_> mm, crack
[05:47] <aa_> so jsut to doubly reiterate, no one will mind me posting 100 bugs to staging
[05:47] <ddaa> absolutely not
[05:47] <ddaa> just be ready to do it again tomorrow
[05:48] <aa_> haha
[05:48] <lalo> kiko: thanks a lot
[06:02] <fabbione> kiko: one second and i will show you
[06:02] <kiko> fabbione, email or bugs would be better, I'm juggling like crazy
[06:02] <fabbione> kiko: ok
[06:11] <kiko> matsubara, in your analysis, if you can say "Existing bug" when it is existing it will help me somewhat
[06:11] <kiko> matsubara, as for the out of order sql queries, one idea might be looking at the server logs, considered that?
[06:12] <kiko> matsubara, at the server sql logs, more precisely
[06:14] <matsubara> kiko: where can I find they? There's no reported bug for the +bugs page yet.
[06:16] <carlos> BjornT: hi, around?
[06:17] <BjornT> hi carlos 
[06:17] <carlos> BjornT: I'm trying to write tests for the traversal code as you requested in your review
[06:18] <carlos> BjornT: but I don't know how to write doctests for it
[06:18] <carlos> I tried using a method that is not supported by my code ('PUT') and I don't get any error. Are the pagetests the only way to test the traversal code?
[06:19] <carlos> I guess that I don't get errors because the traversal code is not executed with getView()
[06:20] <carlos> zope.component.getView
[06:21] <kiko> matsubara, I think only stub can see them.
[06:21] <kiko> matsubara, what +bugs page?
[06:21] <BjornT> carlos: i was thinking that you should test it by manually creating an instance of the class, passing a IPOFile and a test request. then you'd call .traverse(name) manually and check what it returns.
[06:21] <carlos> ok, so that's the way to test it.
[06:21] <carlos> I was not sure if there was a better way to do it
[06:21] <kiko> matsubara, also, about the +bugs search timeout, I think stuart wrote an analysis on it to the launchpad list
[06:22] <carlos> BjornT: thanks
[06:22] <stub> matsubara, kiko: What do we need logged? Full logging isn't running on production at the moment.
[06:23] <kiko> stub, I'm trying to see if we can find a way to tackle the apparently-out-of-order queries we are seeing occasionally.
[06:24] <matsubara> kiko: he answered the email pointing to the bug. thanks stub.
[06:24] <kiko> yep
[06:47] <aa_> oh well, this isn't easy, or too easy
[06:48] <aa_> before I try everything under the sun, any ideas what the crucial part of the login procedure is?
[06:48] <aa_> I have got a cookie, and I have a form I am trying to send to,
[06:48] <aa_> oh I am making no sense!
[06:49] <aa_> maybe missing to send something on the login form, something like the submit buttons, do they get passed to the form handler?
[06:50] <aa_> oh that totally worked!
[07:00] <aa_> muahah https://staging.ubuntu.com/products/bzr/+bug/43906
[07:09] <carlos> aa_: congratulations ;-)
[07:09] <kiko> aa_, you can also use basic auth, ftr
[07:17] <Keybuk> random
[07:17] <Keybuk> would it be possible for a source package to have a "default" upstream?
[07:17] <Keybuk> so when you click on "+ Upstream" on the bug, it automatically fills in the product and Bug tracking system for you?
[07:17] <kiko> what does that mean?
[07:18] <Kinnison> Umm 'source package' is an ephemeral concept
[07:18] <kiko> oh
[07:18] <kiko> Keybuk, done via packaging, for instance?
[07:18] <Keybuk> for instance
[07:18] <Kinnison> that's an idea
[07:18] <kiko> yes, that'd be doable, we've discussed it before
[07:18] <Keybuk> Kinnison: only to Launchpad developers
[07:19] <Kinnison> Keybuk: true
[07:19] <Keybuk> should I file a wishlist somewhere for that?  where?
[07:19] <Kinnison> probably against the launchpad product since it's a concept which would be used all over the place
[07:27] <kiko> Keybuk, it's actually malone, I think
[07:28] <Keybuk> bug 44052
[07:29] <Ubugtu> Malone bug 44052 in launchpad "Default upstream bug reporting details" [Wishlist,Unconfirmed]  http://launchpad.net/bugs/44052
[07:31] <aa_> kiko: hmm, basic auth would only have saved me two hours
[07:31] <kiko> aa_, now you're being cruel
[07:33] <aa_> hehe, oh forgive me master
[07:33] <aa_> cookie auth rules though
[08:13] <bradb> BjornT: Any news on that testbrowser exception I showed you the other day? Is there a bug report open anywhere or should I open one?
[08:15] <BjornT> bradb: i plan to fix it tomorrow. there's no bug open on it.
[08:16] <bradb> BjornT: Should I open the bug on the Launchpad product?
[08:16] <BjornT> bradb: yeah, that'd be good.
[08:19] <kiko> carlos, how are your 1-2h going today?
[08:19] <carlos> not yet started
[08:19] <kiko> carlos, don't forget to start :)
[08:19] <carlos> I was distracted this morning
[08:19] <carlos> yeah, don't worry
[08:19] <kiko> it's easy to get bogged down and not swap
[08:20] <carlos> kiko: I was thinking on doing the translation domains review as part of that 1-2h slot
[08:21] <kiko> okay, sounds good
[08:21] <kiko> a task which can start and end in the allotted time
[08:21] <carlos> right
[08:21] <dilys> Merge to devel/launchpad/: [r=jamesh]  Person.inTeam caching to avoid timeouts (r3546: Stuart Bishop)
[08:22] <kiko> no way 
[08:22] <kiko> no way
[08:22] <kiko> no way!
[08:22] <kiko> teamparticipation caching?
[08:22] <kiko> and no CC?
[08:22] <kiko> SteveA?
[08:22] <SteveA> yeah, it's cool
[08:22] <SteveA> minimal performance hack.  it'll get more elegant with CC
[08:23] <kiko> we just lost the one thing I could wave around to make you work on it!
[08:23] <SteveA> btw...
[08:23] <kiko> about that dvd? :)
[08:23] <SteveA> stu's landing did two trivial unrelated things too
[08:23] <kiko> grumble
[08:23] <SteveA>       Enable XMLRPC listener on production
[08:23] <SteveA>       Don't bitch about CVEs without descriptions, as the datasource is external and we just have to cope
[08:23] <kiko> that's so stub
[08:24] <kiko> so XMLRPC can be used now 
[08:24] <kiko> nice
[08:24] <SteveA> that's so "branches are more expensive than they should be"
[08:24] <kiko> so or cause?
[08:24] <SteveA> that's *so*
[08:24] <SteveA> val speak
[08:24] <kiko> I see
[08:24] <kiko> he could have done 3 merges
[08:24] <SteveA> the next format would be cooties
[08:25] <kiko> then again, merges take 4h minimum each
[08:25] <SteveA> yeah
[08:25] <SteveA> apparently gcc has a huge test suite
[08:25] <SteveA> so they don't run it on every commit, so jbailey tells me
[08:25] <SteveA> OTOH, stu tells me there are some simple things he's looking at to make the test suite faster
[08:25] <SteveA> to do with faster DB and librarian setup/teardown
[08:35] <bradb> BjornT: bug 44064
[08:35] <Ubugtu> Malone bug 44064 in launchpad "Pagetest using testbrowser causes ValueError and AttributeError" [Normal,Confirmed]  http://launchpad.net/bugs/44064
[08:41] <BjornT> thanks
[09:03] <carlos> BjornT: tomorrow, I will need your help for the widget usage you suggested for the language selector
[09:04] <carlos> I have more or less done, but I had to do a needed small change, and I'm not able to get it working
[09:04] <carlos> I need to switch tasks now
[09:05] <kiko> rock on carlos 
[09:06] <aa_> well, nothing amazing I guess, but: http://pida.berlios.de/images/br.png gives https://staging.ubuntu.com/products/bzr/+bug/43925
[09:36] <sabdfl> kiko: there is definitely an oops
[09:36] <sabdfl> easy fix
[09:37] <sabdfl> and easy test for future reference
[09:38] <sabdfl> i have a branch off current RF
[09:38] <sabdfl> patch should apply cleanly to whatever is going to be rolled out this week (or is rolled out)
[10:19] <kiko> sabdfl, hah. I should have seen that -- it was obvious
[10:22] <sabdfl> with hindsight yes :-)
[10:23] <sabdfl> should add the IFoo.providedBy(dummy_foo) test everywhere we have dummy_foo's
[10:23] <sabdfl> what's the rollout story this week?
[10:23] <kiko> tomorrow I hear
[10:24] <kiko> rollout was delayed because producing the production branch is taking too long
[10:24] <sabdfl> bzr-ness?
[10:24] <kiko> mmmmm
[10:24] <kiko> topic of the day
[10:24] <sabdfl> i feel better about it now i have a plan to win
[10:24] <SteveA> we should be using the interface verification APIs more than we are
[10:25] <sabdfl> yes, it's such an easy test
[10:25] <SteveA> that includes the providedBy check, and also checks an object's methods and attributes against the interface
[10:25] <sabdfl> be nice if the test failure told you what was missing
[10:25] <SteveA> yep
[10:25] <SteveA> we should find a way of doing this by inspecting what is registered
[10:25] <SteveA> rather than manually
[10:26] <SteveA> we can explicitly disable things that won't verify and we know why they won't
[10:26] <SteveA> (like special magic going on, for example)
[10:29] <aa_> hey, guys, is there a sneaky way I can get a product list from the launchpad?
[10:29] <kiko> aa_, products/+all?
[10:29] <kiko> it's not very sneaky
[10:29] <aa_> my client is working quite nicely, has console and gui front-ends
[10:30] <kiko> ali, you are remarkable
[10:30] <aa_> (and of course can be used direct from peethon)
[10:30] <SteveA> interesting
[10:30] <SteveA> one thing to watch out for is this
[10:31] <SteveA> when we have xmlrpc APIs, we'll be careful about changing them, to be nice to people writing tools to access launchpad that way
[10:31] <SteveA> we can't make a similar promise about pages of launchpad that are for browsers to use
[10:31] <kiko> tis life
[10:31] <aa_> yeah, of course
[10:32] <aa_> this is just temporary until the xmlrpc anyway
[10:41] <aa_> um, any way to insert <pre> style text in a comment? I am thinking about exceptions
[10:41] <kiko> not really -- kind of a wart.
[10:41] <aa_> I am sure it is in a document somewhere, I just can't find it
[10:41] <aa_> oh
[10:41] <aa_> well, let's get a scalpel and some cold coagulant
[10:45] <sivang> aa_: are you ali from #pygtk ?
[10:49] <aa_> sivang: yikes, um maybe
[10:51] <sabdfl> kiko, stevea, can we get a production rollout this week? seems we have good stuff in the queue
[10:52] <sabdfl> salgado: ping
[10:52] <salgado> sabdfl, pong
[10:52] <SteveA> sabdfl: i think stub is planning one.  he was going to do one tuesday, but there were bzr issues.
[10:53] <SteveA> he avoided one today, because of hug day
[10:53] <SteveA> so, i expect stub will do one tomorrow
[10:53] <SteveA> he is aware that one is due
[10:54] <sabdfl> thanks
[10:55] <sabdfl> salgado: on mirror management, if i register a mirror now, does it immediately show up on a list?
[10:55] <sabdfl> it would be nice to be able to call for mirrors to register this week
[10:55] <sabdfl> show them all irrespective of probing status
[10:55] <sabdfl> then bring up the probing scripts for the release
[10:55] <salgado> yes, they will show up on a list automatically
[10:56] <sabdfl> even if they have not been probed?
[10:56] <salgado> yes
[10:56] <sabdfl> ok, thanks
[10:56] <salgado> and the mirror probed is already running on production
[10:56] <sabdfl> i'm going to play with it locally, can I do some UI tweaks if I find low-hanging fruit or is that likely to get conflicts?
[10:57] <salgado> I've got some feedback from mdz on that, but I'm working on the cdimage stuff, so I didn't touch the UI since it landed
[10:57] <sabdfl> salgado: http://localhost:8086/distros/ubuntu/+allmirrors
[10:57] <sabdfl> dude
[10:58] <sabdfl> balance that page!
[10:58] <sabdfl> i'll DOIT
[10:58] <kiko> spoken like a true cowboy ;)
[10:59] <sabdfl> http://localhost:8086/distros/ubuntu/+mirror/valid-mirror
[10:59] <sabdfl> what's with the balance there, too?
[10:59] <sabdfl> why is that a 2col?
[10:59] <sabdfl> or rather, badly balanced 3col
[10:59] <salgado> well. when it landed it had the menu on the right side and two portlets on the left. I didn't touch it since them
[10:59] <sabdfl> ah, right, we changed the template
[10:59] <sabdfl> the menu moved
[11:00] <sabdfl> i mailed asking folks to rebalance their pages
[11:00] <sabdfl> will do these two and also tweak the pages
[11:00] <salgado> yeah, I didn't got time to do that, sorry
[11:04] <sabdfl> salgado: why the links to allmirrors at the top of a lot of those pages?
[11:08] <sabdfl> salgado: you have name, displayname, description all as textlines
[11:08] <sabdfl> and no explanation as to what to put in each of those, why they are different, why you need all three
[11:09] <salgado> sabdfl, bzr tells me the +allmirrors link was added by mpt. not sure if that was intentional or not
[11:12] <SteveA> sabdfl: i just saw that kiko has added "rebalancing portlets" to the meeting agenda for the launchpad allhands meeting tomorrow
[11:19] <sabdfl> hey bradb
[11:19] <sabdfl> did mpt discuss that new UI approach with anyone?
[11:19] <sabdfl> kiko? stevea?
[11:20] <salgado> I think the way I defined them, the description doesn't make much sense, at least. I'll check if all of them are really important to have
[11:20] <bradb> sabdfl: hi
[11:24] <SteveA> sabdfl: new UI approach?
[11:25] <SteveA> i haven't been following the discussion on irc here
[11:25] <SteveA> i'm due to have a talk with mpt tomorrow morning
[11:25] <SteveA> sabdfl: i'm up for a brief phone call if you want to clarify some UI direction
[11:25] <lifeless> morning
[11:27] <SteveA> hi robert
[11:27] <sabdfl> SteveA: calling
[11:30] <SteveA> https://staging.ubuntu.com/distros/ubuntu/+mirror/arcticnetwork-archive
[11:32] <sabdfl> https://launchpad.net/distros/ubuntu/+spec/zeroconf
[11:40] <carlos> kiko: I just updated https://wiki.ubuntu.com/MissingPotFiles
[11:40] <carlos> kiko: the ones assigned to me are the ones that I need  to import manually or that I need to check to be sure that should not be on language packs
[11:42] <sabdfl> carlos: great work!
[11:44] <sabdfl> salgado: how do i use the "upload file list" feature?
[11:44] <carlos> sabdfl: thanks
[11:46] <salgado> sabdfl, this is one of the things that wasn't clear in the spec, so it was implemented and is being removed now that we defined how we'll work with RELEASE mirrors
[11:47] <salgado> (that was supposed to give us the list of files to probe on a RELEASE mirror, but every mirror owner would be responsible for uploading one for his mirror)
[11:47] <sabdfl> ok
[11:48] <sabdfl> better that it just get the files from the mirror being mirrored
[11:48] <salgado> we could do that, and then fall back to http://releases.ubuntu.com/.manifest if one is not found in the mirror, can't we?
[11:48] <sabdfl> salgado: i'd like to ensure this is not enabled for read-only distributions
[11:49] <sabdfl> salgado: all distributions using this system could be expected to publish a .manifest
[11:49] <sabdfl> it's only ubuntu and its derivatives
[11:51] <salgado> but that is going to be the same .manifest we have on releases.u.c. I was thinking that somebody could change things and then generate a new file list for us, but that doesn't make much sense
[11:52] <sabdfl> no
[11:52] <sabdfl> they either fully mirror ubuntu, or they don't
[11:52] <salgado> is there an easy way to tell if a distribution is read only or not?
[11:52] <sabdfl> kiko: ping
[11:53] <sabdfl> salgado: no, i'm adding it now :-)
[11:53] <sabdfl> basically, we only want mirror management for some distros
[11:53] <sabdfl> like we only want soyuz (archive management etc)
[11:54] <salgado> right
[11:54] <sabdfl> night and thanks, SteveA
[11:54] <salgado> kiko left already
[11:55] <sabdfl> np if he's left
[11:55] <sabdfl> just wanted to point out that we need to be careful to filter out the read-only distros from some services
[11:55] <sabdfl> like shipit and mirror management
[11:55] <sabdfl> and archives, uploads, publishing etc
[11:56] <sabdfl> how do i disable a menu item?
[11:56] <salgado> sabdfl, I usually remove it from the ApplicationMenu.links
[11:56] <salgado> IIRC
[11:57] <salgado> I did that somewhere
[12:00] <salgado> wow, playing with self.links inside the menu class is obviously crack
[12:03] <SteveA> um... return Link('+whatever', title, enabled=False) should do it
[12:03] <elmo> look, stevea is sleep-ircing
[12:03] <SteveA> salgado: yeah, your sense is good.  i'm not sure we'll support playing with self.links in the future