/srv/irclogs.ubuntu.com/2006/08/04/#launchpad.txt

=== AndreNoel [n=noel@200.175.38.38.adsl.gvt.net.br] has joined #launchpad
=== sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad
=== bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #launchpad
=== bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad
lifelessbradb: around ?01:27
bradblifeless: yeah01:27
lifelessdo you think, that if I send an email to new-bugs, cc'd to $person, malone would be sane in subscrbing $person automatically?01:28
lifelessbe^01:30
lifelessbradb: ^01:30
bradblifeless: I don't know that there's a correct answer to that question, but it would probably be more sane than not.01:30
lucasvolifeless: in that case I would add a header to the first email LP sends to $person that he has been subscribed because....01:30
bradbRoundup does that, I believe.01:30
lifelesswould you like a wishlist bug or a placeholder spec ?01:30
bradblifeless: bug sounds good01:31
lifelesshow do you tell the bugmail to be wishlist ?01:31
bradblifeless: you can't change priority via email, unfortunately01:32
lifelessha!01:32
lifelessis that by design ?01:32
bradblifeless: not really01:33
lifelesswant a bug on that too ?01:33
bradblifeless: er, n/m, i'm on crack01:36
=== bradb wonders if the email ui might be on crack though. /me checks something
bradblifeless: you can change importance through the email UI, but if it's working properly that should be restricted to only bugcontacts and drivers01:37
lifelessfair enough01:38
lifeless... how ?01:38
bradblifeless: https://help.launchpad.net/UsingMaloneEmail#head-193f41e9738ba7e7f971421b5ef98657eedad87301:40
lifelessthanks01:41
bradbnp01:41
lifelessbug 55113 is for thee01:41
Ubugtu'Malone bug 55113 in malone "ccing a person in mail to malone should subscribe them to the bugs\n\taffected." [Untriaged,Unconfirmed]  http://launchpad.net/bugs/55113'01:41
bradbthanks01:41
lifelessaww, rfc822 normalisation fucks over malone.01:42
lifelessnew bug coming up01:42
lifelessbradb: also01:45
lifelessbradb: why does it take malone so long to acknowledge my new bug filings via email ?01:45
bradblifeless: AIUI, the emails are processed by a cron job every N minutes. bjornt could confirm.01:46
lifelessI was wondering if the 'group actions when emailing' code was grouping new bug mail too01:46
lifelessbecause its a new bug no-one can possibly have followed up on it immediately01:47
lifelessso it would make sense to reply immediately IMO01:47
bradbthat may be true. if you want to make sure bjornt sees it, feel free to file a bug.01:49
lifelessok01:49
lifelessI've filed another one, on the syntax01:50
lifelessaccepting accepts: /products/malone would be really nice UI01:50
lifeless(as well as accpeting affects /products/malone)01:50
bluefoxicysfllaw:  are you about?01:51
bradblifeless: you mean "accepting affects: /products/malone", presumably?01:51
lifelessyes01:52
lifelessI also wrote a cute email to demonstrate this :)01:52
lifelesshttps://launchpad.net/products/malone/+bug/5511501:52
UbugtuMalone bug 55115 in malone "control lines in bugmail should accept : prefixes" [Untriaged,Unconfirmed]  01:52
bradbright01:52
bluefoxicy\:01:53
kiko-zzzbluefoxicy, can you remind me tomorrow to generate the stats for you? i'm so tired tonight..01:53
lifelessheh, 3 of the last 5 bugs across malone reported by me :)01:53
bluefoxicykiko-zzz:  nods.  I still say it'd be nice to have a feature to spit out various statistics through launchpad.01:53
=== bradb would like to tag these bugs as "email"
bluefoxicykiko-zzz:  I'm in no hurry ;)01:53
lifeless4 of the last 501:54
kiko-zzzbluefoxicy, yeah, but the devil's in the details -- how many statistics, and what sort of flexibility you want in generating them (per-month? per-week? grouped? by person? etc. it gets hairy)01:54
bluefoxicykiko-zzz:  flexible infra and step feature by feature :)01:55
bluefoxicyanyway nighters, see you another time01:55
sfllawbluefoxicy: Yes.01:55
sfllawI'm making supper though.01:55
sfllawHow can I help you?01:55
sfllaw(I may pop out to check the stove.)01:55
bluefoxicysfllaw:  oh, I was just looking for stats on how many bugs get reported per month in Ubuntu on launchpad01:57
bluefoxicykiko said either you or he may be able to help me with that :)01:57
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
bluefoxicy(there's other interesting data that I could use too, but it's not really important)02:01
sfllawPer month?02:02
sfllawI don't know specifically.02:02
sfllawLemme look at my charts.02:02
sfllawWe seem to get about 1000 per week.02:03
sfllawSo about 3500-4000 per month.02:03
bluefoxicyI thought the number was increasing overtime?02:04
=== lifeless waves at sfllaw
lifelesssfllaw: btw there is a distributed test manager written in python already02:04
sfllawHuh.02:05
sfllawNeato.02:05
sfllawI'm not adverse to borrowing.02:06
lifelessI'll hunt down a link02:06
lifelesshttp://www.codesourcery.com/qmtest/02:08
lifelessI have not used it myself02:08
sfllawAh.  CodeSourcery.02:11
sfllawI'll ask scjody about it.02:11
sfllawThanks.02:11
lifelessscjody ?02:12
sfllawWhoops.  Wrong guy.02:12
sfllawI mean Carlos O'Donnel.02:12
sfllawSomeone I know at CodeSourcery.02:12
lifelessah cool02:12
lifelessaltogether now02:12
lifeless'its a small small world'02:13
bluefoxicysfllaw:  off the top of your head do you have a number for somewhere around say July 2004?  I tried doing a search for all bugs (oldest first) of all statuses and importances, including duplicates, in Ubuntu; results showed around 350-400 bugs between 6912 through 7250 being in Ubuntu02:13
bluefoxicyperhaps the search doesn't do what I think :)02:13
sfllawbluefoxicy: We didn't keep track of figures then.02:13
sfllawYou might be able to bribe kiko or bradb to extract them for you.02:13
bluefoxicy(I only looked at bugs between 7/01 and 7/30)02:13
bluefoxicysfllaw:  ah.  Okay.  I guess I'll wait for kiko to get up tomorrow then.02:14
bradblifeless: verifyObject(IFoo, foo) raises a BrokenImplementationError claiming that foo doesn't provide method bar, when really it appears the problem is that the current user doesn't have the perms to access method bar. does raising an exception there seem correct to you?02:14
sfllawOf course, back then we were using Bugzilla.02:14
sfllawSo we may have lost this data.02:14
lifelessfoo is presumably a security proxy ?02:15
bradblifeless: yeah02:15
bluefoxicysfllaw:  well, the dates are still in the bugs; https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/6912 for example shows it affects Ubuntu and was reported on 2004-07-0102:15
UbugtuMalone bug 6912 in linux-source-2.6.15 "kernel-source-2.4.26: Kernel panic with NFS traffic over IPsec" [Unknown,Unknown]  02:15
bradbI'm also wondering if I really mean to be verifying the object, or instead doing verifyClass or even IFoo.providedBy.02:16
bluefoxicysfllaw:  but if the data is lost then I'll just have to go with what I can get.  :)02:16
lifelessand bar is part of IFoo ?02:16
bradblifeless: yeah. works fine when logged in as priv'd user02:16
sfllawbluefoxicy: Is this for some kind of research?02:16
=== Keybuk [n=scott@quest.netsplit.com] has joined #launchpad
lifelessso, I'm not 100% on the underlying mechanism of the security proxy here. But - verifyObject will be probing for all attributes, and should be triggering an access denied exception when it tries to probe for bar02:17
lifelesswhy are you calling verifyObject ?02:17
bluefoxicysfllaw: It's not really that important, just flashing a bunch of numbers in a presentation I'm drawing up to explain an idea I had for pitti's automated-problem-reports spec02:17
bradblifeless: I want some kind of verification that things are providing the right interfaces02:18
bradb(in tests)02:18
=== bluefoxicy sticks the thing up on his server
lifelessbradb: is verifyObject called outside the test code path ?02:19
bradblifeless: maybe verifyClass is more appropriate02:19
bradblifeless: I'm calling it directly in a doctest.02:19
lifelessok02:19
lifelessbradb: local interrupt, bb in a couple minutes02:20
bradbsure, np02:20
sfllawbluefoxicy: Neato.02:21
bluefoxicyuh.  Hmm.  Server not listening.  *goes across the room for a bit*02:25
=== rpedro [n=rpedro@87-196-71-56.net.novis.pt] has joined #launchpad
lifelessbradb: so02:35
lifelessverifyClass will probably fail the same way02:35
lifeless(it will attempt to find an unboundmethod on the class, and that would allow security holes if you could get at that, then run it with the instance that is the proxy02:35
lifelessI think your test for 'do we get the right interface back' needs to either:02:36
lifeless - be done with a user that has access to the interface as a whole or02:36
lifeless - be done with a more restricted interface that is safe to give to everyone02:36
lifeless - or ask if it implements, not if it verifies02:37
bradbverify class seems to work02:37
lifelesssurprising02:37
bradber, verifyClass02:37
bradbi'm not surprised, tbh02:37
bradbbecause BugNomination is not security-wrapped02:38
bradbbut an object returned by bug.addNomination will be02:38
bluefoxicysfllaw:  http://bluefox.kicks-ass.org/stuff/bluefox/slides/slides/img4.html  <-- that slide is where I intended the data go; of course, it's just flashing numbers around, considering we already have the drinking-from-the-firehose spec pointing out that the bug load is too high.02:38
lifelessbradb: so testing approach wise, heres a thought02:39
lifelessbradb: verifying that objects implement the interface is best done very close to the code - i.e. within the security proxy boundary, in content-class-level tests02:39
=== mdz [n=mdz@studiocity-motorola-bsr1-70-36-194-85.vnnyca.adelphia.net] has joined #launchpad
lifelessbradb: outside that boundary, you may not be able to access the entire interface, so just asking if it claims to implement is enough - as long as you have detailed tests at the lower layer02:40
bradblifeless: right. i guess i still find it confusing that verifyObject would raise an error in this case. maybe it's not easy to say what the right behaviour should be, in that case.02:42
bradbthough, i think not raising an error is easier to understand02:43
lifelesswell02:49
lifelessit cant verify it02:49
lifelessso verifyObject *should* raise an error :002:49
bradblifeless: that it can't verify it seems like an implementation detail though02:51
lifelesserrr02:52
lifelessI'm not sure how that matters02:52
bradbI guess I can see how it makes sense.02:53
=== Rui [n=rmps@89.152.8.64] has joined #launchpad
lifelesswhen you ask verifyObject to verify something, it checks the entire interface to see that your current code can treat all the attributes named as attributes, and callables as callables02:56
lifelessit does not matter *why* you cant use a specific bit in the right way, it only matters that you cannot.02:56
bradblifeless: right02:58
bradbyour logic makes sense02:59
=== Rui [n=rmps@89.152.8.64] has left #launchpad ["Client]
=== bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #launchpad
=== kiko_ [n=kiko@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
=== stub [n=stub@ppp-58.8.3.37.revip2.asianet.co.th] has joined #launchpad
=== rpedro [n=rpedro@87-196-71-56.net.novis.pt] has joined #launchpad
=== quail [n=quail@unaffiliated/quaillinux/x-000001] has joined #launchpad
=== xenru|clone [n=Miranda@85.192.12.90] has joined #launchpad
=== mpt [n=mpt@203.118.156.188] has joined #launchpad
=== jamesh [n=james@81.16.227.227] has joined #launchpad
=== mpt_ [n=mpt@203.118.156.188] has joined #launchpad
=== Fujitsu [n=Fujitsu@c58-107-168-5.eburwd7.vic.optusnet.com.au] has joined #launchpad
=== Spads [n=crack@host-87-74-55-236.bulldogdsl.com] has joined #launchpad
SteveAgood morning08:54
=== rpedro [n=rpedro@87-196-15-9.net.novis.pt] has joined #launchpad
=== stub [n=stub@ppp-58.8.3.37.revip2.asianet.co.th] has joined #launchpad
=== BjornT [n=bjorn@195.182.78.95] has joined #launchpad
=== BjornT- [n=bjorn@195.182.78.95] has joined #launchpad
=== sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad
=== jamesh [n=james@203-59-20-109.dyn.iinet.net.au] has joined #launchpad
sivangmorning09:39
=== glatzor [n=sebi@ppp-88-217-0-39.dynamic.mnet-online.de] has joined #launchpad
sabdflhi sivang09:42
sivanghey sabdfl 09:43
SteveAmpt_: ping09:45
=== ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad
ddaaGood morning!09:49
SteveAmorning ddaa09:49
ddaampool: ping09:49
SteveAyou have a review09:49
mpoolddaa: hello09:49
ddaaSteveA: duh!09:49
=== ddaa kicks emacs
SteveAuse vim09:50
SteveAit is betta09:50
=== lbm [n=lbm@82.192.173.92] has joined #launchpad
SteveAemacs sucks vim rocks.09:50
ddaait's too modal for my taste09:50
SteveA</trolling>09:50
mpool"beeping and non-beeping modes"09:50
mpool:)09:50
ddaampool: hihihi09:50
jameshhi ddaa09:51
ddaahey jamesh09:51
ddaampool: you seem keen at nailing some kind of roadmap09:51
=== sivang reverted to vim after emacs's fonts got b0rked on edgy
ddaampool: I may have given the impression of waffling in the past days in those discussions09:51
ddaaactually, I was braindumping09:52
mpoolddaa: not at all, i think your mails have been very informative09:52
mpoolthere are two things i would like to talk with you about 09:52
mpool- general planning09:52
mpool- roundtripping09:52
=== ddaa thinks he rather turn down The Offspring
ddaasince the former is dependent on the latter let's start on roundtripping09:54
ddaahere or in #bzr?09:54
mpoolhow about on skype?09:54
ddaaany reason not to use ekiga09:55
ddaa?09:55
lifelessok, I'm popping away for the weekend09:55
=== jdub [n=jdub@ppp121-112.static.internode.on.net] has joined #launchpad
mpoollifeless: have a good weekend09:55
lifelesstchau tchau, though I may pop in from time to time09:55
jdubhey dudes09:55
ddaalifeless: hey09:55
jdubany of you guys experienced this bug -09:56
jdubhttp://mail.python.org/pipermail/python-bugs-list/2005-June/029183.html09:56
jdub?09:56
ddaalifeless: did you do this braindump about uploading/downloading souce trees for importd?09:56
jdub"gzip dies on gz files with many appended headers"09:56
mpoolddaa: i don't have ekiga on this machine09:56
mpoolbut otherwise it'd be ok09:56
ddaaI'm hopefully starting to do some work on that today or monday, so it would be useful09:56
mpoolhi jdub09:56
lifelessjdub: cool09:57
lifelessjdub: lovely bug, and no, but I relly must get my gzip tuning patch upstream09:57
jdubha ha09:57
lifelessddaa: dang, I knew I forgot something09:57
lifelessddaa: its in my TODO09:57
lifelessddaa: but I've been busy with 0.10 all day09:58
ddaalifeless: I KNOW the true meaning of this sort of answer :)09:58
mpoolddaa: so, skype?09:58
ddaayeah, was connecting the headset09:58
mpoolcool09:58
lifelessddaa: its agonising working with blueprint at the moment - so many page refreshes, and page load from here is about 5 seconds09:58
mpoollifeless: there are some similar issues with branches in lp i think - maybe not quite so bad09:59
=== jamesh [n=james@203-59-20-109.dyn.iinet.net.au] has joined #launchpad
=== Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #launchpad
jameshddaa: here's the first draft of my team branches article: https://chinstrap.ubuntu.com/~jamesh/team-branches.html10:06
jameshif you want to point out bits you think should be added/removed/changed10:06
=== ddaa is on voice with mpool
=== imbrandon_ [n=brandon@ubuntu/member/pdpc.active.imbrandon] has joined #launchpad
=== BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad
sivangwhere should I target a bug in the team expiray email notification? currently I opened it against 'launchpad', maybe this should be against FOAF ?10:22
sivangs/FOAF/registery10:22
sivangmalone #5515610:23
UbugtuMalone bug 55156 in launchpad "team expairy email should be more useful." [Untriaged,Unconfirmed]  http://launchpad.net/bugs/5515610:23
ddaajamesh: can you post the text to the ML so people can easily put comments in context?10:48
ddaaor a bzr branch, or a wiki...10:48
=== danilos [n=danilo@82.117.204.27] has joined #launchpad
=== doko_ [n=doko@dslb-088-073-098-217.pools.arcor-ip.net] has joined #launchpad
=== jdub [n=jdub@ppp121-112.static.internode.on.net] has left #launchpad []
KinnisonIs there a mechanism to mass-unsubscribe from bugs?11:08
stubInsert beer to continue11:10
sivangheh11:11
sivangstub-o-matic11:11
Kinnisonregretfully I have little option for delivery of beer11:12
=== Kinnison keeps on clicking
Nafallohi! where do I change Status on support tickets? :-)11:31
jameshKinnison: stub will be in London next week ...11:39
=== BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad
=== ddaa notes with great satisfaction that the emacs import is now up to revision 40936
jameshhow many revs do you think it has?11:52
ddaa76334 revs on MAIN11:53
ddaasadly, it's a roomba import ATM11:53
ddaameaning we'll have to start it over again on hoover before publishing it11:53
ddaaalso, as usual, there's no guarantee it's going to pass the final cross check at the end11:54
=== ddaa will run the python import directly on hoover
ddaakudos to the emacs sysadmin, it only lost the cvs connection once, on the initial changeset (most import do, cvs appears to be unable to do check-out like operation in the same connection as a rlog)11:57
stubSo we can no longer import SVN branches if there is no longer a corresponding sourcepackage?11:59
ddaastub: http://svn.python.org/projects/python/trunk12:00
ddaaoops12:00
ddaastub: https://launchpad.net/products/launchpad-bazaar/+bug/4624012:00
UbugtuMalone bug 46240 in launchpad-bazaar "posting $series/+source yields a confusing warning" [High,Confirmed]  12:00
ddaaKnown problem, but merely confusing, and relatively low profile.12:01
stubta12:03
sabdflddaa: do those imports go much more quickly with native-bzr tech?12:47
ddaaYes, the diff*history cost of baz was a real killer for really large branches.12:49
ddaaSo we squashed down a really large quadratic factor on the cost of large initial imports.12:49
ddaaBut it's still short of blindingly fast12:50
ddaaThe emacs import has been running since Tuesday 07:1012:50
ddaaMy uninformed performance guess is that most of cost lies in server round-trip. SVN import almost certainly do many more requests than they have to. CVS is probably better off. But in both cases we are still server-roundtrip bound, and we can probably do pipelining.12:54
ddaaBut since it's a guess and not a profiling result, it's virtually worthless.12:54
ddaaMh, actually, just since wednesday 07:10, it seems12:56
cprovgood morning, guys 01:28
mpt_hi cprov01:42
mpt_SteveA, pong01:42
mpt_cprov, did you see the message from Roshan Shariff on ubuntu-devel@?01:42
cprovmpt_: hi, not I'm not subscribed, can you forward it to me (btw, I will subscribe myself rigth now)01:43
mpt_cprov, well, it's mostly not interesting, but there's just one message about a possible soyuz problem01:43
mpt_cprov, sent01:43
cprovmpt_: thanks01:44
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
SteveAhi mpt_ 01:57
=== salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
SteveAddaa: so, if we can get a tarball of the whole svn repository, we could do the import from a local server02:08
SteveAand much reduce the network roundtripping02:08
ddaaThat would indeed be an option. But we had a bad experience with tarballs of cvs repos in the past. The specific issue is that we were sometimes given only a partial tarball that did not include the CVS config information.02:09
ddaaThere's also the issue that tarballs may give a a transitory state of the repo.02:10
SteveAwhat do you mean "transitory state"?02:10
ddaathings like commit-in-progress02:10
ddaahalf done modifications02:10
SteveAI don't think that would be an issue for svn02:10
SteveAbut even so, it would allow you to get the older history02:10
SteveAand then just update for the newer stuff02:11
ddaait's an issue for any sort of database where you break the transaction abstraction.02:11
ddaathe problem is not about the older stuff, it's more that we may end up with an invalid repository, or with a repository where the last commits are incorrect02:11
SteveAso, import it ignoring commits for "the last 3 days"02:12
jameshddaa: the commits in an fsfs Subversion repo should be atomic02:12
SteveAthen update the last three days against the actual live repository02:12
jameshthey'll either be committed, or they won't be02:12
ddaajamesh: they might be atomic on the systema as a whole, but there still can be a race with the time it takes to generate the tarball.02:12
ddaaI do not know the details.02:13
ddaaBut it's a problem congruent to why one should not back-up live filesystems with "cat", but use "dump" instead.02:13
ddaaSteveA: the "import up to some point in the near past" thing is possible02:14
ddaabut that does not alleviate my concern about overall repository consistency.02:14
ddaamaybe it's a misplaced concern, i do not know enough about svn02:14
lifelessthere is a protocol in svn02:15
lifelesscalled 'dump02:15
ddaaoh, right02:15
lifelessit is safe02:15
ddaaWe could use that.02:15
=== lifeless removes the anal plug
lifelessgnight all02:15
ddaathat would also likely prevent people from giving us incomplete repos02:16
=== herzi_x41 [n=herzi@pD9E29F97.dip.t-dialin.net] has joined #launchpad
ddaaso, yes, importing from svn dumps would be okay02:16
herzi_x41can someone please delete the monkey-bubble product from launchpad? it was not created by the maintainers and the reported bug is supposed to be an ubuntu bug.02:17
herzi_x41thank you02:17
ddaastub: ^^02:17
jameshherzi_x41: people can't file new bugs on it now.02:21
=== bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad
jameshherzi_x41: previously it was possible to file new bugs on products that hadn't explicitly stated that they were using Malone, but that has since been fixed02:22
mpt_Malone's front page should be inviting volunteers to clean up those old bugs, with a link to list them all02:23
mpt_if there are too many for us to fix by hand02:23
herzi_x41jamesh: thank you02:24
=== matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
=== looksaus [n=mark@86-39-97-101.customer.fulladsl.be] has joined #launchpad
looksaushi, I'm part of a group that is developing some code for a LocoTeam02:48
looksausour project is registered in Launchpad02:48
looksausis there a canonical way to create a mailing list for these people?02:49
looksaus(within the Canonical/Ubuntu Foundation infrastructure, that is)02:49
looksausI know we can probably ask for a @lists.ubuntu.com mailing list, but is that the right way?02:50
lucasvolooksaus: yes it is.02:58
lucasvoafaik LP doesn't provide any mailinglist services02:58
looksauslucasvo, thx for the help02:58
looksausnow I only have to find out where to ask for this @lists.ubuntu.com list02:59
looksausshouldn't be too difficult02:59
=== flacoste-lunch [n=francis@modemcable207.210-200-24.mc.videotron.ca] has joined #launchpad
kiko_mpt_, good idea. where's your patch? :)03:08
kiko_oh, did I miss stub?03:10
kiko_or is he travelling already?03:10
flacoste-lunchkiko: good morning!03:14
kikohello francis03:14
=== bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad
kikoI bet you are cross with me!03:15
mpt_kiko, it's beyond me, but I did report a bug about it several months ago :-)03:15
kikompt_, scratch my head thinking why that would be beyond you!03:15
mpt_argh, now Malone is going to be uncooperative in returning bugs that use "malone" in the summary03:16
=== flacoste-lunch wonders what 'cross with me' means?
mpt_cross ~= angry03:17
mpt_bug 3364203:18
UbugtuMalone bug 33642 in malone "Weed out open non-bugwatch bugs on products/distros that don't use Malone" [Medium,Unconfirmed]  http://launchpad.net/bugs/3364203:18
mpt_Similarly bug 3996003:19
UbugtuMalone bug 39960 in malone "Weed out obsolete uses of bug watches" [Medium,Unconfirmed]  http://launchpad.net/bugs/3996003:19
=== mpt_ goes back to sleep
flacoste-lunchkiko: me angry? not at all! why should I be angry? because I haven't yet received my reviews, c'mon, it takes more than that for me to lose my cool :-)03:21
kikowell, I've been horribly overburdeend03:21
flacoste-lunchkiko: yeah, i know, plus that patch is big, do you know when you think you'll find time for it?03:27
kikoflacoste-lunch, no promises. I have it half-done in vi for two days now :-(03:28
SteveAkiko: did you see I did a braindump spec for tag descriptions?03:28
kikoSteveA, so I did, I got emailed about it today03:28
kikoSteveA, or.. hmm did I. whats's the spec name?03:28
SteveAhttps://launchpad.net/products/malone/+spec/tag-definition03:29
=== imbrandon [n=brandon@ubuntu/member/pdpc.active.imbrandon] has joined #launchpad
SteveABjornT pointed out an issue, which is we could have different tag definitions for the same tag in a single bug, where it has more than one target03:32
SteveAI think that indicates a problem that one or both projects need to sort out out-of-band03:32
SteveAso we should display both definitions in that case03:33
=== LarstiQ [n=larstiq@cust.7.157.adsl.cistron.nl] has joined #launchpad
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
sabdflhttps://launchpad.canonical.com/OneZeroPageLayout04:00
sabdflplease comment, folks, at the bottom04:01
kikosabdfl, "the leader has not yet arrived. please stand by"04:01
sabdflSteveA: i don't mind tag definitions, but it does not make sense to have them balkanised04:01
kikoSteveA, +1 to what sabdfl just said.04:02
sabdflhmm... is it call time?04:02
kikosabdfl, well, that's what SteveA pinged me about!04:02
sabdflso it is04:02
SteveAI don't understand what you mean.  Maybe you can explain in the phone call04:03
=== ddaa hacks around a nasty test order dependency in the cscvs test suite
azeemW604:04
azeemeh, sorry04:04
sabdflSteveA: kiko and i are on the call04:06
=== niemeyer [n=niemeyer@200-140-230-218.ctame7043.dsl.brasiltelecom.net.br] has joined #launchpad
=== rpedro [n=rpedro@87-196-12-26.net.novis.pt] has joined #launchpad
sabdflBjornT: was it you that add the screenshots to MaloneHighlights?05:38
SteveAthat was mpt05:38
SteveAwell05:38
SteveAbjorn and james came up with a list of URLs05:38
SteveAand the mail screenshot05:39
SteveAthen mpt did the actual shooting and cropping05:39
sabdflthanks mpt_05:39
sabdfli have a few tweaks, will ask him to update it05:39
sabdfla little05:39
sabdfldoes anyone else think that the bugtask header would be more readable if it was:05:40
mpt_I should have used PillarName for the reporting-by-mail screenshot05:40
sabdflupstream evolution-exchange05:40
sabdflupstream libsoup05:40
SteveAkiko is the one sending it along to the python guys05:40
sabdflubuntu evolution-exchange05:40
sabdfldebian evolution-sxchange05:40
kikoSteveA, or so I am supposed to05:41
sabdflthe (postfixed) thing is harder to read05:41
sabdflmpt_: could I ask you to tweak those screenshots a little?05:41
jameshdepends on which bit of the target name you consider important05:41
sabdflthey are very classy - thanks for that05:41
mpt_sure, mail me the exact changes required05:41
=== mpt_ really should be asleep :-)
jameshthe package/product name or the distro name/that it is an upstream05:42
=== cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad
sabdflmpt_: well done. night :-)05:48
sabdflmail sent05:48
=== jamesh [n=james@203-59-20-109.dyn.iinet.net.au] has joined #launchpad
=== bradb & # lunch
=== herzi_x41 [n=herzi@pD9E29F97.dip.t-dialin.net] has left #launchpad []
sabdflWHOA06:38
sabdflhttps://dogfood.ubuntu.com/distros/ubuntu/dapper.006:39
sabdflkiko: ^^^ not cool06:39
kikosabdfl, yeah, clunky isn't it.06:40
=== lbm [n=lbm@82.192.173.92] has joined #launchpad
=== Mr-Petah [n=Mr-Petah@unaffiliated/mrpetah/x-000001] has joined #launchpad
Mr-Petahwow07:14
Mr-Petahhi all07:14
=== JanC [n=janc@lugwv/member/JanC] has joined #launchpad
bluefoxicykiko~07:35
bluefoxicysafllowperson says to ask you to extract information from the tables07:35
bradbBjornT: ping07:44
=== abhay [n=abhay@pdpc/supporter/student/Aranis] has joined #launchpad
BjornThi bradb 07:46
=== bradb msgs
=== shenki [n=shenki@ppp167-129.lns3.adl4.internode.on.net] has joined #launchpad
=== shenki [n=shenki@ppp167-129.lns3.adl4.internode.on.net] has left #launchpad ["Leaving"]
flacoste-lunchkiko: ping08:27
kikoflacoste-lunch, ahooo08:29
kikowhat's the flavor?08:29
kikodidn't mean to interrupt lunch08:29
flacosteno interruption, i'm back ;-)08:29
bradbif I do foo.bar = UTC_NOW, do I have to reretrive "foo" before foo.bar will return a datetime value? (instead of returning the SQL of the SQLConstant UTC_NOW)08:33
Mr-Petahi have one question, any people from canary islands?08:39
kikobradb, not sure -- jamesh would know though08:41
bradbI decided to just instantiate it as a datetime object instead08:42
=== Mr-Petah esta Ausente, Razon: ( Volver... no s cuando, pero volver... xD | http://mrpetah.homelinux.net ) | Desde: ( Viernes, Ahosto 4, 2006. 16:45:48 ) Xlack v2.1
=== scotth [n=scotth@157.182.209.170] has joined #launchpad
=== flacoste [n=francis@modemcable207.210-200-24.mc.videotron.ca] has left #launchpad ["Bye"]
bluefoxicykiko:  busy?10:49
kikoyes10:50
bluefoxicykay.10:50
kikoterribly today10:50
=== bluefoxicy comes up with something else to do for the moment.
LarstiQhello bluefoxicy 10:50
bluefoxicyHi winedev guy10:50
=== LarstiQ giggles
bluefoxicyI haven't seen you in a coon's age, or whatever the term is10:51
=== LarstiQ nods
LarstiQhad some shifts in priorities10:51
bluefoxicyI'm trying to get a job; meanwhile I've been spitting out random ideas, tracking what's going on in Ubuntu, generally trying to do whatever to keep from being bored.10:53
bluefoxicyI specced out a hardened team like the one in Gentoo for Ubuntu, just to amuse myself; nobody'd ever set something like that up, it's a battlefield.  Also I took interest in pitti's automated crash reporter and came up with a way to keep the massive workload of sifting through reports in check; and am looking at isolating probable security vulnerabilities using the reports.10:55
=== Myk0n [n=hydrus@81.20.248.70] has joined #launchpad
LarstiQthat does sound like you are keeping yourself busy10:56
bluefoxicywell if I don't, I get bored.  then I talk in #-devel a lot, and the devs get pissed at me.10:56
=== LarstiQ grins
=== scotth [n=scotth@157.182.209.170] has left #launchpad []
bluefoxicyLarstiQ:  currently I need to catch one of these guys when they're not busy and bribe them to get a couple statistics out of the launchpad database for me ;)  But it's not a priority10:59
LarstiQbluefoxicy: you could try mailing launchpad-users?11:00
bluefoxicyI think users don't have the kind of access I need.  I basically need bug counts per month for Ubuntu, and possibly some other stuff (It would be interesting to also graph the number of bugs closed; number of duplicates; number of confirmed bugs; and number of newly triaged bugs)11:04
bluefoxicyBut it's not that important, since it's just to illustrate a problem that's already known.11:05
LarstiQ-users is a way to communicate with the devs that is less prone to being lost than a request on irc11:05
bluefoxicyah11:05
LarstiQI suppose you could also try a support ticket on launchpad11:05
=== LarstiQ never used that though
=== bluefoxicy is starting to not like mailing lists because he's on a billion of them.
LarstiQbluefoxicy: how about figuring out if the support tracker works? :)11:06
bluefoxicyheh sure why not.11:08
bluefoxicyLarstiQ:  should I file a support ticket under Ubuntu or Launchpad, is now the issue.11:08
bluefoxicyright.  Launchpad.11:09
=== Myk0n [n=hydrus@81.20.248.70] has left #launchpad []
=== zygis [n=zygis@85.206.184.114] has joined #launchpad
bluefoxicyLarstiQ:  https://launchpad.net/products/launchpad/+ticket/1381 Well it posts :)11:19
=== BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad
LarstiQreading that it might even be fit for a spec, but we'll see what happens11:25
bluefoxicyoww my fucking skull *ingests a melted Ginger altoids and his sinuses go nuts* X_X11:26
=== mpt__ [n=mpt@203.118.156.188] has joined #launchpad

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