[00:02] <Rocket2DMn> k, thanks for the info guys
[00:02] <Rocket2DMn> is there a bug report for it?
[00:03] <Hobbsee> yes, but it's private
[00:06] <Rocket2DMn> well im in bugcontrol, is it so private i cant see it?
[00:10] <Rocket2DMn> wait thats a stupid question, i can only see ubuntu private bugs
[00:11] <spm> Rocket2DMn: user disabled again
[00:11]  * Hobbsee hands spm a bigger hammer
[00:12] <spm> heh
[00:15] <wgrant> Rocket2DMn: You can't implicitly see Ubuntu private bugs either...
[00:15] <Rocket2DMn> thanks spm
[00:15] <Rocket2DMn> wgrant, yeah i guess thats true
[00:16] <Rocket2DMn> i just wanted to follow the status on the bug
[00:16] <wgrant> Launchpad fortunately leaks lots of information out of other channels, so I've been following the status even though the bug is private.
[00:26] <kiko> wgrant, hey, we don't leak that much!!
[00:28] <wgrant> kiko: The recent world-burning issue wasn't disclosed too widely, true. It was well described in the usual leak media so as to not reveal too much.
[00:41] <stewart> any timeframe for lp to understand bzr 1.9 format branches? (or something to make sure only branch formats supported by lp are hosted on lp ?)
[00:42]  * Hobbsee prods launchpad
[00:42] <Hobbsee> oh no, it lives after 25 seconds.
[00:44] <jml> stewart: the latter isn't going to happen any time soon.
[00:44] <jml> stewart: the former should happen this release, AIUI
[00:44]  * jml double checks
[00:44] <stewart> jml: yay - what timeframe are releases?
[00:45] <wgrant> Tomorrow!
[00:45] <jml> stewart: once every month. next one is tomorrow.
[00:45] <stewart> awesome
[00:45] <jml> stewart: we almost always upgrade our bzr every release
[00:45] <kiko> jml, 1.10 or1.11 this time?
[00:46] <jml> kiko: 1.10, I think, but I haven't been following it. I've been head-down in package branches.
[00:46] <wgrant> Yay!
[00:47] <jml> kiko: 1.10.
[00:48] <mwhudson> kiko: 1.11 isn't out yet
[00:50] <stewart> $ bzr push --overwrite
[00:50] <stewart> Using saved push location: bzr+ssh://bazaar.launchpad.net/~stewart-flamingspork/drizzle/linux-sparc2/
[00:50] <stewart> bzr: ERROR: Server sent an unexpected error: ('error', "Unknown repository format: 'Bazaar RepositoryFormatKnitPack6 (bzr 1.9)\\n'")
[00:50] <stewart> hrrm... anybody have any ideas?
[00:50] <stewart> (same without --overwrite)
[00:51] <wgrant> Use sftp, maybe.
[00:51] <wgrant> Or delete the branch.
[00:52] <jml> stewart: sftp.
[00:52]  * stewart trying
[00:54] <mwhudson> though if you want other people to access the branch, using an older format is sorta required
[00:59] <stewart> gah... so i'll have to go delete the branch and then find some magic option to push as 1.6
[00:59] <spiv> stewart: "bzr init --1.6 bzr+ssh://bazaar.launchpad.net/~stewart-flamingspork/drizzle/linux-sparc2/", then push to it
[01:00] <spiv> mwhudson: how soon will we have bzr 1.9 in LP?
[01:00] <kiko> spiv, we'll have 1.10 on wednesday.
[01:00] <wgrant> spiv: It was just discussed - tomorrow.
[01:00] <spiv> Sweet.
[01:01]  * wgrant likes LP's aggressive and normally fairly stable release cycles.
[01:01] <spiv> Normally LP tracks bzr releases wonderfully well, then as soon as we do a release that introduces a new format... :P
[01:02] <jml> we love you too spiv :)
[01:06] <kiko> spiv, when you add a new format then launchpad breaks :)
[01:14] <hggdh> hello, folks. Maurizio is back ;-(
[01:14] <wgrant> hggdh: When? I think spm disabled him not too long ago.
[01:14] <wgrant> And the bug will be fixed tomorrow!
[01:14] <hggdh> COOL!
[01:15] <hggdh> last one was 27 minutes ago
[01:15] <hggdh> spm disabled him (methinks) two days ago
[01:15] <wgrant> spm disabled him an hour ago.
[01:16] <hggdh> at least he linked to a blueprint that makes a bit of sense: https://blueprints.launchpad.net/ubuntu/+spec/cleanup-cruft
[01:17] <hggdh> but oh boy, the linked bugs are legion there
[01:20] <hggdh> can this blueprint be cleaned?
[01:21] <wgrant> Ideally spm would 'delete' the bugs, and Blueprint wouldn't reveal the existence of bug<->blueprint links if you can't see the bug.
[01:21] <wgrant> The former can be done now, but the latter requires Blueprint to have somebody working on it.
[01:21] <wgrant> Which hasn't been the case for a very long time.
[01:21] <hggdh> perhaps I can do it
[01:21] <hggdh> I will try
[01:22] <wgrant> You can unlink them.
[01:22] <wgrant> Unless you can't see them.
[01:22] <hggdh> I can see them. trying to unlink now
[01:22] <hggdh> yay
[01:23] <hggdh> cool. I did not know I could do that. Sorry for the request.
[01:28] <Pilky> Hey, I've just tried pushing a branch that is using the bzr 1.9 format to launchpad and now the branch on launchpad is showing the error: "Unknown repository format: 'Bazaar RepositoryFormatKnitPack6 (bzr 1.9)\n'"
[01:29] <Pilky> anyone know how to fix that, or at least nuke the branch on launch pad so I can start afresh (it is a new project so I'm fine re-creating the branch locally)
[02:27] <poolie1> lp keeps losing my login credentials
[02:27] <poolie1> is it just me?
[02:29] <wgrant> poolie1: It's working fine for me.
[02:32] <jml> poolie1: is this the firefox RSS thing again?
[02:32] <wgrant> No, I just checked that.
[02:32] <wgrant> It's definitely still fixed.
[02:32] <jml> ummm...
[02:32] <wgrant> That was my first thought...
[02:33] <jml> poolie1: doing anything else crazy with your browser?
[02:33] <jml> (does firefox have a --no-plugins option?)
[02:34] <Hobbsee> iirc it's --safe-mode?
[02:35] <wgrant> Something like that.
[02:49] <poolie1> jml, not that i know of
[02:50] <jml> poolie1: if you can, I'd recommend running without addons for a while and see if you still get the logouts.
[02:51] <jml> poolie1: or follow one of a number of other strategies to get a reproducible recipe :)
[02:52] <MFen> what's up with dch not respecting DEBEMAIL any more?
[02:57] <Hobbsee> MFen: wfm.
[02:57] <MFen> maybe i'm having environment variable problems.
[02:58] <jamesh> did you remember to export them?
[03:58] <MFen> sweet! my ppa contains code https://launchpad.net/~corydodt/+archive
[03:59] <MFen> o_O
[06:51] <MTecknology> kiko: Feeling better at all?
[06:51] <kiko> well
[06:51] <kiko> somewhat
[06:51] <kiko> better than friday
[06:51] <kiko> not perfect though, by a longshot!
[06:51] <MTecknology> improvement's always good though :)
[06:53] <MTecknology> kiko: turns out there was a little bug in that plugin that made it not work right, since it's working me and one other guy are looking into porting it to 6
[06:53] <MTecknology> if possible
[06:54] <MTecknology> kiko: make sure you feel better, alright?
[06:55] <kiko> yeah, will rest a little bit
[06:55] <kiko> MTecknology, wow, I didn't know that porting it was even possible
[06:55] <MTecknology> any reason you think it's not
[06:56] <kiko> let me check
[06:57] <kiko> so maybe it is possible and we just started too early on it (before 6 was available)
[06:58] <MTecknology> oh
[06:58] <MTecknology> it looks like the guy has one of them ported to 6
[06:58] <wgrant> kiko: Are there docs on using the JS webservice API client, or do I have to work out the rest myself?
[06:58] <MTecknology> I think he's still working on the teams though
[07:00] <MTecknology> kiko: swe3tdave is the guy that I've been working with on those ports, I haven't done the work since I've been busy porting a theme
[07:00] <kiko> neat
[07:01] <kiko> wgrant, I'm not sure right now -- worth asking leonardr when he's around
[07:01] <MTecknology> Just figured I'd bring up his name since he might help you guys get the rest of it going
[07:01] <wgrant> kiko: I /think/ I've worked out most bits myself. It'll be useful for doing stuff with Greasemonkey.
[07:06] <MTecknology> kiko: this is swe3tdave; swe3tdave: this is kiko; kiko: swe3tdave said he should be able to get most of the ports done by the end of the week...
[07:07] <MTecknology> I just wanted to introduce the two of you, and maybe help keep redundant work from being done since swe3tdave has been doing a crap load of work on this.
[07:08] <swe3tdave> i'm almost done, i have two function left that i have to rewrite completly and i have to figure out the new form api to do that
[07:09] <MTecknology> Rinchen: perhaps you have interest too?? ^^
[07:11] <MTecknology> kiko: anyway - feel better ; sorry I keep jumping topic
[07:17] <kiko> that's pretty cool
[07:17] <kiko> well it /is/ kinda late for me :)
[07:19] <MTecknology> kiko-zzz: yes, sleep, sleep well, sleep well and healthy
[07:19]  * kiko-zzz waves
[07:19]  * MTecknology waves his muscles at kiko-zzz   ..*.-_-.*./
[07:20] <MTecknology> kiko-zzz: remind me to ask you something when you feel better
[09:54] <rkistner> i'm having trouble browsing source code on launchpad
[09:54] <rkistner> i get the following error if i try to visit: http://bazaar.launchpad.net/~bzr/bzr/trunk/annotate/3908?file_id=branch.py-20050309040759-e4baf4e0d046576e
[09:54] <rkistner> Sorry, there was a problem connecting to the Launchpad server.
[09:54] <rkistner> Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
[13:46] <darius12> hi, I 'm evaluating using launchpad for bugtracking for the eclipse integration
[13:47] <darius12> there is already an eclipse-team and it is open so joining will probably not be a problem
[13:48] <darius12> would it be possible to file bugs and assign them to this team then? Even if they are about packages that are not yet official?
[13:48] <beuno_> darius12, you should talk to the team members
[13:50] <darius12> well, the question is about launchpad and the way it works first. If there is a problem with the specific team, we can make a new one
[13:51] <darius12> Development is actually taking place upstream (debian)
[13:51] <beuno> darius12, there really isn't *one* way to use Launchpad, so it's a lot about hay each team works
[13:51] <darius12> so it is acceptable to file bugs to launchpad even if they are not about ubuntu packages?
[13:52] <beuno> darius12, there are many upstream projects in Launchpad
[13:52] <beuno> which one are you refering to specifically?
[13:52] <darius12> well, a new one most likely
[13:53] <darius12> Let me tell you what I want to do exactly
[13:53] <beuno> sure
[13:53] <darius12> I 'd like to help create debian/ubuntu packages for recent eclipse
[13:54] <beuno> so this is for packaging, not an upstream project?
[13:54] <darius12> yes, it is packaging
[13:54] <darius12> but it will take a little time before it is ready to be "official"
[13:54] <beuno> it sounds like you want to work with the MOTU's on this one
[13:54] <beuno> get them to review the pacakging, etc
[13:55] <darius12> it is not ready for that yet
[13:55] <darius12> we are building a community/team for this
[13:55] <darius12> and we need something to help with project management (a bug tracker)
[13:56] <darius12> There is a large number of small tasks that need to be done and we need a place to keep them
[13:56] <darius12> I was wondering if launchpad can be the answer to this
[13:56]  * beuno hands off the question to BjornT and bac and goes on a call
[14:24] <danilos> darius12: you should be able to create a project and host bugs in it
[14:26] <darius12> thanks, danilos :)
[14:28] <danilos> darius12: actually, a team for trying out packaging might be good enough
[14:29] <darius12> danilos: how would bugs be filed then? (i.e., against what)
[14:33] <danilos> darius12: yeah, you'd need a project for that
[14:33] <danilos> darius12: so, in general, if there is not already an existing project for that particular piece of software, you can create it
[14:34] <darius12> so, it is either an alioth project or a launchpad project (something like eclipse-package)
[14:34] <darius12> I 'll ask the rest of the team what they prefer, thanks :-)
[15:03] <Rinchen> interesting MTecknology
[15:07] <MTecknology> Rinchen: just thought it could be helpful
[15:33] <Rinchen> ping intellectronica
[15:34] <intellectronica> Rinchen: yo
[15:34] <Rinchen> ah good, just checking to see if the bot was working.
[15:34] <Rinchen> ;-)
[15:34] <intellectronica> :D
[15:35] <Rinchen> I wonder if it's like a virus which transfers users daily. I wonder if danilos is a real person or a bot?
[15:35] <intellectronica> fwiw i know few real people of that height
[15:36] <danilos> Rinchen: it's a bot
[15:37] <danilos> Rinchen: btw, howdy
[15:37] <danilos> Rinchen: are you back with us for a while? :)
[18:04] <thekorn> hi, I've an API related question once again ;)
[18:04] <thekorn> who is the owner of a task?
[18:05] <thekorn> the user who created this task? - and if so why does +apidoc say that bug_task.owner is writable?
[18:06] <Ursinha> thekorn, I guess it's the person who has the task assigned to himself
[18:08] <thekorn> Ursinha, hmm, I think that's bug_task.assignee_link
[18:08] <thekorn> let me check
[18:11] <thekorn> yes, bug_task.owner is equal to "Filed here by:" in the web UI
[18:12] <beuno> uhm, then that shouldn't be writable...?
[18:12] <thekorn> maybe it's just a documentation issue,
[18:13] <thekorn> changing this value does not work
[18:13] <thekorn> (has no effect)
[18:13] <beuno> thekorn, the docs are on the wiki, right?
[18:13] <beuno> it sounds like a bug to be filed or a wiki page to be edited
[18:13] <thekorn> beuno, no I'm referring to https://edge.launchpad.net/+apidoc/
[18:14] <thekorn> section is bug_task, and there "owner"
[18:14] <thekorn> sorry, owner_link
[18:14] <beuno> thekorn, bug it is
[18:15] <thekorn> hmm, owner is marked as "writeable" in all sections
[18:16] <beuno> leonardr, ping?
[18:16] <leonardr> beuno, hi
[18:17] <beuno> hi leonardr
[18:17] <beuno> we need an API guru
[18:17] <beuno> do you know anything about ^
[18:20] <leonardr> yes, i'm responsible for the launchpad api
[18:21] <leonardr> for the framework, that is. if you have questions about some specific part of it i can tell you who to talk t
[18:21] <leonardr> o
[18:24] <thekorn> leonardr, hi, the question was why owner_link is marked as "writeable" on https://edge.launchpad.net/+apidoc/ nad if this is a bug, and if so, where should I report it?
[18:25] <leonardr> do you know if it's actually writable?
[18:25] <leonardr> also, which owner_link are you talking about? many objects have an owner_link
[18:25] <leonardr> and in general i don't see why it shouldn't be writable
[18:26] <thekorn> well, b.bug_tasks[0].owner = launchpad.me works, but has no effect
[18:27] <thekorn> hmm, owner is the one who e.g. created a task, why should this be changeable?
[18:28] <thekorn> owner != assignee, afaik
[18:28] <leonardr> ok
[18:29] <leonardr> in that case, i think it's a bug. file a bug against launchpad bugs
[18:29] <thekorn> ok, will do, thanks leonardr, beuno and Ursinha
[18:30] <Ursinha> thekorn, no problem, thanks for reporting us the bug
[18:59] <MvG> Hi! Someone from vcs-imports here willing to fix https://code.launchpad.net/~vcs-imports/vpnc/trunk ? See https://answers.launchpad.net/launchpad/+question/54518 for details.
[19:01] <Rinchen> hi MvG
[19:01] <Rinchen> I'll have a quick look
[19:01] <MvG> Rinchen: Thanks!
[19:03] <Rinchen> MvG, unfortunately I can't help with that one. That'll require mwhudson I think.
[19:03] <MvG> Rinchen: Sad. Thanks for looking, though.
[19:04] <Rinchen> MvG, yeah, it's the twisted error that gives it away
[19:12] <rockstar> MvG, hi.
[19:13] <rockstar> Rinchen, I have a pretty good idea where that bug is, and am hoping to spend some time on it in this next cycle.
[19:13] <Rinchen> rockstar, awesome. I saw cscvs and I ran
[19:13] <Rinchen> fast
[19:13] <Rinchen> :-)
[19:13] <rockstar> Rinchen, the twisted error is usually misleading, as there's an exception bubbling up, and eventually, Twisted accepts the blame.
[19:13] <Rinchen> I'm glad you've taken the challenge with that program.
[19:13] <Rinchen> oh, how nice of it!
[19:15] <rockstar> Rinchen, :)
[19:15]  * MvG is back, been afk, sorry.
[19:17] <MvG> Is cscvs used to import svn as well, not only cvs. The name seems misleading there.
[19:17] <rockstar> MvG, yes.
[19:17] <rockstar> It's wierd.
[19:18] <MvG> rockstar: Can you try a reimport, see if that solves it? Or import it locally or something?
[19:18] <MvG> To rule out strange divergent changes to the repository.
[19:18] <rockstar> MvG, I think the issue stems from a svn merge.
[19:20] <MvG> rockstar: Can't rule that out, though I always thought a svn merge was like a normal editing modification with a bit of special metadata stored under some keyword.
[19:21] <MvG> Gotta go for now, but i would be really happy if this got solved soon, or if I could read more details here in chat when I come back.
[19:21] <rockstar> MvG, well, cscvs currently chokes if you svn merge a revision that adds a file.
[19:24] <thumper> thekorn: re the API, did you remember to do the "object.save" or whatever the method is to have pending assignments?
[19:25]  * thumper runs to drop of the girls at school
[19:25] <thekorn> thumper, yes I ran bug.lp_save()
[19:34] <swe3tdave> For those who were looking forward to the OpenID_Launchpad module for Drupal 6, i think i'm done porting it. If anyone want to test it, its in Bazaar: lp:~loco-drupal-dev/loco-drupal/drupal-6.x
[19:38] <MvG> rockstar: Your opinion closely matches the answer on https://answers.launchpad.net/launchpad/+question/54518 whcih I had thought would only affect CVS, not SVN. I still don't completely get it, but am willing to accept it as a fact for now.
[19:39] <Rinchen> sweet, swe3tdave.  I've pinged stu to let him know as well
[19:40] <swe3tdave> Rinchen, thx
[19:40] <_Groo_> hi/2 all..
[19:47] <rockstar> MvG, the answer you linked to was mine.  :)
[19:49] <warren> is there a way to have a URL to bazaar.launchpad.net that goes to the latest version of a particular file?
[19:49] <warren> http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/1009?file_id=dhcpdk12linux.conf-20080129180034-aiosbwg7a1bwv42c-1 for example I want to link from elsewhere so people can view the latest version of this file, but not this particular revision
[19:49] <beuno> warren, yes. Do you have a URL handy?
[19:50] <beuno> warren, http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/head:?file_id=dhcpdk12linux.conf-20080129180034-aiosbwg7a1bwv42c-1
[19:50] <beuno> the fix to make the links be constructed that way has landed in trunk
[19:50] <beuno> but hasn't been rolled out to Launchpad yet
[19:50]  * beuno nudges mwhudson 
[19:51] <kiko> wednesday
[19:52] <mwhudson> is there a new loggerhead in RF yet?
[19:52] <mwhudson> i haven't landed one
[19:52] <beuno> mwhudson, there isn't. We need to get it there
[19:52] <mwhudson> i guess it might be a bit late for this rollout?
[19:53] <beuno> but there have been quite a few changes, so I'd really prefer you do the merging and reviewing, since I'm still unclear on what can break or not  :)
[19:53] <warren> beuno: that URL you gave me is still of revision 1009
[19:53]  * mwhudson does a bzr missing
[19:53] <beuno> warren, isn't revision 1009 the latest?
[19:54] <warren> beuno: oh I see, thanks.
[19:54] <beuno> warren, :)
[19:54] <mwhudson> oh, we really want trunk r252 in production!
[19:54] <beuno> mwhudson, guess what
[19:55] <beuno> it already is
[19:55] <mwhudson> oh
[19:55] <beuno> there where cowboys involved
[19:55] <beuno> no luck
[19:55] <beuno> which is still very weird to me
[19:55] <beuno> since it consistently drops memory usage for me
[19:55] <beuno> I haven't had any time to test it on the MySQL branch
[19:56] <beuno> my only remaining theory is that that branch is evil
[19:56] <mwhudson> does it make requests faster too?
[19:57] <beuno> yeap, it takes about 1/3rd of the time to process it
[19:57] <beuno> (very unscientificly measured)
[19:57] <mwhudson> interesting
[19:58] <mwhudson> at the very least we should tweak the threadpool settings we use
[19:58] <mwhudson> at the extreme, we could consider a different http server
[19:58] <beuno> mwhudson, there was some talk with poolie about moving from threads to processes so memory issues would die with each thread
[19:58] <mwhudson> yeah, that would make some sense
[19:58] <beuno> but that means either moving to not using the full revision graph, which I don't think we can easily do
[19:58] <beuno> or cache the revision graph
[19:59] <beuno> which is sort-of doable, but I don't know what the performance impact of that is
[19:59] <mwhudson> well, we could compute the revision graph in the parent, /then/ fork, perhaps
[19:59] <mwhudson> but yeah -- difficulties
[20:00] <beuno> mwhudson, OTOH, if we do cache the revision graph on disk, we will have to hit bzr much less
[20:00] <mwhudson> oh, you mean cache it in sqlite or something somehow?
[20:01] <beuno> I tried using some magic jam added to bzrlib to load the revnos lazily, but it just works with mainline revs
[20:01] <beuno> yeap, in sqlite
[20:01] <beuno> although it feels like regressing, maybe it's just the way to got for now
[20:05] <mwhudson> i guess we should analyse what information we need from the revision graph, and how to represent it in sql
[20:05] <rockstar> mwhudson, yea, I was just thinking that.
[20:05] <beuno> well, initially, I was thinking that maybe we could just serialize it and stick it in the DB
[20:05] <mwhudson> a list of tuples of strings and integers isn't a super natural relational structure
[20:05] <mwhudson> (and somehow i doubt sqlite has WITH RECURSIVE yet)
[20:05] <rockstar> mwhudson, it does not.
[20:52] <LarstiQ> beuno, mwhudson: bzr-svn also does some caching of course
[20:53] <beuno> LarstiQ, right. We've been playing with Loggerhead on top of bzr-svn during UDS with lifeless
[20:53] <LarstiQ> ok
[20:53] <beuno> the cache sometimes got in the way, but I believe lifeless filed all the relevant bugs and patches
[20:54] <beuno> it would be interesting to see how bzr-svn does it though...
[20:54] <jelmer> in 0.5, the cache can be turned off without any significant performance problems if you have enough bandwidth to the svn server
[21:07] <krisives> Umm, I have an odd experience with using Launchpad
[21:07] <krisives> I opened it up for the first time in a long while and it said I was logged in as somoene I am not
[21:08] <krisives> This is my personal notebook (not public in any way) and I've never owned the account I'm logged into
[21:08] <krisives> What should I do?
[21:09] <Rinchen> krisives, hi
[21:09] <krisives> hi Rin
[21:10] <Rinchen> krisives, can you PM me the destination link of the person link in the upper right hand corner please?
[21:10] <Rinchen> krisives, I'd like to have that before you sign-out. It's odd that you would be logged in as someone else
[21:11] <Rinchen> flacoste, ^^
[21:12] <flacoste> Rinchen: hmm, reuse of session identifier?
[21:12] <flacoste> if that's the case, krisives is very lucky
[21:12] <Rinchen> flacoste, my thoughts, yes.
[21:12] <flacoste> got a SHA1 collision
[21:12] <flacoste> either we have too many users
[21:12] <Rinchen> lol
[21:13] <krisives> Is this some PHP session 1 in a million stuff here?
[21:14] <Rinchen> no php here :-)
[21:15] <Rinchen> zope, python, apache, openid
[21:15] <krisives> oh, didnt know what LP was made in
[21:16] <Rinchen> krisives, sugar, spice, and everything nice....
[21:25] <mthaddon> krisives: can you confirm if you have a cookie from Launchpad?
[21:25] <krisives> I can't
[21:25] <krisives> I'm using Chrome since I was on windows
[21:25] <krisives> no idea how to do that in Chrome
[21:33] <poolie> hello
[21:34] <poolie> krisives: http://chromespot.com/showpost.php?s=2244eb1e7fd42d08bbf3bd3fc1213320&p=3182&postcount=5
[21:35] <krisives> ty, reading
[21:36] <krisives> Thanks poolie worked like a charm
[21:37] <krisives> no cookies other than for help.launchpad.net MOIN_SESSION, which appears to be unrelated
[21:48] <mthaddon> krisives: thx, we're looking into it
[22:10] <mthaddon> krisives: we've disabled the caching til we can figure out what the issue was, so you shouldn't see this issue any more
[22:14]  * Hobbsee shakes head at this contact form.
[22:24] <wgrant> Hobbsee: Do you need to add somebody to ~ubuntumembers?
[22:25] <wgrant> Anyway, that feature is now disabled for teams unless you're already a member.
[22:25] <Hobbsee> wgrant: yeah.  so i wasn't the only one who got that mail.
[22:26]  * Hobbsee wonders if that went to all the members on ~ubuntumembers
[22:26] <wgrant> Probably.
[22:29] <Hobbsee> nasty.
[22:29] <Hobbsee> I did ponder a response back of "You fail.  Go away" or something for it.