[01:27] <lifeless> bradb: around ?
[01:27] <bradb> lifeless: yeah
[01:28] <lifeless> do you think, that if I send an email to new-bugs, cc'd to $person, malone would be sane in subscrbing $person automatically?
[01:30] <lifeless> be^
[01:30] <lifeless> bradb: ^
[01:30] <bradb> lifeless: I don't know that there's a correct answer to that question, but it would probably be more sane than not.
[01:30] <lucasvo> lifeless: in that case I would add a header to the first email LP sends to $person that he has been subscribed because....
[01:30] <bradb> Roundup does that, I believe.
[01:30] <lifeless> would you like a wishlist bug or a placeholder spec ?
[01:31] <bradb> lifeless: bug sounds good
[01:31] <lifeless> how do you tell the bugmail to be wishlist ?
[01:32] <bradb> lifeless: you can't change priority via email, unfortunately
[01:32] <lifeless> ha!
[01:32] <lifeless> is that by design ?
[01:33] <bradb> lifeless: not really
[01:33] <lifeless> want a bug on that too ?
[01:36] <bradb> lifeless: er, n/m, i'm on crack
[01:37] <bradb> lifeless: you can change importance through the email UI, but if it's working properly that should be restricted to only bugcontacts and drivers
[01:38] <lifeless> fair enough
[01:38] <lifeless> ... how ?
[01:40] <bradb> lifeless: https://help.launchpad.net/UsingMaloneEmail#head-193f41e9738ba7e7f971421b5ef98657eedad873
[01:41] <lifeless> thanks
[01:41] <bradb> np
[01:41] <lifeless> bug 55113 is for thee
[01: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] <bradb> thanks
[01:42] <lifeless> aww, rfc822 normalisation fucks over malone.
[01:42] <lifeless> new bug coming up
[01:45] <lifeless> bradb: also
[01:45] <lifeless> bradb: why does it take malone so long to acknowledge my new bug filings via email ?
[01:46] <bradb> lifeless: AIUI, the emails are processed by a cron job every N minutes. bjornt could confirm.
[01:46] <lifeless> I was wondering if the 'group actions when emailing' code was grouping new bug mail too
[01:47] <lifeless> because its a new bug no-one can possibly have followed up on it immediately
[01:47] <lifeless> so it would make sense to reply immediately IMO
[01:49] <bradb> that may be true. if you want to make sure bjornt sees it, feel free to file a bug.
[01:49] <lifeless> ok
[01:50] <lifeless> I've filed another one, on the syntax
[01:50] <lifeless> accepting accepts: /products/malone would be really nice UI
[01:50] <lifeless> (as well as accpeting affects /products/malone)
[01:51] <bluefoxicy> sfllaw:  are you about?
[01:51] <bradb> lifeless: you mean "accepting affects: /products/malone", presumably?
[01:52] <lifeless> yes
[01:52] <lifeless> I also wrote a cute email to demonstrate this :)
[01:52] <lifeless> https://launchpad.net/products/malone/+bug/55115
[01:52] <Ubugtu> Malone bug 55115 in malone "control lines in bugmail should accept : prefixes" [Untriaged,Unconfirmed]  
[01:52] <bradb> right
[01:53] <bluefoxicy> \:
[01:53] <kiko-zzz> bluefoxicy, can you remind me tomorrow to generate the stats for you? i'm so tired tonight..
[01:53] <lifeless> heh, 3 of the last 5 bugs across malone reported by me :)
[01:53] <bluefoxicy> kiko-zzz:  nods.  I still say it'd be nice to have a feature to spit out various statistics through launchpad.
[01:53] <bluefoxicy> kiko-zzz:  I'm in no hurry ;)
[01:54] <lifeless> 4 of the last 5
[01:54] <kiko-zzz> bluefoxicy, 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:55] <bluefoxicy> kiko-zzz:  flexible infra and step feature by feature :)
[01:55] <bluefoxicy> anyway nighters, see you another time
[01:55] <sfllaw> bluefoxicy: Yes.
[01:55] <sfllaw> I'm making supper though.
[01:55] <sfllaw> How can I help you?
[01:55] <sfllaw> (I may pop out to check the stove.)
[01:57] <bluefoxicy> sfllaw:  oh, I was just looking for stats on how many bugs get reported per month in Ubuntu on launchpad
[01:57] <bluefoxicy> kiko said either you or he may be able to help me with that :)
[02:01] <bluefoxicy> (there's other interesting data that I could use too, but it's not really important)
[02:02] <sfllaw> Per month?
[02:02] <sfllaw> I don't know specifically.
[02:02] <sfllaw> Lemme look at my charts.
[02:03] <sfllaw> We seem to get about 1000 per week.
[02:03] <sfllaw> So about 3500-4000 per month.
[02:04] <bluefoxicy> I thought the number was increasing overtime?
[02:04] <lifeless> sfllaw: btw there is a distributed test manager written in python already
[02:05] <sfllaw> Huh.
[02:05] <sfllaw> Neato.
[02:06] <sfllaw> I'm not adverse to borrowing.
[02:06] <lifeless> I'll hunt down a link
[02:08] <lifeless> http://www.codesourcery.com/qmtest/
[02:08] <lifeless> I have not used it myself
[02:11] <sfllaw> Ah.  CodeSourcery.
[02:11] <sfllaw> I'll ask scjody about it.
[02:11] <sfllaw> Thanks.
[02:12] <lifeless> scjody ?
[02:12] <sfllaw> Whoops.  Wrong guy.
[02:12] <sfllaw> I mean Carlos O'Donnel.
[02:12] <sfllaw> Someone I know at CodeSourcery.
[02:12] <lifeless> ah cool
[02:12] <lifeless> altogether now
[02:13] <lifeless> 'its a small small world'
[02:13] <bluefoxicy> sfllaw:  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 Ubuntu
[02:13] <bluefoxicy> perhaps the search doesn't do what I think :)
[02:13] <sfllaw> bluefoxicy: We didn't keep track of figures then.
[02:13] <sfllaw> You 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:14] <bluefoxicy> sfllaw:  ah.  Okay.  I guess I'll wait for kiko to get up tomorrow then.
[02:14] <bradb> lifeless: 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] <sfllaw> Of course, back then we were using Bugzilla.
[02:14] <sfllaw> So we may have lost this data.
[02:15] <lifeless> foo is presumably a security proxy ?
[02:15] <bradb> lifeless: yeah
[02:15] <bluefoxicy> sfllaw:  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-01
[02:15] <Ubugtu> Malone bug 6912 in linux-source-2.6.15 "kernel-source-2.4.26: Kernel panic with NFS traffic over IPsec" [Unknown,Unknown]  
[02:16] <bradb> I'm also wondering if I really mean to be verifying the object, or instead doing verifyClass or even IFoo.providedBy.
[02:16] <bluefoxicy> sfllaw:  but if the data is lost then I'll just have to go with what I can get.  :)
[02:16] <lifeless> and bar is part of IFoo ?
[02:16] <bradb> lifeless: yeah. works fine when logged in as priv'd user
[02:16] <sfllaw> bluefoxicy: Is this for some kind of research?
[02:17] <lifeless> so, 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 bar
[02:17] <lifeless> why are you calling verifyObject ?
[02:17] <bluefoxicy> sfllaw: 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 spec
[02:18] <bradb> lifeless: I want some kind of verification that things are providing the right interfaces
[02:18] <bradb> (in tests)
[02:19] <lifeless> bradb: is verifyObject called outside the test code path ?
[02:19] <bradb> lifeless: maybe verifyClass is more appropriate
[02:19] <bradb> lifeless: I'm calling it directly in a doctest.
[02:19] <lifeless> ok
[02:20] <lifeless> bradb: local interrupt, bb in a couple minutes
[02:20] <bradb> sure, np
[02:21] <sfllaw> bluefoxicy: Neato.
[02:25] <bluefoxicy> uh.  Hmm.  Server not listening.  *goes across the room for a bit*
[02:35] <lifeless> bradb: so
[02:35] <lifeless> verifyClass will probably fail the same way
[02: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 proxy
[02:36] <lifeless> I 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 or
[02:36] <lifeless>  - be done with a more restricted interface that is safe to give to everyone
[02:37] <lifeless>  - or ask if it implements, not if it verifies
[02:37] <bradb> verify class seems to work
[02:37] <lifeless> surprising
[02:37] <bradb> er, verifyClass
[02:37] <bradb> i'm not surprised, tbh
[02:38] <bradb> because BugNomination is not security-wrapped
[02:38] <bradb> but an object returned by bug.addNomination will be
[02:38] <bluefoxicy> sfllaw:  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:39] <lifeless> bradb: so testing approach wise, heres a thought
[02:39] <lifeless> bradb: 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 tests
[02:40] <lifeless> bradb: 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 layer
[02:42] <bradb> lifeless: 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:43] <bradb> though, i think not raising an error is easier to understand
[02:49] <lifeless> well
[02:49] <lifeless> it cant verify it
[02:49] <lifeless> so verifyObject *should* raise an error :0
[02:51] <bradb> lifeless: that it can't verify it seems like an implementation detail though
[02:52] <lifeless> errr
[02:52] <lifeless> I'm not sure how that matters
[02:53] <bradb> I guess I can see how it makes sense.
[02:56] <lifeless> when 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 callables
[02:56] <lifeless> it does not matter *why* you cant use a specific bit in the right way, it only matters that you cannot.
[02:58] <bradb> lifeless: right
[02:59] <bradb> your logic makes sense
[08:54] <SteveA> good morning
[09:39] <sivang> morning
[09:42] <sabdfl> hi sivang
[09:43] <sivang> hey sabdfl 
[09:45] <SteveA> mpt_: ping
[09:49] <ddaa> Good morning!
[09:49] <SteveA> morning ddaa
[09:49] <ddaa> mpool: ping
[09:49] <SteveA> you have a review
[09:49] <mpool> ddaa: hello
[09:49] <ddaa> SteveA: duh!
[09:50] <SteveA> use vim
[09:50] <SteveA> it is betta
[09:50] <SteveA> emacs sucks vim rocks.
[09:50] <ddaa> it's too modal for my taste

