[12:52] (trusting archives should be a property of the chroot, not the real-root) [12:52] I guess that should properly be a bug against launchpad with diff in it, yes? [12:54] lamont: indeed, file a bug on launchpad-buildd product, please. [12:54] will do === lamont adds it to his list. :-) === jml_ [n=jml@203-113-250-169-static.TAS.netspace.net.au] has joined #launchpad [01:33] lamont, you got mail [01:36] kiko: thanks [01:37] although we exposed the bug by adding a brand spanking new architecture... which kinda fits your model [01:37] and the mail lets me understand why the lucky packages were, um, lucky === doko_ [n=doko@dslb-088-073-079-061.pools.arcor-ip.net] has joined #launchpad === merriam [n=merriam@85-211-21-215.dyn.gotadsl.co.uk] has joined #launchpad === pitoow [n=nao_@201-24-64-126.fnsce702.dsl.brasiltelecom.net.br] has joined #launchpad [02:24] ScottK, do I need to add any special tags to https://bugs.edge.launchpad.net/ubuntu/+bug/148792 ? [02:24] Launchpad bug 148792 in ubuntu "Package OGMRip" [Undecided,New] [02:26] needs-packaging [02:28] thanks ajmitch [02:31] Ew, getdeb. [02:33] heh [02:40] New bug: #148796 in malone ""Page not found error", when someone updated the bug, while you were editing" [Undecided,New] https://launchpad.net/bugs/148796 === ryanakca [n=ryan@ubuntu/member/ryanakca] has joined #launchpad === jml [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #launchpad === stub [n=stub@ppp-58.8.4.60.revip2.asianet.co.th] has joined #launchpad === superm1 [n=superm1@ubuntu/member/superm1] has joined #launchpad === cprov [n=cprov@canonical/launchpad/cprov] has joined #launchpad === zzorn is now known as zzorn_sleep [05:01] "You have been subscribed to a public bug by a mysterious stranger" [05:01] "You have been subscribed to a public bug by sunspot activity" === stdin [i=stdin@pdpc/supporter/active/stdin] has joined #launchpad === mayeco [n=mayeco@mayeco-kubuntu.cpe.cableonda.net] has joined #launchpad === thumper [n=tim@125-236-193-95.adsl.xtra.co.nz] has joined #launchpad [06:02] heyyy [06:02] you are changing things in launchpad right? [07:11] uh yes [07:11] yes we are === silwol [n=silwol@194.152.122.177] has joined #launchpad === silwol [n=silwol@194.152.122.177] has joined #launchpad === merriam [n=merriam@85-211-143-106.dyn.gotadsl.co.uk] has joined #launchpad === jtv [n=jtv@ppp-58.8.244.204.revip2.asianet.co.th] has joined #launchpad === StevenK [n=stevenk@14.5.233.220.exetel.com.au] has joined #launchpad [07:46] Am I able to put multiple affects lines into a signed mail I send into Malone? If so, will it do the right thing. [07:47] StevenK: yes [07:48] StevenK: https://help.launchpad.net/UsingMaloneEmail#head-5ea87d70dba160e5903ca01b9eedd8d8476aa2a1 gives an example of doing that. [07:49] Excellent, thanks === StevenK [n=stevenk@14.5.233.220.exetel.com.au] has left #launchpad [] === fernando110 [i=fernando@gateway/tor/x-8c1fe4ae72e50293] has joined #launchpad === Philip5 [n=Philip@c83-253-56-100.bredband.comhem.se] has joined #launchpad === Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad === carlos [n=carlos@canonical/launchpad/carlos] has joined #launchpad [08:43] morning [08:43] Hi carlos. === Spads [n=spacehob@unaffiliated/spads] has joined #launchpad === doko_ is now known as doko === zzorn_ [n=zz@212.16.103.33] has joined #launchpad === zzorn [n=zz@212.16.103.33] has joined #launchpad === allenap [n=allenap@87-194-166-60.bethere.co.uk] has joined #launchpad === poolie_ [n=mbp@ppp112-44.static.internode.on.net] has joined #launchpad === mwh [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #launchpad === schwuk [n=dave@ubuntu/member/schwuk] has joined #launchpad === fernando110 [i=fernando@gateway/tor/x-723bcbe64e17fdd8] has joined #launchpad === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad === elkbuntu [n=melissa@ubuntu/member/elkbuntu] has joined #launchpad === bigjools [n=ed@canonical/launchpad/bigjools] has joined #launchpad === intellectronica [n=intellec@host81-153-175-29.range81-153.btcentralplus.com] has joined #launchpad === mrevell [n=matthew@canonical/launchpad/mrevell] has joined #launchpad === mrevell_ [n=matthew@77-100-239-119.cable.ubr05.wolv.blueyonder.co.uk] has joined #launchpad === mrevell_ is now known as mrevell [10:39] Hobbsee: hi, you didn't ping me again yesterday. Do you still need to talk with me? === jtv [n=jtv@ppp-58.10.64.153.revip2.asianet.co.th] has joined #launchpad === Hobbsee thinks [10:44] mornign mrevell [10:44] hi Hobbsee [11:14] time to leave.. flight to london in 2 hours === jsk [n=jonathan@client-82-14-75-239.glfd.adsl.virgin.net] has joined #launchpad === mwhudson [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #launchpad === thisfred [n=thisfred@a80-127-80-154.adsl.xs4all.nl] has joined #launchpad === ddaa [n=ddaa@canonical/launchpad/ddaa] has joined #launchpad [11:46] hi guys: minor gripe about the launchpad translation exports: the structure of and filenames in the exported tarballs seem to be in flux, which makes automating translation synchronization with my applications sort of a pain. Is it documented somewhere how exactly those files are packed, and more importantly, is there a point at which the stucture will remain stable? ;) === mpt [n=mpt@canonical/launchpad/mpt] has left #launchpad ["http://mpt.net.nz/"] [11:49] thisfred: can you show me where (url) you request these tarballs? [11:50] thisfred (so I can figure out what exactly goes into them) [11:50] jtv, for instance: https://translations.launchpad.net/silva-find/trunk/+pots/silva-find/+export [11:50] thanks, I'm taking a look [11:50] thanks very much! [11:53] thisfred: is there any chance that these are after-effects of files being renamed or moved around in the past? [11:54] jtv, possibly, but I don't think so, I mean, I always took care to upload the same thing I got from launchpad in terms of structure and filenames. [11:55] I'm sure I always uploaded a single tarred flat directory with .pot and .po's [11:55] now I'm getting files directly in the zip and the .pot in a directory, that has a different name than before [11:56] also it used to be nl.po, en.po etc. now it's name-of-project-en.po [11:56] hmmm [11:56] that's all easily changed in my scripts of course [11:56] I just wanna make sure it won't be changing very soon again ;) [11:57] We're also doing lots of imports for Gutsy at the moment of course, so if those contain changes... [11:57] I don't think any of my projects are in gutsy [11:58] And Launchpad-native translations, right? [12:00] thisfred: I don't know too much about the naming logic for these files, but I'm asking around. [12:00] jtv, thanks [12:00] I'm not 100% sure what you mean by launchpad native [12:01] Nor I, never mind that :) === mwhudson [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #launchpad [12:04] thisfred: do you remember when you uploaded these PO and POT files? [12:04] (btw, "breadcrumbs" -> "broodkruimels"?) [12:05] thisfred: we got already bug reports about it and plan to fix it, don't worry [12:05] jtv: is what we talked this morning [12:05] jtv, I'll have a look [12:06] carlos, oh, ok, I'll wait for the dust to settle then :) [12:06] thisfred: carlos just mentioned that this sounds like a known problem. I'mg digging up the bug URL. [12:06] thisfred: https://bugs.edge.launchpad.net/rosetta/+bug/148286 and https://bugs.edge.launchpad.net/rosetta/+bug/148276 [12:06] Launchpad bug 148286 in rosetta "multiple template export has wrong directory names" [High,Confirmed] [12:06] ah, that's it. [12:07] many thanks! [12:07] carlos: thanks from me too! [12:07] I'll subscribe to those === fernando110 [i=fernando@gateway/tor/x-5dbfb31c9eb2b772] has joined #launchpad === mpt [n=mpt@canonical/launchpad/mpt] has joined #launchpad [12:09] and jvt: I didn't actually do *all* of the dutch translations, but I'll follow the breadcrumbs ;) [12:09] :) [12:15] New bug: #148901 in malone "less bugs listed when sorting" [Undecided,New] https://launchpad.net/bugs/148901 === Spads [i=spacehob@unaffiliated/spads] has joined #launchpad [12:35] thisfred: you may want to follow bug 148276 as well. [12:35] Launchpad bug 148276 in rosetta "po files should have the same name as when they were uploaded" [Medium,Confirmed] https://launchpad.net/bugs/148276 [12:36] thisfred: note there's only one digit of difference between those two bug numbers, a bit confusing. [12:38] jtv, thanks, but I just clicked them, so I don't run the risk of mistyping ;) [12:42] thisfred: for me just _noticing_ the difference is sometimes difficult. [12:45] New bug: #148905 in malone "unexpectedformdata on clicking "1 bug fixed elsewhere" on gcc" [Undecided,New] https://launchpad.net/bugs/148905 === bigon [n=bigon@ubuntu/member/bigon] has joined #launchpad === mwhudson_ [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #launchpad === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad === gmb [n=gmb@i-83-67-5-113.freedom2surf.net] has joined #launchpad === matsubara [n=matsubar@canonical/launchpad/matsubara] has joined #launchpad === niemeyer [n=niemeyer@200-140-230-150.ctame705.dsl.brasiltelecom.net.br] has joined #launchpad === tyabux [n=joerlend@249-191.dsl.freewave.no] has joined #Launchpad === salgado [n=salgado@canonical/launchpad/salgado] has joined #launchpad === schwuk [n=dave@ubuntu/member/schwuk] has joined #launchpad === raphink [i=raphink@ubuntu/member/raphink] has joined #launchpad === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #launchpad === mantiena-baltix [n=ubuntu@ctv-84-55-7-167.init.lt] has joined #launchpad [02:47] hi all [02:49] who is reponsible for PPA in launchpad ? It seems there are big problems with PPA - it doesn't install python :( [02:51] mantiena-baltix: cprov [02:52] mantiena-baltix: well, PPA chroot is the same used in ubuntu primary archive, can I see the failed build log ? [02:55] New bug: #148939 in launchpad "OOPS validating a sign only gpg key" [Medium,Confirmed] https://launchpad.net/bugs/148939 [02:59] cprov, yes, of course: http://launchpadlibrarian.net/9721899/buildlog_ubuntu-feisty-i386.pingus_0.7.1-1%7Efeisty1_FAILEDTOBUILD.txt.gz === flacoste [n=francis@modemcable040.144-201-24.mc.videotron.ca] has joined #launchpad [03:06] mantiena-baltix: I think you should depend on python, but I'm not the best person to ask. Can you request help on #motu ? [03:08] build-depend maybe? [03:09] cprov: #ubuntu-motu, you mean? === Hobbsee looks in [03:10] Fujitsu: yes, off course, thanks. [03:10] cprov: that looks like a good question for a buildd admin - to try to install tha tmanually [03:11] or throw the source at a normal feisty pbuilder. [03:11] You'd need to try to install them manually in that chroot to work out what was wrong, yes. [03:12] cprov, problem isn't in build-deps (pingus package is taken from ubuntu gutsy), problem is in PPA, other packages, which have build without problems now fails because PPA doesn't install python [03:13] look for example at 2 kde-guildance build logs: [03:13] http://launchpadlibrarian.net/9721881/buildlog_ubuntu-feisty-i386.kde-guidance_0.8.0svn20070928-0feisty2_FAILEDTOBUILD.txt.gz [03:14] mantiena-baltix: you are building gutsy on feisty, are you considering that, right ? [03:14] http://launchpadlibrarian.net/9249766/buildlog_ubuntu-feisty-i386.kde-guidance_0.8.0svn20070727-0feisty6_FULLYBUILT.txt.gz [03:14] cprov, I'm backporting from gutsy to feisty [03:15] It's hard to tell exactly what has gone wrong without access to the chroots. [03:17] look at the build log of pingus or kde-guidance - there is the same problem: [03:17] scons: Depends: python but it is not going to be installed [03:17] Depends: python-central (>= 0.5.8) but it is not going to be installed [03:17] as a check, you include py-central in the build-deps, and see why it bails [03:17] but that's probably not the source of the problem. [03:18] but to say that the python on the buildds is botched is kinda useless - particularly with no buildd access. [03:18] mantiena-baltix: it might be related with the the recent changes we made in chroots for Partner archive, let me try something, one sec and you can retry the failure builds [03:19] cprov, thanks [03:22] mantiena-baltix: i386 PPA should be sane now, retry one of the builds, please. [03:23] ok [03:24] btw, why there are no way to remove package from PPA archive ? === mrevell is now known as mrevell-luncheon [03:26] mantiena-baltix: because it's not yet implemented , "version bump (tm)" [03:29] :) [03:35] cprov, hehe, it seems your fix helps - kde-guidance is in build process for about 4 minutes (previously it fails after 2 minutes) :) === sinzui [n=sinzui@pool-70-17-91-59.res.east.verizon.net] has joined #launchpad [03:38] mantiena-baltix: great ! thanks for the feedback, I wasn't aware of this issue [03:39] cprov: How did partner manage to break it? [03:39] Fujitsu: when there's enough crack in soyuz, just *looking* at it the wrong way can break it. [03:39] s/can/will/ [03:40] Fujitsu: partner requires us to use -updates chroots for the supported 'release' pocket (dapper, edgy, feisty) [03:40] New bug: #148960 in launchpad-bazaar "Same user subscribed twice to a branch" [Undecided,New] https://launchpad.net/bugs/148960 [03:41] Hobbsee: from the soyuz PoV, the crack is on your packages ;) [03:41] cprov: no, no, we dont upload crack. people can actually audit our packages and see that [03:41] cprov: soyuz is just deluded. [03:41] cprov, thanks for the fix - I alredy have successful guidance backport, it's time for pingus :) [03:42] btw, amd64 is fixed too ? [03:42] mantiena-baltix: yes, amd64 is ready to go too === adeuring [n=abel@Fc16f.f.ppp-pool.de] has joined #launchpad === mthaddon [n=mthaddon@canonical/launchpad/mthaddon] has joined #launchpad === Rinchen [n=joey@canonical/launchpad/pdpc.supporter.professional.rinchen] has joined #launchpad === Kopfgeldjaeger [n=nicolai@p54AD7FED.dip.t-dialin.net] has joined #launchpad [03:55] hi [03:56] ho === mrevell-luncheon is now known as mrevell [03:58] hi [03:59] m === ddaa orders a copy of White Snow for mwhudson === Hobbsee orders some coke === jtv [n=jtv@125-24-222-37.adsl.totbb.net] has joined #launchpad [04:00] Hobbsee: I did not realize one could read "White Snow" in this way... [04:00] e [04:00] me [04:01] ddaa: dunno which way you're thinking about. my statement was mostly unrelated. [04:01] it's probably better [04:01] Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating about Launchpad development! [04:01] who is here today? [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:01] me [04:02] me [04:02] stub sends apologies [04:02] me [04:02] me [04:02] me [04:02] me [04:03] me! [04:03] == Agenda == [04:03] * Roll call [04:03] * Agenda [04:03] * Next meeting [04:03] * Actions from last meeting [04:03] * Oops report (Matsubara) [04:03] * Critical Bugs (Rinchen) [04:03] * Bug tags [04:03] * Operations report (mthaddon) [04:03] * DBA report (stub) [04:03] * Sysadmin requests (Rinchen) [04:03] * A top user-affecting issue (mrevell) [04:04] ---- [04:04] (other items) [04:04] ---- [04:04] * Blockers [04:04] [04:05] Next meeting: same time next week [04:05] does anyone know they won't be able to attend? [04:05] I won't [04:05] I'm on vacation. [04:05] I probably won't [04:06] thanks [04:06] I neither -- more complex appointment at a dentist [04:06] adeuring: good luck [04:06] i won't [04:06] SteveA: thanks :) [04:07] * Actions from the last meeting [04:07] there are none [04:07] * Oops report (Matsubara) [04:07] Thanks jamesh for fixing #132270 [04:07] Today's oops report is about bugs 148939, 44871, OOPS-641E1615 [04:07] Launchpad bug 148939 in launchpad "OOPS validating a sign only gpg key" [Medium,Confirmed] https://launchpad.net/bugs/148939 [04:07] Launchpad bug 44871 in launchpad "xmlrpc should return appropriate response for a GET" [Medium,Confirmed] https://launchpad.net/bugs/44871 [04:07] https://devpad.canonical.com/~jamesh/oops.cgi/641E1615 [04:07] Someone from the foundations team want to take #148939? [04:07] mwh, can you take #44871? [04:08] salgado: do you think you have time for #148939? [04:08] I already privmsg'd jtv about the OOPS and jtv will file a bug and follow up on it. [04:09] mwhudson: can you take #44871? [04:09] flacoste, can you maybe give it to ddaa? [04:09] matsubara: i can look at it, at least, i have no intuition as to how hard it will be [04:09] mwhudson: btw, why do you have 2 nicknames? [04:09] matsubara: two machines [04:09] One for casual, one for formal. [04:09] flacoste, I was actually hoping to bribe matsubara on doing that, but I can give it a try today to see if it's easy. if it is then it's fine [04:09] why mwhudson for xmlrpc? [04:09] salgado: you might want to try bribing ddaa instead :-) [04:09] matsubara: why have 2 names, when you can have 3? [04:10] that should be a foundations team issue [04:10] otherwise, i can probably take both [04:10] matsubara: assign both to me [04:10] I'm happy with the foundation bugs I already have. [04:10] i'll delegate if necessary [04:10] thanks flacoste [04:10] But I can look into this if needed. [04:10] ddaa, this bug will make you even happier :) [04:10] also, it's likely to be reasonably tricky zope internals [04:10] matsubara: and put it on the 1.1.10 milestone [04:10] flacoste: sure thing [04:11] so, I think I'm done here. thanks all [04:11] SteveA: back to you [04:12] thanks matsubara [04:12] sorry for disturbing, but I wanna ask important question - when there will be an ability to register new milestone or new release for other distros in launchpad ? It's too hard to track bugs when there are no ability to set the target milestone :( [04:12] * Critical Bugs (Rinchen) [04:12] Hi, one for this week, a PPA item: Bug #144392 [04:12] Launchpad bug 144392 in soyuz "cron.daily dies after poppy restart because of permission problems with queue dot-lock file" [Critical,In progress] https://launchpad.net/bugs/144392 - Assigned to Celso Providelo (cprov) [04:12] mantiena-baltix: Il'l add that to the agenda for later. [04:12] I think that bug was actually fixed === lakin [n=lakin@S01060013101832ce.cg.shawcable.net] has joined #launchpad [04:13] cprov, this appears to be assigned to you [04:13] Rinchen: very trivial 50 lines [04:13] Great! Do you have a target? [04:13] kiko: can you check those ? [04:13] SteveA: thanks, I'm waiting :) [04:14] cprov, or to reword, will it be by tomorrow? I suspect we'll want to cherry this? [04:14] Rinchen, I don't think it's affecting us right now [04:14] it can be manually fixed [04:14] the bug is only to avoid it happening again [04:14] that's even better. Can you (kiko) or cprov please comment in the bug report to that effect. [04:14] Rinchen: yes, it'd be good, otherwise we will cry again when elmo need to reboot production machines [04:14] moving on.. back to you Steve. Thanks cprov. [04:15] so... should that bug be critical or just high? [04:15] elmo never reboots machines! [04:15] btw, matsubara pointed out that the IE7 bug has been fixed earlier this week. I don't have the bug number handy though [04:15] kiko: yes, http://www.ubuntu.com/usn/usn-518-1, I do [04:16] elmo, shhh :) [04:16] Rinchen: should that bug be critical or just high? [04:16] high. [04:16] it has a workaround. [04:16] based on the above, I agree with high [04:16] ok, please change its importance [04:17] * Bug tags === joerlend__ [n=joerlend@249-191.dsl.freewave.no] has joined #Launchpad [04:17] we have a number of proposals for new bug tags today [04:17] done [04:17] oops-tools: Bugs related to the scripts used to generate oops reports, oops.cgi and the processes related to oops in general [04:17] from matsubara [04:17] looks good to me [04:17] any objections? [04:18] great [04:18] accepted, thanks matsubara [04:18] thanks SteveA [04:18] three proposals from francis: [04:18] librarian: Bugs related to the Librarian component [04:18] +1 from me. other comments? [04:18] +1 [04:18] i thought that existed already! [04:19] openid: Bugs related to the OpenID implementation [04:19] mwhudson: existing is different from being officially used and having a standard definition [04:19] SteveA: ah [04:19] no objections to 'librarian', so approved. [04:19] +1 on openid, particularly as we'll be expanding our openid service in the future. [04:20] I'm happy with OpenID if it will help Foundations. [04:20] yes [04:20] no objections to openid, so approved. [04:20] I think that's a good idea. [04:20] I have a request [04:20] can we merge xmlrpc and api tags? [04:20] i think that's a good idea [04:20] kiko: +1 [04:20] kiko: +1 [04:20] +1 [04:20] thanks. [04:20] kiko: they'll potentially be using separate infrastructure though ... [04:20] +1 here [04:21] jamesh, but does it matter so much? [04:21] I'd like to keep separate tags for external public APIS [04:21] and internal APIs we use within the DC [04:21] xmlrpc will likely become a private internal thing (only? mostly?) but i'm still fine with merging them [04:21] well [04:21] hang on [04:21] we're confusing the name of a protocol "XMLRPC" with the kind of service [04:21] we will continue using xmlrpc for internal apis [04:22] then we should change the definitions and keep the two tags [04:22] we'll need to maintain some xmlrpc apis externally, for compatibility with older ubuntu releases [04:22] I think apis should include legacy public xmlrpc [04:22] the key word here is 'public' [04:22] we may need a new tag for 'internal-only apis' === barry would be fine with a 'public api' tag and a 'private api' tag [04:22] public-api private-api? [04:23] I think 'apis' does well for 'public api' [04:23] and it's shorter [04:23] SteveA: that's fine too [04:23] so 'api' and 'private-api' [04:23] SteveA: +1 [04:23] fine [04:23] +1 [04:23] although, again, it's not so much private as 'internal' [04:23] kiko? [04:23] so, I'd prefer internal-api tbh [04:23] and still get rid of 'xmlrpc' as a tag === lbm [n=lbm@0x555373ab.adsl.cybercity.dk] has joined #launchpad [04:23] works for me [04:23] I'm happy with that. === flacoste too [04:24] people: Bugs related to the management of Persons and Teams. This would include registration bugs, but exclude bugs related to login and password recovery. [04:24] the third proposal from flacoste [04:24] i'm not too sure about that one [04:24] I think the scope needs some work [04:24] i think it could be well merged with my other proposal [04:24] flacoste, to include FOAF? [04:24] perhaps with more examples [04:24] Rinchen: be careful of the term FOAF [04:25] Rinchen: i proposed originally foaf as tag name [04:25] it has a specific usage in the internet community === Rinchen nods in agreement. [04:25] which is not the same as what we casually refer to as foaf [04:25] although we do have a FOAF export somewhere I think [04:25] I'm fine with the tag name 'people', but I want the scope to be clearer [04:25] flacoste: can we leave this until next week? [04:26] SteveA: we can [04:26] matsubara, your comments as well to flacoste post meeting on this tag would be interesting to have. [04:26] flacoste, I just work here! [04:26] ok, so that stays there until next week, and get more examples [04:26] any remaining questions on new bug tags? [04:26] thanks for your proposals, kiko, flacoste, matsubara === Hobbsee wants a take-over-the-world tag. :P [04:27] ahem. [04:27] roger, Rinchen [04:27] matsubara: remind me: should I update the tags page? [04:27] flacoste: yes please [04:27] ok, thanks [04:28] * Operations report (mthaddon) [04:28] New deployment scripts testing well so far (used in the 1.1.9 release) [04:28] New PQM box finally working (still need to plan with IS for ramdisk testing) and showing improved timing [04:28] Also need to coordinate with IS on DB upgrade [04:28] I think that's it from me unless there are any questions [04:28] mthaddon, how much did it improve? [04:29] https://devpad.canonical.com/~mthaddon/pqm_durations.html [04:29] around 40 minutes I think [04:29] mthaddon: I'd like to know the results of the ramdisk work so that we can deploy it for week 3 if it is a successful experiment [04:29] 110 down to 66 roughly [04:29] minutes [04:29] score [04:29] thanks admins, for the new box! [04:29] SteveA, understood - got bogged down with the PQM bug yesterday... will hope to find time today === lakin [n=lakin@S01060013101832ce.cg.shawcable.net] has joined #launchpad [04:30] * DBA report (stub) [04:30] hmm, I was expecting to see that on the launchpad list [04:30] * Sysadmin requests (Rinchen) [04:30] Hi! Is anyone blocked on an RT or have any that are becoming urgent? [04:30] one very nice side effect (PQM for LP is now on it's own box) is that the timing seems to be a lot less variable as well - very consistent timing for a run [04:30] As usual we've had several complete this week. [04:30] Rinchen, just the ramdisk testing for PQM that has alredy been managed. [04:31] mthaddon, yes, I had noticed that. [04:31] kiko, ok thanks. [04:31] Rinchen: jtv is blocked on one RT ticket [04:31] Rinchen, thanks for handling bdmurray's request [04:31] jtv: ? [04:31] The RT blocking mpt was resolved earlier this week as well as one for bdmurray [04:31] carlos: not actually blocked, it's just a damn nuisance [04:31] ah right, you're welcome [04:31] carlos, topic? I didn't see it in the weekly [04:32] jtv: well... it's blocking us to relay on you being able to act if there are requests that need you attention... [04:32] or jtv...topic and/or number [04:32] * A top user-affecting issue (mrevell) [04:32] Rinchen: having jtv member of rosetta@launchpad.net alias [04:32] Rinchen: don't have number handy [04:32] jtv: please tell Rinchen after the meeting [04:32] mthaddon: would be fun to include stddev alongside average in https://devpad.canonical.com/~mthaddon/pqm_durations.html :-) [04:32] ok [04:32] This week's issue concerns how we announce changes that will affect the way people use Launchpad. [04:32] I asked the launchpad-users list for input on how to improve these announcements. [04:32] Some people supported announcing changes in Launchpad's UI, perhaps as a message above the green breadcrumb bar. [04:32] I'd like to know what people think of this idea. In particular, how do we decide how which changes warrant a UI message. [04:33] If we don't have time in this meeting, please see the launchpad-users thread "Announcing Coming Changes in Launchpad". [04:33] mrevell, I think it's really the best idea [04:33] Thanks, back to you SteveA. [04:33] I'm not sure the message above the bar is the best way to do it [04:33] mrevell: ones that actually influence people's workflow [04:33] we have a spec for such announcements somewhere [04:33] so that people can confirm an announcement [04:33] but I think we need to find a way of informing people, yes [04:33] and won't be shown it again [04:33] SteveA: any chance we can mirror that to lp-users or something? [04:33] I think a bubble announcement that shows until you dismiss it is the best idea [04:33] SteveA: (the full spec) [04:33] but we don't show an announcement that has already happened [04:33] it was ages ago [04:33] mwhudson, I think if we see more variance in the timings on the new box that might be useful [04:33] so might need rejiggering or something [04:34] Hobbsee: we'll make it public if/when we find it [04:34] moving on... [04:34] thanks mrevell [04:34] I can take a look for the spec [04:34] SteveA: cool, OK [04:34] mantiena-baltix: proposed an item. [04:34]