[03:15] kiko: yes, expiry is on [03:16] 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] sladen: The expiry script isn't running yet. [03:17] We are in the middle of the roadmap to turn it back on. [04:18] 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] wgrant: is there some Python/API script I can use in the meantime? [04:19] sladen: Not sure, sorry. [05:52] Help! Branches aren't pushing! I expect an LP error! http://paste.ubuntu.com/530504/ [05:52] The push isn't coming up on LP [05:53] okay, it came [05:54] I think bzr was unable to poke LP to scan immediately [05:54] but it DID push the branch [05:59] bilalakhtar: it's https://bugs.launchpad.net/launchpad-code/+bug/674305 [05:59] Launchpad bug 674305 in Launchpad Bazaar Integration "bzr push occasionally reports AssertionError on terminal (affected: 2, heat: 10)" [High,Triaged] [06:00] 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] bilalakhtar: please link that pastebin to the bug, though [06:01] spiv: yes, doing that already [06:01] bilalakhtar: and specifically highlight that that pastebin shows it can happen even in the "No new revisions to push" case. [06:03] spiv: oops, missed that in my first comment, doing it now === almaisan-away is now known as al-maisan [06:45] * micahg wonders why PPAs are still building for Jaunty === Nafallo_ is now known as Nafallo [09:24] henninge, hey, what's up? [09:26] danilo_: Hi! === al-maisan is now known as almaisan-away === matsubara_ is now known as matsubara [11:22] Are there any networking issues in the canonical datacentre right now? [11:23] 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] losa ping? [11:31] maxb, losa: I'm seeing errors when pushing branches, too. [11:31] huh, bazaar.launchpad.net:22 appears up to me [11:31] wow [11:31] never got bzr: ERROR: Server sent an unexpected error: ('error', "") [11:31] before [11:31] maxb: Yeah, they're (I think) internal XML-RPC server errors. [11:32] there are issues with the data center [11:32] I just checked [11:32] maxb: Apparently there are DC issues [11:32] Hah [11:32] Great minds. [11:32] (Actually, I just tend to follow jml around in the hope that I'll do something that looks smart) [11:32] gmb: I'm just easily distracted [11:48] [3 [12:01] good morning! quick question, how can I set the default visibility of bugs and branches for a given project? [12:24] nessita: I think that might require admin intervention. Also privacy usually requires a commercial subscription === mrevell is now known as mrevell-lunch [12:30] so, what's going on here? http://paste.ubuntu.com/530670/ [12:30] xmlrpclib.Fault: [12:31] jml: https://bugs.launchpad.net/launchpad-code/+bug/674305 [12:31] Launchpad bug 674305 in Launchpad Bazaar Integration "bzr push occasionally reports AssertionError on terminal (affected: 4, heat: 20)" [High,Triaged] [12:31] * spiv -> zzz [12:31] jml: there was a little discussion on #launchpad-dev 12-ish hours ago [12:32] spiv: ta === zyga is now known as zyga-food === mrevell-lunch is now known as mrevell === almaisan-away is now known as al-maisan === beuno_ is now known as beuno === zyga-food is now known as zyga [13:46] doh! http://paste.ubuntu.com/530702/ [14:01] is there a way i can monitor a build through my shell? [14:02] like.. all the output from that builder redirected to my konsole === linuxjedi_ is now known as LinuxJedi [14:09] shadeslayer: no, that's not possible [14:09] bigjools: ok [14:09] shadeslayer: with a small bit of work the logtail could be exposed through the API though [14:10] that would be cool [14:10] i just want that i login via lp-shell and can monitor the build when i put in the build number [14:11] shadeslayer: please file a bug and perhaps someone will pick it up [14:12] i probably will === matsubara is now known as matsubara-lunch === Ursinha is now known as Ursinha-lunch === LinuxJedi is now known as LinuxJedi|away [14:58] "Toto, I have a feeling we're not on edge.launchpad.net any more." [14:58] mpt: indeed not === Ursinha-lunch is now known as Ursinha === matsubara-lunch is now known as matsubara === Meths_ is now known as Meths === LinuxJedi|away is now known as LinuxJedi === yofel_ is now known as yofel === jordi__ is now known as jordi === al-maisan is now known as almaisan-away [16:58] launchpad failed to import an svn branch ( https://code.launchpad.net/~bdrung/+junk/opal-compiler ). where should i file this bug? [17:01] bdrung: bugs.launchpad.net/launchpad-code === oubiwann-away is now known as oubiwann === oubiwann is now known as oubiwann-away === oubiwann-away is now known as oubiwann === LinuxJedi is now known as LinuxJedi|away [18:14] any news on when the launchpad builder will support making orig.tar files for source format 3? [18:24] I thought that it's fixed. === almaisan-away is now known as al-maisan === LinuxJedi|away is now known as LinuxJedi === shadeslayer is now known as evilshadeslayer [19:12] nope, had the problem when building from a receipie in edge today [20:10] I'm getting "xmlrpclib.Fault: " when trying to push up changes. (full traceback: http://www.pastie.org/private/kbgfabcx0bgv6rl2bksjtg) [20:11] we're having some load issues on an internal system [20:11] we hope to have it fixed early next week :(. Until then please retry. [20:11] flacoste: ^ its a shame we can't get something done sooner [20:12] lifeless: thanks. [20:12] aaron01: from my understanding, it succeeds? [20:12] flacoste: seems to, yes. [20:13] 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] It used to be very easy to do this with regular projects, but apparently something was changed. === flacoste changed the topic of #launchpad to: Transient warnings when pushing to Launchpad: ETA for fix is next week | Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ === al-maisan is now known as almaisan-away === matsubara is now known as matsubara-afk === flacoste changed the topic of #launchpad to: Due to increase load, you may encounter spurious stack traces when pushing to Launchpad | Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ [23:09] hi folks, there is anyway to support plugins in lp? [23:10] i will use bzr-colo and need push in lp === flacoste changed the topic of #launchpad to: Code imports disabled for the week-end due to increased load. This should eliminate the traceback people were seeing on bzr push | Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/