[09:50] <mpool> "beeping and non-beeping modes"
[09:50] <mpool> :)
[09:50] <ddaa> mpool: hihihi
[09:51] <jamesh> hi ddaa
[09:51] <ddaa> hey jamesh
[09:51] <ddaa> mpool: you seem keen at nailing some kind of roadmap
[09:51] <ddaa> mpool: I may have given the impression of waffling in the past days in those discussions
[09:52] <ddaa> actually, I was braindumping
[09:52] <mpool> ddaa: not at all, i think your mails have been very informative
[09:52] <mpool> there are two things i would like to talk with you about 
[09:52] <mpool> - general planning
[09:52] <mpool> - roundtripping
[09:54] <ddaa> since the former is dependent on the latter let's start on roundtripping
[09:54] <ddaa> here or in #bzr?
[09:54] <mpool> how about on skype?
[09:55] <ddaa> any reason not to use ekiga
[09:55] <ddaa> ?
[09:55] <lifeless> ok, I'm popping away for the weekend
[09:55] <mpool> lifeless: have a good weekend
[09:55] <lifeless> tchau tchau, though I may pop in from time to time
[09:55] <jdub> hey dudes
[09:55] <ddaa> lifeless: hey
[09:56] <jdub> any of you guys experienced this bug -
[09:56] <jdub> http://mail.python.org/pipermail/python-bugs-list/2005-June/029183.html
[09:56] <jdub> ?
[09:56] <ddaa> lifeless: 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] <mpool> ddaa: i don't have ekiga on this machine
[09:56] <mpool> but otherwise it'd be ok
[09:56] <ddaa> I'm hopefully starting to do some work on that today or monday, so it would be useful
[09:56] <mpool> hi jdub
[09:57] <lifeless> jdub: cool
[09:57] <lifeless> jdub: lovely bug, and no, but I relly must get my gzip tuning patch upstream
[09:57] <jdub> ha ha
[09:57] <lifeless> ddaa: dang, I knew I forgot something
[09:57] <lifeless> ddaa: its in my TODO
[09:58] <lifeless> ddaa: but I've been busy with 0.10 all day
[09:58] <ddaa> lifeless: I KNOW the true meaning of this sort of answer :)
[09:58] <mpool> ddaa: so, skype?
[09:58] <ddaa> yeah, was connecting the headset
[09:58] <mpool> cool
[09:58] <lifeless> ddaa: its agonising working with blueprint at the moment - so many page refreshes, and page load from here is about 5 seconds
[09:59] <mpool> lifeless: there are some similar issues with branches in lp i think - maybe not quite so bad
[10:06] <jamesh> ddaa: here's the first draft of my team branches article: https://chinstrap.ubuntu.com/~jamesh/team-branches.html
[10:06] <jamesh> if you want to point out bits you think should be added/removed/changed
[10:22] <sivang> where 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] <sivang> s/FOAF/registery
[10:23] <sivang> malone #55156
[10:23] <Ubugtu> Malone bug 55156 in launchpad "team expairy email should be more useful." [Untriaged,Unconfirmed]  http://launchpad.net/bugs/55156
[10:48] <ddaa> jamesh: can you post the text to the ML so people can easily put comments in context?
[10:48] <ddaa> or a bzr branch, or a wiki...
[11:08] <Kinnison> Is there a mechanism to mass-unsubscribe from bugs?
[11:10] <stub> Insert beer to continue
[11:11] <sivang> heh
[11:11] <sivang> stub-o-matic
[11:12] <Kinnison> regretfully I have little option for delivery of beer
[11:31] <Nafallo> hi! where do I change Status on support tickets? :-)
[11:39] <jamesh> Kinnison: stub will be in London next week ...
[11:52] <jamesh> how many revs do you think it has?
[11:53] <ddaa> 76334 revs on MAIN
[11:53] <ddaa> sadly, it's a roomba import ATM
[11:53] <ddaa> meaning we'll have to start it over again on hoover before publishing it
[11:54] <ddaa> also, as usual, there's no guarantee it's going to pass the final cross check at the end
[11:57] <ddaa> kudos 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:59] <stub> So we can no longer import SVN branches if there is no longer a corresponding sourcepackage?
[12:00] <ddaa> stub: http://svn.python.org/projects/python/trunk
[12:00] <ddaa> oops
[12:00] <ddaa> stub: https://launchpad.net/products/launchpad-bazaar/+bug/46240
[12:00] <Ubugtu> Malone bug 46240 in launchpad-bazaar "posting $series/+source yields a confusing warning" [High,Confirmed]  
[12:01] <ddaa> Known problem, but merely confusing, and relatively low profile.
[12:03] <stub> ta
[12:47] <sabdfl> ddaa: do those imports go much more quickly with native-bzr tech?
[12:49] <ddaa> Yes, the diff*history cost of baz was a real killer for really large branches.
[12:49] <ddaa> So we squashed down a really large quadratic factor on the cost of large initial imports.
[12:50] <ddaa> But it's still short of blindingly fast
[12:50] <ddaa> The emacs import has been running since Tuesday 07:10
[12:54] <ddaa> My 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] <ddaa> But since it's a guess and not a profiling result, it's virtually worthless.
[12:56] <ddaa> Mh, actually, just since wednesday 07:10, it seems
[01:28] <cprov> good morning, guys 
[01:42] <mpt_> hi cprov
[01:42] <mpt_> SteveA, pong
[01:42] <mpt_> cprov, did you see the message from Roshan Shariff on ubuntu-devel@?
[01:43] <cprov> mpt_: 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 problem
[01:43] <mpt_> cprov, sent
[01:44] <cprov> mpt_: thanks
[01:57] <SteveA> hi mpt_ 
[02:08] <SteveA> ddaa: so, if we can get a tarball of the whole svn repository, we could do the import from a local server
[02:08] <SteveA> and much reduce the network roundtripping
[02:09] <ddaa> That 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:10] <ddaa> There's also the issue that tarballs may give a a transitory state of the repo.
[02:10] <SteveA> what do you mean "transitory state"?
[02:10] <ddaa> things like commit-in-progress
[02:10] <ddaa> half done modifications
[02:10] <SteveA> I don't think that would be an issue for svn
[02:10] <SteveA> but even so, it would allow you to get the older history
[02:11] <SteveA> and then just update for the newer stuff
[02:11] <ddaa> it's an issue for any sort of database where you break the transaction abstraction.
[02:11] <ddaa> the 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 incorrect
[02:12] <SteveA> so, import it ignoring commits for "the last 3 days"
[02:12] <jamesh> ddaa: the commits in an fsfs Subversion repo should be atomic
[02:12] <SteveA> then update the last three days against the actual live repository
[02:12] <jamesh> they'll either be committed, or they won't be
[02:12] <ddaa> jamesh: 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:13] <ddaa> I do not know the details.
[02:13] <ddaa> But it's a problem congruent to why one should not back-up live filesystems with "cat", but use "dump" instead.
[02:14] <ddaa> SteveA: the "import up to some point in the near past" thing is possible
[02:14] <ddaa> but that does not alleviate my concern about overall repository consistency.
[02:14] <ddaa> maybe it's a misplaced concern, i do not know enough about svn
[02:15] <lifeless> there is a protocol in svn
[02:15] <lifeless> called 'dump
[02:15] <ddaa> oh, right
[02:15] <lifeless> it is safe
[02:15] <ddaa> We could use that.
[02:15] <lifeless> gnight all
[02:16] <ddaa> that would also likely prevent people from giving us incomplete repos
[02:16] <ddaa> so, yes, importing from svn dumps would be okay
[02:17] <herzi_x41> can 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_x41> thank you
[02:17] <ddaa> stub: ^^
[02:21] <jamesh> herzi_x41: people can't file new bugs on it now.
[02:22] <jamesh> herzi_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 fixed
[02:23] <mpt_> Malone's front page should be inviting volunteers to clean up those old bugs, with a link to list them all
[02:23] <mpt_> if there are too many for us to fix by hand
[02:24] <herzi_x41> jamesh: thank you
[02:48] <looksaus> hi, I'm part of a group that is developing some code for a LocoTeam
[02:48] <looksaus> our project is registered in Launchpad
[02:49] <looksaus> is there a canonical way to create a mailing list for these people?
[02:49] <looksaus> (within the Canonical/Ubuntu Foundation infrastructure, that is)
[02:50] <looksaus> I know we can probably ask for a @lists.ubuntu.com mailing list, but is that the right way?
[02:58] <lucasvo> looksaus: yes it is.
[02:58] <lucasvo> afaik LP doesn't provide any mailinglist services
[02:58] <looksaus> lucasvo, thx for the help
[02:59] <looksaus> now I only have to find out where to ask for this @lists.ubuntu.com list
[02:59] <looksaus> shouldn't be too difficult
[03:08] <kiko_> mpt_, good idea. where's your patch? :)
[03:10] <kiko_> oh, did I miss stub?
[03:10] <kiko_> or is he travelling already?
[03:14] <flacoste-lunch> kiko: good morning!
[03:14] <kiko> hello francis
[03:15] <kiko> I 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] <kiko> mpt_, scratch my head thinking why that would be beyond you!
[03:16] <mpt_> argh, now Malone is going to be uncooperative in returning bugs that use "malone" in the summary
[03:17] <mpt_> cross ~= angry
[03:18] <mpt_> bug 33642
[03:18] <Ubugtu> Malone bug 33642 in malone "Weed out open non-bugwatch bugs on products/distros that don't use Malone" [Medium,Unconfirmed]  http://launchpad.net/bugs/33642
[03:19] <mpt_> Similarly bug 39960
[03:19] <Ubugtu> Malone bug 39960 in malone "Weed out obsolete uses of bug watches" [Medium,Unconfirmed]  http://launchpad.net/bugs/39960
[03:21] <flacoste-lunch> kiko: 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] <kiko> well, I've been horribly overburdeend
[03:27] <flacoste-lunch> kiko: yeah, i know, plus that patch is big, do you know when you think you'll find time for it?
[03:28] <kiko> flacoste-lunch, no promises. I have it half-done in vi for two days now :-(
[03:28] <SteveA> kiko: did you see I did a braindump spec for tag descriptions?
[03:28] <kiko> SteveA, so I did, I got emailed about it today
[03:28] <kiko> SteveA, or.. hmm did I. whats's the spec name?
[03:29] <SteveA> https://launchpad.net/products/malone/+spec/tag-definition
[03:32] <SteveA> BjornT 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 target
[03:32] <SteveA> I think that indicates a problem that one or both projects need to sort out out-of-band
[03:33] <SteveA> so we should display both definitions in that case
[04:00] <sabdfl> https://launchpad.canonical.com/OneZeroPageLayout
[04:01] <sabdfl> please comment, folks, at the bottom
[04:01] <kiko> sabdfl, "the leader has not yet arrived. please stand by"
[04:01] <sabdfl> SteveA: i don't mind tag definitions, but it does not make sense to have them balkanised
[04:02] <kiko> SteveA, +1 to what sabdfl just said.
[04:02] <sabdfl> hmm... is it call time?
[04:02] <kiko> sabdfl, well, that's what SteveA pinged me about!
[04:02] <sabdfl> so it is
[04:03] <SteveA> I don't understand what you mean.  Maybe you can explain in the phone call
[04:04] <azeem> W6
[04:04] <azeem> eh, sorry
[04:06] <sabdfl> SteveA: kiko and i are on the call
[05:38] <sabdfl> BjornT: was it you that add the screenshots to MaloneHighlights?
[05:38] <SteveA> that was mpt
[05:38] <SteveA> well
[05:38] <SteveA> bjorn and james came up with a list of URLs
[05:39] <SteveA> and the mail screenshot
[05:39] <SteveA> then mpt did the actual shooting and cropping
[05:39] <sabdfl> thanks mpt_
[05:39] <sabdfl> i have a few tweaks, will ask him to update it
[05:39] <sabdfl> a little
[05:40] <sabdfl> does 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 screenshot
[05:40] <sabdfl> upstream evolution-exchange
[05:40] <sabdfl> upstream libsoup
[05:40] <SteveA> kiko is the one sending it along to the python guys
[05:40] <sabdfl> ubuntu evolution-exchange
[05:40] <sabdfl> debian evolution-sxchange
[05:41] <kiko> SteveA, or so I am supposed to
[05:41] <sabdfl> the (postfixed) thing is harder to read
[05:41] <sabdfl> mpt_: could I ask you to tweak those screenshots a little?
[05:41] <jamesh> depends on which bit of the target name you consider important
[05:41] <sabdfl> they are very classy - thanks for that
[05:41] <mpt_> sure, mail me the exact changes required
[05:42] <jamesh> the package/product name or the distro name/that it is an upstream
[05:48] <sabdfl> mpt_: well done. night :-)
[05:48] <sabdfl> mail sent
[06:38] <sabdfl> WHOA
[06:39] <sabdfl> https://dogfood.ubuntu.com/distros/ubuntu/dapper.0
[06:39] <sabdfl> kiko: ^^^ not cool
[06:40] <kiko> sabdfl, yeah, clunky isn't it.
[07:14] <Mr-Petah> wow
[07:14] <Mr-Petah> hi all
[07:35] <bluefoxicy> kiko~
[07:35] <bluefoxicy> safllowperson says to ask you to extract information from the tables
[07:44] <bradb> BjornT: ping
[07:46] <BjornT> hi bradb 
[08:27] <flacoste-lunch> kiko: ping
[08:29] <kiko> flacoste-lunch, ahooo
[08:29] <kiko> what's the flavor?
[08:29] <kiko> didn't mean to interrupt lunch
[08:29] <flacoste> no interruption, i'm back ;-)
[08:33] <bradb> if 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:39] <Mr-Petah> i have one question, any people from canary islands?
[08:41] <kiko> bradb, not sure -- jamesh would know though
[08:42] <bradb> I decided to just instantiate it as a datetime object instead
[10:49] <bluefoxicy> kiko:  busy?
[10:50] <kiko> yes
[10:50] <bluefoxicy> kay.
[10:50] <kiko> terribly today
[10:50] <LarstiQ> hello bluefoxicy 
[10:50] <bluefoxicy> Hi winedev guy
[10:51] <bluefoxicy> I haven't seen you in a coon's age, or whatever the term is
[10:51] <LarstiQ> had some shifts in priorities
[10:53] <bluefoxicy> I'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:55] <bluefoxicy> I 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:56] <LarstiQ> that does sound like you are keeping yourself busy
[10:56] <bluefoxicy> well if I don't, I get bored.  then I talk in #-devel a lot, and the devs get pissed at me.
[10:59] <bluefoxicy> LarstiQ:  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 priority
[11:00] <LarstiQ> bluefoxicy: you could try mailing launchpad-users?
[11:04] <bluefoxicy> I 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:05] <bluefoxicy> But 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 irc
[11:05] <bluefoxicy> ah
[11:05] <LarstiQ> I suppose you could also try a support ticket on launchpad
[11:06] <LarstiQ> bluefoxicy: how about figuring out if the support tracker works? :)
[11:08] <bluefoxicy> heh sure why not.
[11:08] <bluefoxicy> LarstiQ:  should I file a support ticket under Ubuntu or Launchpad, is now the issue.
[11:09] <bluefoxicy> right.  Launchpad.
[11:19] <bluefoxicy> LarstiQ:  https://launchpad.net/products/launchpad/+ticket/1381 Well it posts :)
[11:25] <LarstiQ> reading that it might even be fit for a spec, but we'll see what happens
[11:26] <bluefoxicy> oww my fucking skull *ingests a melted Ginger altoids and his sinuses go nuts* X_X