[12:57] <nictuku> hi. I have a project that is ubuntu-related, but hosted in a trac system. Should I register it in launchpad? what are the benefits?
[12:57] <nictuku> oh better https://launchpad.net/faq
[01:46] <ddaa> nictuku: if you do not see any benefit offhand, I suggest to abstain until you know what you want to use launchpad for ;)
[01:47] <ddaa> I think one of the big things right now is Rosetta for translations.
[01:47] <ddaa> (compared to trac, which has pretty much everything already)
[01:48] <nictuku> =]  blast, I've register already now.
[01:49] <ddaa> well, if you register your SVN details you will get a free daily import to bzr. In a few weeks, that bit is a bit broken/in works at the moment.
[01:49] <sivang> night ddaa 
[01:50] <ddaa> then the malone bug tracker allows you to cooperate more closely with the ubuntu distro guys
[01:50] <ddaa> I dunno if it has support for watching trac bugs though...
[01:50] <ddaa> sivang: nigh
[01:51] <ddaa> sivang: then if you are an ubuntu packager, you can use launchpad to build packages too
[01:51] <ddaa> oops
[01:51] <ddaa> s/sivang/nictuku/
[01:51] <ddaa> nictuku: that's about all I can think off hand.
[01:52] <ddaa> nictuku: does that answer your question?
[01:52] <nictuku> very much! thank you
[01:53] <ddaa> there's also a bunch of other random features, but trac probably fills your need for those already.
[01:57] <nictuku> ahm
[01:57] <nictuku> i created a bug tracker that would integrate to trac, but it didn't work and now I can't delete it =] 
[01:57] <ddaa> lanuchpad is bad at deleting stuff
[01:58] <ddaa> I cannot help you with bug tracking, it's not by dept at all.
[01:58] <ddaa> I suggest you post to launchpad-users to explain your problem, that would also give good user feedback for the team to be more aware of whatever was your problem
[01:59] <ddaa> alternatively, just nag stub, it's the db admin.
[01:59] <nictuku> and a small bug report. I created a new project and when trying to search for it no result was returned. 
[01:59] <ddaa> yeah, I noticed, that. I think it's a caching issue.
[02:00] <nictuku> Maybe it's because the search key is too small (nwu). if that uses mysql's full text search or alike, it could be.
[02:00] <ddaa> it uses postgres
[02:01] <ddaa> I do not know really what would be the issue.
[02:01] <ddaa> stub would
[02:01] <ddaa> stub: come on you coward, I know you are awake!
[02:12] <stub> eh?
[02:13] <stub> Searching is word searching. Some terms might be too small to get any hits.
[02:13] <nictuku> ahm.. I'm sorry but how can I delete both the project and the bug tracker? 
[02:14] <stub> give me the project name and the bug tracker name, or urls to them.
[02:14] <stub> I don't think you can hide them.
[02:14] <nictuku> nwu, nwu-bugs
[02:15] <ddaa> stub: hiding is implemented, but unsurprisingly it's agressively broken...
[02:16] <ddaa> or was the last time I heard of it.
[02:16] <stub> All trashed
[02:17] <nictuku> thank you, and sorry again
[02:24] <stub> np
[02:59] <mpt> Gooooooooooooooooooooood afternoon Launchpadders!
[03:02] <ajmitch_> hi
[04:14] <jblack> jb-home: ping
[04:14] <jblack> never mind. he's not here
[04:35] <jamesh> lifeless: how do I go about creating new branches in rocketfuel?
[04:40] <jblack> jamesh: You mean in rocketfuel-built? 
[04:41] <jblack> jamesh: He'll have to adjust pqm and he'll probably want to adjust the config as well.
[04:41] <jblack> I think he's offline right now (he's got heavy construction next doors, so went to a cafe). 
[04:42] <jblack> If you send him an email about the new branch for pqm and where he can get the official branch (or perhaps your branch), then he should be able to add it
[04:42] <lifeless> jamesh: you need to email me the details so I can setup PQM
[04:42] <lifeless> jamesh: as jblack is saying.
[04:43] <jamesh> lifeless: okay.
[04:43] <lifeless> jamesh: I'll do the initial tag into pqm, and then we update the config, and finally the launchpad sourcecode/Makefile
[04:43] <lifeless> jamesh: if you can prep an updated configs branch with each of staging, production, development etc, and the launchpad changes to run the test suite for your new branch when make check is run on sourcecode/ 
[04:44] <lifeless> that would be very helpful
[04:44] <jamesh> lifeless: I can do the config updates after it is set up in pqm, and my LP branch updates sourcecode/Makefile
[04:45] <lifeless> jamesh: ok, excellent. email me the details, what its called etc
[04:51] <lifeless> jamesh: one little bid of red tape, then it gets done.
[04:51] <jamesh> oh?
[04:51] <lifeless> check your mail ;)
[04:51] <jamesh> got it now
[04:52] <jamesh> lifeless: he reviewed the code on launchpad-reviews in the last day with an rs=SteveA on the pygpgme code
[04:52] <jamesh> if that helps
[04:52] <lifeless> so far I've always got an explicit nod from him for things going into rf
[04:53] <jamesh> fair enough
[04:53] <lifeless> New things are rare enough that  enough that checking explicitly is not onerous
[04:53] <lifeless> oh damn, I forget the other ques
[04:53] <lifeless> tions
[04:57] <jamesh> lifeless: if you want to use gpgme in bzr, you might want to consider using this code there too
[04:58] <lifeless> yes
[04:58] <lifeless> Is it open source ?
[04:58] <jamesh> I suppose so.  I did it in my spare time
[04:58] <lifeless> I would like it if you could make that definite
[04:58] <lifeless> ;)
[05:05] <lifeless> hmm
[05:05] <lifeless> cute hack someday, make bzr selftest use a progress bar.
[05:12] <jamesh> lifeless: license should be definite now.
[05:13] <jamesh> LGPL, to match the library it is wrapping
[05:13] <lifeless> cool
[05:13] <LaserJock> is it possible to look at binary packages on LP? I see a greyed out link on the left when I look at the source package page
[05:13] <lifeless> does it have a home page ? 
[05:14] <jamesh> LaserJock: sure.  There are links to it from the source packages, or from a distro arch release page
[05:14] <jamesh> lifeless: not yet.
[05:15] <LaserJock> jamesh: but is there a URL that wouldn't depend on arch and release. I'm looking for a general URL scheme for binary packages.
[05:15] <LaserJock> specifically for bugs listings
[05:16] <jamesh> LaserJock: binary packages don't really make much sense without an arch
[05:16] <jamesh> LaserJock: the bugs are categorised by source package name too
[05:17] <LaserJock> jamesh: well I was thinking a listing of all bugs against a particular binary package quite a few users don't know what the source package is named necessarily
[05:18] <jamesh> LaserJock: if it is a GUI app, do Help -> Get Help Online
[05:18] <jamesh> then pick bugs in the menu on the right of that web page
[05:20] <LaserJock> well, I was trying to write some documentation on how to find bugs in Ubuntu but I guess I'll just stick to source packages for now. I guess I can just put <release>/<arch> but that seems a bit much.
[05:23] <jamesh> LaserJock: searches at https://launchpad.net/distros/ubuntu/+bugs will search all Ubuntu bugs
[05:23] <jamesh> which is sometimes a good solution if you don't know the source package name (or know which package the problem resides in)
[05:25] <LaserJock> jamesh: yes I realize that, I was just shooting for something URL based like bugs.debian.org/<package> versus bugs.debian.org/src:<package> but it's not a big problem. I just wondered if I was doing something wrong
[06:13] <mpt> Is the datacenter migration still going on?
[06:19] <lifeless> no
[07:18] <dilys> Merge to devel/launchpad/: [trivial]  Add person_sort_key stored procedure, fucntional index and tests to sort people correctly by name (r3136: Stuart Bishop)
[08:23] <SteveA> hello
[08:24] <SteveA> lifeless, jamesh: definitely want the new gpg wrapper in RF, provided all tests pass.
[08:29] <lifeless> SteveA: cool.
[08:29] <jblack> stevea: You must have read my mind. I was just looking into testament for that purpose.
[08:30] <jblack> for a new wrapper. Not for any particular wrapper that had already been written.
[08:32] <SteveA> jblack: this is largely on jamesh's initiative.  he just turned up after LCA with a new gpgme wrapper. 
[08:33] <jblack> Awesome. 
[08:33] <carlos> morning
[08:33] <SteveA> stub: i'm about to send you a signed email asking you to merge two launchpad accounts.  The user in question has the gpg key registered with one, but no longer has access to its email address.  He has access to the email addresses from the other.
[08:37] <SteveA> hello carlos 
[08:39] <carlos> SteveA: hi
[08:46] <lifeless> pqm down for maintenance
[08:46] <lifeless> back soon
[08:49] <lifeless> spiv: can you try bb again ?
[08:51] <stub> SteveA: You can merge accounts yourself now - there is a web ui for it somewhere (which I have to use too - can't do account merging sanely from the psql command line)
[08:51] <stub> (linked from launchpad.net/people if you are logged in as an admin)
[08:57] <stub> lifeless: Ping me when things are back up. I need to get onto balleny to tag and test todays production release.
[08:57] <lifeless> its back up
[09:05] <jblack> jamesh: ping
[09:06] <jamesh> jblack: pong
[09:06] <jblack> jamesh: How are you planning on doing the gpg script for rf?
[09:06] <jamesh> jblack: what do you mean?
[09:07] <jblack> well, I'm the writer of bzr-submit-merge.
[09:08] <jblack> I'm wondering what you'd like from me. I could easily add "bzr testament" output to the email request.
[09:09] <lifeless> jblack: I am betting jamesh is about to ECONTEXT
[09:09] <lifeless> jblack: I know I am
[09:09] <jamesh> jblack: the gpg stuff I've been working on is within the web app
[09:09] <jamesh> jblack: replacing one libgpgme wrapper with another one
[09:09] <jblack> Ok. A few minutes ago, SteveA talked about "the new gpg wrapper in RF"
[09:09] <jblack> Oh, ok.
[09:10] <jblack> Never mind. =)
[09:16] <SteveA> stub: it is taking a while...
[09:17] <stub> It has a high probability of getting blocked on other request's locks - it needs to touch a great many tables
[09:17] <SteveA> stub: OOPS-45C282
[09:17] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/45C282
[09:17] <SteveA> we should turn off timeouts for that request, perhaps
[09:18] <SteveA> it is all transactional, right?  so it either works or doesn't.
[09:18] <jamesh> perhaps an zopeless script would help for some of these administrative merges
[09:18] <stub> Yup - fully transactional. Try again.
[09:18] <stub> Hmm... statistician is running.
[09:19] <stub> Doing its evil queries :-(
[09:19] <stub> Definitely should farm that one out to a replica database
[09:19] <SteveA> yes
[09:20] <sivang> morning all
[09:20] <sivang> hey jblack , how you been?
[09:21] <SteveA> stub: OOPS-45A275.  how much longer with the statistician be running?
[09:21] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/45A275
[09:21] <stub> I'll kill it so we can confirm it is the bastard
[09:21] <SteveA> ok
[09:22] <stub> SteveA: ok. dead. hit it.
[09:23] <SteveA> OOPS-45C284.
[09:23] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/45C284
[09:23] <SteveA> i'll try one more time
[09:24] <SteveA> OOPS-45B304.
[09:24] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/45B304
[09:24] <stub> Yup. evil queries from the statistician are still running (client killed, but PostgreSQL hasn't noticed yet)
[09:24] <SteveA> ok
[09:25] <stub> SteveA: ok. and again?
[09:25] <stub> We have lucille connections , at least one of which is 'idle in transaction' which is not good.
[09:25] <stub> but the batch jobs are all dead
[09:28] <SteveA> wow
[09:28] <SteveA> it wasn't even timing out on the merge
[09:28] <SteveA> it was timing out on the "are you sure" page
[09:29] <lifeless> stub: statistician should be able to run unisolated no ?
[09:29] <SteveA> stub: it all worked.  very quickly now.
[09:29] <stub> SteveA: ok. statistician is evil and needs refactoring.
[09:29] <stub> Or running on a replica database (which will also need refactoring since it still needs to write the stats to the production db)
[09:30] <SteveA> <p style="notveryubuntu">or kicking in the nuts and breaking its nose on your knee.</p>
[09:32] <SteveA> stub: can you do an async replica easily
[09:32] <SteveA> ?
[09:33] <stub> A replica good enough for the statistician is easy - just restore the nightly backup into a fresh db like I do for staging. No software required.
[09:39] <SteveA> <p style="jazzclub">niiice.</p>
[09:41] <SteveA> spiv: hello
[09:45] <SteveA> spiv: ping
[10:18] <mpt> BjornT, ping
[10:18] <BjornT> hi mpt 
[10:18] <mpt> BjornT, how do I edit a Malone attachment?
[10:19] <mpt> There's a test for it
[10:19] <mpt> but I can't see how to get to the edit URL by clicking anywhere
[10:19] <BjornT> mpt: it should be an edit link in the portlet, i think
[10:19] <mpt> well, that won't work
[10:20] <mpt> if there's more than one attachment :-)
[10:20] <BjornT> mpt: well, there should be one link per attachment :)
[10:20] <mpt> so if the bug has 16 attachments
[10:20] <mpt> there should be 16 "Edit Attachment N" links in the portlet
[10:21] <mpt> heh
[10:21] <mpt> oh!
[10:21] <BjornT> mpt: well, at the moment there's a small "(edit)" after the title
[10:21] <mpt> There's a bug attachments portlet!
[10:21] <BjornT> mpt: feel free to improve it ;)
[10:22] <mpt> Giving it a pink background would work
[10:22] <mpt> otherwise it's pretty unnoticable
[10:24] <mpt> SteveA, have you had time to review https://wiki.launchpad.canonical.com/SimplifyingMalone yet?
[10:24] <jamesh> mpt: blink tag, maybe?
[10:24] <BjornT> yeah, i think we really should try to work and incorporate more information in the main context area
[10:25] <mpt> well, we could have an "(edit)" link next to the attachment in the comment itself
[10:25] <mpt> jamesh, or <marquee>, or both
[10:26] <mpt> BjornT, but it would be ... it *is* rather weird to be able to re-title an attachment that lives inside someone's comment box
[10:27] <BjornT> mpt: yeah, that would be quite weird.
[10:28] <mpt> attachments sit on the fence of editable description vs. non-editable comments
[10:42] <SteveA> hi mpt 
[10:42] <mpt> hi SteveA 
[10:45] <SteveA> mpt: voice call?
[10:46] <mpt> sure
[10:50] <SteveA> hmm...
[10:51] <SteveA> this is a bit like last time, where the connection was dropping often
[10:51] <SteveA> are you still using wireless?
[10:51] <SteveA> maybe a wired connection would work better?
[11:12] <stub> Launchpad is going down in 10 minutes for the weekly code update. Estimated downtime is about 10 mins. wikis will be in readonly mode.
[11:16] <stub> Update: Launchpad is going down in 15 minutes for the weekly code update. Estimated downtime is about 10 mins. wikis will be in readonly mode.
[11:21] <Kinnison> stub: the rollout for the db patches, 17-0 17-1 and 18-0 ?
[11:22] <stub> Kinnison: Not 18-0, and 17-1 is already applied to production. So just 17-0
[11:23] <stub> (The 'patch' patches I use for backporting patches I apply to the live DB)
[11:23] <Kinnison> heh
[11:23] <Kinnison> cool, nothing for me to worry about in that lot
[11:28] <Kinnison> stub: publisher is finished, from the ftpmaster side you're good to go
[11:33] <Kinnison> stub: say as soon as you're done please
[11:35] <dooglus> wouldn't it be better to do the code update at night time?
[11:35] <dooglus> ;)
[11:35] <daf> it's always night time somewhere
[11:36] <dooglus> yeah, but at the moment it's only night time for the Australians
[11:37] <daf> well, it's only 21:30 for them
[11:37] <daf> it's the west coast USA that's being let off, I reckon
[11:37] <dooglus> what time is it in Wales?
[11:38] <daf> 10:32
[11:38] <daf> (GMT - 00:05)
[11:38] <dooglus> I had a really vivid dream that I was in Wales last night.
[11:38] <daf> yes?
[11:39] <dooglus> yes, I was walking around the Gower peninsula, & it was really beautiful.  I don't often remember dreams, but this was really nice.
[11:39] <stub> Kinnison: done
[11:40] <daf> yay
[11:40] <daf> dooglus: ah, lovely
[11:44] <Kinnison> stub: ftpmaster reenabled, thanks
[11:57] <mpt_> SteveA, matsubara or someone could land my builds listing work because that's all published on chinstrap
[11:58] <SteveA> mpt: mail the list with the details, i'll follow up later
[11:58] <daf> SteveA: could you add an "oops" milestone to shipit for me?
[11:58] <mpt_> ok
[11:58] <SteveA> daf: ok
[11:59] <SteveA> although... launchpad developers should be able to do so.
[11:59] <SteveA> how can we make it so?
[11:59] <daf> I'm not sure
[11:59] <daf> is shipit marked as a Launchpad product?
[11:59] <daf> I mean, is it in the Launchpad project?
[11:59] <SteveA> wtf
[11:59] <mpt_> yes
[11:59] <SteveA> https://launchpad.net/products/shipit
[11:59] <SteveA> we have two series here
[11:59] <SteveA> 
[11:59] <SteveA> Muhammad khawar (2005-12-10)
[11:59] <SteveA>     How can i order the product.
[12:00] <SteveA> 
[12:00] <SteveA> that's one series
[12:00] <SteveA> Arif (2005-10-05)
[12:00] <SteveA>     lunix 5.10 or higher/lower
[12:00] <SteveA> 
[12:00] <SteveA> that's another
[12:00] <SteveA> why are random people allowed to add product series to my product?
[12:00] <SteveA> well, i suppose people can release unofficial series
[12:00] <SteveA> but still.
[12:00] <daf> ...while Launchpad developers can't add milestones
[12:00] <SteveA>  No revision control details recorded for Muhammad khawar
[12:01] <daf> bzr uncommit
[12:01] <mpt_> Wasn't the big idea that anyone could make branches of someone else's product, for easier forking?
[12:01] <mpt_> and have it listed on the product page
[12:02] <daf> mpt_: don't say the F word -- we *branch*
[12:02] <SteveA> yes for branches
[12:02] <SteveA> not sure about product series
[12:02] <mpt_> for easier ... varying
[12:02] <SteveA> but maybe
[12:02] <SteveA> we should probably have the concept of "endorsed by product owner" series
[12:02] <SteveA> and other series
[12:02] <SteveA> but anyway...
[12:02] <mpt_> and the difference between a product series and a branch seems to be part of what ddaa was talking about earlier
[12:02] <SteveA> stub: can you remove these product series from shipit?
[12:03] <daf> mpt_: not having that sorted out seems to be blocking lots of things
[12:03] <SteveA> anyone see any harm in changing the shipit registrant to launchpad-developers?
[12:03] <SteveA> (people/launchpad i mean)
[12:03] <mpt_> daf, yes, it seems to be an amorphous mess
[12:03] <SteveA> mpt_: go to sleep!
[12:03] <mpt_> right
[12:03] <carlos> SteveA: hi, do you have sometime to talk about https://launchpad.net/malone/bugs/31333 ?
[12:03] <Ubugtu> malone bug 31333 in rosetta "Separate update in POST from rendering of form via redirect()" [Normal,Confirmed]  
[12:04] <daf> I should write a bot that keeps track of people's timezones and tells them to go to bed
[12:04] <SteveA> daf: mpt needs to be up early to get some network stuff sorted out
[12:05] <SteveA> carlos: yes, what do you want to talk about?
[12:05] <carlos> SteveA: I did the redirect already
[12:05] <carlos> SteveA: but the form is rendered anyway...
[12:05] <SteveA> i need to see the code
[12:05] <SteveA> is it in RF?
[12:05] <stub> SteveA: trashed
[12:05] <SteveA> stub: ta
[12:05] <carlos> without the redirect, yes
[12:06] <SteveA> carlos: i don't follow
[12:06] <carlos> ok
[12:06] <SteveA> can you say the same thing but in more words?
[12:06] <carlos> SteveA: we have the translation form
[12:06] <carlos> with every submit, we handle the form and render the next page
[12:06] <carlos> at the same time
[12:07] <seb128> hi
[12:07] <carlos> I think you suggested to split it and handle the post first and then render the page using a redirect
[12:07] <seb128> is there a way to merge 2 upstreams product?
[12:07] <SteveA> hi seb128 
[12:08] <SteveA> i think that's a question for stub 
[12:08] <seb128> https://launchpad.net/products/sj https://launchpad.net/products/sound-juicer are both sound-juicer
[12:08] <stub> seb128: Not yet. We can write it though.
[12:08] <SteveA> carlos: okay.  let's talk on #c-m
[12:08] <SteveA> daf: would you join us please?
[12:09] <daf> certainly
[12:09] <seb128> is that possible for an lp admin to drop "sj" and keep only sound-juicer?
[12:09] <stub> seb128: I can drop 'sj' if there aren't too many dependancies (eg. bugs assigned)
[12:09] <seb128> https://launchpad.net/products/sj points no bugs or translation
[12:11] <stub> Got productseries and productreleases
[12:12] <stub> And packaging.
[12:12] <stub> Looking pretty embedded.
[12:13] <jordi> SteveA: hey
[12:13] <stub> I'll hide it
[12:13] <jordi> got my email?
[12:13] <SteveA> hello jordi
[12:13] <cprov> stub: hi, did you manage to upgrade mawson postgres ?
[12:13] <SteveA> jordi: i do now
[12:13] <stub> cprov: Nope. I need to poke Znarl or elmo about installing the PG8 packages.
[12:13] <jordi> sorry - I hadn't seen it bounced, I hadn't powered on my laptop in a week
[12:14] <cprov> stub: in the mean while could you look a DB patch in my small-fixes (it's in PendingReviews)
[12:14] <stub> cprov: I did. Check your email (approved)
[12:14] <cprov> stub: would be nice to have it in production asap
[12:15] <cprov> stub: duh ,,, not yet, sorry 
[12:15] <cprov> stub: I will merge in RF, so you can roll it out 
[12:17] <lifeless> BjornT: your bug-29848 patch conflicts
[12:17] <lifeless> BjornT: just a heads up
[12:18] <BjornT> lifeless: ok
[12:37] <dilys> Merge to devel/launchpad/: New cronscript to flag expired team memberships and some other cleanups. r=jamesh (r3137: Guilherme Salgado)
[12:50] <salgado> lifeless, around?
[01:03] <kiko> hello morning warriors
[01:12] <SteveA> whoa... google maps have improved the resolution of vilnius.  http://maps.google.com/maps?f=q&hl=en&q=vilnius+lithuania&t=k&ll=54.709248,25.211944&spn=0.001754,0.006781&t=k
[01:12] <SteveA> um
[01:12] <SteveA> wrong url
[01:13] <kiko> hey SteveA 
[01:13] <kiko> how did it go yesterday?
[01:13] <SteveA> not so bad
[01:14] <jordi> kiko: goooood morning
[01:14] <SteveA> http://maps.google.com/maps?f=q&hl=en&q=vilnius+lithuania&t=k&ll=54.677175,25.274144&spn=0.0013,0.006781&t=k
[01:14] <SteveA> that's better
[01:23] <dilys> Merge to devel/launchpad/: Fixes https://launchpad.net/products/soyuz/+bug/31324 (Broken traversal on Binary package build summary page) r=kiko (r3138: Diogo Matsubara)
[01:24] <kiko> that took a long time
[01:25] <matsubara> weird test failure yesterday night. 
[01:26] <stub> Were do MOTU requests go now?
[01:26] <stub> Malone?
[01:26] <kiko> as always, stub 
[01:33] <niemeyer> kiko: What is CrowdControl?
[01:33] <kiko> niemeyer, the future. :)
[01:34] <kiko> stub, how's rollout?
[01:34] <niemeyer> Ah! I want it!
[01:34] <niemeyer> :-)
[01:34] <stub> kiko: done. No probs.
[01:34] <niemeyer> kiko: Now, what is it about?
[01:35] <kiko> stub, rock and roll. will send out report shortly
[01:35] <kiko> niemeyer, shy about looking at the wiki? :)
[01:36] <niemeyer> kiko: Amazing.. it's there.. you surprise me sometimes.
[01:37] <SteveA> niemeyer: it is an object abstraction for efficently asking whether a person or an abstract group of people is part of some other group of people
[01:38] <SteveA> that ends up making few database calls, or no database calls in some cases
[01:38] <SteveA> been planned since the cape-town meetings
[01:38] <sivang> SteveA: can you spot where you are on the google map? :)
[01:38] <SteveA> yes
[01:38] <SteveA> in the centre of that map
[01:38] <SteveA> across the street from me is the belarussian embassy
[01:38] <niemeyer> SteveA: Nice.. somewhat like the std Zope3 security policy itself
[01:39] <SteveA> niemeyer: sort of.  except we're concerned with people and teams in launchpad rather than principals and groups.
[01:39] <sivang> what are Buttress-Gods-Only pages ?
[01:40] <kiko> stub, did you find out what marilize was reporting yesterday?
[01:40] <niemeyer> SteveA: Understood. These concepts match pretty well with each other (prncipal=people, groups=teams), even then..
[01:41] <niemeyer> Or, principal=person
[01:41] <stub> kiko: What was marilize reporting yesterday?
[01:41] <SteveA> niemeyer: sure, we usually map a principal to a person, so we can do person-based security
[01:41] <kiko> stub, that shipit was broken?
[01:41] <SteveA> i'm not sure whether teams in launchpad map onto zope principal groups.
[01:42] <SteveA> the thing with ICrowd is that it has a very simple interface, so that you can do a lot with it underneath
[01:42] <SteveA> and you can map a range of things onto an ICrowd
[01:42] <stub> There was a problem with shipit we fixed an hour or three ago. No idea if it was what was happening yesterday - nobody bothered to email me that there was a problem.
[01:43] <SteveA> there is no nagios monitoring for shipit or launchpad webapps
[01:43] <kiko> stub, what was wrong with shipit?
[01:43] <SteveA> karl said that if we can have a simple webpage with some content in it, to be checked by nagios, then we can have such monitoring
[01:44] <stub> (16:55:41) Znarl: The IP for shipit was up on the old shipit server after it was rebooted.  I've made sure it won't come up again.
[01:44] <SteveA> so /+heartbeat or something would do
[01:44] <stub> The root document would do it too
[01:44] <kiko> SteveA, the homepage is pretty simple.
[01:45] <SteveA> for shipit, yes. for launchpad, no
[01:45] <kiko> I meant for shipit.
[01:45] <SteveA> karl wanted to have some specific content (such as an HTML comment) that would definitely be there
[01:45] <SteveA> i like the idea of having a separate page for this
[01:46] <SteveA> particularly as front pages can appear with a 200 if virtual hosting is messed up
[01:46] <SteveA> but a sub-page will usually get a 404 or 503
[01:49] <kiko> stub, can you give me the details on what was rolled out, or better yet, email launchpad?
[01:50] <dilys> Merge to devel/launchpad/: [r=stub]  Add a new column (pocket) to build table, required for enhanced buildd-system. (r3139: Celso Providelo)
[01:50] <stub> kiko: What we discussed yesterday. (21:37:58) stub: kiko: I'm thinking of r3123 with r3128 cherry picked, 3126
[01:51] <kiko> stub, I'd appreciate it if you made a point of emailing the list every time you rolled out, as part of the production rollout process.
[01:52] <cprov> stub: could you cherrypick this r3139 ? it will be import to the progess of the "upload to released pockets" task during this week 
[01:52] <stub> cprov: IIRC that has a database patch so that will need some downtime
[01:53] <cprov> stub: really ? when can you manage to get it in ?
[01:53] <stub> cprov: Can it wait until a quiet period tomorrow?
[01:53] <cprov> stub: I think so, having it tomorrow you be ok 
[01:53] <stub> You tell me, its your branch. Does it have a database patch?
[01:54] <cprov> stub: should I send an email in lp list to remind you ?
[01:54] <SteveA> jblack: hello
[01:54] <cprov> stub: yes, it's that build table patch you approved this morning 
[01:54] <jblack> SteveA: Hi
[01:54] <stub> cprov: sure
[01:58] <niemeyer> SteveA: SuperSpecialPermissions is quite interesting
[01:58] <SteveA> niemeyer: it isn't right, though.  i've grown suspicious of permissions for launchpad.
[01:58] <cprov> stub: sent
[01:59] <SteveA> they're mostly working out now, but there are many areas where they don't work out so well
[01:59] <niemeyer> SteveA: In what sense?
[01:59] <SteveA> sorry -- too busy to talk about it today
[02:01] <niemeyer> SteveA: No problems. Let me know when you get the time. I'm designing the system for Gantry and will be glad to reuse your knowledge.
[02:01] <kiko> matsubara, I have a question for you
[02:01] <kiko> have you seen this error?
[02:01] <kiko>    7 NotFoundError: 'Unpublished binary package: linux-image'
[02:01] <kiko> \
[02:02] <kiko>    6 NotFoundError: (<Branch at INSTANCE-ID>, 'getPackageName')
[02:02] <kiko>     0% from search bots, 83% referred from local sites
[02:02] <kiko>        6 https://launchpad.net/products/update-manager/+series/main/+index
[02:02] <kiko>         OOPS-44A490, OOPS-44A491, OOPS-44C487, OOPS-44C488, OOPS-44D564
[02:02] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/44A490
[02:02] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/44A491
[02:02] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/44C487
[02:02] <kiko> that's also a bug
[02:02] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/44C488
[02:02] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/44D564
[02:02] <matsubara> not yet. I think someone was getting that error yesterday.
[02:02] <kiko> yeah
[02:06] <kiko> salgado, how's MM going?
[02:07] <BjornT> kiko, matsubara: the first NotFoundError is bug 31367
[02:07] <Ubugtu> malone bug 31367 in malone "Specifying a non-published binary package when filing a bug causes an oops" [Normal,Unconfirmed]  http://launchpad.net/bugs/31367
[02:08] <matsubara> thank BjornT 
[02:08] <matsubara> s/thank/thanks/
[02:08] <salgado> kiko, it needs more tests and some cleanup. but right now I'm trying to fix bug 31114, as it was amongst the top oopses
[02:08] <Ubugtu> malone bug 31114 in launchpad "oops when searching unknown people" [Normal,Confirmed]  http://launchpad.net/bugs/31114
[02:09] <kiko> salgado, okay. do you have an ETA for landing MM?
[02:10] <stub> kiko: Emailing the launchpad mailing list is already part of the procedure. I just need to follow it better.
[02:10] <kiko> stub, indeed, you do :)
[02:10] <salgado> kiko, I hope to land it on the review queue tomorrow, but I can't give an ETA for landing it on rocketfuel
[02:10] <kiko> is it a lot of code?
[02:13] <salgado> no more than 2k lines, I think
[02:13] <kiko> mmmkay
[02:14] <kiko> who's the victim?
[02:14] <salgado> I guess spiv, as there's a reasonable amount of twisted code in there
[02:23] <kiko> salgado, can you put the branch up yet
[02:23] <kiko> ?
[02:24] <salgado> kiko, I think so, but most of the changes are not committed yet, and the code is still pretty messy, because I was experimenting a lot
[02:25] <kiko> mmmmkay
[02:25] <kiko> I just want to get this to spiv sooner rather than later. I guess you can put it up by tonight, right?
[02:29] <kiko> salgado, the reason I'm asking is because I'd like us to work on ShipitForDapper 
[02:29] <daf> kiko: carlos and I cooked up a fix for #31333
[02:29] <daf> kiko: https://chinstrap.ubuntu.com/~dsilvers/paste/fileiYnUHn.html
[02:29] <kiko> cooking, mmmm
[02:29] <carlos> kiko: could you do a fast review? it's really small (main changes are pagetests fixes)
[02:30] <kiko> I have a question
[02:30] <daf> fire away
[02:30] <kiko> why does the final hunk lack a Content-Length?
[02:31] <kiko> the rest seems fine
[02:32] <daf> hmm, that is odd
[02:32] <kiko> I am curious as to the pages that used to be 200 oks that are now redirects.
[02:32] <kiko> because we did not add any extra code to redirect
[02:33] <daf> er, yes we did
[02:33] <kiko> ah, I see
[02:33] <daf> the final hunk should have a Content-Lengh
[02:33] <daf> we missed that test failure somehow, but it's in the log
[02:33] <kiko> so the code in the 3rd hunk in browser/pofile.py
[02:34] <kiko> is what changes status on 31-rosetta-pofile-translation-form-long-msgid.txt, xx-rosetta-pofile-translate-newlines-check.txt and 45-test-distro-closed-permissions.txt?
[02:34] <kiko> daf, if you confirm and verify that, r=kiko.
[02:35] <daf> that's right
[02:36] <kiko> lots of tests for that callsite, nice.
[02:36] <daf> I have one doubt
[02:36] <kiko> good work.
[02:36] <kiko> I have many more
[02:36] <daf> if we extend LaunchpadView to support redirects
[02:37] <kiko> yes?
[02:37] <daf> (adding self.redirecting = False in __init__, def redirect(self, url): self.redirecting = True; self.request.response.redirect(url); def render(self): if self.redirecting ...)
[02:37] <daf> then we should update this code
[02:37] <SteveA> daf: i want to see how the translate page works for rosetta, before we improve LaunchpadView
[02:38] <kiko> that's what I was about to say
[02:38] <daf> that's fine
[02:38] <kiko> but SteveA is such a smart-alec
[02:38] <kiko> he second-guesses my every move
[02:38] <daf> I just want to make sure we remember to update this when that happens
[02:38] <kiko> I bet he will guess what I will do now
[02:38] <SteveA> will the tests not show that?
[02:38] <daf> yes, if the code breaks
[02:38] <SteveA> then that's fine
[02:38] <SteveA> nothing to worry about
[02:39] <daf> ok
[02:40] <SteveA> ?
[02:40] <SteveA> "daf gets a review"?
[02:41] <daf> 13:34:58 <kiko> daf, if you confirm and verify that, r=kiko.
[02:41] <SteveA> okay, cool :-)
[02:41] <daf> :)
[02:41] <SteveA> i'm having a crusade against too much [trivial] 
[02:41] <SteveA> instant-reviews are good
[02:42] <daf> agreed
[03:15] <kiko> salgado, have some time to chat?
[03:17] <kiko> say yes
[03:17] <salgado> kiko, sure
[03:17] <kiko> I'll be up shortly then
[03:17] <kiko> it's all good news
[03:23] <jbailey> From a bug page (like https://launchpad.net/distros/ubuntu/+source/cdbs/+bug/25678 ) is there an easy way to get to the package build information?
[03:23] <Ubugtu> malone bug 25678 in cdbs "cdbs: FTBFS: DVI file can't be opened" [Major,Unconfirmed]  
[03:23] <jbailey> Ubugtu: Thanks.
[03:23] <jbailey> I'm guessing there probably is and my eyes are probably just sliding over it.
[03:24] <seb128> jbailey: top right frame, click on "overview"
[03:25] <seb128> pick the package version you want from the new page
[03:25] <jbailey> Ah, okay.
[03:25] <seb128> dunno if that's an "easy way", that's in the "5 clicks to do something" spirit of launchpad ...
[03:25] <jbailey> It's half of what I'm looking for - I can see when it built, but I haven't found the build logs yet.
[03:26] <jbailey> eh
[03:26] <jbailey> Build log:  	 not available
[03:26] <jbailey> Probably why I don't see a link that looks like I expect. =)
[03:26] <jbailey> Oh, it's inherited.
[03:26] <jbailey> 'k, so I'm just getting eaten by transition love.
[03:26] <jbailey> Thanks eb
[03:26] <jbailey> er.
[03:26] <jbailey> sb.
[03:31] <seb128> np :)
[04:01] <raphink> hi guys
[04:01] <raphink> :)
[04:01] <raphink> I've got some issues with a few packages of mine
[04:02] <raphink> they got uploaded as NEW some time ago
[04:02] <raphink> they appear on my LP page
[04:02] <raphink> but somehow they were never built
[04:02] <raphink> and never appeared in dapper-changes
[04:02] <raphink> any idea?
[04:02] <Kinnison> then they were never accepted through NEW
[04:02] <Kinnison> talk to a distro admin such as kamion or elmo
[04:02] <raphink> https://launchpad.net/people/raphink/+packages : konq-kim and revu-tools are the targetted ones ;)
[04:03] <raphink> I never got anything from elmo either
[04:03] <raphink> well konq-kim was accepted, that I know
[04:03] <raphink> revu-tools I do not know
[04:04] <Kinnison> if konq-kim was accepted then it should have been built
[04:05] <Kinnison> https://launchpad.net/+builds/+build/167304
[04:05] <Kinnison> suggests it was built
[04:05] <ogra> you normally get a notification mail that it sits in the NEW queue
[04:05] <ogra> and that you should contact the queue admin ...
[04:05] <dilys> Merge to devel/launchpad/: [r=lifeless]  fix bug 29848, make sure the affects command works as expected. (r3140: Bjorn Tillenius)
[04:05] <raphink> Kinnison: http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=konq-kim&searchon=names&subword=1&version=all&release=all 
[04:06] <raphink> suggests it never appeared in the distro though
[04:06] <Kinnison> so the binaries are probably in NEW
[04:06] <Kinnison> or they exploded horribly
[04:07] <Kinnison> you should ask kamion or elmo if the binary is in NEW
[04:07] <Kinnison> Once you have exhausted the distro side of investigation, then ask here
[04:07] <raphink> Kinnison: there is no interface for NEW right?
[04:07] <Kinnison> there's no UI for NEW, not yet, no
[04:07] <raphink> Kinnison: I have pinged elmo about konq-kim and revu-tools several times already
[04:09] <Kinnison> well...      184 | -B | konq-kim             | 0.8.3-0ubuntu1       | ten days
[04:09] <Kinnison> it's in new
[04:11] <Kinnison> So you should ask kamion about accepting the binary
[04:12] <ogra> or wait until elmo gets to your mail :)
[04:12] <ogra> (if you already pinged him its probably not a good idea to bother both of them)
[04:13] <SteveA> stub: still around?
[04:14] <stub> SteveA: Yes
[04:29] <kiko> cprov, lunch?
[04:30] <daf> carlos: when's the Dapper import for Rosetta scheduled?
[04:30] <carlos> daf: I have the test done
[04:30] <carlos> daf: and it's working now  with our tests
[04:30] <carlos> I'm pushing my branch
[04:30] <carlos> I guess next week
[04:30] <kiko> carlos, you KNOW next week
[04:31] <kiko> and minus weekends and sleeping until it's done!
[04:31] <carlos> kiko: it depends on cprov's branch merge
[04:31] <kiko> you must be joking
[04:31] <carlos> kiko: ?
[04:31] <kiko> you are depending on cprov's branch?!
[04:31] <kiko> that is a disaster
[04:31] <carlos> ??
[04:31] <kiko> cprov's branch is a monster
[04:31] <carlos> kiko: that branch is what triggers the import!
[04:31] <kiko> can't you roll this code out on drescher?
[04:32] <carlos> kiko: I branched it and added the test as you asked me last week...
[04:32] <dilys> Merge to devel/launchpad/: [r=kiko]  fix bug 31333: the translation page should not be rendered when it is redirecting after a POST (r3141: Dafydd Harries)
[04:32] <kiko> that way it won't be tied to production code
[04:32] <carlos> kiko: drescher?
[04:32] <carlos> kiko: don't know
[04:32] <carlos> cprov: ?
[04:32] <kiko> yes, the machine which holds soyuz.
[04:32] <carlos> oh
[04:32] <cprov> kiko: it still being a monster, mostly because you do not redirect efforts to review it ... 
[04:32] <carlos> I was not aware of that
[04:33] <kiko> cprov, we all have our problems
[04:33] <cprov> kiko: I know
[04:33] <carlos> cprov: do you think that the publish method will work without your branch changes?
[04:33] <cprov> carlos: not the entire soyuz production is tied to my branch
[04:34] <carlos> kiko: the test will not work as it depends on cprov's branch
[04:34] <carlos> kiko: the code fixes is just one line change
[04:34] <kiko> deesaster
[04:34] <kiko> I'll talk to cprov about this
[04:35] <Alinux> hello when I update my georgian .po file I get parser error---??   ./ka.po:16:7: parse error
[04:35] <carlos> kiko: ok
[04:35] <Alinux>  intltool-update ka
[04:35] <Alinux> ./ka.po:16:7: parse error
[04:35] <Alinux> /usr/bin/msgmerge: found 1 fatal error
[04:35] <Alinux> ./ka.po:16:7: parse error
[04:35] <Alinux> /usr/bin/msgfmt: found 1 fatal error
[04:35] <Alinux> :/
[04:35] <daf> Alinux: what's on line 16 of the PO file?
[04:35] <carlos> Alinux: could you send me the file?
[04:35] <Alinux> carlos, yes
[04:35] <cprov> carlos: are you talking about the interface fix yesterday ? don't think so, looks like to have the entire upload system working properly you'll need my branch anyway 
[04:36] <carlos> cprov: yes, I'm talking about that
[04:36] <carlos> cprov: ok
[04:36] <cprov> carlos: can we run your code in drescher (like an emergency solution)?
[04:36] <Alinux> carlos, http://alinuxos.no-ip.org/gtk20.po
[04:36] <Alinux> :/
[04:36] <carlos> cprov: as long as we can do uploads into librarian and access to production db... it should work
[04:37] <Alinux> daf, seems regular...
[04:37] <cprov> carlos: I mean incorporate rosetta tasks in soyuz-production 
[04:37] <carlos> cprov: the upload is triggered by soyuz directly
[04:37] <cprov> carlos: right, it should make the situation a little bit better
[04:38] <cprov> carlos: yes, we could keep your branch in soyuz-production branch, even if it hurts my brain to maintain it up to date :(
[04:38] <kiko> we need to land that branch
[04:39] <daf> Alinux: looks like the line endings got messed up somehow
[04:39] <kiko> salgado-lunch to the rescue
[04:39] <daf> Alinux: did you perhaps edit the file on an Apple machine?
[04:39] <Alinux> daf, no
[04:39] <Alinux> Ubuntu
[04:39] <carlos> daf: but some lines are correct
[04:39] <daf> strange
[04:39] <Alinux> :(
[04:39] <daf> carlos: yes, almost all of them, I think
[04:39] <Alinux> I become mad with this gtk file
[04:40] <carlos> cprov: well, my branch is one line fix
[04:40] <daf> oh no, I'm wrong
[04:40] <carlos> cprov: I don't think it will cause you lots of problems....
[04:40] <daf> Alinux: did you get this file from Rosetta?
[04:40] <Alinux> and I will die...if I will able to retranslate everything :(
[04:40] <Alinux> daf, no from GNOME directly
[04:40] <cprov> carlos: one line + mine (16K lines), isn't it ?
[04:40] <daf> Alinux: weird
[04:40] <daf> Alinux: anyhow, I can fix the file for you
[04:41] <Alinux> daf, ? how dear ?
[04:41] <carlos> cprov: I mean that my patch will not be difficult to maintain... if it's a monster... that's another history...
[04:42] <carlos> Alinux: yea, it's a matter of change the ^M char by new line chars
[04:42] <daf> Alinux: http://muse.19inch.net/~daf/tmp/gtk20.po
[04:42] <daf> Alinux: see if that works for you
[04:42] <Alinux> daf
[04:42] <Alinux> ok
[04:42] <Alinux> I'll ty it
[04:42] <cprov> carlos: ehe, dude stop call soyuz-production "a monster", it's a nice branch, working stuff, almost magical :)
[04:42] <kiko> matsubara-lunch, is https://chinstrap.ubuntu.com/~jamesh/oops.cgi/2006-02-14/C507 familiar to you?
[04:43] <carlos> cprov: monster == big
[04:43] <carlos> ;-)
[04:43] <cprov> carlos: btw, did you get your test working properly yesterday ?
[04:43] <carlos> cprov: yes
[04:43] <daf> kiko: looks familiar
[04:43] <kiko> yeah
[04:43] <carlos> cprov: I wanted to talk with you to get it merged into your branch
[04:43] <carlos> cprov: but I'm still pushing it
[04:43] <kiko> I see 
[04:44] <cprov> carlos: very good, so upload/rosetta integration is working !
[04:44] <carlos> yes
[04:44] <daf> kiko: can't remember if it has a bug, though
[04:44] <carlos> cprov: but I had to do a transaction.commit()
[04:44] <carlos> cprov: to get the files from librarian
[04:44] <daf> kiko: you saw it in today's summary?
[04:44] <kiko> it does
[04:44] <cprov> carlos: yes, let's do it ... first I would like to fix that annoying failure, let's move to ##soyuz1.0
[04:44] <kiko> bug 4845
[04:44] <Alinux> daf, thank you brother !!! :) works!
[04:44] <Ubugtu> malone bug 4845 in malone "assigning of package bug targets needs input validation" [Normal,In progress]  http://launchpad.net/bugs/4845
[04:45] <Alinux>  intltool-update ka
[04:45] <Alinux> ....................................................... done.
[04:45] <Alinux> 530 translated messages, 1 fuzzy translation, 1 untranslated message.
[04:45] <daf> Alinux: great :)
[04:45] <Alinux> daf, where was the problem for curiosity ?
[04:45] <Alinux> :D
[04:45] <cprov> carlos: how did it affect the other tests ?
[04:45] <daf> Alinux: for some reasons, some newlines (ASCII 10) were converted to carriage returns in the file (ASCII 13)
[04:45] <Alinux> daf, or cn you tell me a good manual, or howto
[04:45] <Alinux> to don't make this errors?
[04:46] <daf> Alinux: the fix was to run: perl -i -p -e 's/\r/\n/g' on the file
[04:46] <daf> I don't know how it happened
[04:46] <Alinux> daf, :)
[04:46] <daf> maybe the file in GNOME CVS was bad
[04:46] <Alinux> strange...
[04:46] <daf> yes, very
[04:46] <daf> can you let us know if it happens again?
[04:46] <Alinux> daf, :)
[04:47] <Alinux> Yes bro, I'm in Ubuntu Georgian Team :)
[04:47] <Alinux> I'm with you all :)
[04:47] <daf> cool
[04:47] <Alinux> same team same passion :)
[04:47] <Alinux> but I'm newbie... as you see
[04:48] <Alinux> ;)
[04:48] <Alinux> http://svn.inet.ge/svn/ka_GE/ here is my Georgian repo
[04:48] <Alinux> when rosetta will ready for dapper...
[04:48] <daf> well, we all start off as newbies
[04:49] <Alinux> then I make mega updates :)
[04:49] <daf> Carlos and Celso are planning the Rosetta Dapper transition now
[04:49] <Alinux> daf, when ?
[04:49] <daf> it should be ready within the next 2 weeks
[04:49] <Alinux> now ?
[04:49] <Alinux> ah
[04:49] <Alinux> starting
[04:49] <Alinux> good nes carlos ;)
[04:49] <daf> yeah, I know, I want to translate dapper too
[04:49] <Alinux> news
[04:50] <Alinux> daf, do you know some good i18n resurces in a net ?
[04:50] <daf> hmm
[04:50] <Alinux> tips howtos triks?
[04:51] <daf> hmm
[04:51] <daf> the GTP has some good resources
[04:51] <daf> http://developer.gnome.org/projects/gtp/resources.html
[04:51] <daf> (I wrote one of them ;)
[04:52] <Alinux> daf, ;)
[04:52] <Alinux> daf, one very important question
[04:52] <Alinux> then I got cvs write acces on GNOME too...
[04:52] <Alinux> are ubuntus GNOME similar to mother GNOME ?
[04:53] <Alinux> how can I coordinate commits?
[04:53] <daf> they are similar, yes
[04:54] <daf> I suggest:
[04:54] <tvon> Ubuntu is pretty faithful to upstream gnome
[04:54] <daf> translate GNOME in Rosetta
[04:54] <daf> export the PO files, commit them to CVS
[04:54] <daf> Ubuntu will use them automatically
[04:55] <Alinux> daf, I translate locally, cause it's faster with gtranslator... then I import translation into rosetta and after that... commit into gnome cvs 
[04:55] <Alinux>  :)
[04:55] <Alinux> ow abot this way?
[04:55] <daf> that's fine
[04:55] <Alinux> ah good
[04:55] <Alinux> cause normally ubuntus gnome has + things
[04:55] <daf> you know about l10n-status.gnome.org, right?
[04:56] <Alinux> so in gnome + things will be ignored :)
[04:56] <Alinux> http://l10n-status.gnome.org/gnome-2.14/ka/index.html
[04:56] <Alinux> poor georgian translations :)
[04:57] <Alinux> :) our coordinator is a hero :)
[04:57] <Alinux> 2 years ...nothing commited :)
[04:57] <daf> !
[04:57] <daf> ow
[04:57] <Alinux> he is a M$ guy :)
[04:57] <daf> perhaps it's time for a new coordinator
[04:57] <Alinux> I'm talking on gnome list abut this...
[04:57] <daf> good idea
[04:57] <Alinux> there is a war ...
[04:58] <daf> ah...
[04:58] <Alinux> Christian and Danilo are not happy with it..
[04:58] <daf> well, they're good guys
[04:58] <Alinux> so maybe I or my friend will be new coordinators...
[04:59] <Alinux>   Catalan
[04:59] <Alinux> 
[04:59] <Alinux> Jordi Mallach and Josep Puigdemont 
[04:59] <Alinux> I would like Catalan situation
[04:59] <Alinux> one coordinator + svn acces helper.
[04:59] <jordi> heh
[05:00] <jordi> we're pretty healthy right now
[05:00] <Alinux> jordi, respect :)
[05:00] <Alinux> josep is great guy...
[05:00] <Alinux> he helps me a lot.
[05:00] <kiko-fud> matsubara-lunch, so, is bug 4845 really in progress? :-)
[05:00] <Ubugtu> malone bug 4845 in malone "assigning of package bug targets needs input validation" [Normal,In progress]  http://launchpad.net/bugs/4845
[05:00] <Alinux> you catalans are similar to georgians :)
[05:00] <jordi> kiko-fud: so, soonish there'll be a third Portuguese variant in the launchpad.
[05:00] <jordi> Alinux: does he?
[05:01] <Alinux> smal number of people, but great patriots of own language :)
[05:01] <Alinux> jordi, yes...
[05:01] <jordi> it's the only way, or we'd be ruled out by Spanish.
[05:01] <Alinux> he supports me a lot :) in this Saint war too :)
[05:01] <Alinux> similar situation with Bascues
[05:02] <Alinux> I like them too :)
[05:02] <jordi> their level of translation isn't as good though.
[05:02] <jordi> They don't have as many volunteers
[05:02] <Alinux> jordi, heh
[05:02] <Alinux> the same situation by us...
[05:03] <Alinux> :) m$ coordiantors... liar aparent colaboration :)
[05:03] <Alinux> blergh!
[05:04] <Alinux> ok boys...thank you a lot...I'll continue .po file updateing :)
[05:04] <Alinux> god bless you all...
[05:05] <jordi> laters
[05:05] <Alinux> daf, jordi, thanks!
[05:05] <Alinux> :)
[05:06] <daf> no problem
[05:17] <Alinux> can someone tell me which source package provides gtk20-properties.po?
[05:18] <Alinux> dpkg -S /usr/share/locale-langpack/it/LC_MESSAGES/gtk20-properties.mo
[05:18] <Alinux> language-pack-gnome-it-base: /usr/share/locale-langpack/it/LC_MESSAGES/gtk20-properties.mo
[05:18] <Alinux> but it's not enough :)
[05:18] <Alinux> I must download a source code to update a .po file.
[05:19] <daf> it's in the same package as gtk20
[05:19] <daf> is there a problem with downloading from l10n-status.gnome.org?
[05:20] <Alinux> daf, for example
[05:20] <Alinux> I have an old gtk20-properties.po file
[05:20] <Alinux> and I can donload gtk20-properties.pot file from l10n-status.gnome.org
[05:21] <Alinux> how can I refresh gtk20-properties.po  using gtk20-properties.pot file ?
[05:21] <Alinux> I know only source download and inttool-update xy
[05:21] <Alinux> method
[05:22] <Alinux> daf, maybe there is some other better and faster way ?
[05:22] <daf> ah
[05:22] <daf> there is a way
[05:22] <Alinux> ??? :D
[05:24] <daf> msgfmt -U ka.po gtk20-properties.pot
[05:24] <daf> er
[05:24] <daf> I meant:
[05:24] <matsubara> kiko-fud: yes, it is. I worked on it for some time, but had to re-schedule some priorities. It seems it is a oops report bug, so I'll take care of it soon. :-)
[05:24] <daf> msgmerge -U ka.po gtk20-properties.pot
[05:25] <daf> carlos: 90 occurrences of timeouts on RequestQueryTimedOut: ERROR: canceling query due to user request SELECT DISTINCT POSubmission.id FROM POSubmission JOIN POMsgSet ON... yesterday
[05:26] <AlinuxOS> daf, ;)
[05:26] <AlinuxOS> magic
[05:26] <AlinuxOS> thak you!
[05:26] <AlinuxOS> probing right now
[05:27] <kiko-fud> matsubara, thanks.
[05:29] <carlos> daf: that's a problem with suggestions
[05:29] <carlos> know bug and already started the fix, well, another one
[05:33] <daf> carlos: right; what's the ETA on that?
[05:35] <carlos> daf: tomorrow I will request a review for it
[05:35] <lamont> Kinnison: is there any thought of importing the old buildlogs into launchpad?
[05:36] <Kinnison> lamont: no reason why it could not be done, no thought/effort gone into it so far
[05:36] <lamont> right.  feel free to harvest http://people.u.c/~lamont/buildLogs whenever - if you tell me they're all in launchpad, then I can nuke the tree.
[05:37] <lamont> hrm... actually, the suites still being built in DAK will continue to populate that tree....
[05:45] <daf> stub: which revisions went live today?
[05:46] <bradb> jbailey: So:
[05:46] <salgado> daf, 3123 with 3126 and 3128 cherry picked
[05:46] <bradb> bug 2245
[05:46] <Ubugtu> malone bug 2245 in malone "No list of interesting (to me) bugs" [Normal,Needs info]  http://launchpad.net/bugs/2245
[05:47] <salgado> that's what kiko's report says
[05:47] <bradb> bug 31414
[05:47] <Ubugtu> malone bug 31414 in malone "Source and Binary Package Name on the +editstatus page are confusing" [Normal,Unconfirmed]  http://launchpad.net/bugs/31414
[05:47] <bradb> bug 29176
[05:47] <Ubugtu> malone bug 29176 in malone "Changing source package doesn't notify the new bug contact about the change" [Normal,Confirmed]  http://launchpad.net/bugs/29176
[05:47] <bradb> bug 31415
[05:47] <Ubugtu> malone bug 31415 in launchpad "jbailey suggested Launchpad should have a News page or developer blog" [Normal,Unconfirmed]  http://launchpad.net/bugs/31415
[05:49] <jbailey> bradb: 'jbailey suggests'.  Is the bug assigned against me?  Will I be patched until I no longer have this request?
[05:49] <jbailey> Starting with ducttape on the mouth, followed by tying me to a chair?
[05:50] <bradb> heh
[05:50] <bradb> Always better to frame things in terms of specific users, in any case.
[05:51] <daf> salgado: thanks
[05:51] <daf> salgado: how do you know that, by the way?
[05:51] <salgado> daf, kiko's report
[05:51] <daf> oh, right
[05:51] <kiko> somebody needs to do it
[05:51] <salgado> and somebody needs to read it
[05:52] <kiko> I pay people extra just to read them
[05:56] <daf> ah, that means matsubara's fixws for #31039, #31158 and #31324 missed out
[05:57] <daf> still, fix released for 7/33 of our OOPS bugs
[05:59] <salgado> kiko, can you get me a dump of production or staging db?
[05:59] <kiko> a dump would be a stub request
[05:59] <salgado> I need the publishing records in order to test with a real mirror
[06:00] <kiko> I see.
[06:01] <kiko> there are dumps on asuka somewhere I believe
[06:01] <salgado> I don't have access to asuka, though
[06:03] <kiko> kiko@asuka:~$ ls -l /var/lib/postgresql/launchpad_prod.dump
[06:03] <kiko> -rw-r--r--  1 postgres postgres 6638735337 Jan 31 16:27 /var/lib/postgresql/launchpad_prod.dump
[06:03] <kiko> salgado, you sure you want that dump?
[06:04] <mantiena-baltix> Hi all
[06:04] <mantiena-baltix> doko, are you online ?
[06:04] <salgado> kiko, maybe not
[06:05] <kiko> I can try and gzip it 
[06:05] <kiko> it will still be at least 2gigs
[06:06] <salgado> 2gigs means two days to download it. I'll find another way
[06:06] <kiko> I can do a dump of that specific table...
[06:07] <salgado> I guess I'd still need quite a few other tables referenced by that one
[06:08] <kiko> you would.
[06:08] <kiko> you could ask cprov to do a run on drescher for you.
[06:08] <kiko> how does that sound?
[06:09] <salgado> and then I access drescher's postgres directly?
[06:10] <cprov> salgado: what do you need in drescher ?
[06:11] <salgado> cprov, the publishing records so I can test the mirror prober against a real mirror
[06:11] <kiko> salgado, no, drescher uses production. is that a problem?
[06:11] <kiko> salgado, can you run it in read-only mode?
[06:11] <cprov> salgado: couldn't you wait until tomorrow ? we will have a production code for playing in mawson
[06:12] <cprov> I mean prodcution DB copy 
[06:12] <kiko> I guess we can wait, yeah
[06:13] <salgado> yes, I think that'd be better
[06:13] <cprov> salgado: we also need to ensure mawson has external access for mirror probing, maybe you can already submit an RT and get it done by tomorrow 
[06:13] <doko> mantiena-baltix: yes
[06:17] <cprov> kiko: we can share mawson as a production **sand_box**, free playing with controlled production DB copy. btw, "dogfood" term has lost its meaness now, every tool is released
[06:17] <kiko> cprov, let's call it sandbox, I'm happy
[06:18] <mantiena-baltix> doko, could you tell me, what I should do if I wanna backport newest OpenOffice.org2 from dapper to ubuntu breezy
[06:18] <cprov> kiko: fine
[06:18] <kiko> salgado, talk to Znarl, I've pinged him on #canonical.
[06:18] <Znarl> salgado : Hello.
[06:19] <salgado> hi Znarl. I explained what I need on #canonical
[06:19] <mantiena-baltix> doko, I get some error when I try to compile latest dapper version (but some OOo 2.0.1 release candidate compiles fine)
[06:21] <mantiena-baltix> Kamion, hi, maybe you know who implemented cd integrity check in ubuntu dapper live CD ?
[06:26] <Kamion> mantiena-baltix: this isn't an appropriate channel for this question, and I don't pay attention here much - had to scroll through a couple of hundred pages of scrollback to reach that
[06:26] <Kamion> mantiena-baltix: but the answer is Mithrandir
[06:26] <kiko> Kamion, is it appropriate to ask you about the status of the CoC here, however? ;-)
[06:27] <Kamion> kiko: didn't I already mail you?
[06:27] <kiko> nope :)
[06:27] <Kamion> oh man, I suc
[06:27] <Kamion> k
[06:27] <Kamion> as does my k key
[06:28] <kiko> aha! your k key is more reliable than your CoC emails!
[06:28] <doko> mantiena-baltix: this seems to be off topic for this channel
[06:29] <kiko> hey BjornT?
[06:29] <BjornT> hi kiko 
[06:29] <doko> mantiena-baltix: why do you want to make a separate backport?
[06:31] <Kamion> kiko: OK, mailed to launchpad@ now, sorry about that - really thought I'd done it already
[06:31] <kiko> no problemo
[06:31] <kiko> BjornT, does the support tracker have outgoing email yet?
[06:31] <kiko> or just incoming?
[06:33] <BjornT> kiko: it has outgoing as well, but only to the ticket's subscribers. what's lacking is the equivalent to 'bug contacts' for support. i'm planning to get that done this or next week.
[06:33] <kiko> I see. thanks.
[06:33] <kiko> BjornT, and they would be attached to what, product and package names in a distro?
[06:34] <mantiena-baltix> Kamion, thans
[06:35] <kiko> BjornT, and what else of STT is missing implementing?
[06:36] <BjornT> kiko: yes, and distro-wide as well
[06:36] <kiko> I see.
[06:37] <kiko> daf, is there an HTML version of jamesh' reports?!
[06:38] <BjornT> kiko: still left re STT is the tracking of which comment that was the actual answer and the automatic closing of inactive tickets.
[06:39] <kiko> BjornT, so we don't track yet who answered the question?
[06:39] <BjornT> kiko: no. well, at the moment it's assumed to be the last (non-submitter) who commented on the ticket.
[06:40] <kiko> I see
[06:41] <kiko> hey 
[06:42] <kiko> has anyone tried to run single stories based on spiv/lifeless' landing this week?
[06:42] <mantiena-baltix> doko, because there are important bugs in backport from people.ubuntu.com/~doko and I wanna fix these bugs. I can use OOo sources from people.ubuntu.com/~doko backport, but it seems in sources ubuntu dapper contains more patches ;)
[06:44] <carlos> see you!
[06:47] <bradb> kiko: Hm, it may have broken our test runner.
[06:47] <bradb> I just tried: python test.py -f --test=^10-set-upstream
[06:47] <bradb> And it ran 0 tests, even though:
[06:47] <bradb> bradb@oxygen:~/canonical/malone-bug-contacts-report/lib/canonical/launchpad/pagetests $ find . -name "*10-set-upstream*"
[06:47] <bradb> ./initial-bug-contacts/10-set-upstream-bugcontact.txt
[06:48] <kiko> bradb, that seems unfortunate. can you confirm?
[06:48] <bradb> python test.py -f --test=^person-bug-pag works as expected. Runs 1 test. /me tries other things.
[06:49] <bradb> Damn, "python test.py -f --test=^20-file-upstream-bug.txt" runs 0 tests.
[06:50] <kiko> borkage?
[06:50] <bradb> Yeah. It'd take somewhat more time to see what's going on, so I should probably just email spiv.
[06:51] <mantiena-baltix> doko, for example there are no fontwork and no gallery in latest ubuntu dapper OOo 2.0.1 and in backport from people.ubuntu.com/~doko :(
[06:51] <kiko> bradb, sounds about right -- spiv and lifeless.
[06:51] <bradb> kiko: right
[06:54] <bradb> Ah right, it was indeed lifeless who landed it too. I thought it was spiv.
[06:56] <kiko> it was both of them :)
[06:57] <daf> kiko: totally
[06:58] <kiko> which part super daf?
[06:58] <daf> https://chinstrap.ubuntu.com/~jamesh/oops-summaries/
[06:58] <kiko> rock and rollsin
[06:58] <kiko> wow, that is great
[06:59] <daf> isn't it?
[07:01] <kiko> yeah, totally
[07:02] <kiko> BjornT, tell me about bug 29176
[07:02] <Ubugtu> malone bug 29176 in malone "Changing source package doesn't notify the new bug contact about the change" [Normal,Confirmed]  http://launchpad.net/bugs/29176
[07:02] <kiko> BjornT, is the real problem that we don't subscribe the new bug contact?
[07:18] <BjornT> kiko: yes, that is correct
[07:20] <bradb> kiko: Explicit bug contact subscriptions cause these problems: 1. a bug contact does not get subscribed to all bugs, until we do more work and add more UI to make it so, 2. deciding that you no longer want to be a bug contact means you will continue to get bugmail from the existing bugs unless we add more code and UI to ask if the user wants to delete their existing subs 3. it's more effort to distinguish between a bug the user cho
[07:20] <bradb> All of these issues go away with implicit subscriptions.
[07:21] <bradb> (not too mention the extra work jamesh_ did to manually add Cc's for existing bug reports, which would have been unnecessary if the sub's were explicit.)
[07:22] <bradb> s/were explicit/were implicit/
[07:36] <Kamion> bradb: cut off at "a bug the user cho"
[07:37] <bradb> 3. it's more effort to distinguish between a bug the user chose to sub to vs. one they were sub'd to as a bug contact and 4. bug 29176.
[07:37] <Ubugtu> malone bug 29176 in malone "Changing source package doesn't notify the new bug contact about the change" [Normal,Confirmed]  http://launchpad.net/bugs/29176
[07:43] <kiko> bradb, I love your crusading for implicit subscriptions :)
[07:47] <bradb> "Crusade" makes it sound religious. Just going by the information I've collected.
[07:48] <bradb> (Including a phone convo this morning with jbailey, outlining some of the key problems he's having with Malone, where he specificially asked me if they could be made implicit. :)
[08:01] <SteveA> matsubara: those are excellent support emails
[08:01] <matsubara> SteveA: thanks.
[08:09] <mpt_> good evening SteveA 
[08:10] <SteveA> hello mpt_ 
[08:13] <mpt_> SteveA, I logged in to the DI-624 admin interface (completely different from the DSL-302G one!) and changed it to WEP, and now even DHCP doesn't work
[08:13] <SteveA> don't change it to WEP
[08:13] <SteveA> turn it off
[08:13] <mpt_> oh, ok
[08:15] <daf> "my router doesn't work if I do this"
[08:15] <daf> "don't do that"
[08:17] <SteveA> does your linux machine connect?
[08:19] <mpt_> Now DNS but nothing else
[08:19] <mpt_> just like when it was on WPA
[08:19] <mpt_> this is nuts
[08:20] <SteveA> mpt_: this will be easier now
[08:20] <SteveA> because there is no supplicant thing to worry about
[08:20] <SteveA> can we get skype going again?
[08:20] <mpt_> right, though I'd be surprised if that was the problem
[08:20] <mpt_> since it was working before
[08:20] <mpt_> sure
[08:45] <ddaa> hey SteveA, did you get in touch with mdz about non-MAIN imports?
[08:47] <mdz> no
[08:48] <ddaa> mdz: well, I guess we can settle this here and now.
[08:48] <mdz> what is the question?
[08:48] <ddaa> mdz: as you might know, the transition of the RCS import infrastructure (importd) to bzr has been delayed. I'm currently in the final stages of planning the transition again.
[08:49] <ddaa> In Montreal, fabbione and niemeyer insisted that imports for non-MAIN branches be high priority.
[08:50] <ddaa> Generally, we would like to postpone any new feature until the whole importd system works with bzr end-to-end. The initial phase will use baz as an intermediate step.
[08:51] <ddaa> However I wanted the plan to include provisions for the case where would have to do non-MAIN imports before that.
[08:51] <ddaa> But lifeless and SteveA said I should not.
[08:52] <ddaa> mdz: so, we need to know how serious the need for non-MAIN RCS imports is, and whether it's likely that we would have to do something about it while we are in transition.
[08:53] <ddaa> Note that native end-to-end bzr imports is likely to take several months.
[08:53] <ddaa> mdz: maybe SteveA would be able to formulate the issue better than I...
[08:54] <mdz> I don't have a very clear idea offhand of how many of our upstream sources come from MAIN branches and how many non-MAIN
[08:55] <mdz> so it's difficult to say how critical it is for the plan
[08:55] <mdz> it should be possible to do that analysis and base your decision on the result
[08:55] <ddaa> mpf...
[08:55] <mdz> I understood that there was a widget somewhere which would guess at the correspondence between a tree from a tarball and an RCS revision
[08:56] <ddaa> mdz: that's a latter step of non-MAIN import support.
[08:56] <ddaa> anyway, analysis to know whether we should do an analysis... too much indirection
[08:57] <mdz> maybe I misunderstand the terminology, but I would expect that non-MAIN import support would have end-to-end importd functionality as a prerequisite
[08:57] <mdz> but in that case this question would be moot
[08:57] <ddaa> mdz: there actually was some bare-bone support for non-MAIN imports in Arch, in the past. But then there was a regression that was never fixed.
[08:58] <mdz> but surely we aren't going to invest resources in fixing up Arch imports rather than working on bzr imports
[08:58] <ddaa> bare-bones: need to figure out the branch point manually and do a lot of manual prodding to get the stuff in shape.
[08:59] <mdz> tech board meeting is starting now, will be back later
[09:00] <ddaa> mdz: definitely, before there _are_ bzr imports, nothing happens. The question is what might happen while there are bzr imports, but behind the scenes something that kills puppies every day using baz as an intermediate.
[09:08] <ddaa> lifeless: 
[09:09] <ddaa> lifeless: hey, I'll be around late today, that might be a good day to do some ping-pong over the open issues for the bzr transition plan.
[09:09] <lifeless> ok
[09:11] <mpt> SteveA, that works
[09:12] <SteveA> i see
[09:12] <SteveA> that is interesting
[09:12] <SteveA> here is what i suspect
[09:13] <SteveA> i suspect that the router has in some way run out of routable addresses
[09:13] <SteveA> and is doing some kind of bridging
[09:13] <SteveA> so that the hardware addresses are visible to the ISP, perhaps
[09:13] <SteveA> so, we have established that it is not a problem with your computer or your set-up
[09:14] <SteveA> you can check this by re-requesting a dhcp lease
[09:14] <SteveA> dhclient eth0
[09:14] <SteveA> and checking that you can still do stuff afterward
 Worked after one DHCPNAK
[09:15] <SteveA> ok
[09:15] <SteveA> cool
[09:16] <SteveA> so, there is definitely some limit to how many computers you can connect, given the current set-up of your router
[09:16] <SteveA> you may be able to reconfigure the router to not do any kind of bridging
[09:16] <SteveA> so that it would look to the ISP like a single computer
[09:16] <SteveA> i'm not totally sure that this is the issue, but it is one possibility
[09:17] <SteveA> anyhow, right now, you can effectively use either your mac or your ubuntu machine
[09:17] <SteveA> by setting the ubuntu machine to use that mac address
[09:18] <mpt_> but not both at the same time?
[09:19] <SteveA> not with the same mac address, no
[09:19] <mpt_> the wireless admin interface says that DHCP server is disabled
[09:20] <SteveA> okay
[09:20] <SteveA> so you are getting dhcp from the ISP
[09:20] <SteveA> the solution is to reconfigure the router to do its own internal dhcp and NAT
[09:21] <mpt_> i.e. checking the "Enabled" radiobutton? :-)
[09:22] <SteveA> perhaps.  perhaps not
[09:22] <SteveA> next thing, change the mac address back on the linux machine, and restart the mac
[09:22] <SteveA> then call me again
[09:23] <mpt_> ok
[10:03] <ddaa> stub: can you delete this branch, please? https://launchpad.net/people/soto/+branch/sympa/sympa-4.1
[10:04] <ddaa> WHOT?
[10:05] <ddaa> holy freakin shit! I cannot approve new RCS imports :(
[10:06] <ddaa> oh yes I can
[10:06] <ddaa> there's just a bug that causes Launchpad to display "request ignored, you must specify a source package"
[10:07] <ddaa> "Failure: changes applied but I'll pretend not so you get angry"
[10:08] <ddaa> Somebody has been playing Mao with a lying rule...
[10:32] <SteveA> mpt: so, do you have both computers connected now?
[10:36] <SteveA> mpt: so, is it working?
[10:39] <mpt> no, but resolv.conf says 192.168.0.1 when on the Mac it says 10.1.1.1
[10:39] <mpt> SteveA: that's after successful dhclient eth0
[10:40] <SteveA> for now, just edit resolv.conf
[10:41] <dilys> Merge to devel/launchpad/: [trivial]  fix bug # 30458, fix PENDING builds ordering, improve buildd-system tests (r3142: Celso Providelo)
[10:42] <mpt> SteveA, still no routing
[10:43] <elmo> cprov: did someone already report a bug about buildds not restarting on reboot?
[10:43] <cprov> elmo: not yet, I can fix the package ...
[10:43] <mpt> SteveA, and running dhclient sets resolv.conf back to 192.168.0.1
[10:43] <SteveA> mpt: pardon?
[10:44] <cprov> elmo: but report it please 
[10:44] <mpt> SteveA, as in pinging 148.88.8.6 does nothing
[10:44] <SteveA> mpt: just a sec
[10:44] <SteveA>  /join #c-m