[03:15] <sladen> kiko: yes, expiry is on
[03:16] <sladen> kiko: but I haven't seen any of the bugs actually expired.  Is it possible that LP is actually going to wait 60 days /from/ when it was enabled before the first bugs are expired (even if they are already >= 60 days without update?)
[03:16] <wgrant> sladen: The expiry script isn't running yet.
[03:17] <wgrant> We are in the middle of the roadmap to turn it back on.
[04:18] <sladen> wgrant: ah right, when does it start (I've been seeing emails about it for the last couple of months, so assumed that it had happened by now)
[04:18] <sladen> wgrant: is there some Python/API script I can use in the meantime?
[04:19] <wgrant> sladen: Not sure, sorry.
[05:52] <bilalakhtar> Help! Branches aren't pushing! I expect an LP error! http://paste.ubuntu.com/530504/
[05:52] <bilalakhtar> The push isn't coming up on LP
[05:53] <bilalakhtar> okay, it came
[05:54] <bilalakhtar> I think bzr was unable to poke LP to scan immediately
[05:54] <bilalakhtar> but it DID push the branch
[05:59] <spiv> bilalakhtar: it's https://bugs.launchpad.net/launchpad-code/+bug/674305
[06:00] <spiv> bilalakhtar: as you saw, the push succeeds, and it appears LP still scans the branch just fine, so I'm not sure if it has any impact other than looking scary.
[06:01] <spiv> bilalakhtar: please link that pastebin to the bug, though
[06:01] <bilalakhtar> spiv: yes, doing that already
[06:01] <spiv> bilalakhtar: and specifically highlight that that pastebin shows it can happen even in the "No new revisions to push" case.
[06:03] <bilalakhtar> spiv: oops, missed that in my first comment, doing it now
[06:45]  * micahg wonders why PPAs are still building for Jaunty
[09:24] <danilo_> henninge, hey, what's up?
[09:26] <henninge> danilo_: Hi!
[11:22] <maxb> Are there any networking issues in the canonical datacentre right now?
[11:23] <maxb> I can't reach security.ubuntu.com or archive.canonical.com, and traceroute dies with gi1-0-1.oxygen.canonical.com being the last successful hop
[11:29] <maxb> losa ping?
[11:31] <gmb> maxb, losa: I'm seeing errors when pushing branches, too.
[11:31] <maxb> huh, bazaar.launchpad.net:22 appears up to me
[11:31] <jml> wow
[11:31] <jml> never got bzr: ERROR: Server sent an unexpected error: ('error', "<Fault -1: 'Unexpected Zope exception: RequestExpired: request expired.'>")
[11:31] <jml>  before
[11:31] <gmb> maxb: Yeah, they're (I think) internal XML-RPC server errors.
[11:32] <jml> there are issues with the data center
[11:32] <jml> I just checked
[11:32] <gmb> maxb: Apparently there are DC issues
[11:32] <gmb> Hah
[11:32] <gmb> Great minds.
[11:32] <gmb> (Actually, I just tend to follow jml around in the hope that I'll do something that looks smart)
[11:32] <jml> gmb: I'm just easily distracted
[11:48] <wgrant> [3
[12:01] <nessita> good morning! quick question, how can I set the default visibility of bugs and branches for a given project?
[12:24] <maxb> nessita: I think that might require admin intervention. Also privacy usually requires a commercial subscription
[12:30] <jml> so, what's going on here? http://paste.ubuntu.com/530670/
[12:30] <jml> xmlrpclib.Fault: <Fault -1: 'Unexpected Zope exception: AssertionError: '>
[12:31] <spiv> jml: https://bugs.launchpad.net/launchpad-code/+bug/674305
[12:31]  * spiv -> zzz
[12:31] <spiv> jml: there was a little discussion on #launchpad-dev 12-ish hours ago
[12:32] <jml> spiv: ta
[13:46] <fta> doh! http://paste.ubuntu.com/530702/
[14:01] <shadeslayer> is there a way i can monitor a build through my shell?
[14:02] <shadeslayer> like.. all the output from that builder redirected to my konsole
[14:09] <bigjools> shadeslayer: no, that's not possible
[14:09] <shadeslayer> bigjools: ok
[14:09] <bigjools> shadeslayer: with a small bit of work the logtail could be exposed through the API though
[14:10] <shadeslayer> that would be cool
[14:10] <shadeslayer> i just want that i login via lp-shell and can monitor the build when i put in the build number
[14:11] <bigjools> shadeslayer: please file a bug and perhaps someone will pick it up
[14:12] <shadeslayer> i probably will
[14:58] <mpt> "Toto, I have a feeling we're not on edge.launchpad.net any more."
[14:58] <jml> mpt: indeed not
[16:58] <bdrung> launchpad failed to import an svn branch ( https://code.launchpad.net/~bdrung/+junk/opal-compiler ). where should i file this bug?
[17:01] <jml> bdrung: bugs.launchpad.net/launchpad-code
[18:14] <shtylman> any news on when the launchpad builder will support making orig.tar files for source format 3?
[18:24] <ari-tczew> I thought that it's fixed.
[19:12] <shtylman> nope, had the problem when building from a receipie in edge today
[20:10] <aaron01> I'm getting "xmlrpclib.Fault: <Fault -1: 'Unexpected Zope exception: AssertionError: '>" when trying to push up changes. (full traceback: http://www.pastie.org/private/kbgfabcx0bgv6rl2bksjtg)
[20:11] <lifeless> we're having some load issues on an internal system
[20:11] <lifeless> we hope to have it fixed early next week :(. Until then please retry.
[20:11] <lifeless> flacoste: ^ its a shame we can't get something done sooner
[20:12] <aaron01> lifeless: thanks.
[20:12] <flacoste> aaron01: from my understanding, it succeeds?
[20:12] <aaron01> flacoste: seems to, yes.
[20:13] <sense> I've created a project on Launchpad for my LoCo and would like to make sure my subteam leaders can add the already existing Launchpad projects as subprojects of the new ubuntu-nl project. However, I heard that due to a recent change it it necessary to have a special kind of project if you want to use subprojects. Is it possible to use an already existing Launchpad project for this, and how do I do this?
[20:14] <sense> It used to be very easy to do this with regular projects, but apparently something was changed.
[23:09] <ovnicraft> hi folks, there is anyway to support plugins in lp?
[23:10] <ovnicraft> i will use bzr-colo and need push in lp