[02:35] <AlinuxOS> alive?
[02:35] <AlinuxOS> :D
[06:15] <dilys> Merge to devel/launchpad/: [trivial]  Update Librarian front page (r3023: Stuart Bishop)
[07:43] <jblack> Hypothetical question...
[07:43] <jblack> If somebody attached a bzr branch to the wrong product.. how does one move it? 
[07:47] <spiv> jblack: There's an "Administer" link
[07:47] <jblack> Ahh. I see it now. Thanks
[07:56] <jblack> Oh cool. I have two launchpad accounts
[07:58] <spiv> You should be able to merge them.
[08:01] <jblack> I'm not quite sure how I ended up with a "name79" anyways.
[08:24] <carlos> morning
[09:44] <SteveA> hi
[09:51] <Kinnison> Urgh
[09:51] <jblack> Granted, I'm not a rockstar, but me waving shouldn't cause waves of nausea...
[09:52] <jblack> kinnison: Do you have a blog? 
[09:53] <SteveA> stub: voice call sometime today?
[09:54] <stub> SteveA: Sure
[09:54] <Kinnison> jblack: yes
[09:54] <Kinnison> jblack: blog.digital-scurf.org
[09:55] <jblack> do you have rss? 
[09:57] <Kinnison> jblack: atom
[09:57] <Kinnison> jblack: why?
[09:57] <jblack> I'd like to add it to planet.revisioncontrol.net
[09:58] <jblack> I need a feed if I'm to do so. Random guessing didn't work
[09:58] <Kinnison> aah
[09:58] <Kinnison> Use http://blog.digital-scurf.org/?flav=atom&planet=revisioncontrol.net please
[09:59] <jblack> even though its ironically not a planet?
[09:59] <SteveA> an artificial planet?
[09:59] <SteveA> "That's no moon!"
[10:00] <Kinnison> jblack: I use the "planet" thing to offer filtering
[10:00] <Kinnison> jblack: In the future, my blog will refuse to serve content without a planet argument which matches the source IP I designate for that planet
[10:15] <BjornT> any reviewer available for a small review? (preventing bugs from locking up the email interface)
[10:22] <kiko> morning
[10:22] <kiko> SteveA!
[10:22] <kiko> stub!
[10:22] <stub> kiko!
[10:22] <kiko> how goes it guys?
[10:23] <mdz> terrible
[10:23] <mdz> my mail is fucked
[10:23] <kiko> complainer
[10:23] <carlos> jordi, ping
[10:23] <jblack> postfix? 
[10:23] <kiko> stub, tell me about gina on production
[10:23] <kiko> also, stub 
[10:24] <kiko> I think we'll be running the initial soyuz run off celso's branch while we work on the review for merging
[10:24] <kiko> so I guess we should just rollout from last week -- or perhaps you want to roll out later this week and pick up your change that fixes celebrities?
[10:26] <stub> kiko: Gina is running daily on drescher, importing *-security, *-updates, *-backports as well as dapper
[10:26] <kiko> stub, why do we get no log output?
[10:26] <stub> Because it isn't producing any?
[10:27] <kiko> I find that a bit remarkable
[10:27] <stub> We are not running -v, so we will only see warnings and errors
[10:27] <kiko> but warnings are very common
[10:27] <stub> I can run it with -v for a day or three to see what happens
[10:27] <kiko> that would be k-rad
[10:28] <Kinnison> Which ideally will be in ca. 36 hours (not set in stone)
[10:30] <SteveA> kiko: hey
[10:30] <kiko> stub, gina hasn't imported any packages since 2006-01-15
[10:31] <kiko> and the last "publishing" was in 2005-12-22
[10:31] <SteveA> they have different hours in canada?
[10:31] <kiko> hey SteveA 
[10:31] <kiko> SteveA, he meant circa
[10:31] <Kinnison> kiko: Erm, that's not good
[10:32] <kiko> that's what launchpad_prod says anyway
[10:33] <Kinnison> blurgh
[10:33] <kiko> stub, is that what you expected to see?
[10:34] <stub> cron output isn't happening from drescher :-/
[10:34] <Kinnison> erm, gina's running on drescher?
[10:34] <kiko> stub, ah, that's more like it.
[10:35] <stub> All stuck in mailq
[10:37] <carlos> stub, hi, is the launchpad_carlos db ready to use?
[10:37] <kiko> stub, why did we decide to run gina on drescher?
[10:45] <stub> kiko: Because we need to run it somewhere, and that is the box earmarked for this sort of thing (gina, publisher etc.)
[10:45] <kiko> stub, cool.
[10:45] <kiko> so any clue why she isn't running?
[10:45] <kiko> have you been rolling out to drescher too?
[10:46] <Kinnison> stub: the instance you're running gina from -- where is that?
[10:47] <kiko> ok
[10:49] <stub> carlos: almost ready - data is there, just need to setup the permissions. just sorting gina first.
[10:49] <stub> Kinnison: /srv/launchpad.net/gina
[10:49] <carlos> stub, ok
[10:49] <Kinnison> stub: Right
[10:49] <Kinnison> stub: and which path is she reading the archive from?
[10:50] <jordi> carlos: pong
[10:50] <stub> kiko: I haven't been updating the codebase on rollouts - I'd assumed she was running happily
[10:51] <kiko> stub, I would imagine she'd need to stay updated with schema changes etc, though I guess there hasn't been one recently
[10:51] <seb128> hi
[10:51] <kiko> anyway
[10:51] <seb128> is launchpad broken atm?
[10:51] <kiko> I think it makes sense to roll out to drescher consistently with the rest of the webapp
[10:51] <Kinnison> seb128: seems to load for me. What page isn't working for you?
[10:51] <seb128> I get timeout pages while trying to do changes
[10:51] <carlos> jordi, could you answer to Simon Michael about the rosetta vs. upstream translations? 
[10:51] <seb128> OOPS-24A202
[10:51] <kiko> seb128, not entirely broken, but tell me an oops id
[10:51] <carlos> jordi, I think you asked about that already to me
[10:51] <kiko> ah
[10:52] <seb128> if you need the oops
[10:52] <carlos> but I don't see an answer to that email
[10:52] <seb128> that's while trying to edit settings for #29515
[10:55] <Kinnison> stub: I repeat -- Which archive path are you reading from for gina? (or are you waiting for a code update in order to tell me that?)
[10:55] <stub>             root /srv/archive.ubuntu.com/www/ubuntu
[10:56] <stub> (this is configs/gina/launchpad.conf)
[10:57] <jordi> carlos: I will
[10:57] <carlos> jordi, thanks
[10:57] <Kinnison> stub: right
[10:58] <Kinnison> Which user do you run gina as?
[10:59] <seb128> kiko: it works now ...
[11:02] <stub> Thailand's international connection is really sucky today :-/
[11:14] <Kinnison> stub: you use lp_import for gina runs?
[11:15] <stub> I assumed so
[11:15] <stub> (there wasn't a gina account on the box)
[11:15] <Kinnison> Thanks
[11:15] <Kinnison> That's perfect
[11:16] <Kinnison> Nope
[11:16] <Kinnison> It's exactly the right user for you to use
[11:17] <Kinnison> s/htis/this/
[11:17] <stub> Yay... fresh code
[11:34] <kiko> stub, what's going on?
[11:35] <stub> Just finished reconfiguring gina's launchpad.conf, which had grown hair (damn required elements) and fired off Gina
[11:35] <stub> I'm logging since we won't see cron output until elmo or Znarl get a chance to look at that box
[11:36] <kiko> okay cool
[11:36] <stub> Oops. Connection refused exceptions when attempting to upload to the Librarian
[11:36] <kiko> stub, it's fixed already -- I asked elmo.
[11:36] <kiko> stub, heh :)
[11:36] <kiko> and he has delivered the goods he says
[11:42] <matsubara> good morning!
[11:45] <BjornT> stub: would you have time to take a quick look at my process-email fix? (and then roll it out later)
[11:46] <stub> BjornT: Sure. I'd like to delay rollout until tomorrow though a the network is being flaky today
[11:47] <BjornT> stub: ok, that's cool. i'll mail you the diff.
[11:50] <kiko> SteveA?
[11:54] <kiko> where's jamesh?
[11:54] <kiko> hey matsubara 
[11:54] <Kinnison> kiko lives in a personal void
[11:54] <Kinnison> sorry, personnel void
[11:56] <matsubara> kiko: hey, how's london?
[11:57] <kiko> it sucks
[11:57] <kiko> it's freezing
[11:57] <kiko> there are no naked girls
[11:57] <kiko> and the shower doesn't work properly
[11:57] <kiko> (probably explains why there are no naked girls)
[11:58] <stub> Come to Bangkok. Its 30 degrees and there are naked girls.
[11:58] <kiko> in fact
[11:58] <kiko> the only good thing about london is the bandwidth to the datacenter
[11:59] <Kinnison> It's more the lack of latency
[11:59] <Znarl> We have very good international bandwidth so I'm supprised it's an issue.
[12:00] <dilys> Merge to devel/launchpad/: [trivial]  Production gina config updates (r3024: Stuart Bishop)
[12:00] <kiko> Znarl, other countries don't, though.
[12:01] <Kinnison> Znarl: brazil's internet connection is two bits of wet twine, strung between the thighs of a columbian drug lord
[12:01] <kiko> shut up already
[12:01] <Kinnison> dude, it's only funny 'cos it's true
[12:02] <kiko> stub, what revision are you intending to cut the production rollout on, do you know?
[12:03] <stub> kiko: 3018 for sure - possibly later as there is at least one thing that should be cherry picked (3021 - the celebrity optimization)
[12:03] <stub> And BjornT's email fix when it lands
[12:03] <kiko> stub, when you know will you tell me so I can finish off the report?
[12:04] <stub> 3018 plus those two cherry picks should do it. I've got nothing else flagged.
[12:04] <kiko> I have done till 3018. 
[12:04] <kiko> cool.
[12:04] <kiko> are you confident the celebrities fix will work 100%?
[12:04] <stub> carlos: what box do you need to connect to that database from again?
[12:05] <stub> kiko: Its running on staging, so worst case is the optimization doesn't.
[12:05] <kiko> stub, you know, it would be cool to be able to generate a oops on demand
[12:05] <stub> We could leave it a week easily enough, but I expect you are right and that it will help a lot of the OOPS timeouts we currently see
[12:06] <kiko> because then we'd be able to tell if the optimization works
[12:06] <kiko> stub, is there a page that is particularly bad on staging that I'd manage to get an oops on while insisting?
[12:06] <stub> There is a test that does that I think - jamesh's db_timeout tests use it
[12:07] <SteveA>  url?oopsplease=1
[12:07] <stub> I'm not aware of pages that can reliably generate timeouts at the moment - one of the bug reports could do it
[12:07] <stub> If you just want an oops, go to https://launchpad.net/idontexist
[12:07] <kiko> man staging is SLOW
[12:10] <stub> carlos: that db should be available to you now from mawson
[12:12] <kiko> so staging is busted. stub?
[12:12] <stub> it is?
[12:13] <kiko> I mean, my ping is 45ms to it.
[12:13] <kiko> no reply for the last 5 minutes
[12:14] <stub> kiko: Fixed. Looks like it had failed to shutdown properly before.
[12:14] <kiko> thanks man
[12:15] <kiko> hmph
[12:17] <kiko> I ROCK
[12:17] <kiko> OOPS-24S1
[12:17] <kiko> it is so easy to cause a timeout
[12:17] <kiko> just try to find a person named "a" in +editstatus
[12:24] <stub> BjornT: You are just deleting the email when you can't create an email.Message instance. The message should have been stuffed into the Librarian before this happens so that we can examine the dud email.
[12:27] <kiko> stub, by the way, the query that timed out for me in staging, it's on the same query as I posted to email :)
[12:28] <kiko> stub, I see /no/ query for celebrities in my timeout, which is pretty remarkable
[12:29] <kiko> are they cached once per instance or something?
[12:29] <kiko> no that can't be
[12:29] <stub> If it is a public page, it might not need to use any of them
[12:29] <kiko> it's +editstatus
[12:30] <kiko> SteveA, stub, spiv: what's happening to jamesh' fix that nukes out __len__?
[12:31] <stub> There should be one request per request per celebrity accessed. I would expect most pages to at least need to access the launchpad developers celebrity, as this is queried at the start of each request if you are authenticated.
[12:31] <kiko> sorry can you repeat that stub, I lost that line
[12:31] <stub> There should be one request per request per celebrity accessed. I would expect most pages to at least need to access the launchpad developers celebrity, as this is queried at the start of each request if you are authenticated.
[12:31] <kiko> and admins?
[12:31] <stub> one db request per http request
[12:31] <kiko> sounds perfect, but it doesn't show up in this oops report:
[12:32] <kiko> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/2006-01-24/S1
[12:32] <kiko> the next big win in terms of number of queries would be caching the inTeam query.
[12:32] <BjornT> stub: true. although, instead of going through the trouble of uploading it to the librarian, i think it's enough to simply print the raw message in the log. would that be ok? (i don't think that error will happen often, so far it's never happened afaik)
[12:32] <kiko> I think that would probably be okay -- what do you think stub?
[12:32] <stub> kiko: You can't see them because they are now by id
[12:33] <kiko> oh that's the first two queries now?
[12:33] <carlos> stub, thanks, it works!
[12:33] <carlos> stub, so I should ping you every time I want an update?
[12:33] <stub> BjornT: If it is a large message, it will be lost. And then you have to worry about encoding etc. I think it would be better to simply move the 'stuff this in the librarian' section up a few lines.
[12:34] <SteveA> stub: when i land some Crowds security updates, we'll need just celebrity ids a lot of the time
[12:34] <carlos> stub, isn't it possible to get an update weekly? (that's what I need to run a cron job)
[12:34] <stub> 15158 is the launchpad developers team
[12:34] <stub> carlos: Yes - I will automate it, but I havn't done it yet. So ping me next week in case I haven't
[12:34] <carlos> stub, ok, thanks
[12:36] <BjornT> stub: ok, i'll do that then.
[12:36] <stub> BjornT: Rest of it looks fine. r=stub if you don't think it will need a rereview
[12:37] <BjornT> thanks
[12:40] <kiko> again: SteveA, stub, spiv: what's happening to jamesh' fix that nukes out __len__?
[12:42] <stub> kiko: I havn't seen it, and I havn't seen it land
[12:43] <kiko> I saw it in -reviews but it died out
[12:43] <daf> summary says all three branches are in merge-conditional
[12:53] <kiko> daf, and yet..
[12:53] <daf> indeed
[12:54] <daf> hmm, perhaps the bug list should use months for weeks old > ~12
[12:54] <daf> or even 8
[12:58] <Kinnison> stub: ping?
[12:59] <stub> Kinnison: pong 
[12:59] <Kinnison> stub: We need to discuss access from drescher
[12:59] <stub> Ok. Can it wait an hour? I was just heading out with wifey for food
[01:01] <Kinnison> stub: Erm, Yes, I guess so, although if you can add at minimum 'ro' access for lp_archive on drescher then I'd appreciate it
[01:02] <kiko> stub, ping me when you're back
[01:02] <stub> Kinnison: Done
[01:02] <stub> kiko: ok
[01:02] <kiko> thanks.
[01:03] <Kinnison> stub: thanks dude, have a good lunch
[01:27] <ddaa> it seems that every launchpad developer and his dog agree that the sidebar are a problem... can somebody remind me why we still have them?
[01:28] <ddaa> Is that just "because it would be a lot of work to fix all the pages"?
[01:28] <ddaa> or something else?
[01:37] <salgado> hey BjornT, would you like to review that patch to fix bug 5394? (it's on the review queue already)
[01:37] <Ubugtu> Malone bug 5394: "Clicking on "Advanced search" should preserve simple search criteria" Fix req. for: malone (upstream), Severity: Normal, Assigned to: Guilherme Salgado, Status: In Progress http://launchpad.net/bugs/5394
[01:48] <mantiena> Hi all
[01:53] <salgado> cprov/Kinnison, I have the feeling that the guess{Sources,Binaries} methods should read the Release files in the mirror to do their work. am I right?
[01:54] <salgado> cprov/Kinnison, if so, is there any existing code to parse that file's content or do I need to write it myself?
[01:54] <mantiena> SteveA, labas
[01:56] <niemeyer> salgado: Isn't it a standard "tags" file?
[01:56] <niemeyer> salgado: There's code for parsing it already
[01:57] <salgado> I'm not sure what a standard "tags" file is. :-(
[01:58] <niemeyer> salgado: apt_pkg can handle it, and there's some wrapper code in archivepublisher.tagfiles
[01:58] <salgado> ahhh, nice
[01:59] <salgado> thanks niemeyer. :)
[01:59] <niemeyer> You're welcome ;)
[02:00] <mantiena> kiko, Hi are you alive ? ;)
[02:12] <SteveA> BjornT: hello
[02:12] <stub> ddaa: One reason is that a lot of the information is actually needed. If it is removed from the side bar, it needs to go somewhere else. The other is that mpt has to work with a number of mandatory design points.
[02:12] <SteveA> BjornT: are mails sent to the email interface bouncing right now?
[02:13] <stub> SteveA: They are being queued
[02:13] <ddaa> stub: is "three columns layout" part of the mandatory design points?
[02:13] <SteveA> stub: might be better to bounce them
[02:13] <mantiena> SteveA, are you busy now ?
[02:13] <SteveA> because processing a command after quite a while may have unexpected consequences
[02:14] <SteveA> if other things have been done in the mean time through the web interface
[02:14] <SteveA> ddaa: you can talk with me about UI things in launchpad.
[02:15] <stub> SteveA: That needs to go through rt then - I can't change that. We could also just copy over an updated process-email.py and turn it back on.
[02:15] <ddaa> SteveA: nothing very specific ATM. Just weird feeling. Everybody seems to say "sidebars are a problem" but it feels like it's not possible to get rid of them for some unspoken reason.
[02:15] <SteveA> stub: copying over process-email.py would be good.
[02:15] <ddaa> then maybe I'm violating some taboo by asking that here...
[02:16] <SteveA> ddaa: there's ongoing work to make many pages two column rather than three column.
[02:16] <BjornT> salgado: sure, i can review your branch. i'll see if i have time to do it today, otherwise i'll do it tomorrow morning
[02:17] <SteveA> mantiena: yes, quite busy right now.
[02:17] <salgado> BjornT, that's great, thank you!
[02:18] <ddaa> SteveA: is there a generic reason why "just one column" is not possible?
[02:19] <stub> But where would all the portlets go?
[02:19] <SteveA> ddaa: i'm interested in discussing this, but i need to go out for a while now
[02:20] <ddaa> stub: when they contain useful information, they can go at the top of the body. When they do not, they can just go away.
[02:21] <dooglus> sometimes malone fails to honour the newlines I put between the lines I write in a comment, and other times it doesn't.  how does it decide?
[02:21] <ddaa> I'm picking one page at random. /people/ddaa. "Latest David Allouche Support Requests"... That has nothing to do here...
[02:22] <dooglus> see https://launchpad.net/distros/ubuntu/+source/checkinstall/+bug/29536 for example.  It joins lines together which should be separate.
[02:22] <Ubugtu> Malone bug 29536: "installwatch.so has moved; somebody should tell checkinstall" Fix req. for: checkinstall (Ubuntu), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed
[02:22] <dooglus> yes, that one.
[02:23] <ddaa> The person details portlet, fine... Is that really useful on _all_ the person pages? I do not think so. Better to just put that in the person index.
[02:23] <ddaa> Then we have the sitemap and the menu.
[02:24] <ddaa> They are actually the same feature, suffering from a split brain syndrome.
[02:24] <ddaa> mpt made a lot of good work here, that makes the issue only more apparent
[02:27] <ddaa> There's also the fact some people (e.g. jblack) had trouble associating the menu with the "context".
[02:27] <ddaa> So, I think it would be beneficial to collapse the sitemap, details, and menu in one thing, at the top of the page.
[02:28] <ddaa> here... one column in the person pages!
[02:28] <ddaa> okay, a bit handwavy, that makes the point.
[02:33] <Kinnison> stub: So, can we talk databases?
[02:36] <stub> Kinnison: I've got kiko off channel, but sure
[02:37] <Kinnison> Well, first-up I need to start prodding a bunch of tables to prepare stuff for deployment
[02:37] <Kinnison> stub: I need UPDATE on distribution and distrorelease, INSERT on componentselection and sectionselection, and INSERT on distrocomponentuploader
[02:38] <Kinnison> stub: (that's all I've worked out so far)
[02:39] <stub> Kinnison: Ok. I'll create you an account with full read access and extra permissions on whatever tables you need (starting with the ones you just mentioned)
[02:42] <Kinnison> stub: thanks
[02:43] <mantiena> SteveA, when you will be not so busy then please look why I still can't add Baltix milestone or release (look at https://launchpad.net/distros/baltix/+addmilestone ). kiko told me, that this will be fixed during the week, but now is 1,5 week after
[02:44] <kiko> mantiena, the fix hasn't been rolled out yet. hold on for stub.
[02:45] <stub> update was put off today due to a flaky network connection here. I'll be doing the update in about 16 hours time
[02:47] <kiko> great.
[02:48] <ddaa> is that timeout well known?
[02:48] <ddaa> https://launchpad.net/distros/ubuntu/+allpackages
[02:48] <ddaa> (I hope by doing so, everybody will check and it will show up in the error report this week)
[02:54] <ddaa> Kinnison: sourcepackage-buildlog.pt says something interesting
[02:54] <Kinnison> does it now?
[02:54] <ddaa>       The build log is produced when we try to compile the source package into binary packages which can be installed on your distribution. There may not be a build log if this is a read-only distribution (one we just monitor but don't actually produce in the Launchpad, like Ubuntu and its derivatives).
[02:54] <ddaa> Still true?
[02:55] <ddaa> Just hunting for explicit ubuntu references, stumbled on that (legitimate) bit by chance, and made me wonder...
[02:57] <Kinnison> Umm, that's confusing as fuck
[02:58] <ddaa> strange, I thought fuck what instead quite straightforward
[02:58] <ddaa> and backwards
[02:58] <ddaa> forward
[03:03] <Kinnison> That needs better text
[03:03] <Kinnison> I don't have time to do it
[03:03] <Kinnison> file a bug against soyuz please
[03:03] <ddaa> i/e i/o, I got a bug to go
[03:07] <ddaa> bug 29548
[03:07] <Ubugtu> Malone bug 29548: "buildlog informative portlet is confusing as fuck" Fix req. for: soyuz (upstream), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/29548
[03:07] <Kinnison> thanks
[03:08] <mpt__> Ubugtu, language!
[03:08] <bradb> Ubugtu has no morals
[03:09] <mantiena> stub, so, after 16 hours I will have a posibility yo add new milestone/new release in Baltix distribution ?
[03:09] <mpt__> Part of the problem is that Launchpad knows darn well whether there's a build log or not, so it shouldn't be saying "there may not be a build log"
[03:09] <ddaa> anyway...
[03:10] <ddaa> it's hidden in a portlet
[03:10] <ddaa> you actually have to look for it to find it
[03:11] <ddaa> But right, that should be displayed in the page body IFF there is no build log.
[03:11] <stub> mantiena: I don't know if anyone has landed a fix for that particular bug or not. 
[03:11] <ddaa> and I do not think there is no point explaining what a build log is if there's one...
[03:12] <ddaa> please do not omit to remove of those negations in the previous sentence
[03:14] <kiko> stub, I did.
[03:15] <stub> mantiena: yes
[03:17] <mantiena> ok, I'm then waiting ;)
[03:18] <ddaa> kiko: sent final reply to your branch/series/bzr cleanup
[03:19] <kiko> thanks ddaa 
[03:19] <ddaa> my pleasure
[03:20] <ddaa> the concept of ProductSeries is fucked up IMO
[03:20] <kiko> many things are
[03:20] <kiko> but it may be useful in the HCT scenario, last I considered it?
[03:21] <ddaa> I think it actually means something quite important to HCT
[03:21] <ddaa> as I mentioned in my mail, I think each series should in the end be associated to branch generated by Dyson.
[03:21] <ddaa> but niemeyer is the authority on that sort of stuff
[03:22] <ddaa> well, except series without releases, which currently exist to be able to do RCS imports, which I consider a bug.
[03:49] <ddaa> stub: re bugwatches
[03:49] <ddaa> what is the problem, too many watches to gnome bugzilla in malone?
[03:50] <dilys> Merge to devel/launchpad/: [r=stub]  improve error handling in process-mail.py, so that it can continue to run even if an email causes an unexpected exception. (r3025: Bjorn Tillenius)
[03:50] <stub> too many bug watches for a system that checks them one at a time
[03:51] <ddaa> Is the issue that this causes a rush of requests on the gnome bugzilla?
[03:51] <ddaa> if that's the case, that should be fixable just by throttling... say one bug per second...
[03:52] <ddaa> or maybe one every 5 seconds
[03:52] <ddaa> that would avoid the DOS issue.
[03:52] <ddaa> or am I missing something important?
[03:53] <bradb> BjornT, stub: Do we need r3025 cherrypicked? 
[03:53] <stub> ddaa: I'm not sure of the load issues on the bugzilla end. Just that it was suggested by Gnome people that we should turn it off until we implemented checking in batches
[03:54] <stub> bradb: I've already cherry picked the code I was sent to review, which won't be as good but good enough until the real rollout tomorrow
[03:55] <bradb> stub: Ah, so the email interface is up currently?
[03:55] <stub> Hopefully :-)
[03:55] <bradb> ok, thanks
[03:57] <BjornT> stub: it seems like it isn't running due to a stale lock file
[03:57] <stub> BjornT: I've removed the lock file
[04:00] <BjornT> stub: ah, some other changes in mail/incoming.py hasn't been rolled out yet. forgot about those.
[04:03] <BjornT> stub: r3018 is needed as well. will it be rolled out tomorrow? i'll see if i can give you a patch against the current production version of incoming.py.
[04:04] <stub> 3018 will go out tomorrow
[04:04] <bradb> BjornT: So, it's currently down, but will be back up tomorrow?
[04:05] <kiko> bradb, stub, ddaa: fixing Bugzilla watch updating is something I hope BjornT is taking care of :-)
[04:06] <ddaa> kiko: how much would you take to sell me a soul to work on fixing importd problems?
[04:06] <kiko> BjornT, I can help you explain how I think checkwatches should work, if you like.
[04:07] <kiko> ddaa, mmmm. I'd need to know more about what's bothering you right now.
[04:07] <kiko> but it should be possible, definitely
[04:07] <ddaa> a number of things, we can have a chat about that if you wish
[04:08] <kiko> yeah, but this week it appears that I'll hardly be able to, because of the soyuz rollout.
[04:08] <kiko> I can try though
[04:08] <BjornT> kiko: yes, it's on my list to fix. i havn't thought much yet about how checkwatches should work, so feel free to give suggestions if you have time.
[04:08] <ddaa> kiko: it's nothing that cannot wait _yet_ another month...
[04:11] <kiko> BjornT, I do have time -- do you want to take a look at it and come back and ping me?
[04:11] <kiko> ddaa, I don't have too many wildcards free right now, hmmm
[04:12] <ddaa> it's a bunch of issues that have been staying below the "need to fix now!" threshold for a long time but are seriously impairing the quality of RCS import service.
[04:13] <ddaa> talk about that later
[04:14] <BjornT> bradb: actually, it looks like the email interface is up running now. stub, did you do anything else then removing the lock file? i saw one error message about an import error, but it seems to work now.
[04:15] <bradb> BjornT: How often doesn't process-mail get run?
[04:15] <BjornT> kiko: sure, i'll take a look at it now. it's probably best to fix checkwatches.py before i fix any else about bug watches
[04:16] <kiko> sure.
[04:16] <BjornT> bradb: every 3 minute
[04:16] <bradb> thanks
[04:53] <dilys> Merge to devel/launchpad/: r=kiko Community fixes to various scripts: link-external-sourcecode, launchpad-database-setup, Makefile (r3026: Christian Reis)
[04:55] <kiko> sivang, I think utilities/launchpad-database-setup improves things
[05:17] <dilys> Merge to devel/launchpad/: r=kiko Additional community fix to launchpad-database-setup (r3027: Christian Reis)
[05:20] <kiko> heh
[05:20] <kiko> BjornT, how's it going?
[05:21] <BjornT> kiko: sorry, i got side tracked by other things. let me have a quick look now
[05:22] <kiko> \o/
[05:25] <BjornT> kiko: ok, it was a quite small script. so, what were your thoughts about how it should work?
[05:25] <kiko> heh
[05:25] <kiko> BjornT, you need to look at canonical/malone/externalsystem.py
[05:26] <kiko> that's the engine for the script
[05:28] <BjornT> kiko: yeah, i'm looking at it. it's still not that big :)
[05:28] <kiko> heh
[05:28] <kiko> ok
[05:29] <kiko> BjornT, so, the easiest fix I can see is:
[05:30] <kiko> - Adding an ExternalSystem.get_bug_status_multiple()
[05:30] <kiko> - Grouping the bug watches by bugtracker in scripts/checkwatches.py and invoking that method
[05:30] <kiko> what do you think?
[05:32] <BjornT> kiko: yes. although i'd like it to be ExternalSystem.update_bug_watches() instead, since we want to update more than just status in the future.
[05:32] <daf> YAGNI
[05:33] <kiko> daf, no, I suspect he's right
[05:33] <kiko> we will want to grab some extra information at least -- pri/sev might be good ideas
[05:38] <kiko> salgado, how do you make launchpad access a different port on anthem? just set an env variable?
[05:39] <salgado> kiko, that might work, although I've never done that
[05:40] <kiko> how do you do it normally? for mpt for instance?
[05:40] <salgado> kiko, that was port forwarding, from port X on anthem to port Y on his box
[05:40] <kiko> I see.
[05:44] <kiko> BjornT, that sounds find by me. do you have any other questions? it shouldn't be rocket science to do that plus a test I'd say
[05:47] <BjornT> kiko: no, it looks quite straight forward to me. i guess the only thing would be to decide how many bugs we should request at once. i'm not sure if it's feasible to make a request for all bugs, or if we should batch it up.
[05:48] <kiko> I think a request with all bugs is doable, but give it a try and see how long gnome takes to respond
[05:49] <BjornT> yeah, i'll try and how it goes.
[05:50] <kiko> gnome and ubuntu are likely to be hardest hit
[05:50] <kiko> if you want to batch it, do it in, say 100-bug chunks?
[05:53] <BjornT> yeah, 100-bug chunks should probably be ok. we'll see how it performs.
[05:54] <kiko> cool.
[06:25] <seb128> hi
[06:25] <seb128> what should be done when a package has no upstream component?
[06:25] <seb128> filling a bug on launchpad?
[06:31] <Kinnison> pardon
[06:32] <seb128> when I try to open an upstream task on "file-roller" I get a "Invalid value" for the product
[06:33] <seb128> what is the standard way to require the registration of a product?
[06:36] <kiko> BjornT, how does one unwrap a security proxied instance?
[06:36] <BjornT> kiko: why do you want to unwrap it?
[06:36] <kiko> I need to do a select using a dbschema the database gave me back, and it's security proxied.
[06:36] <kiko> is there a way to do things differently?
[06:37] <BjornT> kiko: what error do you get?
[06:37] <kiko> id being a ForbiddenAttribute.
[06:38] <kiko> BjornT, what do you say?
[06:38] <kiko> bug 3315
[06:38] <Ubugtu> Malone bug 3315: "change dbschema test to use proxies directly" Fix req. for: launchpad (upstream), Severity: Normal, Assigned to: Steve Alexander, Status: Confirmed http://launchpad.net/bugs/3315
[06:39] <BjornT> kiko: ok, the correct fix would be to add security declarations for it. if you can't do it, please file a bug about it and use zope.security.proxy.removeSecurityProxy
[06:39] <kiko> the bug is already filed :)
[06:42] <mdz> seb128: better would be to register the upstream
[06:42] <BjornT> kiko: ok :) so i guess you could use removeSecurityProxy together with an XXX referencing the bug, and nag SteveA to fix that bug.
[06:42] <kiko> yeah
[06:42] <seb128> mdz: most of the GNOME stuff are known as upstream component by launchpad
[06:42] <seb128> and I doubt upstream went to register them
[06:44] <mdz> seb128: right, one of us did
[06:45] <seb128> as I understand the workflow, when I forward a bug I'm supposed to open an upstream task
[06:45] <seb128> and to put a watch on it
[06:45] <seb128> right?
[06:50] <kiko> right.
[06:51] <seb128> so I need an upstream component
[06:52] <seb128> and I would be happier if I don't have to track an upstream and try to explain him what launchpad is and that he should use it to register file-roller so I can set some bugs correctly :p
[06:55] <ddaa> seb128: people already think you are packaging all of gnome
[06:55] <kiko> seb128, why don't you register it anyway? :)
[06:55] <seb128> kiko: how? that was my question .... :)
[06:55] <ddaa> then people will think you are _also_ programming all of GNOME :)
[06:55] <kiko> products/+new?
[06:56] <seb128> kiko: let me give a try
[06:56] <seb128> ddaa: people already think that's I'm creating bugs all over GNOME, that's enough :p
[06:57] <ddaa> you are too modest
[06:57] <ddaa> get in the spirit of it
[06:57] <ddaa> World Domination!
[06:57] <ddaa> ;)
[07:00] <seb128> hum, in fact there is already a "fileroller"
[07:00] <seb128> instead of "file-roller"
[07:00] <ddaa> mh... I knew there was a RCS import about that...
[07:00] <ddaa> please don't rename it, yet
[07:00] <seb128> k, using "fileroller" works for me
[07:00] <seb128> it was just not obvious why it was not working :)
[07:01] <ddaa> at some point in the future I'll make a big announcement "you can rename product and series and it won't break RCS imports"
[07:01] <seb128> one other step to world domination :)
[07:02] <ddaa> yeah, I guess. In a subgenius sense...
[07:02] <ddaa> probably not
[07:02] <ddaa> the situation is just a bug in importd
[07:03] <kiko> smart answer
[07:09] <janimo> jordi, what is the frequency of rosetta imports?
[07:09] <janimo> or latency to be more correct
[07:10] <janimo> same question for imports in bazaar of projects registerd in LP
[07:10] <janimo> right now that bazaar label on the product says 'testing'
[07:11] <ddaa> mh?
[07:11] <ddaa> janimo: for RCS imports, the answer is usually "when I come around to babysitting it"
[07:11] <janimo> ah, they're not automatic then
[07:11] <ddaa> at the moment, it's "no new imports please, because we are in a transition"
[07:12] <janimo> swicthing to bzr imports?
[07:12] <ddaa> janimo: yes, they require a lot of babysitting, that's something I want to get fixed after we have migrated to bzr
[07:12] <janimo> is one of rosetta and bazar importing prerequisitve of the other?
[07:13] <ddaa> maybe not make it fully automatic (but why not?), but at least have a workflow...
[07:13] <ddaa> janimo: nope, they are independent
[07:13] <janimo> thanks David
[07:13] <ddaa> !
[07:14] <ddaa> janimo: you ever saw that cartoon about paranoia?
[07:14] <janimo> nope
[07:14] <ddaa> someby looking at a map reading "you are here"
[07:14] <ddaa> "news travel fast..."
[07:14] <janimo> ah that :)
[07:14] <janimo> why, are you paranoid?
[07:14] <ddaa> that's how it feels when an unknown nickname calls you by your first name
[07:15] <janimo> ddaa, I was a gnu-arch lurker and occasional annoyance to tom&co :)
[07:15] <janimo> 'please no weird filenames', 'they're good, get used to them' type of talks :)
[07:16] <ddaa> okay, this explains that :)
[07:16] <ddaa> yeah... bzr is in large part a reaction to all the UI wrongness in Arch
[07:51] <ddaa> That mode rocks
[07:52] <ddaa> Dudes stop savagely wrapping wiki pages. Use longlines.el instead and get state-of-the-arch 1980 soft word wrapping in emaics.
[07:52] <ddaa> s/state-of-the-arch/state-of-the-art/
[07:53] <ddaa> Then you just have to teach your finger to stop typing M-q
[08:04] <ddaa> niemeyer: ping
[08:06] <niemeyer> Pongus!
[08:07] <ddaa> -> #buildd-ng
[09:05] <AlinuxOS> alive lions ? :)
[09:06] <Burgwork> AlinuxOS, as opposed to dead tigers?
[09:07] <AlinuxOS> :D
[09:07] <AlinuxOS> loooolz
[09:07] <AlinuxOS> Bucciarati, I've got a question :)
[09:07] <sivang> Hi all :)
[09:08] <Burgwork> salut sivang 
[09:08] <sivang> hey Burgwork , 'sup?
[09:08] <Burgwork> not much, grinding away at work
[09:08] <AlinuxOS> how can I translate things that are in /usr/share/applications/ *.desktop sufix... I need translate gnome-menus in my language..
[09:08] <AlinuxOS> but no way out...
[09:09] <AlinuxOS> http://alnuxos.no-ip.org/ubuntu.png :) hehe Georigna Ubuntu :)
[09:09] <sivang> hmm, so kiko fixed stuff in utilities/launchpad-database-setup, how can I see what did he merge as a fix?
[09:09] <AlinuxOS> firs time in a history :)
[09:09] <sivang> (just now saw his comment)
[09:11] <salgado> sivang, the easyest way (AFAIK) is to "bzr diff $((revno-1))..$revno", where revno is the revision of his merge
[09:11] <sivang> salgado: ok, and if dilly's informed about that, that means that PQM has accepted his patch and the code is already changed right?
[09:12] <salgado> right
[09:12] <sivang> salgado: thanks
[09:13] <salgado> sivang, you're welcome
[09:13] <salgado> need to go now...
[09:14] <AlinuxOS> people how can I translate gnome-menus in my own language...?
[09:14] <AlinuxOS> I've alredy done it... compile .po file into .mo file... put it in right directory..but menus are still in english :((
[10:15] <carlos> AlinuxOS, the menus are not using the .mo files
[10:15] <carlos> it's done on build time
[10:15] <carlos> we are designed a way to update them with language packs and we hope it will be included with dapper but we don't have that finished
[10:22] <janimo> carlos you do rosetta imports too?
[10:23] <carlos> janimo, I can manage them, yes
[10:23] <janimo> carlos, you know how often they are picked from the wiki?
[10:24] <janimo> not a nudge juts curios
[10:24] <carlos> oh, that kind of import... no idea, jordi is on charge of that 
[10:24] <janimo> ah I see, thanks
[10:25] <carlos> janimo, anyway, we integrated it into launchpad already, you can do the upload directly and wait for us to handled the new import
[10:25] <janimo> can I do the upload of po files myself?
[10:26] <janimo> I registered a new project and added it to the wiki pointing to the po files
[10:26] <carlos> yes, but will still need an admin review
[10:26] <carlos> the first time
[10:26] <carlos> janimo, yeah, the wiki needs to be updated
[10:26] <carlos> janimo, create a new product branch/series
[10:26] <janimo> done that already
[10:27] <carlos> and select the translations view
[10:27] <janimo> thunar project
[10:27] <janimo> ok doing it now
[10:27] <carlos> there, you should have an option to do the .pot and .po uploads
[10:27] <carlos> just upload a tarball with all them
[10:27] <janimo> Administrator help         needed. thunar has not yet been         setup for translation through Rosetta.
[10:28] <janimo> I don't see where I can upload
[10:29] <carlos> hmm
[10:29] <carlos> ok I found a bug...
[10:29] <carlos> the link is not where it should be
[10:29] <carlos> go back to the series
[10:29] <carlos> and select the overview option
[10:29] <carlos> at the end, you will see a "Request translations upload"
[10:29] <carlos> option
[10:29] <janimo> ah I see it
[10:30] <janimo> LP interface is very confusing
[10:30] <janimo> but in a way I cannot put my finger on as to file a bugreport
[10:30] <carlos> janimo, why?
[10:30] <janimo> cannot put my finger on, what I said
[10:31] <janimo> maybe too much ifo at a time in a page
[10:31] <janimo> it looks like text but it's menu
[10:31] <janimo> navigation is difficult too
[10:32] <carlos> janimo, perhaps you should talk with mpt, our UI expert to know your complains and try to improve it, but anyway, if you could try to file bugs that's the best way to get a solution...
[10:33] <janimo> carlos, I know it is hard because it is not anything in particular it is the general feeling
[10:33] <janimo> I know this is not helpful
[10:34] <carlos> we are aware of some of the problems I suppose you have and we are fixing them, but if you really want them fixed... you should comunicate with us ;-)
[10:36] <janimo> carlos, one thing that happens often is that I have to use the browser back button
[10:36] <janimo> as there's no (visible) way to get back using links in the page
[10:37] <janimo> hmm, another but this may not be a LP issue: sometimes if I directly enter an URL it gives an error page
[10:37] <janimo> as if some pages were only accesible after you visited their parent url
[10:40] <janimo> or if I go to a page I shpuldn't see links to actions I do not have the permission to do (edit team emblem, edit members)
[10:41] <janimo> the menus are very crowded, as from any LP page you can go directly to any other part of lp
[10:41] <janimo> which is probably good after you are used to it
[10:41] <janimo> but is overwhelming for a good while
[10:42] <janimo> another one - I cannot say off the top of my head but if I am using it right now I keep seeing some issues :)
[10:43] <janimo> the pages are usually long, one needs to scroll down, and the menus then get out of sight
[10:50] <janimo> carlos upload asks for po template and po files. is the po template a potfile (list of .c files) ?
[10:50] <carlos> janimo, please, file bugs about that against products/launchpad
[10:50] <carlos> janimo, yes
[10:50] <carlos> potfile
[10:50] <janimo> ok, uploaded the tat
[10:51] <janimo> carlos, any specific issue that you have in mind wrt bugfiling?
[10:51] <janimo> or everything I said above ? :)
[10:51] <janimo> s/tat/tar/
[10:52] <janimo> hmm, oh well uploading a po tarball results in LP error :)
[10:52] <mpt> janimo, have a read of https://wiki.launchpad.canonical.com/MatthewPaulThomas/DesignProblems and see if it gives you some inspiration :-)
[10:52] <janimo> mpt, thanks
[10:53] <carlos> janimo, please, file a bug with the OOPS number you got
[10:54] <janimo> instead of telling me to report a bug against LP, it could just autofile it against itself :)
[10:54] <janimo> it;s all there: the url I was at, the oops number :)
[10:54] <janimo> I guess I 'll have to tell it again by hand
[10:58] <carlos> janimo, yes, please :-)
[10:59] <janimo> ok I'll start filing bugs now, hope it won't prevent this
[10:59] <janimo> good night carlos
[10:59] <carlos> night
[11:06] <janimo> mpt, good reading I find most of my issues are well known, so I will only report stuff that is not there if I find such