=== mholthaus [n=mholthau@162.23.76.83.cust.bluewin.ch] has joined #launchpad === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad [12:40] http://svn.haxx.se/dev/archive-2006-08/0916.shtml [12:40] kiko: any idea what's up with that? [12:40] lemmesee [12:41] LarstiQ, I think we're going to change that. [12:41] the idea was that doing that we'd be able to ensure the translations were freely available to any project that signed up to use launchpad [12:42] thus never artificially restricting the translations just because one project was licensed incompatibly from another [12:42] I think the current thinking is instead to place translations in the public domain [12:42] I could be wrong but that's what I think [12:42] I'm not sure what exactly kfogel meant with that [12:43] ianal, but can't public domain still be problematic with copyright assignment? [12:44] since the one doesn't say anything about the other [12:44] and then there is countries where you can't place something in the public domain [12:44] I think if something is placed in the public domain copyright is basically waived [12:45] I think the original author retains no special rights [12:45] however I'm not sure === LarstiQ nods [12:45] I think it's better than the current situation AAR. [12:45] iirc, France doesn't allow you to do that [12:45] kiko: probably [12:46] kiko: are you going to followup on svn, or do you want me to do that? [12:46] LarstiQ, hmm, I'm not on that mailing list. You can help me by following up, but I think I should get my story straight before you do that [12:46] let me email the list [12:46] svn ? [12:47] kiko: sure [12:47] lifeless: yes, http://svn.haxx.se/dev/archive-2006-08/0916.shtml [12:48] LarstiQ, email sent [12:56] kiko, have you seen the outstanding issues? [01:03] jamesh: https://launchpad.net/products/bzr/+calendar/2006-W36 [01:03] WEEEEEEEEEE [01:03] kiko: whos owning calendar these days ? [01:03] lifeless, nobody. [01:03] ah [01:03] file bugs they sometimes get fixed [01:03] have a look at that page [01:03] I'm not sure if its a bug or not [01:03] would if it loaded [01:03] it will [01:03] /wait/ for it [01:04] stub's interested in this thing it appears [01:04] I'm going to grab brekkie, back in a bit [01:04] not sure it's a bug! === kiko chuckles [01:04] I see 4 bazjillion mark shuttleworth subscriptions [01:04] I see 4 bazjillion stuart bishop ones [01:04] I think its a bug ;) [01:10] file it! [01:32] done === asabil [i=asabil@gateway/tor/x-6d898ad0c052e011] has joined #launchpad [01:40] New bug: #58052 in launchpad "product calendar shows brazillions of subscribers" [Untriaged,Unconfirmed] http://launchpad.net/bugs/58052 === Keybuk [n=scott@quest.netsplit.com] has joined #launchpad === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #launchpad === doko [n=doko@dslb-088-073-065-198.pools.arcor-ip.net] has joined #launchpad === spiv [n=andrew@ppp245-86.static.internode.on.net] has joined #launchpad === z\ [n=pjphem@unaffiliated/madsheep] has joined #launchpad === z\ [n=pjphem@unaffiliated/madsheep] has left #launchpad ["Leaving"] === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad [03:10] mpt: could you look at doing some alternative wording for person-portlet-details.pt? specifically the bit in the "not: context/preferredemail" block. === somerville32 [n=somervil@fctnnbsc15w-156034073036.nb.aliant.net] has joined #launchpad [03:35] I found some duplicate feature specifications (or very similiar specifications) - What is the procedure for handling that? === erdalronahi [n=erdal@129.218-78-194.adsl-static.isp.belgacom.be] has joined #launchpad [03:37] Hi, can you add the package name "myspell-ku" to the database? I need to file a bug against it. [03:37] It should be synced from SID [03:38] Sorry, to the "Ubuntu Database" [03:38] That's what they told me in #ubuntu-motu === cprov-afk is now known as cprov-ZzZ [03:45] Or is there a better way to sync a package from SID? It's "myspell-ku", the Kurdish spellchecker [03:46] I think everyone is idle :( [03:47] Too bad. Well, it's night in Europe... [03:47] Night in easter canada too [03:47] lol [03:47] *eastern [03:51] Then good night everybody [04:13] lifeless: are we doing a rollout this week? [04:14] (given stub is on holiday) [04:20] I'll look at whats pending after lunch === mpt_ [n=mpt@203-167-187-202.dsl.clear.net.nz] has joined #launchpad === mpt__ [n=mpt@203-167-187-202.dsl.clear.net.nz] has joined #launchpad === Spads [n=crack@host-84-9-51-91.bulldogdsl.com] has joined #launchpad === Fujitsu [n=Fujitsu@c58-107-57-8.eburwd7.vic.optusnet.com.au] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [08:07] LP login is broken :( [08:08] ah no, it's a problem with konqueror :s [08:08] sorry [08:08] :P [08:09] Launchpad is perfect, so it must be something at your end [08:09] hehe :) [08:09] yes === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === janimo [n=jani@Home03207.cluj.astral.ro] has joined #launchpad [08:32] good morning! [08:32] Good morning :] === mpt_ [n=mpt@203-167-187-87.dsl.clear.net.nz] has joined #launchpad [08:34] hi SteveA [08:35] who is in charge of upstream imports to bzr? [08:36] janimo: ddaa [08:36] janimo: ddaa is the main person handling them. What's the question? [08:37] how often do they happen? [08:37] and whether the old failed ones are automatically retried for native bzr now [08:37] I have 6 products registered and one succeeded so far [08:37] I think at the moment they are updated once every 24 hours [08:37] others are failed or testing === carlos [n=carlos@214.Red-88-0-159.dynamicIP.rima-tde.net] has joined #launchpad === jkakar [n=jkakar@204.174.36.228] has joined #launchpad [09:02] SteveA: the page in flacoste's tt-search branch is the "guided ticket entry" page [09:03] it is part of a single work flow, from my reading [09:05] a single workflow can span many URLs [09:06] and sometimes, a progammer will consider something an atomic workflow [09:06] but it actually gets used as separate pages in practice [09:06] SteveA: launchpad.net seems to be either slow or not responding. [09:06] I've seen too many bugs caused by having a self-posting form that doesn't redirect to the next page [09:06] but instead renders the next page directly. it's an anti-pattern for webapps [09:07] so, we should always prefer redirection [09:07] spiv: hmm [09:07] I got a 502 proxy error a few minutes ago, although another page request worked concurrently. Hmm, I *think* it's just slow. [09:07] maybe one app server is down [09:07] I got the front page to load ok, but it wasn't quick... [09:08] same here, slow front page [09:08] that's what slow/unreliable usually means [09:08] load average: 3.07, 5.18, 4.80 [09:08] on gangotri [09:09] i'm stupid about loads... what does that mena? [09:09] busy but ok [09:09] there is an average of 3 processes that are ready and waiting to run [09:09] roughly just means that X number of processes had to wait in the last time slice [09:09] gandwana has loads of about 0.50 [09:10] is it actually doing stuff? [09:10] there are various cron jobs running on gangotri [09:10] we have rosetta-poimport.py [09:10] you could use the "kill -USR1" to find out [09:10] update-bugtask-targetnamecaches.py [09:10] send-bug-notifications.py [09:11] let me look at db load, one sec [09:11] the rosetta one has been running almost 1 hr [09:12] update-bugtask-targetnamecaches.py seems pretty active [09:13] It seems responsive again now. [09:14] there are no long running queries on the bd [09:31] morning dudes === malcc [n=malcolm@host86-138-251-144.range86-138.btcentralplus.com] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [09:37] mpool: hi, around? [09:39] hi SteveA [09:39] yes, i think so [09:44] short voice call? [09:46] sure, call me on +61 4 1618 9900? [09:47] oh, belay that [09:47] ok. or, skype / voip? === seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad === janimo [n=jani@Home03207.cluj.astral.ro] has left #launchpad [] === dpryo [n=hn@batman.ws.interweb.no] has joined #launchpad === dholbach [n=daniel@ubuntu/member/dholbach] has joined #launchpad [10:26] hello [10:27] would it make sense to deny people joining teams if they don't supply an email adress? [10:27] like https://launchpad.net/people/arun-pg tried to join https://launchpad.net/people/ubuntu-core-dev/+members -- I can't mail him, because I don't know his address === mpt_ [n=mpt@203-167-187-87.dsl.clear.net.nz] has joined #launchpad [10:37] mpt_: hi [10:38] dholbach: either that, or we add to launchpad a way to send people a message even when they don't show their email address [10:42] or let it be an interim solution until LP knows how to do messaging === mholthaus [n=mholthau@162.23.76.83.cust.bluewin.ch] has joined #launchpad [10:43] shall I file a bug report on that? [10:43] yes, or raise it on the launchpad-users list for some discussion, perhaps [10:44] Ok, I'll mail the list. === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [10:48] Good morning in here. [10:50] good morning ddaa [10:50] i was just talking with mpool, and we'll be talking again shortly [10:50] anything that you want to have injected into the conversation? [10:51] if you tell me what the conversation is about, I might [10:52] we already talked about getting launchpad devs to use the latest bzr packages, and how we'll arrange that [10:52] we'll be talking a bit about overall bzr stuff and lp:////// urls [10:53] nothing comes to mind. I'm way out of touch about bzr. The BranchIndirection spec appeared to be going on well before my leave. [10:55] dunno, maybe I'd need to publicize my position on #bzr a bit more [10:55] yesterday we had some issue with sftp hosting, and some #bzr guy kept asking questions about the internals of the supermirror to j-a-meinel, while I was replying to them... [10:56] Which evoked impressions of monthy python sketches to me [10:57] I'm also none too happy of not being able to keep up with the bzr community === Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #launchpad [11:00] i have an idea [11:01] SteveA: unrelated, but important: can you escalate rt 16533 and rt 16534? [11:01] ddaa: how about a weekly 1hr launchpad-bzr public meeting in #bzr ? [11:01] invite people to discuss supermirror issues [11:01] bzr facilities in launchpad [11:01] etc. === spiv [n=andrew@218-214-66-203.people.net.au] has joined #launchpad [11:15] Not too sure about that one. For one thing, one hour meeting means at least 2 hours preparation and summary. [11:16] I would like to that punctually, to get a sense of what people expect. But I think that doing that regularly might lead to too many wishlist items... [11:16] that seems like a gross overestimate [11:16] That's a conservative estimate of what I spend for the launchpad-bazaar meeting. [11:16] about one hour before, and about one hour after. [11:17] then, you are spending too long polishing the summary [11:17] okay, remove the "at least" bit [11:17] then, you are spending too long polishing the summary [11:19] Mh... what does it mean when a cvs server sends 'E Terminated with fatal signal 9\n' [11:19] Interesting import failure :) [11:21] so the sysadmin killed your session? [11:22] looks like [11:22] SteveA: hi, still around? [11:22] mpool: yes, on the phone [11:22] dholbach: the person in question does have an email address -- they've just elected to hide it. [11:23] jamesh: that's a problem :) [11:23] dholbach: just pointing out that it is different to "person without an email" [11:23] oh yeah, sorry [11:23] SteveA: i'm be here and am on skype - just ping me when you're ready [11:24] ok === cprov-ZzZ is now known as cprov [11:31] ddaa: let's briefly discuss this: what is the purpose of writing the summary of the launchpad-bazaar meeting? === SteveA pings mpool [11:32] 1. recap'ing actions and status to prepare the agenda for the next week [11:32] 2. allow other parties to get the benefit of the meeting (sabdfl is using them) [11:32] Also, sometimes I need to look back on older summaries to check for the status or resolution of some old item. [11:33] At least, that's the uses I'm aware of. [11:33] But maybe I'm missing something essential. [11:33] I do not have much experience with that meeting ting. [11:35] i think those are good but perhaps you're past the point of good return on your time [11:37] I'm trying hard everytime to avoid excessive polish while still producing something comprehensive and pleasant to use. Maybe I'll grow better at doing it. [11:39] try doing just a bunch of non-nested bulleted lists [11:39] see if that works as well [11:41] FWIW the review meeting minutes I do during the meeting [11:43] Anyway. I like the idea of a public #bzr meeting, but not a weekly one. [11:43] Maybe every two weeks or every months. [11:44] I do no think we can deliver fast enough to avoid a feeling of frustration if we do a weekly meeting. [11:44] Hopefully, that will change in the future... [11:52] it would be worth scheduling one or two and see if people find them useful [11:52] might give some idea of how often they should be [11:53] remember that we have a new launchpad-bzr person starting soon too [11:54] Unless proved otherwise, I'll rather assume that new person will mostly work on things we have not even touched yet (like private branches). [11:56] I'd be very happy to see a full-timer help spiv, jamesh and me on what we are currently doing, but your suggestion of making him work on private branches at first suggests it's not quite going to happen that way. [11:56] is this actually what should be printed or is there a missing .join()? "bzr: ERROR: Failed to gpg sign data with command '[u'/usr/bin/gnome-gpg', '--clearsign'] '" === jinty [n=jinty@19.Red-83-50-220.dynamicIP.rima-tde.net] has joined #launchpad [12:15] lifeless: I've got the bug fix for product-release-finder ready, including some tests for the main code. Do you want me to put it on your queue or the general queue? [12:21] mine please [12:21] I'll peek after dinner tonight [12:23] lifeless: some very large vcs imports (glibc, mplayer, etc.) fail to os.fork() when spawning gpg with "OSError: [Errno 12] Cannot allocate memory " [12:23] I checked one of the roomba systems where that happened, and the /proc/sys/vm/overcommit_ratio is 50, so I do not see how that could happen [12:25] Any idea how to work around that issue? [12:32] lifeless: I've changed the script to catch and log errors rather than bail out too, so we should have a better idea of how well the script works on the next run [12:33] we can probably kill the persistant URL cache implementation too, since it now handles the case where the releases have already been created/populated === mholthaus_ [n=mholthau@162.23.76.83.cust.bluewin.ch] has joined #launchpad === teolemon [n=famille@car75-5-82-234-128-149.fbx.proxad.net] has joined #launchpad === teolemon [n=famille@car75-5-82-234-128-149.fbx.proxad.net] has left #launchpad [] === cprov is now known as cprov-out === andrewski [n=andrewsk@c-68-83-71-99.hsd1.pa.comcast.net] has joined #launchpad [01:37] if i have a bug that i want to reject (because the requested feature should happen upstream), but also want to open a bug upstream in case it could be added, should i still use "Rejected" on the bug? or would something else suit? i could see a case being made for "in progress", but i don't really like it. === seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad [01:45] andrewski: what is the bug? [01:46] a feature request on my program [01:46] andrewski: what is the bug number? [01:46] https://launchpad.net/products/pygmy/+bug/58082 [01:46] Malone bug 58082 in pygmy "Feature Request: Queuing songs" [Untriaged,Unconfirmed] [01:47] what does "upstream" mean in this context? [01:47] specifically, queuing songs belongs upstream in MPD, so i wouldn't implement anything in my program without it first being added to MPD. [01:47] anticipated that question. :) [01:47] what bug tracker does MPD use? [01:47] if i recall correctly, its own; i'd have to look. h/o [01:48] it uses its own implementation of mantis: http://musicpd.org/mantis/main_page.php. [01:49] okay. We don't have support for Mantis bug watches [01:49] I'd suggest filing the bug upstream and make a note of the URL in the LP bug [01:50] sure. question remains about the status for the LP bug in the meantime.... [01:50] are you sure you'd want to reject the LP bug though? Surely you'd need to do some work in pygmy to expose the feature [01:50] right, which is why i'm asking what status would be appropriate. :-P [01:51] just give it a low importance and it will be bumped down to the bug listing [01:51] should i confirm it? i mean, obviously, it's a valid request. [01:51] I mean, you aren't talking about rejecting the feature -- it's just that the implementation is deferred til the feature gets added to MPD [01:52] right... so where's the "deferred" status? :-P [01:52] you may as well, since it is a valid bug [01:52] there isn't one. They usually cause more problems than they solve [01:52] fair enough; i seem to recall coming across conversations about them somewhere. [01:52] (search for rants about bugzilla RESOLVED LATER and RESOLVED REMIND) [01:52] lol, i can imagine. [01:53] anyway, i must be going now. thanks for the help! === andrewski [n=andrewsk@c-68-83-71-99.hsd1.pa.comcast.net] has left #launchpad [] === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === niemeyer [n=niemeyer@200-203-209-139.ctame7004.dsl.brasiltelecom.net.br] has joined #launchpad === spiv [n=andrew@218-214-66-203.people.net.au] has joined #launchpad [02:48] hmm, mantis [02:48] SteveA, can https://launchpad.net/products/launchpad/+bug/1016 be rejected? === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has left #launchpad [] === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [02:54] jamesh: is it possible to tell in brief what needs be done in order to add support for another bug tracker? === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad === cprov-out is now known as cprov === Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #launchpad [03:00] sivang: basically we have two levels of support for an external bug tracker. [03:01] sivang: the first is that we simply recognize bug urls, can construct a url from knowing the base url of the tracker and a bug number, and we make it possible to register such a bug tracker. === flacoste [n=francis@modemcable207.210-200-24.mc.videotron.ca] has joined #launchpad [03:04] BjornT: I see [03:04] sivang: that includes adding a new BugTrackerType, and a regexp and code for constructing bug urls in bugwatch.py. unfortunately we don't yet have tests that explain how it works. [03:04] BjornT: well, the code should serve as good enough documentation probably ,) [03:06] sivang: the second level is that we support fetching the status from the remote bug tracker. that's more tricky. the first step is to look at the bug tracker, to see what different ways we can use to get the information we need. for example, for bugzilla we can simply post a list of bug numbers, getting an xml list of all the bugs, containing the information we need. [03:06] sivang: after that, doc/external-systems.txt should hopefull explain what needs to be done. [03:07] BjornT: coo, thanks. [03:09] sivang: if you plan on adding support for other bug trackers, please tell me about it so that i know. there should be a bug open for each bug tracker we want to support, so you could add a note there. [03:11] sivang: something that would help a lot, if you don't have time to code, would be to simply learn about the bug tracker and add the information we need to know. for example, how do bug urls look like, and how can we best poll the bug tracker for bug statuses. [03:11] BjornT: Granted , wouldn't do anything without notifying you in advance, and ofcourse I wold have to do some research about that bug tracker to see if it's worthwhile. [03:12] BjornT: is it okay to add the this information on the bug note? [03:13] sivang: yeah. the bug report is probably the best place to add this information. [03:13] BjornT: okay, thanks. === kiko [n=kiko@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [03:30] SteveA, any news on a rollout? [03:32] kiko: is the launchpad mailing list moderated? I mean is it possible for non-subscribers to send email there provided manual approval? [03:32] let me check ddaa, but I think so yes [03:33] Good, I'm following up on a discussion with Jelmer, and some of it would be of interest to the launchpad mailing list IMO === LarstiQ has the feeling he is missing some context in that svn corruption mail [03:35] kiko: I know nothing about a rollout. [03:35] SteveA, this is very distressing. [03:36] did you arrange to have specific things rolled out? [03:37] no, but there was a plan to have a two-week interval, and while I am fine with delaying another week, I need to know to be able to produce a report without having to spend the night at the office. [03:37] I'm not concerned whether we will have a rollout or not. I'm concerned with the fact that nobody knows! [03:37] as stub is on vacation, there will be no rollout unless specifically agreed with lifeless [03:38] so no rollout this week. mmmkay. [03:38] so, I'm not expecting a rollout while stub is on vacation. [03:38] thanks. [03:38] when is stub back? [03:40] kiko: monday [03:41] SteveA, okay. so probably a rollout on tuesday. thanks! [03:44] jamesh: ping [03:47] kiko: did your mail get through? [03:48] LarstiQ, nobody answered yet. [03:49] k [03:55] flacoste: pong [03:56] jamesh: regarding the UTC_NOW problem in the script [03:56] jamesh: in the test i mean [03:56] yep? [03:56] jamesh: do you think it would be an improvement if instead of comparing with datetime.now I compared with the result of select(UTC_NOW)?Y [03:57] that way the comparison would be against the same base and so shouldn't lead to spurious failures === carlos [n=carlos@214.Red-88-0-159.dynamicIP.rima-tde.net] has joined #launchpad [03:57] malcc, how's our testing plan going? [03:57] flacoste: my original question was whether you benefit much from comparing the ticket created with a default creation date with those with specified creation dates. [03:58] flacoste: i.e. would you be losing much test coverage by only creating tickets with known time deltas between them in that test? [03:58] kiko: There's now a document: https://launchpad.canonical.com/SoyuzSystemTest and work making it happen is underway [03:58] kiko: Nothing impressive to see yet [03:58] malcc, you rock === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad [03:58] jamesh: you mean, do not create any ticket with the default time? [03:58] yeah [03:59] the only drawback is that the default value of datecreated wouldn't be tested [03:59] but I guess that's not a big loss [03:59] so I'll do that === bradb & # dentist === jamesh has seen enough time related test failures in LP over the years [04:02] time should be something we can set in the test environment [04:03] both the current time, and the database's notion of time [04:03] john carmack learned this [04:04] when developing 3d real time games [04:04] I think the last time related test failure was a test coded to only pass on one day [04:04] yes [04:04] which was the day it got merged [04:05] jamesh: Class! Wish I'd thought of that... [04:05] we've had other ones related to time zones too [04:05] the timezone one was a test that would only pass in the UK [04:06] which was okay because the tests were being run in the UK [04:08] malcc, it was my fault. :) [04:08] salgado: bug 1016 should be rejected when we remove makepagetest.py from our tree. [04:10] SteveA, do you want me to remove it or do we want to keep it for some more time? [04:11] BjornT! rock on! === kiko can't wait to see staging tomorrow [04:12] carlos: have you seen sabdfl's mail about translation interface? basically, most changes should be external to what we do (i.e. css) [04:13] danilos: not really [04:13] that message is rendered using the standard notification system [04:13] carlos: oh, no, I was talking about everything else [04:13] so we need to move back to render it directly [04:13] hmm [04:14] then I didn't see that message [04:14] carlos: i.e. there's nothing apart from that which would need changing on our part [04:14] carlos: that's the message I am talking about :) [04:14] oh, sorry, I misunderstood you [04:16] afk to do some soyuz coding [04:19] coding away from the keyboard? [04:19] impressive [04:23] bbl [04:23] kiko-afk: well, changed my mind, I'll post the message to the bazaar mailing list instead [04:36] salgado: sure, please do remove it, and then when that is in RF, the bug can be rejected [04:41] SteveA, will do. do I have r=SteveA on that removal? [04:42] yes [04:42] thanks! [04:43] the product-release-finder code has a class whose __contains__() method mutates the object ... === glatzor [n=sebi@ppp-82-135-7-215.dynamic.mnet-online.de] has joined #launchpad === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad === cprov is now known as cprov-lunch === Keybuk [n=scott@quest.netsplit.com] has joined #launchpad === belito [n=user@201.240.3.198] has joined #launchpad [06:00] Goooooooooooooooooood morning Launchpadders! [06:02] buenos dias [06:02] buenos dias mpt_ [06:03] bom dia! [06:04] were you from mpt_ [06:05] New Zealand :-) [06:05] carlos, did you see Og Maciel's message to rosetta-users@ on the 22nd about OOo translations? [06:08] spiv, awake? === mpt_ suspects not [06:09] mpt_: isn't it quite early in NZ? [06:13] jamesh, yeah, and even earlier in Australia [06:14] mpt_: I suppose you could call midnight early [06:14] heh [06:14] oh, jamesh, you'll know [06:14] jamesh, can you confirm that the proposed solution in bug 57175 is correct? [06:14] Malone bug 57175 in launchpad "Bad publish command for uploading gpg key" [Low,Confirmed] http://launchpad.net/bugs/57175 [06:15] mpt_: yep. The gpg man page also says it should be --keyserver [06:17] ok, ta [06:35] mpt_: no, but I just read it [06:38] carlos: according to our plan, I should mail -translaators and rosetta-users with news about edgy? [06:38] even if there's stuff missing still [06:39] yeah, we should prepare the announcement [06:39] ok [06:39] jordi: if you are going to do it, please, use the wiki to prepare it so we can review it, ok? [06:40] carlos: which wiki? [06:41] if it's the lp wiki, I really need to get access to that somehow [06:41] yeah, the lp wiki === Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has joined #launchpad [07:03] carlos, a reply would be good, even if to say "Sorry, I have no idea what's going on, please let us know immediately the next time you notice it" === ogra [n=ogra@ubuntu/member/ogra] has joined #launchpad [07:03] hey guys [07:03] i have a slight prob with the edubuntu seeds on the supermirror [07:04] seems they dont get updated properly [07:04] mpt_: I know, there is a bug report about it and I guess this confirms it [07:05] to be more exact, the http mirror of /~ubuntu-core-dev/ubuntu-seeds/edubuntu.edgy is out of date by several hours [07:06] the branch the CDs are built from is http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/edubuntu.edgy/ [07:06] the source for it is http://people.ubuntu.com/~cjwatson/seeds/edubuntu-edgy/ [07:06] Kamion: I believe ddaa has been looking at that problem. [07:07] Kamion: I'd like to diagnose the problem, but I do not have the required production privileges [07:07] who has them ? [07:07] Dunno, maybe only stub and sysadmin... [07:08] probably lifeless [07:08] who have not the time and/or knowledge to diagnose the problem [07:08] (we're preparing a new knot CD so its somewhat time critical for me to have it working again soon) [07:09] ogra: RT 16534 and RT 16533 [07:10] thanks [07:10] :) [07:10] to diagnose the sftp branch publication issue I need to know a branch that is out of date at I time when I can increase the verbosity of the the cronscript [07:10] That will give me useful info to narrow down the problem. [07:10] well, my branch is out of date currently ... [07:10] My guess ATM is a regression in the branch puller logic that occured during yesterday's rollout [07:10] since some hours [07:11] so that could be a good test candidate ;) [07:11] Thanks for telling me, but I still do not have the privileges AFAIK [07:11] Kamion: indepently, all the vcs-imports are currently broken [07:11] why is it trying to connect to escudero? [07:12] specify "it" [07:12] stub is on vacation till monday [07:12] python /srv/sm-ng/production/launchpad/cronscripts/supermirror-pull.py [07:12] elmo: because that's the place where the importd branches are supposed to be [07:13] ah, hm [07:13] unfortunately, they are not there anymore, as RT 16534 says [07:13] yes, I know [07:13] I'm still confused - we publicize the importd stuff both on escudero and the supermirror - or? [07:13] salgado, I'm around now === ogra just gets dinner ... bbl [07:14] ddaa: afaik, there wasn't a rollout yesterday [07:14] the branch in question managed to pull up to timestamp: Tue 2006-08-29 12:07:14 +0200 [07:14] so if something's broken, it broke today, by the looks of it === Kamion -> dinner as well [07:15] elmo: escudero is where importd slave put the bzr branches they have published, then the supermirror finds them there and put them in the public SFTP area. [07:15] mpt_, did I ping you recently? [07:15] or else something about the next revision is unusual [07:15] elmo: I can find you the RT where I asked for the internal http server on escudero for importd branches [07:15] ddaa: no, that's fine, it's coming back to me [07:15] it's an interesting complicated setup [07:15] the next revision is a perfectly ordinary one-line change in one file though [07:15] anyhoo [07:15] elmo: in the near future, I plan to put more importd data on escudero, but that will only need to be accessible to importd through sftp. [07:16] Kamion: it looks like it's not _quite_ broken, but instead it's just much slower than it should be. [07:16] ddaa: so - the reason importd doesn't exist on escudero is that there was a HW RAID failure, and we've had to roll back to data that's 24 hours old [07:16] ddaa: how bad is that for /srv/importd on escudero? [07:16] elmo: it's gone [07:16] gar [07:16] I know it's gone dude [07:17] but I have a backup copy, 24 hours out-of-date (from the time of crash), ready to put back in place [07:17] but I didn't want to do that without talking to you first [07:17] what do you mean by "how bad is that"? [07:17] ha okay [07:18] as in - will stuff break. because we havethe 24 hours out-of-date version, and we have the uptodate but from a very corrupt FS version [07:18] it's fine to loose the 24 hours [07:18]