[00:00] <ubotu> New bug: #177582 in launchpad "launchpad karma go down if i commit in PPA" [Undecided,New] https://launchpad.net/bugs/177582
[00:38] <pochu> mthaddon: ^ :-)
[00:39] <jml> everybody loves a release
[00:46] <pochu> Oh, is there a topic length limit?
[00:46] <jml> pochu: it's entirely possible
[00:46] <pochu> And do you know when the mailing lists will go beta?
[00:48]  * Fujitsu thought they were on staging already.
[00:48] <pochu> Really? That's nice to hear.
[01:05] <pochu> Fujitsu: do you know of an url where I can see it? I can't find anything there...
[01:34] <somerville32> mthaddon, Is Launchpad still processing uploads?
[01:34] <mthaddon> somerville32, it will be for another 30 mins or so 
[02:13] <harrisony> 1 minute till launchpad goes down :D
[02:18]  * somerville32 prays for launchpad.
[04:03] <Fujitsu> Yay, it's back.
[04:03] <harrisony> yay, party
[04:08] <Fujitsu> Aha, so we can finally delete upstream links!
[04:08] <Fujitsu> Though the UI is ugly.
[04:33] <lamont> hrm... looks like the build-queue-depth got cleaned up, too.
[04:33] <lamont> although it still isn't a link to the actual dump of missing builds
[04:34]  * lamont wonders if he should worry that all 3 hppa buildds are idle, expects it's just queue-builder running again
[04:34] <Fujitsu> lamont: It could well be that various Soyuz bits haven't started yet.
[04:35]  * Fujitsu thought we had the fixed queue-builder now.
[04:35] <Fujitsu> So it's a bit less completely insane.
[04:35] <lamont> yeah
[04:35] <lamont> something like that
[04:36] <Fujitsu> Oh, bleh, that didn't make it.
[04:36] <lamont> 2007/354/04 98.8315 98.8886 98.0103 87.6458 97.4733 97.3818 97.0145
[04:36] <lamont> nicer numbers.
[04:36] <Fujitsu> Not bad, not bad.
[04:36]  * lamont can't be bothered to remember which is which other than where i386 and hppa land. :-)
[04:36] <Fujitsu> Right.
[04:36] <lamont> i386 first, hppa is the low one. 
[04:36] <Fujitsu> It will be good when I'm not sure which is hppa.
[04:37] <lamont> in decreasing order, those are amd64, i386, powerpc, ia64, sparc, lpia, hppa
[04:38] <lamont> so i386 amd64 ppc (duh... first 3 architectues and such), then came the hppa and ia64 architectures, then sparc and lpia
[04:38] <lamont> iz chronological. :-)
[04:39] <lamont> too much work to rearrange history when I add another column.
[04:49] <tonyyarusso> Hey, quick question: I was wondering if teams could have address redirection like users.  As in, ubuntu-ca@ubuntu.com would forward to the default contact for the Ubuntu Canada team, etc., so that teams could have a more consistent contact address.
[04:51] <elmo> tonyyarusso: launchpad doesn't run ubuntu.com email, so that's not really a launchpad question
[04:51] <elmo> tonyyarusso: but it's a reasonable idea, but bear in mind CDC hosted loco teams are welcome to have aliases (that they can control), so you guys could standardize on contact@ubuntu-$CC.org too
[04:51] <tonyyarusso> elmo: Really?  Hmm, okay.  What handles the Ubuntu member stuff then?  I was under the impression it was a side thing of LP.
[04:52] <elmo> tonyyarusso: the data's pulled out of LP, ubuntu.com email itself is otherwise independent
[04:52] <tonyyarusso> elmo: That actually would probably be nicer - IF we could actually control our hosting, which raises another question entirely... (See the RT queue for entries from myself and Brian Burger)
[04:54] <elmo> tonyyarusso: err
[04:54] <elmo> tonyyarusso: I'm not really sure what you mean by control your hosting.  but in any event, I only see a ticket from you in the queue, not Brian
[04:54] <tonyyarusso> o rly?
[04:54]  * tonyyarusso goes to look for updates
[04:55] <elmo> tonyyarusso: I'll try to respond to it tomorrow, 'cos it's almost 5am here
[04:55] <tonyyarusso> elmo: Here's Brian's - https://rt.ubuntu.com/Ticket/Display.html?id=207
[04:55] <elmo> oh
[04:56] <elmo> I didn't recognise blurdesign@ as Brian
[04:56] <elmo> (i was visually scanning the email addresseS)
[04:56] <tonyyarusso> Yeah, it hides pretty well.
[04:57] <elmo> so anyway, I'll try and look at you and his.  sorry for the delay in responding, we've just been a bit swamped, but it's slowly getting better
[04:57] <tonyyarusso> That part's not LP-related of course, but if you could see what you can do to speed up the RT turnaround in general that would be _much_ appreciated.  :)
[04:57] <tonyyarusso> But for now...good grief go to bed you silly goose.
[05:10] <slangasek> is anyone about who can help me understand why udev 117-3 hasn't reached the Ubuntu accepted queue yet despite having been uploaded >1h ago?
[05:10] <slangasek> binary packages seem to be making it to the accepted queue just fine, I don't see any source packages there and udev in particular seems to be abnormally delayed
[06:52] <bdmurray> Is codebrowse.launchpad.net not working?
[06:53] <stdin> bdmurray: works here
[06:54] <bdmurray> I'm getting 500s for python-launchpad-bugs and bughelper
[06:54] <spiv> mwhudson: ^
[06:54] <bdmurray> like this url
[06:54] <bdmurray> http://codebrowse.launchpad.net/~bughelper-dev/python-launchpad-bugs/main/revision/54
[06:56] <stdin> yeah, I get 500 with revision/54 but not from http://codebrowse.launchpad.net/~bughelper-dev/python-launchpad-bugs/main/files
[06:58] <spiv> I cannot view a revision on any branch I've tried.
[07:41] <Fujitsu> Erm, Soyuz seems to have eaten many hundreds of builds.
[07:41] <Fujitsu> The ~450 needs-build on hppa have evaporated.
[07:42] <Fujitsu> In fact, I can't see any Ubuntu needs-build builds.
[07:48] <Fujitsu> All needs-build (at the time of the rollout) build records seem to have entirely ceased to be. This is probably a bit of a problem.
[07:49] <Fujitsu> lamont: Soyuz has brought hppa up-to-date for you.
[07:50] <Peng> Well that's a way more efficient way to cut through the queue than actually building everything and stuff...
[07:51] <Fujitsu> Yep.
[08:10] <ubotu> New bug: #177621 in soyuz "Hundreds of builds incorrectly marked as superseded" [Undecided,New] https://launchpad.net/bugs/177621
[08:32] <mwhudson> what on earth
[08:45] <StevenHarperUK> Does anyone know when the translation exports are due back?
[08:46] <kiko-zzz> StevenHarperUK, jtv should have them fixed by tomorrow
[08:46] <StevenHarperUK> wow that long -its been 3 days already,  they must have been *really broken
[08:46] <jtv> StevenHarperUK: They were...
[08:47] <jtv> StevenHarperUK: I have the fix, it just takes a lot of time to make _really sure_ it's the right one
[08:47] <kiko-zzz> what happened was that with the DB refactoring the distribution series opening process became broken
[08:47] <StevenHarperUK> Ok thanks for  the info - ill check back tommorrow
[08:47] <kiko-zzz> and a side-effect of us running a broken import was exports breaking
[08:48] <kiko-zzz> jtv, do you think the cleanup itself will take a long time to run?
[08:48] <StevenHarperUK> Ah a DB change that breaks data is not a nice job to clean up - I don't envy that job
[08:50] <jtv> kiko-zzz: it may...  I've got a test run that takes forever--but may be livelocked with another long-running query.
[09:07] <mwhudson> huh, codebrowse seems to be working again, after not much more significant than a bunch of restarts :/
[09:07] <Fujitsu> It's TurboGears. It can do what it wants.
[09:08] <mwhudson> damn right
[09:08] <mwhudson> anyways, means i can go and have breakfast
[09:08] <Fujitsu> Heh.
[10:11]  * Fujitsu wonders who destroyed *.ppa
[10:15] <Fujitsu> Nice descriptive errors from PPA buildds: <Fault 8002: 'error'>
[10:25] <kiko-zzz> Fujitsu, all of them?
[10:27] <mwhudson> yay xml-rpc
[10:27] <Fujitsu> kiko-zzz: They were all missing (no route to host or so) for a while, then some came back, some with the 'error' Fault, but I think they're all back now.
[10:27] <Fujitsu> Soyuz hasn't regurgitated the builds it ate earlier, though :(
[10:28] <Fujitsu> Oh, the PPA buildds are gone again.
[10:40]  * kiko-zzz frowns
[10:41] <kiko-zzz> bigjools?
[10:42] <bigjools> oof - cprov/infinity were doing something with them
[10:42] <cprov> Fujitsu: infinity is upgrading the PPA builders 
[10:42] <Fujitsu> Aha.
[10:42] <cprov> Fujitsu: they will be back in a bit (20 minutes or so)
[10:43] <Fujitsu> cprov: Was the upgrade meant to destroy all needs-build builds and mark them superseded?
[10:44] <cprov> Fujitsu: no
[10:44] <Fujitsu> Well, it appears to have.
[10:44] <kiko-zzz> cprov, hmmmm. wonder if that has to do with the patch that bigjools put in last
[10:45] <bigjools> my patch didn't touch builds
[10:45] <kiko-zzz> it didn't?
[10:45] <Fujitsu> Making lots and lots of builds vanish is probably inadvisable.
[10:45] <bigjools> you're talking about the obsolescence thing?
[10:45] <kiko-zzz> bigjools, the patch we reviewed together. the candidate/elected patch.
[10:46] <Fujitsu> See bug #177621, /+builds with the lack of hppa backlog, https://edge.launchpad.net/ubuntu/hardy/+source/koffice2/1.9.95.1-0ubuntu4 for an example...
[10:46] <ubotu> Launchpad bug 177621 in soyuz "Hundreds of builds incorrectly marked as superseded" [Undecided,New] https://launchpad.net/bugs/177621
[10:46] <bigjools> oh that patch
[12:03] <TeTeT> quick thumbs up for the PPA help, it's really excellent. I wanted to upload a package, forgot all of the syntax for dput and got it working within 5 mins with help of LP->PPA->Help->PPAQuickStart.
[13:08] <mtaylor> any launchpad admins around who can help me out with a hosted bzr branch? 
[13:08] <mtaylor> I'm trying to do this: 
[13:08] <mtaylor> bzr upgrade --dirstate-tags bzr+ssh://monty@bazaar.launchpad.net/%7Endb-connectors/ndb-connectors/devel
[13:08] <mtaylor> which isn't working
[13:09] <mtaylor> so then I tried it with sftp
[13:09] <mtaylor> and then that aborted :(
[13:09] <mtaylor> so now I can't restart the sftp bit, because I get
[13:09] <mtaylor> bzr: ERROR: File exists: '/~ndb-connectors/ndb-connectors/devel/.bzr.backup': mkdir failed: unable to mkdir
[13:09] <mtaylor> so I'm guessing someone might actually have to do it there on the machine? 
[13:10] <mtaylor> it would also be great if the same upgrade could be run on /~ndb-connectors/ndb-connectors/telco-6.3, too...
[13:16] <lamont> kewl. build queue depth now seems to match hardy/needs-build for at least hppa
[13:23] <mwhudson> mtaylor: let me grub around on the filesystem for you
[13:24] <mtaylor> mwhudson: thanks
[13:26] <mwhudson> mtaylor: the branch you want to upgrade is at revision 379?
[13:26] <mwhudson> mtaylor: "Added tags and updated update_from_swigsvn to use them."
[13:26] <mtaylor> mwhudson: sound about right
[13:28] <mwhudson> mtaylor: done, though you'll need to make some change to the branch to trigger mirroring before you'll be able to see the difference over http:
[13:28] <mtaylor> mwhudson: cool. well I've got some changes I wanted to push that it wasn't letting me... 
[13:28] <mtaylor> so let's see if it'll work now
[13:29] <mwhudson> mtaylor: you want me to do ndb-connectors/ndb-connectors/telco-6.3 too?
[13:29] <mtaylor> mwhudson: please. 
[13:29] <mtaylor> w00t.
[13:29] <mtaylor> push worked
[13:30]  * Hobbsee waves
[13:30] <mwhudson> telco-6.3 done too
[13:33] <mtaylor> mwhudson: thanks a ton
[13:36] <ubotu> New bug: #177653 in launchpad "Oops in new account creation" [Undecided,Confirmed] https://launchpad.net/bugs/177653
[13:50] <ubotu> New bug: #177657 in launchpad "OOPS confirming an non validated email address using the +editemails page" [Undecided,New] https://launchpad.net/bugs/177657
[14:28] <stdin> platinum buildd seems to have died
[14:44] <kiko-zzz> look at that
[14:45] <kiko> milestones in bug listings
[14:45] <kiko> the future is here
[14:47] <Kmos> also rhenium builld is dead
[14:47] <Kmos> buildd
[14:48] <Kmos> promethium
[14:48] <Kmos> infinity is updating them
[14:49] <Hobbsee> well then.  no need to look at why they've died.  good!
[14:49] <Kmos> :)
[14:51] <kiko> good ole infinity
[14:51] <Hobbsee> he even fixed one of the bugs.  woo!
[15:08] <elmo> I don't think infinity is updating them...
[15:43] <pochu> I'm getting timeouts in https://bugs.edge.launchpad.net/ubuntu
[15:44] <pochu> OOPS-719EB85
[15:47] <Kmos> elmo: lamont told me that
[15:48] <lamont> elmo: late my time last night there was a comment that cprov/infinity were doing some update-like activity
 Fujitsu: infinity is upgrading the PPA builders 
