/srv/irclogs.ubuntu.com/2006/10/16/#launchpad.txt

=== doko_ [n=doko@dslb-088-073-076-102.pools.arcor-ip.net] has joined #launchpad
ryanakcahow do you remove a remote bug watch thingy? ex: https://launchpad.net/products/amarok/+bug/64573 is watching the same remote bug twice12:25
UbugtuMalone bug 64573 in amarok "Amarok crashes on iPod connection" [Unknown,Unknown]  12:25
=== mpt [n=mpt@121-72-131-100.dsl.telstraclear.net] has joined #launchpad
mptGoooooooooooooooooooood morning Launchpadders!12:31
=== AlinuxOS [n=alinux@d83-190-23-235.cust.tele2.it] has joined #launchpad
=== AlinuxOS [n=alinux@d83-190-23-235.cust.tele2.it] has joined #launchpad
=== mpt [n=mpt@121-72-131-100.dsl.telstraclear.net] has joined #launchpad
=== jml [n=jml@ppp105-240.lns1.hba1.internode.on.net] has joined #launchpad
jameshmpt: I did a bit of work on the new FormLayout stuff03:28
jameshmpt: a few screenshots are here: https://devpad.canonical.com/~jamesh/images/03:29
jameshthe positioning of the textarea on formlayout-productseries-edit.png one looks a bit weird to me03:30
jameshbut maybe left aligning all the labels would fix that03:31
jameshalso, I am not sure where the "required" markers should go with this layout03:31
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #launchpad
mptjamesh, that looks very cool04:04
mptwell done!04:04
mptYou're right about the textarea04:05
mptbut I don't think there's any better solution04:05
mptThe usual solution should be to make the textarea either the first or the last field in the form.04:06
mptSo all the aligned elements are together, and all the textareas are together.04:06
jameshThe alignment of formlayout-new-distro-task.png also comes out a bit weird since the fields are laid out in two groups04:09
jameshnot sure how much of a problem that is though04:09
jameshwhat do you think about placement of the "(required)" text though?04:09
mptI think it should be removed, in favor of "Foo (optional):" labels for optional fields04:12
mptsee bug 3914204:13
UbugtuMalone bug 39142 in launchpad "Checkboxes should not be flagged as 'required'" [Medium,Confirmed]  http://launchpad.net/bugs/3914204:13
jameshalright.  Same question then: where do you think the "(optional)" labels should be placed?04:14
mpt"Foo (optional):"04:15
=== AstralJava [n=jaska@cm-083-102-068-117.lohjanpuhelin.fi] has left #launchpad []
=== Fujitsu [n=Fujitsu@ubuntu/member/fujitsu] has joined #launchpad
=== stub [n=stub@ppp-58.8.1.171.revip2.asianet.co.th] has joined #launchpad
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
UbugtuNew bug: #66344 in blueprint "Dependency chart becomes unreadable with >12 dependencies" [Undecided,Unconfirmed]  http://launchpad.net/bugs/6634405:05
UbugtuNew bug: #66345 in blueprint "alt="" in dependency charts makes them poorly accessible" [Undecided,Unconfirmed]  http://launchpad.net/bugs/6634505:21
=== stub [n=stub@ppp-58.8.1.219.revip2.asianet.co.th] has joined #launchpad
=== mpt [n=mpt@121-72-131-100.dsl.telstraclear.net] has joined #launchpad
stubI think I'm going to do a full rollout - r415307:54
stub(as long as malcc or cprov agrees - soyuz is running with local patches)07:54
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
=== Fujitsu [n=Fujitsu@ubuntu/member/fujitsu] has joined #launchpad
SteveAmorning08:29
stubMorning08:30
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
stubSteveA: Where are the navigation menus generated from now? I need to change the URLs they all point too08:43
=== stub finds LaunchpadRootFacet
SteveAwhich navigation menus?08:57
SteveAthere are several08:57
SteveAah, okay08:57
SteveAyou'll need to also grep for absolute URLs starting with the paths you're changing08:57
stubThere seem way to many places to change :-(08:58
stub $ grep -R /malone/ .  | wc -l09:01
stub13109:01
SteveAredirects should handle it if you miss any09:01
SteveAparticularly if the redirects have logging09:02
=== mholthaus__ [n=mholthau@140.245.76.83.cust.bluewin.ch] has joined #launchpad
stubThere won't be a redirect for /malone, because that is a perfectly valid URL to the malone product under the new system09:04
stubSo LaunchpadRootFacet handles the top level menu, bug URLs in the navigation and actions portlets in /+bugs still point to /malone/09:07
stubAnd I don't know what generates that popup menu at the top of the page either09:08
lifelessstub: have you just done an update ?09:10
stubof what?09:10
lifelessnever mind09:11
lifeless(got a weirdness in malone)09:11
mptstub, are you going to break URLs of the form https://launchpad.net/bugs/nnn?09:16
SteveAI think we should blacklist "bugs" to keep that working09:18
stubmpt: yup09:18
mptSteveA, agreed09:19
stubThe amazing mutating spec09:19
mptThere was a spec???09:19
stubYup09:19
stubAlthough it didn't have URL changes at all on it originally ;)09:19
mptThat's something wrong with the spec process, perhaps09:20
stubOk. So no tacking on UI changes to non UI specs after the non-UI spec has been implemented09:20
mptSpecs *should* mutate, otherwise for someone starting as a Launchpadder in five years, there will be no useful information outside of the code09:22
mptunless that's an ok thing09:23
stubNah - specs should be obsoleted, possibly by other specs being implemented (IMO)09:24
mptWell, specs can (a) describe how a feature should behave, or (b) describe how something should be changed09:24
mptCurrently we have (b), so our specifications are glorified bug reports09:25
stubSpecs describe work to be done (except for specs flags as informational), and are not documentation that needs to be maintained.09:25
mptBut without (a), it's harder to do QA, or to decide whether something is a bug.09:25
lifelessthe best specs I've seen describe a state to reach09:27
lifeless*and*09:27
lifelesshow to reach it09:27
stubYou are talking about a Launchpadder in 5 years time. Unless the specs are treated as documentation and maintained in lockstep with code, QA using the spec is just silly. And specs should not be documentation, they should be a description of a task that was discussed, approved and implemented at a particular point in time.09:27
mptI see only assertions in that paragraph :-)09:28
stubSpecs should not be mutated, as then they stop being specs and become moving targets. You have no idea what is implemented, what will be implemented, what might be implemented, what was implemented.09:30
stubIf you have one spec, you might have an answer to one of those. Or a very confusing spec that attempts to address two or more.09:31
mptI don't think any of those particularly matter. What matters is whether there's a difference between what the spec says and what the code does.09:31
mptBecause that can be regarded as a bug in one or the other.09:31
mptOtherwise you can't tell whether the divergence was because of design decisions made since the spec was approved, or because the developer was sloppy.09:32
stubWe need a different term then. In most usage, a spec represents an agreed chunk of work generally in the context of someone implementing a spec. Changes to specs during implementation involve negotiation. And changes post signoff are irrelevant as the chunk of work is done.09:33
mptSo, I'm not a wizened software engineer, but I'm thinking of functional specifications09:34
mptAre you thinking of a different kind?09:34
stubSame I think. But I don't see how a spec being implemented today can possibly be relevant in 5 years unless no work was done on that feature over that time.09:34
stubOnce a spec is implemented, its only use is historical information and possibly finger pointing.09:35
stubIf the feature needs to change, write a new spec.09:35
mptOkay, that's great09:39
mptbecause it greatly reduces the rationale for having a separate bug tracker and feature tracker :-) 09:40
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad
stubUse case would be a bounty on implementing a particular spec. The spec at the time the bounty was accepted is what counts, with changes a possibility through negotiation. And changes after signoff just represent destruction of historical record.09:44
=== stub wanders off to sort out flights
=== Spads [n=spacehob@217.205.109.249] has joined #launchpad
=== ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad
=== slgeorge [n=steve@217.205.109.249] has joined #launchpad
=== Znarl [n=karl@bb-82-108-14-161.ukonline.co.uk] has joined #launchpad
=== mpt [n=mpt@121-72-131-100.dsl.telstraclear.net] has joined #launchpad
=== 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
SteveAmpt: ping11:07
mptSteveA, pong11:07
SteveAskype call?11:08
mptsure11:08
mptWell, I could hear you...11:10
UbugtuNew bug: #66367 in launchpad "Number of translations to do" [Undecided,Unconfirmed]  http://launchpad.net/bugs/6636711:10
mptthat's a dupe11:11
SteveAi could not hear you11:11
SteveAlets try echo test, both of us11:11
mptworks fine for me11:12
SteveAtry again pleae11:12
SteveAI'm having intermittent issues hearing voices11:13
mptok11:13
SteveApoo 11:13
SteveAsilence11:13
mpt?11:14
jameshdo you have your microphone muted?11:15
mptIf I did, the echo test wouldn't work...11:15
SteveAno, it's a bluetooth issue I think11:15
mptcomplete silence from you now11:16
SteveAI'll adjust alsa setting11:16
SteveAdon't just hang up!11:16
mptShall I sing?11:16
SteveAno11:16
SteveAhmm11:18
=== mpt thinks pqm.launchpad.net should have less aggressive caching
SteveAalso spracht11:18
jameshmpt: I don't think it has any caching11:20
jameshmpt: the output of the test suite would be buffered, so the web front end wouldn't see each new line as it is generated11:24
jameshstdio only uses the line buffered mode (flush on new line) when outputting to the terminal11:25
mptIt doesnt't send any Expires header, or anything else11:26
mpthttp://www.ircache.net/cgi-bin/cacheability.py?query=http%3A%2F%2Fpqm.launchpad.net%2F11:26
jamesh... so it isn't using caching11:26
jameshthat URL site says that it will be considered stale11:28
jameshhow can you less agressively cache the result than not caching it at all?11:28
=== danilos [n=danilo@ip-115-195.sn1.eutelia.it] has joined #launchpad
mptMaybe Epiphany is looser with caching11:34
=== stub [n=stub@ppp-58.8.1.219.revip2.asianet.co.th] has joined #launchpad
stubdanilos: Do you remember what I was supposed to be runnng against the production database today? I can't find the details in my IRC log and Carlos never emailed me (assuming it was actually Carlos who asked).12:12
danilosstub: copy-translations12:13
stubdapper -> edgy?12:13
danilosstub: let me check the proper syntax, I think it's "copy-translations-from-parent.py dapper edgy"12:13
danilosstub: that's right12:13
stubok - that's all I need. I'll wait until malcc or cprov get online to see if I can combine the downtime with a rollout.12:14
=== stub hopes Carlos wasn't just guessing when he said half an hour
=== sabdfl [n=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad
lifelesslp review teem meeting in 41 minutes12:19
=== mpt [n=mpt@121-72-131-100.dsl.telstraclear.net] has joined #launchpad
mptA 6.8 MB PQM failure message? That has to be some kind of record12:27
spivmpt: lucky you!12:28
mptI must have caused every single pagetest to fail voluminously12:28
stubjamesh: Are you aware of any limits to the size of a regexp?12:31
jameshstub: not off hand12:31
stubI'm wondering how safe it is to use a single |'d regexp when the list grows to be a few hundred items long12:32
jameshstub: I can't see it being worse than maintaining all those regexps separately12:32
stubI'll probably leave it the way it is though, as it will allow the UI to report the id of the regexp matched if we want12:34
stub(yagni?)12:34
jameshstub: fair enough.  If that feature is really needed, it can also be done with named groups12:35
spivstub: If you used named groups (like Moin's markup parser), you could have one regexp but still report an id.12:35
jameshstub: but if you'd prefer to go with multiple regexps for now, go for it.12:35
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad
jamesh(just make sure they don't get recompiled every run)12:35
stubspiv: As in r'(?P<1>exp_1)|(?P<2>exp_2)|...|(?P<n>exp_n)' ?12:38
stubMeans people can't use (?i) syntax but that might be good12:40
spiv>>> re.compile(r'(?P<a>a+)|(?P<b>b+)|(?P<c>c+)').match('aaaaa').groupdict()12:40
spiv{'a': 'aaaaa', 'c': None, 'b': None}12:40
SteveAstub: ask gustavo12:44
SteveAhe maintains regex libs in python12:44
=== Keybuk [n=scott@quest.netsplit.com] has joined #launchpad
SteveAlifeless: review meeting?01:01
stubTests show only 100 named groups01:04
SteveApython library tests?01:04
SteveAnamed groups, so that you can say which pattern a particular name falls foul of01:05
stubMe playing with a command line tests.01:05
stubNon named groups have a similar limit01:05
SteveAoh, a limit in python?01:05
SteveAI was confused by your use of the word "Tests"01:06
SteveAlifeless: ping01:07
lifelessreview meeting01:07
lifelesssorry, had a phone call from mum right at the start01:07
lifelessgetting organised give me 501:08
SteveAok01:10
=== slgeorge [n=steve@217.205.109.249] has left #launchpad ["Leaving"]
lifelessok01:12
lifeless== Agenda ==01:13
lifeless * Roll call01:13
lifeless * Queue status.01:13
lifelesswho art here ?01:13
BjornTme01:13
spivme01:13
SteveAme01:13
jameshme01:13
lifelessqueue status...01:14
SteveAactually... grammar nazi...01:14
SteveAI01:14
lifeless:)01:14
lifeless11 items in the queue01:15
lifelesslongest is the tt-workflow mega branhc01:15
lifelessBjornT: how is that co,ing ?01:15
BjornTlifeless: i think i can finish it tomorrow. but it's taking some time since it's big, and i've also done other reviews in parallel, since it don't want it to block my queue completely.01:16
lifelessBjornT: I've been trying not to allocate anything to you01:16
SteveAtt-workflow?01:16
lifelessBjornT: how many hours so far reviewing it ?01:16
SteveAI can't quite place this01:16
SteveAwho is the author?01:17
=== malcc [n=malcolm@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
spivtt == "ticket tracker", I believe.01:17
lifelesshttps://launchpad.canonical.com/SupportTrackerWorkflowSpec01:17
lifelessflacoste01:17
lifelesssee https://launchpad.canonical.com/PendingReviews for details01:17
SteveAok, thanks.  does francis know that large branches are not welcome in the future, and that he can get support from the review team in working out how to make landings in smaller units?01:18
BjornTlifeless: i haven't checked yet, but i'd say it's almost two full working days. in short, several smaller patches would have been much faster to review.01:18
lifelessSteveA: I think we need to do a general announcement about this01:18
SteveAit's difficult to reverse-engineer a suitable staged landing plan from the whole blob01:18
lifelessSteveA: as I mentioned on the phone to you01:18
SteveAlifeless: I announced it last week in the meeting, btw01:18
BjornTSteveA: i will at least inform him about it in my review.01:18
lifelessSteveA: thank you01:19
SteveAbut I think this will take several announcements01:19
SteveAit was met with general support iirc01:19
SteveAor, my ego is being overactive again01:19
lifelessok, so jamesh - you have two branches over the 2 day goal period - whats up there ?01:19
Keybuksabdfl: ping01:19
lifeless(4 and 7 respectively)01:19
KeybukI still get "Not allowed here" for https://launchpad.net/sprints/uds-mtv/+settopics01:19
jameshlifeless: just posted a review of matsubara's one.  Will get on to Bjorn's one01:19
SteveAwe may need to go to a policy of rejecting large landings unless they've been agreed with a reviewer in advance, sometime over the coming weeks01:20
lifelessSteveA: :) I was proposing something like this to you, and you suggested we wait and talk in allhands01:20
lifelessSteveA: so lets wait, and talk in allhands about it01:20
lifelesseverything else is within our target review period of 2 days01:21
lifelessthough there are a number of branches - BjornT spiv SteveA are the reviewers - that need to be done tomorrow at latest.01:22
=== mdz [n=mdz@217.205.109.249] has joined #launchpad
lifelessjamesh: you were bringing up white space cleanups at the lp meeting last week. How did that go ?01:22
spivI'm not sure that flacoste's 3402 line diff will be reviewed be reviewed tomorrow.01:22
jameshlifeless: I forgot to add it to the agenda.  Will do so for this meeting01:22
BjornTlifeless: i plan to spend all of today and tomorrow reviewing, hopefully i'll finish all my reviews then.01:23
=== Keybuk [n=scott@quest.netsplit.com] has joined #launchpad
SteveAlifeless: I have some review time today01:23
lifelessSteveA: you already have jamesh/launchpad/death-to-tabindex allocated to you01:24
lifelessSteveA: if you have time to do flacostes flacoste/launchpad/tt-views instead, you and spiv can swap :)01:24
lifeless(death to tabindex is 1K lines, largely mechanical01:24
lifelesstt-views is 3.4K lines, and not so mechanical, but seemed probably ok when spiv and I glanced at it01:25
BjornTSteveA: if you have time for some more reviews, you could take salgado's shipit branch from my queue. i think it's fairly small, but i won't get by reviewing it today.01:25
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
lifelessloo01:25
lifelesslol, its pile on stevea day01:25
SteveAstick them in my queue, and we'll see what I can do today01:26
lifelessSteveA: fyi salgado is too busy with 1.0 to review at the moment, so there is some extra pressure on the review team; and the lp coding team has grown recently too01:26
SteveAafter that, I want no more reviews this week01:26
lifelessSteveA: ok01:26
SteveAas I have UI 1.0 stuff to do01:26
spivSteveA: thanks01:26
lifelessjamesh: can you trigger a reviews run please01:27
lifelessok, any other business? 01:27
jameshlifeless: finished01:28
lifelesswicked01:28
lifelessSteveA: your reviews are ready01:28
lifelesshttps://devpad.canonical.com/~jamesh/pending-reviews/01:28
lifelessSteveA: the biggest ones first please!01:28
lifelessany other business 501:29
lifelessany other business 401:29
lifelessany other business 301:29
lifelessany other business 201:29
lifelessany other business 101:29
lifelessthanks for attending!01:29
SteveAthanks lifeless 01:30
ctrlsoftjamesh: hi01:30
=== cprov [n=cprov@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
ctrlsoftjamesh: Is there any easy way to import bugs from trac into lp?01:30
ctrlsoft(not just remote watch, but really migrate)01:32
jameshctrlsoft: not at present.  We have an importer from the XML dump effbot's SourceForge tools generate, but that is not really that user friendly to generate01:32
jameshgetting a better interchange format is a todo01:32
lifelesspoolie: btw, dotted decimal has landed01:32
=== raraavis [n=emurphy@194.18.118.70.cfl.res.rr.com] has joined #launchpad
ctrlsoftjamesh: ok, thanks01:34
poolielifeless: sweet01:35
jameshctrlsoft: we have an XML export format for a product's bugs, so it would be useful to be able to import something in a similar format01:35
jameshbut that code isn't yet ready.01:35
ctrlsoftjamesh: Any spec/bug about it?01:36
jameshctrlsoft: no01:37
jameshctrlsoft: I've already written importers for Ubuntu Bugzilla and SourceForge, so I'd really like to have a sane XML format I could tell people to give me01:39
=== jinty [n=jinty@127.Red-83-50-221.dynamicIP.rima-tde.net] has joined #launchpad
ctrlsoftjamesh: Yeah, that makes sense. I'm happy to write a generator for trac once there's a format01:39
=== salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
=== niemeyer [n=niemeyer@200.138.50.152] has joined #launchpad
=== matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
=== BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad
lifelessgnight all02:36
stubcprov: I would like to roll out r4153 either tonight or (preferably) tomorrow morning my time.02:48
stubcprov: That will add db patches 67-21, 22, 23, 24 and 2602:50
stubcprov: I don't think any of those affect soyuz but thought I should confirm02:53
=== matthewrevell [i=synchron@outbound.silenceisdefeat.org] has joined #launchpad
=== bradb [n=bradb@modemcable077.58-130-66.mc.videotron.ca] has joined #launchpad
UbugtuNew bug: #66408 in malone "URL of bugs does not understand rejected bugtask status" [Undecided,Unconfirmed]  http://launchpad.net/bugs/6640803:10
cprovstub: yes, looks ok, but we need 4155 cherrypick03:18
cprovstub: or we can do it ourself only in drescher03:19
stubcprov: So you don't need those local patches listed on the wiki page?03:19
malccstub: Let me check, I think they were mostly turning something off then back on again and things which are in rf, I'll confirm in a moment03:20
malccstub: Yes, confirmed. Two local fixes undo each other, the third is r4136.03:23
cprovstub: the db patches should be fine too03:25
stubcprov: I will roll out 4155 tomorrow everywhere, including drescer then.03:26
cprovstub: perfect, thank you03:26
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad
=== zwnj [n=zwnj@213.207.218.157] has joined #launchpad
salgadoSteveA, do you have some time to review my latest shipit changes today, so that I can ask stub to include them in tomorrow's roll out?04:26
stubShouldn't we sit on the changes a few days before pushing out brand new code, or is it really urgent?04:26
salgadostub, it is /really/ urgent, and it's quite low risk --just changes the front page04:28
stubok04:29
=== PSUSI [i=hidden-u@iriserv.iradimed.com] has joined #launchpad
PSUSIhow would one go about getting spam removed from bugs on launchpad?04:37
seb128is there a way to mail all the member of a team on launchpad?04:40
=== _thumper_ [n=tim@tpsoft.gotadsl.co.uk] has joined #launchpad
=== gjc [n=gjc@eremita.di.uminho.pt] has joined #launchpad
gjchmm.. lucky me, no nick registration needed here :)04:43
=== _thumper_ [n=tim@tpsoft.gotadsl.co.uk] has joined #launchpad
=== matthewrevell [i=synchron@outbound.silenceisdefeat.org] has joined #launchpad
PSUSIanyone know what to do when someone starts spamming bugs on launchpad?  can it be cleaned up and the offending email unsubscribed?04:58
salgadoPSUSI, although there's no automated way to do so, we can sort it out for you. what's the bug that's beeing spammed?05:02
PSUSII have a list of about 10 bugs that some silly person is also subscribed to and he seems to have recently installed a very broken email blocking probram that has ignored the Errors-to: header and replied with a confirm request to each bug05:03
PSUSIso now this silly confirm request is posted to all of these bugs... standby for list05:04
jameshdistributed spam blocking: get the rest of the world to filter your email05:04
PSUSI35934, 38649, 64174, 44370, 64585, 28925, 45768, 3028405:05
PSUSIhehehe05:05
UbugtuNew bug: #66422 in malone "How to deal with spam" [Undecided,Unconfirmed]  http://launchpad.net/bugs/6642205:05
PSUSII just wish the retarded developers of these things would at least respect the damn Errors-to: header05:06
PSUSII also found a half a dozen of these confirm requests in my mailbox this morning as a result of a few posts to a public mailing list05:06
jameshIt is an argument for requiring that replies maintain some token in the subject line (e.g. the bug number)05:06
PSUSIthe list sets Errors-to: specifically to be able to deal with ( read: unsubscribe ) email addresses that are undeliverable instead of bothering subscribers with that05:07
PSUSII think just setting the From: filed to an undeliverable address would fix it actually05:08
PSUSInormal mail clients will use the Reply-to: anyhow05:08
ddaasome do05:08
ddaait's an ongoing flamewar topic05:09
=== PSUSI flames on then
salgadoseb128, no, we don't have a way to do that yet. (bug 44545)05:09
UbugtuMalone bug 44545 in launchpad "FOAF Request: make all Teams into email-aliases/mailing-lists" [Medium,Unconfirmed]  http://launchpad.net/bugs/4454505:09
PSUSInon broken mail clients will respect it ;)05:09
seb128gjc: ^^05:09
seb128salgado: thank you05:09
PSUSIjamesh: so you are manually cleaning the spam from the bugs and unsubscribing the guy?05:10
PSUSIerr, salgado  even05:10
gjcseb128, salgado: thanks05:11
salgadoseb128, gjc, np.05:12
salgadoPSUSI, I can't do that myself, but I just noticed that he's only subscribed to bug 2892505:14
UbugtuMalone bug 28925 in xserver-xorg-driver-ati "X fails to start in dapper flight3 & 4 with ati X600, onward all the way through dapper 6.06 LTS" [Unknown,Unknown]  http://launchpad.net/bugs/2892505:14
salgadothe problem is that he's notified every time a bug is marked as a duplicate of that one, and that one has lots of dupes05:15
PSUSIsalgado: do you know who can?  and if he isn't subscribed then why did he get notifications from the bug?05:15
PSUSIahhhh05:15
PSUSIyes05:15
salgadoactually, he's subscribed to 47083 which is a dupe of 2892505:16
salgadooh, he reported that one. :/05:16
salgadostub, is there anything we can do to avoid glen-stewart's spam killer to spam bug 47083 and the dupes of 28925?05:20
UbugtuMalone bug 47083 in xserver-xorg-video-ati "installer CD fails to start X on Radeon X800 GTO" [Medium,Unconfirmed]  http://launchpad.net/bugs/4708305:20
elmosalgado: how about a rubber duck deactivates his email, would that work?05:22
stubeh?05:24
salgadoelmo, that may cause OOPSes because we assume that somebody who reported a bug has a preferred email05:25
elmosalgado: sweet05:26
salgadostub, on 47083 we can see an automated reply from the reporter's spam killer asking for a confirmation of the message. a similar message is sent every time a bug is marked as a dupe of 47083 or 28925.05:28
stubBg 4708305:28
stubBug 4708305:28
UbugtuMalone bug 47083 in xserver-xorg-video-ati "installer CD fails to start X on Radeon X800 GTO" [Medium,Unconfirmed]  http://launchpad.net/bugs/4708305:28
stubI'll unsubscribe glen-stewart for a start05:29
stubI wonder if elmo's suggestion would blow anything up? It should work, but unlikely to be tested.05:30
stubHmm... should, because they would become an invalid user.05:31
salgadoI think it'd blow if the guy was the only person subscribed to that bug05:31
salgadomight blow in other cases too05:31
stubNot much we can do anyway - it isn't as if Launchpad will ever be able to communicate with them.05:33
=== lbm [n=lbm@82.192.173.92] has joined #launchpad
=== mdz [n=mdz@87-194-36-33.bethere.co.uk] has joined #launchpad
salgadostub, btw, I think we had enough testing of the mirror prober on staging. there's no need to keep it running there05:45
stubok05:45
=== daq4th [n=darkness@netstation-005.cafe.zSeries.org] has joined #launchpad
=== carlos [n=carlos@146.Red-80-36-81.staticIP.rima-tde.net] has joined #launchpad
carloshi06:40
=== kiko_ [n=kiko@200.103.112.11] has joined #launchpad
=== kiko_ is now known as kiko-fud
kiko-fudbonjour mes amies06:43
kiko-fuderr amis06:43
kiko-fudhow's it going?06:43
SteveAhello world06:45
SteveAsalgado-lunch: still need that review done?06:45
kiko-fudsabdfl, around?06:50
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
kiko-fudhey cprov-lunch 07:08
salgado-lunchSteveA, yeah, I do07:08
cprov-lunchkiko-fud: hey07:08
kiko-fudhow's it going cprov-lunch 07:13
kiko-fudjust saw your update to n-m-a-f07:13
cprov-lunchkiko-fud: yes, very good so far, updating specs & plans, testing new i-f-p (w/o translations) in mawson.07:14
kiko-fudcprov-lunch, the funny part is that mdz doesn't think that changing the RFC address would be a big deal07:15
kiko-fudcprov-lunch, and malcc?07:15
malccChanging my rfc address probably wouldn't be a big deal either07:16
cprov-lunchkiko-fud: well, it's precisely what is in the DSC, it will only change if we modify the SPR07:16
kiko-fudmalcc, so you arrived in one piece?07:17
kiko-fudcprov-lunch, no, mdz was saying that it wouldn't be strictly necessary to store that exact line07:17
kiko-fudas long as we never regenerated old indices files, I guess07:17
malcckiko-fud: Yup, the journey was suspiciously smooth. I think the universe must have a nightmare in store for me on the way home07:17
kiko-fudmalcc, you firm believer in karma?07:18
cprov-lunchkiko-fud: yes, I understood, but better keep it constant, following the DSC, not the Person.displayname, IMHO.07:18
kiko-fudcprov-lunch, yeah, I'm okay too07:19
=== Spads [n=spacehob@host-84-9-50-48.bulldogdsl.com] has joined #launchpad
SteveAsalgado: I'm reviewing your shipit branch now07:56
=== Spads [n=spacehob@host-84-9-50-48.bulldogdsl.com] has joined #launchpad
ddaaSteveA: my hands are falling off, and I'll be going for dinner soon08:05
ddaaI'll reply to poolie about the debian svn issue tomorrow08:05
ddaasome clarifications seem to be needed08:05
malccHmm, looks like the date created patch went into rocketfuel without the matching sampledata changes, anyone regenerating sampledata at the moment gets a bonus 1000 lines for their patch08:08
=== mdz [n=mdz@87-194-36-33.bethere.co.uk] has joined #launchpad
malccAny objection if I do nothing but make newsampledata in a branch and trivial it?08:08
kiko-fudmalcc, no objection, d it.08:09
=== ryanakca_ [n=ryan@unaffiliated/ryanakca] has joined #launchpad
SteveAsalgado: reviewed. well done.08:11
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
=== |telenieko| is now known as telenieko
sivanghi all09:22
sivangis there a way to list package karms joined by maintainers, over a specific team? (ubuntu-dev)09:22
=== lamont has a question for the launchpad gang
lamontcurrently there are 3 or so releases worth of build logs in people.u.c/~lamont/buildLogs - does it make sense to import those into launchpad to go with the binaries that are there?09:57
kiko-fudlamont, good question, check with cprov if it's doable10:28
lamontkiko-fud: you will, or I should?10:30
=== Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad
kiko-fudlamont, if you can, that'd be best10:30
lamontcprov: how about it? ^^^10:30
lamont:-)10:30
malccSo this is build logs which would have been imported by gina, if gina imported build logs, right?10:31
kiko-fudyes.10:31
=== kiko-fud gone
cprovlamont: what buildlogs ? security ?10:31
lamontpeople.ubuntu.com/~lamont/buildLogs - all of warty-breezy build logs10:31
lamontno security logs10:32
lamontjust thinking it might be good to prune the size of that tree on p.u.c10:32
lamontesp since someone went there today looking for an edgy build log, and had to be redirected to launchpad...10:32
cprovlamont: well, not sure if they are useful since they were not done using our buildfarm. really, dunno.10:33
salgadoSteveA, around?10:34
lamontcprov: neither were the binaries... :)10:34
cprovlamont: it's feasible and you want them we can do it. if it was your question.10:34
lamontcprov: the real question was (1) does it  make sense to do it, and (2) if so, how feasable?10:34
cprovlamont: yes ;) legacy10:35
lamontexactly10:35
cprovlamont: it only make sense if you use it 10:35
lamontwell, not personally, but sometimes it's useful to compare the build log with the one that's not working for a security update or some such10:36
cprovlamont: it's feasible, it's just a matter of finding the correspondent build record, upload the log to librarian and update its buildlog field10:36
lamontso it really gets back to a dev-team question of "do we want them".  got it.10:36
lamontcprov: I'll ask dev-team et al, and get back with you10:36
cprovlamont: good, thank you for pointing that, I appreciate it.10:37
lamontnp10:38
SteveAsalgado: hi10:46
salgadohi SteveA.  about the XXX I droped from some config files on my shipit-for-edgy branch... I'd like to keep them since I'm going to remove the variable I added soon10:47
salgadodo you think it'd be okay to not add that variable on the production config files and leave the XXX in them?10:48
=== jkakar [n=jkakar@204.174.36.228] has joined #launchpad
SteveAsalgado: I'd say leave the XXX, add the variable, but add a further line of comment above the variable saying10:56
SteveA # XXX: the following config item is temporary, so the XXX above applies in the long term.10:56
salgadofair enough10:59
salgadoSteveA, do you know if it's possible to check the status used by the redirect using testbrowser or if I have to use an old-style test?11:06
salgadoBjornT, maybe you know ^^?11:06
SteveAI think you can't easily check from a regular "real" browser11:11
SteveAso it may not be so easy from testbrowser11:11
SteveAlooking at the testbrowser code, doesn't look like there's an easy way11:14
SteveAso, write an old-style test for it11:14
BjornTsalgado: i think you can do it by setting browser.handleError = True (or maybe False). but i'm not sure.11:14
salgadoyeah, I couldn't find anything either11:14
=== salgado tries
=== Fujitsu [n=Fujitsu@ubuntu/member/fujitsu] has joined #launchpad
sabdflkiko: briefly now - 'sup?11:33
=== bradb [n=bradb@modemcable077.58-130-66.mc.videotron.ca] has left #launchpad []
=== mdz [n=mdz@george.kkhotels.co.uk] has joined #launchpad

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!