[10:31] <marmuta> Hi, I'm unable to access bug #1195857, it's probably still marked private. Could someone look into making it public?
[10:32] <czajkowski> marmuta: usually that falls to the bug supervisors not so much launchpad, is it an Ubuntu bug ?
[10:33] <wgrant> #ubuntu-bugs is the right place for that
[10:34] <marmuta> I think so, the duplicate bug #1205874 seems to be an Ubuntu bug.
[10:34] <marmuta> OK, thanks, I'll ask there.
[10:35] <czajkowski> wgrant: welcome back
[10:35] <czajkowski> you just landed :)
[10:35] <wgrant> Nah, been home for nearly 12 hours
[10:35] <wgrant> Rather tired, but home
[10:36] <czajkowski> excellent
[10:36] <wgrant> That remains to be seen.
[10:36] <wgrant> :)
[10:39] <czajkowski> go sleep!
[10:40] <wgrant> It's just about that time
[10:42]  * StevenK will be crashing after dinner
[12:32] <saiarcot895> If there are a ton of SIGSEGV/SIGABRT bug reports that apply to distro versions no longer supported (natty and oneiric), is it safe to close them?
[12:36] <cjwatson> saiarcot895: Closing natty/oneiric-specific tasks, maybe, but not the whole bug.  Crashes don't magically get fixed with time.
[12:37] <cjwatson> saiarcot895: http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2009-02-27-bug-triage-rants.html
[18:34] <Corey> I'm seeing a lot ofconnections timing out on tarball uploads.
[18:36] <Corey> Hmm, seems to have resolved, nevermind.
[19:30] <yofel> hi, I just had a build fail twice on chindi04 with http://paste.ubuntu.com/5926389/ - could someone please fix the sbuildrc?