[15:49] <lamont> 1042 UTC
[15:50] <cprov> lamont: nah, they are marked as 'timed out'
[15:50] <lamont> yeah - that'd be different
[15:50] <lamont> although, if one didn't let LP know one was managing them, ISTR they timeout... or was that connect-fail
[15:51] <lamont> the more context-full version of things is that Kmos asked me in /query what was up, and I told him that at one point infinity was apparently updating them or something, and that, in any case, he should ask infinity, not me about them.
 istr infinity was upgrading them.  and launchpad gets pissy when they don't respond because they're offline...
[15:52] <lamont> admittedly, "was" is not exactly precise.
[15:53]  * lamont makes a note to not provide guesses about such things in the future. :(
[15:57] <cprov> lamont: Kmos: NOT OK builders rescued.
[15:58] <cprov> lamont: btw, isn't build-farm clearly faster now ?
[15:59] <kalib> hey guys...
[16:00] <kalib> I downloaded the kubuntu 8.04 with a hope...but it didn't work.. :/
[16:01] <kalib> until 6.10 my sound was pretty cool... but when i tried the 7.10 my sound was not working...and i saw it with so many people on google who has the same problem with notebooks...
[16:01] <h4x0r7h1s> http://bugs.launchpad.net/ubuntu
[16:01] <kalib> i was trieng the 8.04...but it's still not working... :/
[16:01] <h4x0r7h1s> for the past like hour, TIMEOUT ERROR
[16:01] <h4x0r7h1s> see OOPS 719F829
[16:01] <kalib> ok...thanks i'll report it
[16:02] <h4x0r7h1s> I can actually go to home, then to the ubuntu project
[16:02] <h4x0r7h1s> hitting bugs makes it tell me to FOAD
[16:03] <kalib> sure
[16:03] <mwhudson> h4x0r7h1s: i'm trying to get the attention of the bugs developers 
[16:04] <mwhudson> h4x0r7h1s: ah, they know about it
[16:06] <kalib> anyone of you guys know what's goin on about this bug?? So many notebooks with ATI sound are not working...i saw so many people on google with the same problem...
[16:06] <kiko> kalib, try #ubuntu
[16:06] <kalib> you know... for a distro like (k)ubuntu, that says "the best desktop distro.." is a bad new.. :/
[16:07] <pochu> kalib: 1) this is not the right place, 2) 8.04 is supposed to eat your cat, 3) file a bug.
[16:07] <kalib> kiko but...here is the place to talk about bugs, or not??
[16:07] <pochu> kalib: nope.
[16:07] <pochu> That's bugs.launchpad.net/ubuntu
[16:07] <kalib> pochu i'm not talking only about 8.04... i said before... i was using 7.10
[16:07] <kiko> kalib, this is the place to talk about launchpad
[16:08] <pochu> kalib: #ubuntu-bugs is the right place. Let's move to there.
[16:08] <kalib> ok..thanks... sorry... :/
[16:16] <kiko> cprov, does bigjools know how to rescue builders himself if he needs to?
[16:16] <cprov> kiko: any buildd-admins can do it via UI ($builder/+admin)
[16:16] <kiko> cprov, is he a buildd admin?
[16:17] <kiko> cprov, I suggest you start documenting these things somewhere
[16:17] <cprov> kiko: uhm, let me check
[16:17] <cprov> kiko: suggestion accepted.
[16:18] <lamont> kiko: click on the name of the builder, click on 'administer buildd'
[16:19] <lamont> cprov: "Trusted  (Required)"  That should change to reflect the true meaning in the PPA-world.
[16:19] <kiko> yeah, known bug
[16:19]  * cprov nods
[16:20] <lamont> I figured it was... it's just one of those things that anyone who goes to +admin needs to know before they update a builder... I was fortunate enough to have cprov shoulder-surfing the first time I went tehre.
[16:20] <lamont> for a ppa buildd, taht is
[16:21] <cprov> kiko: btw, julian is a lp-buildd-admin via https://edge.launchpad.net/~soyuz-team membership
[18:18] <Spads> bigjools: hey, could you queue a package on dogfood to see if amd64 builds okay?
[18:19] <bigjools> Spads: is the amd64 dogfood builder there?  last time I looked the box had been nicked :)
[18:20] <Spads> bigjools: yes, I nicked it
[18:20] <bigjools> you put it back?
[18:20] <Spads> temporarily
[18:20] <kiko> like magic
[18:20] <Spads> I need to test it
[18:20] <bigjools> ok, I'll fire off some builds, hang on
[18:20]  * Spads nods
[18:20] <Spads> you won't be able to reset it
[18:21] <Spads> but it should be listening for builds
[18:21] <bigjools> ok
[18:21] <bigjools> crap
[18:21] <bigjools> missing chroots
[18:22] <bigjools> Sp
[18:23] <Spads> oh?
[18:24] <Spads> bigjools: the builder is?
[18:24] <bigjools> no, dogfood
[18:29] <bigjools> Spads: ok selenium just got a build
[18:30] <Spads> looking good so far...
[18:31] <Spads> hooray, it has log output now
[18:41] <ubotu> New bug: #177717 in launchpad "+editemails needs to work when there is no preferred email" [Undecided,New] https://launchpad.net/bugs/177717
[18:43] <kiko> bigjools, Spads: I can smell the dog food reheating 
[18:43] <Spads> haha
[18:44] <Spads> well, this is not even close to being in the state it once was
[18:44] <Spads> but the builder seems to be doing something!
[18:48] <bdmurray> kiko: hey there
[18:49] <kiko> bdmurray! my god that's a ong time
[18:50] <bdmurray> what?
[18:52] <kiko> since I've spoken to you
[18:52] <bdmurray> ah, right
[18:52] <bdmurray> I posted this question to the launchpad users mailing list a bit ago
[18:53] <bdmurray> https://lists.ubuntu.com/archives/launchpad-users/2007-August/001837.html
[18:53] <bdmurray> and I'm trying setup the upstream relationship between "linux" and the linux kernel but I forget what I did in August
[18:54] <bdmurray> So I'm a bit stuck it seems
[18:55] <ubotu> New bug: #177721 in launchpad "Test suite doesn't clean up it's own tmp files" [Undecided,New] https://launchpad.net/bugs/177721
[19:05] <ubotu> New bug: #177724 in launchpad "File upload form should give an error message before you upload a file bigger than 60MB" [Undecided,New] https://launchpad.net/bugs/177724
[19:07] <kiko> bdmurray, hmmm
[21:11] <ubotu> New bug: #177755 in launchpad "OOPS resetting password using the open id workflow" [High,New] https://launchpad.net/bugs/177755
[22:26] <bdmurray> Does anybody know where this bug expiry report is?
[23:57] <cr3_> I interrupted a bzr push onto launchpad because my network connection went down and the progress was stalled. now, it seems I have a dead branch in my code section
[23:58] <cr3_> when I try to republish, I get: bzr: ERROR: Can't rename /srv/sm-ng/push-branches/00/00/1e/db/.bzr/repository/lock/pending.298gv5cps463cc3u2ko0.tmp to /srv/sm-ng/push-branches/00/00/1e/db/.bzr/repository/lock/held: /srv/sm-ng/push-branches/00/00/1e/db/.bzr/repository/lock/held already exists