[01:31] <ubotu> New bug: #219752 in malone "Bug subscriber listed twice" [Undecided,New] https://launchpad.net/bugs/219752
[01:55] <jkakar> FYI, I got an OOPS about one minute ago with 'None' as the ID when accessing https://bugs.launchpad.net/bugs/215903.
[01:55] <ubotu> Launchpad bug 215903 in bzr "'bzr pull' should report number of new revisions retrieved" [Wishlist,Confirmed]  - Assigned to Martin Albisetti (beuno)
[01:55] <jkakar> I hit reload and my browser is still spinning.
[01:55] <jkakar> Loaded.
[02:19] <Hobbsee> barry-away: thanks for the replies
[02:22] <Fujitsu> Hmmm, LP is seriously sucking ATM.
[02:22] <Fujitsu> Some of the app servers aren't responded, by the look of things.
[02:22] <Fujitsu> *responding
[02:22] <Fujitsu> And now it's oopsing.
[02:22] <Fujitsu> jkakar: Aha, I just got that too.
[02:23] <jkakar> Fujitsu: Something must be going on. :(
[02:23] <Hobbsee> Fujitsu: power still out?
[02:24] <Hobbsee> or otehr effects from that still?
[02:24] <Fujitsu> Could be, but I thought that was meant to be resolved 10 hours ago.
[02:26] <Hobbsee> yeah, launchpad is borken.
[02:26] <Hobbsee> Oops!
[02:26] <Hobbsee> Sorry, something just went wrong in Launchpad. We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.
[02:26] <Hobbsee> If this is blocking your work, let us know on the launchpad-users mailing list (requires subscription). Include the error ID None in your message.
[02:26] <Hobbsee> just loading https://launchpad.net/ubuntu/hardy/+queue?batch=500
[02:26] <Fujitsu> Sounds very recorded indeed.
[02:27] <Fujitsu> Refresh a couple of times, and it normally works.
[02:27] <Hobbsee> oh, so the edge conversion isn't working
[02:27] <Fujitsu> As long as you catch an app server that isn't either down or None-OOPSing.
[02:27] <Fujitsu> Dare I try to upload something...
[02:27] <artfwo> Hobbsee: the same URL just opened for me with edge redirection
[02:27] <Hobbsee> artfwo: yeah
[02:27] <Hobbsee> artfwo: after you put in the edge, it seems OK
[02:28] <Hobbsee> Fujitsu: timeout.
[02:28] <Fujitsu> Lovely.
[02:28] <Hobbsee> ooh, a number!
[02:28] <Fujitsu> :O
[02:29] <Hobbsee> hmm.  i think i might have just black holed them.
[02:30] <Fujitsu> No.
[02:30] <Fujitsu> It worked.
[02:30] <Fujitsu> I have accepted mails.
[02:30] <Fujitsu> Maybe it just timed out on the listing afterwards.
[02:30] <Hobbsee> the listing doesn't show it anywhere
[02:30] <Fujitsu> Nice from address, though.
[02:30] <Hobbsee> i got a timeout for accepting, but they're nto still showing in unapproved, which they usually do
[02:31] <Fujitsu> `Default Sender'
[02:31] <Hobbsee> heh, what is it?
[02:31] <Fujitsu> Hahahahaha.
[02:31] <Fujitsu> dsilvers
[02:31] <Fujitsu> Nice and old.
[02:31] <Fujitsu> dsilvers@staging.ubuntu.com
[02:33] <Hobbsee> hmm.  the source is listed as pending still.
[02:33] <Fujitsu> That's normal.
[02:33] <Hobbsee> Fujitsu: you migth want to check that after the next publisher cycle
[02:33] <Fujitsu> It all worked, apart from the bogus sender.
[02:33] <Fujitsu> It will be pending for another 32 or so minutes.
[02:34] <Fujitsu> It has even built in most places.
[02:34] <Hobbsee> oh goody.
[02:34] <Hobbsee> then it didn't break
[02:35] <Fujitsu> I wonder if your acceptances normally generate that sender, or if it's just because LP is all screwed up at the moment.
[02:35] <Fujitsu> Can you please kick through pdns-recursor too?
[02:35] <Fujitsu> More NoneType OOPSes. Yay.
[02:36] <Hobbsee> Fujitsu: trying
[02:36] <Hobbsee> Fujitsu: there you go.  accepted without a timeout.
[02:37] <Fujitsu> Danke.
[02:37] <Hobbsee> you're welcome
[02:37] <Fujitsu> Isn't it nice of Kinnison to be processing the queue years after his departure.
[02:38] <Hobbsee> OOPS-841EA2
[02:48] <awmcclain> I'm getting an error when building a package in my ppa. Is something up with the build servers? http://dpaste.com/45880/
[02:48] <Fujitsu> Oh dear.
[02:49] <Fujitsu> LP is generally broken.
[02:49] <Fujitsu> But that's an unrelated issue.
[02:49] <Fujitsu> Retry it after the next XX:20, XX:40, or XX:00.
[02:50] <Fujitsu> Bug #196782
[02:50] <ubotu> Launchpad bug 196782 in soyuz "First build in a new PPA fails" [Low,Triaged] https://launchpad.net/bugs/196782
[02:51] <ubotu> New bug: #219767 in soyuz "Kinnison still dutifully processing the queue years after his departure" [Undecided,New] https://launchpad.net/bugs/219767
[02:55] <Fujitsu> Can anybody get through to production at all at the moment?
[02:57] <artfwo> looks ok
[02:58] <artfwo> but some icons don't show
[02:59] <Fujitsu> Do we want to find a Canonical person to poke a sysadmin?
[03:00] <artfwo> pages generally load with occasional None-oopses fixed by reloading :)
[03:03] <Fujitsu> It's somewhat better for me.
[03:04] <Fujitsu> Edge redirections now work more than 10% of the time.
[03:04] <awmcclain> Fujitsu: You're correct, it "seems" like it built. However, I've added my PPA to my sources.list, sudo apt-get update, and now sudo apt-get install <package> gives me Package <package> is not available, but is referred to by another package.
[03:06] <Fujitsu> awmcclain: Did it finish building within the last 6 minutes?
[03:07] <awmcclain> Fujitsu: One finished 2 hours ago, one 5 minutes, one 6 minutes. I can't install any of them.
[03:07] <Fujitsu> Give it 15 minutes, and try again.
[03:07] <Fujitsu> New packages are only published every 20 minutes.
[03:08] <Fujitsu> So at least those last two won't be there yet.
[03:08] <awmcclain> Fujitsu: Ah. I see. So there's a chance I can see it on my page (https://launchpad.net/~awmcclain/+archive) but not access it from apt-get?
[03:08] <Fujitsu> Correct.
[03:08] <Fujitsu> The build should say ACCEPTED, rather than DONE.
[03:08] <Fujitsu> ... except I don't think PPAs actually show that.
[03:08]  * Fujitsu looks.
[03:09] <awmcclain> Fujitsu: Yes, yes it should. :)
[03:09] <Fujitsu> None of the builds have actually succeeded, you realise?
[03:10] <awmcclain> Next you'll tell me that there's no Santa!
[03:10] <awmcclain> Where can I check build status? Everything was so finnicky I didn't know what to believe.
[03:10] <Fujitsu> https://edge.launchpad.net/~awmcclain/+archive
[03:10] <Fujitsu> Note the big red X.
[03:10] <Fujitsu> Next to all of the archs.
[03:11] <Fujitsu> If you expand each of those packages, you'll see a more detailed status.
[03:11] <Fujitsu> Hovering over the icons (which is a shocking UI decision) will give you the status of each arch individually.
[03:11] <awmcclain> I swear, my page before i reloaded didn't have x's on it.
[03:11] <awmcclain> Ok.
[03:11] <awmcclain> I'll debug.
[03:11] <Fujitsu> Hm, did you kill gold with your lib-io-aio-perl?
[03:12] <awmcclain> <.<
[03:12] <Fujitsu> I'm glad it chrootwaited everywhere else.
[03:12] <awmcclain> I read the docs, I swear!
[03:14] <awmcclain> So... is there something I should do? Restart the build on libio-aio-perl?
[03:15] <Fujitsu> Please don't retry it just yet - work out why it killed gold.
[03:16]  * Hobbsee waits for the next timeout
[03:17] <Hobbsee> yup. dead as a doornail
[03:17] <Hobbsee> someone else will have to fix it first
[03:17] <Fujitsu> Hobbsee: What is? gold?
[03:18] <Hobbsee> Fujitsu: no, acccepting form the queue
[03:18] <Fujitsu> Ah.
[03:18]  * Hobbsee tried to accept a few more builds.  no dice
[03:18] <Hobbsee> Fujitsu: so pdns-* will need to wait
[03:18] <awmcclain> O.O
[03:19] <awmcclain> That wasn't me, was it? All I received was a chroot email
[03:19] <Fujitsu> Hobbsee: It was accepted more than 45 minutes ago.
[03:19] <Fujitsu> awmcclain: You killed gold, but not what Hobbsee's talking about.
[03:19] <awmcclain> Great. I'm a killer.
[03:19] <Hobbsee> Fujitsu: oh, so it did work
[03:19] <Hobbsee> Fujitsu: the others didn't - or at least, still show on the unapproved queue
[03:19] <Fujitsu> Great.
[03:20] <awmcclain> Here's the build log: http://dpaste.com/45884/
[03:20] <Fujitsu> awmcclain: That's a normal issue.
[03:20] <Fujitsu> Bug #196782, as I mentioned above.
[03:20] <ubotu> Launchpad bug 196782 in soyuz "First build in a new PPA fails" [Low,Triaged] https://launchpad.net/bugs/196782
[03:20] <awmcclain> Fujitsu: I then tried to "restart build" using the launchpad ppa
[03:20] <awmcclain> err
[03:20] <awmcclain> launchpad page
[03:20] <awmcclain> and
[03:21] <awmcclain> dead.
[03:21] <Fujitsu> Yeah, I suspect your package is buggy.
[03:21] <Fujitsu> At least it's not silly enough to run an interactive CPAN session.
[03:21] <awmcclain> Well, I've built and installed it on my local gutsy machine
[03:21] <awmcclain> Using apt
[03:21] <awmcclain> No problems.
[03:22] <Fujitsu> Have you built it in sbuild or pbuilder?
[03:22] <Fujitsu> Preferably both.
[03:22] <awmcclain> No, debuild.
[03:22] <Fujitsu> Ah. That doesn't count as building.
[03:22] <awmcclain> Hrm.
[03:22] <awmcclain> I wish someone would have told me that.
[03:24] <Hobbsee> ...i'm fairly sure that if you read the documentation on building packages, they did.
[03:28] <awmcclain> Well, since I already read and complied with the debian packaging policy; built, uploaded, and tested on my distribution using a local repository; and asked in #launchpad and #ubuntu-motu multiple times whether or not there were any caveats about converting a perl module built with dh-make-perl from debian to ubuntu, I figured I had done my due diligence.
[03:29] <awmcclain> Pbuilder or rebuildd is the package I want?
[03:29] <Fujitsu> Not rebuildd.
[03:29] <awmcclain> k
[03:29] <Fujitsu> pbuilder is easier, but sbuild is better.
[03:29] <Fujitsu> As sbuild is more like LP.
[03:29] <awmcclain> Ah.
[03:31] <awmcclain> For these broken builds, is it better to delete or just dput --force?
[03:33] <Fujitsu> Neither.
[03:33] <Fujitsu> Upload a new version.
[03:33] <awmcclain> ah, change the ppa number?
[03:33] <Fujitsu> Every time you delete a version and replace it, a whole flock of kittens die.
[03:34] <awmcclain> Well, I don't like that.
[03:34] <artfwo> make sure you build the source package with -sd
[03:34] <awmcclain> not -S?
[03:34] <artfwo> -S -sd
[03:34] <awmcclain> ok, will do
[03:34] <Fujitsu> -sd is default, isn't it?
[03:34] <awmcclain> That's what I thought
[03:34] <Fujitsu> At least it was when I uploaded something 10 minutes ago.
[03:35] <awmcclain> No, si is default
[03:35] <awmcclain> Wait, so I _shouldn't_ upload original source? Even if it's the first revision?
[03:35] <awmcclain> I thought that went against deb policy
[03:36] <Hobbsee> poor kittens.
[03:36] <Hobbsee> Fujitsu: no, -sd is *not* the deafult.
[03:36] <Hobbsee> awmcclain: if it's the first revision, you need to.  if not, you don't, because the same file is already in the archive.
[03:37] <Fujitsu> Hobbsee: My *_source.changes disagree.
[03:37] <awmcclain> Hobbsee: Understood. And if the first version is a horrible malformed orphan that killed gold?
[03:37] <Hobbsee> oh, interesting.
[03:37] <Hobbsee> i'm completely on crack there
[03:37] <Hobbsee>        -si    By  default,  or  if  specified,  the  original  source  will be
[03:37] <Hobbsee>               included if the version number ends in -0 or  -1,  i.e.  if  the
[03:37] <Hobbsee>               Debian revision part of the version number is 0 or 1.
[03:37] <Fujitsu> Ahh.
[03:37] <Fujitsu> So the same effect as -sd, but conditional.
[03:37] <Fujitsu> That makes more sense.
[03:37] <Hobbsee> yeah
[03:38]  * Hobbsee has written scripts to avoid having to specify the switches, so....
[03:38] <Fujitsu> But -sd is irrelevant in Ubuntu, as we never have a version number matching either of those.
[03:38] <awmcclain> Just to make sure I don't break anything again... I create the source package, then test the build using sbuild?
[03:40] <Fujitsu> Yes please. But sbuild might not be practical if you're not already using LVM.
[03:40] <Fujitsu> In that case, use pbuilder and hope for the best.
[03:40] <Hobbsee> Fujitsu: i wonder if we patch that - or should.
[03:40] <Hobbsee> Fujitsu: would be nice to patch it
[03:41] <awmcclain> Mm, no, not using LVM
[03:42] <artfwo> as I've never used pbuilder or sbuild, would someone clear for me: does it download packages from the net every time or does it pick them from some cache?
[03:43] <Fujitsu> pbuilder caches them.
[03:43] <Fujitsu> sbuild doesn't by default.
[03:43] <awmcclain> Hrm... strange. I've installed pbuilder but I don't have 'pbuilder' in my path
[03:43] <artfwo> aha, thanks :)
[03:46] <Hobbsee> awmcclain: don't you have to run bash again to do so?
[03:46] <Hobbsee> or open a new terminal?
[03:46] <awmcclain> i did, no luck
[03:46] <Fujitsu> Hobbsee: It shouldn't be updating PATH, so that shouldn't be necessary...
[03:46] <Fujitsu> I can't see why it wouldn't be in the default PATH, though.
[03:47] <artfwo> dpkg -L pbuilder?
[03:47] <awmcclain> There we go, had to terminate the connection.
[03:47] <awmcclain> Strange. Normally never have to do that.
[03:48] <awmcclain> There we go.
[03:48] <awmcclain> You have to admit, packaging, when it works, is such magic.
[03:48] <Hobbsee> hehe
[03:49] <awmcclain> Really. It's like you're living in the future. I half-expect a flying car to jet past my window.
[03:52] <awmcclain> Ok, I see how this all works now. My guess is that it's a dependency issue in the chroot environment.
[03:54] <Hobbsee> very likely
[03:55] <awmcclain> Ah ha! Ok. This is interesting: The default perl version dependency generated by dh-make-perl is perl (>= 5.8.8-7ubuntu3.1), but pbuilder is trying to satisfy with 5.8.8-7ubuntu3
[03:56] <Fujitsu> You're using a Gutsy pbuilder, then/
[03:56] <awmcclain> Silly that the versions wouldn't match.
[03:56] <awmcclain> Right.
[03:56] <awmcclain> Shouldn't I?
[03:56] <Fujitsu> That sounds like it wants a Hardy perl.
[04:00] <awmcclain> I'm running gutsy, I downloaded dh-make-perl for gutsy. :-\
[04:00] <awmcclain> Or rather, apt-got it. :)
[04:07] <awmcclain> Ah. I have perl (5.8.8-7ubuntu3.1) gutsy-security; urgency=low  installed on my machine.
[04:07] <awmcclain> So, my version of perl was updated in a security update, but the version that pbuilder uses isn't. Is that correct?
[04:08] <awmcclain> Fujitsu: Safe to try again on launchpad to verify that's what went wrong?
[04:08] <Fujitsu> That wasn't what went wrong.
[04:08] <Fujitsu> It wasn't a dependency issue.
[04:09] <awmcclain> Well, I'm baffled if it could be something else. It's not like the installation is doing anything special.
[04:10] <Fujitsu> It's running tests and failing after a forking test. That sounds special.
[04:10] <Fujitsu> This is the slowest I've seen LP in a very long time :(
[04:10] <Hobbsee> just as long as it doesn't require cpanplus...
[04:11] <Fujitsu> Heh.
[04:20] <awmcclain> Got it. Stalls on tests, since (i think) it's trying to find folders that don't exist (since its chrooting)
[04:27] <Fujitsu> Come on LP, I can't accept three minute latency for comment submission.
[04:28] <maco> the internet said to come here
[04:29] <Fujitsu> Yes.
[04:29] <maco> saving new irc nicks doesnt work....spin spin spin...then boom
[04:29] <Fujitsu> It's horridly broken.
[04:29] <Fujitsu> And there's nobody here.
[04:29] <Fujitsu> Refresh a few times.
[04:29] <Fujitsu> you might get it to work eventually.
[04:29] <maco> funfun
[04:29] <emgent> morning people
[04:30] <maco> 31 more minutes til morning here
[04:30] <Fujitsu> At least we're not getting OOPSes with NoneType IDs any more.
[04:30] <Fujitsu> Hey emgent.
[04:30] <emgent> Fujitsu: thanks for sympa :)
[04:31] <Fujitsu> emgent: You're welcome.
[04:35]  * Hobbsee ponders trying to accept more
[04:35] <Fujitsu> emgent's audit should be in unapproved by now.
[04:36] <emgent> oh ok
[04:36] <emgent> :)
[04:37] <Fujitsu> The Hardy CVE list is looking nice and yellow. It's rather good to see.
[04:38]  * emgent should fix wordpress <= gutsy
[04:39] <Fujitsu> emgent: What about CVE-2008-0191 in Hardy?
[04:39] <ubotu> WordPress 2.2.x and 2.3.x allows remote attackers to obtain sensitive information via an invalid p parameter in an rss2 action to the default URI, which reveals the full path and the SQL database structure. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0191)
[04:39] <Fujitsu> Ah, it's that one.
[04:39] <Fujitsu> So not important.
[04:40] <emgent> I`m working to CVE-2007-6013
[04:40] <ubotu> Wordpress 1.5 through 2.3.1 uses cookie values based on the MD5 hash of a password MD5 hash, which allows attackers to bypass authentication by obtaining the MD5 hash from the user database, then generating the authentication cookie from that hash. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6013)
[04:40] <Fujitsu> So I saw.
[04:40] <Fujitsu> Why does LP break on days I have lots of time to deal with security bugs?
[04:40] <Fujitsu> Just before release?
[04:40] <Hobbsee> because it likes breaking just before release.  duh
[04:41] <emgent> lp is very slow now ARGHù
[04:41] <Hobbsee> Fujitsu: which bits do you want accepted?
[04:41] <Fujitsu> emgent: It's very, very slow, and often finally OOPSes or gives pound-like failures after 5 minutes.
[04:42] <Fujitsu> Hobbsee: Just audit ATM. LP is holding up my other fixes :(
[04:42] <emgent> I will complete my work later
[04:44] <Hobbsee> come on edge.  don't die.
[04:45] <Fujitsu> It's a lot worse than it was earlier.
[04:51] <emgent> Fujitsu: http://cansecwest.com/post/2008-03-20.21:33:00.CanSecWest_PWN2OWN_2008
[04:51] <emgent> have you read? :)
[04:52] <emgent> only ubuntu not owned in this hacking contest
[04:53] <Fujitsu> Yeah, I saw that.
[05:22] <crimsun> Hobbsee: please accept trang and phatch, too (both approved by MOTU-R)
[05:23] <Hobbsee> crimsun: ELAUNCHPADTIMEOUTS.
[05:27] <Fujitsu> Another trang?
[05:28] <Fujitsu> I thought I saw it on -changes earlier.
[05:44] <agmishra> HI i am not able to access https://bugs.launchpad.net/ubuntu/+source/p7zip/+bug/132884 for almost past 1/2 hr
[05:45] <agmishra> Is launchpad down?
[05:45] <Fujitsu> agmishra: Try bugs.edge.launchpad.net. Launchpad is having big issues, and all the sysadmins are asleep.
[05:45] <agmishra> Thanks
[06:07] <bullgard4> Accessing Launchpad is extremely slow at this moment.
[06:07] <Hobbsee> yes, it is
[06:08] <bullgard4> Launchpad asked me to report this fact here.
[06:08] <Hobbsee> bullgard4: no one's around who can change that page :(
[06:08] <Hobbsee> bullgard4: topic updated though, thanks
[06:09] <Fujitsu> I was wondering how I could best phrase somehting like that for the topic.
[06:09] <Fujitsu> That's not a bad job.
[06:09] <Fujitsu> Hopefully we'll be able to poke some Canonical person within a few hours.
[06:09] <bullgard4> Hobbsee: Have a nice sunday! (I am still enjoying Ubuntu.)
[06:10] <Hobbsee> bullgard4: will do
[07:27] <Odd_Bloke> s/monday/Monday/ for those wondering.
[10:25] <ubotu> New bug: #219828 in soyuz "Copies of sources including only architecture independent binaries result in a failed-to-upload build" [High,In progress] https://launchpad.net/bugs/219828
[10:30] <ubotu> New bug: #219829 in soyuz "Show SourcePackageRelease original information in PPA pages" [Medium,Confirmed] https://launchpad.net/bugs/219829
[12:23] <andrea-bs> hi there! there's a problem with bugs atom feeds: "HTTP error code 0: Remote host did not finish sending data"
[12:24] <afflux> I guess that's related to general launchpad-slowness today
[15:01] <mpt> Gooooooooooooooood afternoon Launchpadders!
[15:02] <Hobbsee> good evening mpt!
[15:15] <joh> I recall there being an SVN to BZR howto on launchpad - anyone know where to find it?
[15:17] <Hobbsee> mpt: any idea how many hours until LP is up in a satisfactory fashion?
[15:18] <mpt> Hobbsee, I didn't know it wasn't
[15:18] <mpt> What's wrong?
[15:18] <Hobbsee> mpt: use it for something.  You'll see.
[15:18] <mpt> huhhhhh
[15:18] <Hobbsee> mpt: it's slow, constant timeouts, can't accept packages at all
[15:19] <Hobbsee> sometimes they're getting none-type oopses
[15:19] <Hobbsee> various people have beem coming in here all day from it
[15:19] <Hobbsee> it's been going on since the power outage.
[15:19] <Hobbsee> mpt: didn't you see the /topic?
[15:19] <mpt> I didn't
[15:19] <mpt> one moment
[15:20] <mpt> How long has it been like this?
[15:20] <mpt> Eight hours??
[15:20]  * Hobbsee thinks
[15:21] <Hobbsee> when did the power actually come back on?
[15:21] <Hobbsee> it would be at least that, i'm fairly sure
[15:21] <mpt> Power?
[15:21] <mpt> Hobbsee, please tell me all you know
[15:21] <mpt> (about this, I mean:-)
[15:22] <Hobbsee> mpt: there was a mention of a power outage in the /topic of #ubuntu-devel, hours ago
[15:22] <Hobbsee> [Sat Apr 19 2008] [21:55:02] Topic The channel topic is "Reduced buildd service till 3pm UTC due to power outage || <rest of #ubuntu-devel topic>
[15:23]  * Hobbsee looks for when someone first mentioend it was slow
[15:24] <Hobbsee> mpt: people were commenting 13 hours ago
[15:24] <Hobbsee> mpt: looks like that was the first (fujitsu was talking about it)
[15:24] <mpt> Ok, so what parts of it are working?
[15:25] <Hobbsee> looks like bugs are.
[15:25] <Hobbsee> Fujitsu's thought was that a whole lot of the app servers were down
[15:25] <Hobbsee> i could get a few packages accepted before i started getting mass timeouts
[15:25] <Hobbsee> i think elmo redid a whole bunch of the builds that died
[15:26] <Hobbsee> mpt: tbh, launchpad has been so painfully slow (and timing out consistently) today that no one's really tried to do work with it for an extended period of time, just due to the data loss.
[15:26] <Hobbsee> so i'm not sure of the extent
[15:26] <Hobbsee> (and yes, it's 4 days before the ubuntu release, and no, i'm sure people won't be happy about it)
[15:27] <mpt> ok, I've called SteveA, he's calling elmo now
[15:27] <mpt> I can't load bugs.launchpad.net either
[15:27] <Hobbsee> mpt: oh yes.  producion is totally down, and you have to use edge.
[15:27] <mpt> oh, edge is up?
[15:27] <Hobbsee> knew i forgot something important.
[15:27] <Hobbsee> yes
[15:27] <Hobbsee> well, fsvo up.
[15:27] <Hobbsee> it loads some LP pages without timeouts, at least.
[15:28] <Hobbsee> mpt: it would be good if some of you actually published contact numbers.  if none of the canonical folks are around, which they often aren't on the weekend, this situation isn't uncommon.
[15:28] <mpt> yeah, I'm thinking about that
[15:28] <Hobbsee> last i knew, IS contact numbers were given out to canonical people only.
[15:28] <mpt> but that's something to sort out tomorrow
[15:28] <mpt> priority #1 now is to get it back up again
[15:28] <Hobbsee> come to think of it, i could have called SteveA myself.
[15:29] <Hobbsee> didn't really want to wake him up and having yelling at me, though.
[15:29] <mpt> I'm not getting any response from edge.launchpad.net either
[15:29] <Hobbsee> hmm. it was working.
[15:29] <Hobbsee> looks dead now
[15:29] <Hobbsee> no, it's here.  slow, though
[15:29] <Hobbsee> mpt: you're looking for at least a minute each page load atm.  so, patience...
[15:31] <Nafallo> what's up?
[15:31] <Nafallo> LP borked?
[15:31] <Hobbsee> yes
[15:31] <Hobbsee> try using it
[15:32] <Nafallo> ah. IS is on it already :-)
[15:32] <Hobbsee> mpt: good thing you happen to turn up on weekends....
[15:32] <Hobbsee> Nafallo: you clearly havent tried to use LP for the last 13 hours...
[15:32] <Nafallo> Hobbsee: no. I've been a bit sleepy ;-)
[15:32] <Hobbsee> lucky you
[15:33] <mpt> Hobbsee, did you try contacting other LP developers here in #launchpad?
[15:33] <Hobbsee> mpt: i didn't try pinging them individually, no.
[15:33] <mpt> (or heck, even anyone from Canonical)
[15:33] <Hobbsee> thoguth they weren't here, if they weren't talking, or looking at their screens.
[15:34] <Hobbsee> mpt: i've tried that before.  it didn't work last time.
[15:34] <Hobbsee> then again, it wasn't so close to release last time.
[15:35]  * Hobbsee is surprised you don't have an alerts system for mass oopses, or something.
[15:35] <Hobbsee> mind you, that would probably be down too
[15:36] <mpt> I doubt the proximity to release would affect anyone's responsiveness to this problem
[15:36] <mpt> ok, edge is working for me now
[15:36] <Hobbsee> mpt: last time this happened (christmas buildds breaking), it was discussed that they'd write up a procedure as to how they wanted stuff escalated.  That never happened, and I never heard anything more, so I assumed that they didn't care/want to be notified
[15:37] <Hobbsee> Or if they did, I never saw info on it
[15:37] <mpt> http://news.launchpad.net/maintenance
[15:37] <Hobbsee> presumed it was for a subset of people, and i wasn't one.
[15:38] <Hobbsee> mpt: the first item there was done.  repeatedly.
[15:38] <Hobbsee> mpt: no help if no one's watching
[15:42] <mpt> ok, everything's working for me now
[15:42] <leoquant> there is no planned maintenance, but launchpad seems down now?
[15:42] <mpt> Is there anything still not working for you (that was working before), Hobbsee?
[15:42] <mpt> leoquant, what were you trying to do in particular?
[15:43] <leoquant> bugs/launchpad account etc
[15:43]  * Hobbsee smacks LP bad UI design.
[15:43] <Hobbsee> i'm hitting the button below the menu option, not across from it, so it's not updating, it's actually doing nothing.
[15:44] <Hobbsee> mpt: i still can't acccept from the queue.  (Error ID: OOPS-841EA43) 
[15:45] <Hobbsee> mpt: i filed a bug last week, couldn't reproduce it a few days later, and it's back now.  It's a load problem
[15:45] <mpt> Below what menu option?
[15:45] <Hobbsee> the queue.  it's getting redesigned, and the dogfood stuff looks saner.
[15:45] <Hobbsee> (but thanks)
[15:48] <leoquant> weird ...it is very, very slow. but its there :)
[15:51] <leoquant> waiting for launchpadllibrarian...
[15:51] <Hobbsee> morning elmo!
[15:52] <mpt> thanks elmargol 
[15:52] <mpt> elmo, even
[15:53] <Hobbsee> (Error ID: OOPS-841EA48) 
[15:53] <Hobbsee> sigh, more timeouts.  i assume slangasek will have to deal with the queue on monday.
[15:54] <mpt> Your first oops is still too new for me to see
[15:55] <Hobbsee> mpt: can you add it to your meeting agenda to actually get an emergency plan written and published?  This isn't the first time, and the "we'll deal with it later" approach didn't seem to work too well last time.
[15:56] <Hobbsee> mpt: can't imagine you guys want to be called up for random things, by any community member, if there's no protocol of what you do and don't want to know about.
[15:56] <Hobbsee> especially while you're asleep
[15:58] <mpt> Hobbsee, done.
[15:58] <Hobbsee> mpt: thankyou.
[16:36] <mpt> a queue timeout, eh
[16:37] <Hobbsee> yes
[16:40] <mpt> Hobbsee, anyway, until we have a published plan of that type, I'll elaborate on the one described on <http://news.launchpad.net/maintenance>: Refer to Launchpad developers by IRC nickname, and if that fails, any Canonical person
[16:40] <Hobbsee> mpt: right.
[17:12] <nand> The QA webserver (ISO testing tracker && brainstorm) was down until recently. I wonder if this was related...
[21:12] <joh> Hi, how do I import my svn repository into bzr on launchpad?
[21:22] <Zelut> I have followed the PPA instructions here - https://help.launchpad.net/PPAQuickStart
[21:22] <Zelut> my submission was accepted but there is no .deb available.  Did I miss a step?
[21:33] <joh> Eh wth, how did launchpad discover 2 of my old email addresses? :S
[21:35] <stdin> Zelut: how long ago did you upload?
[21:47] <mdke> any lp-bzr gurus around? I'd like to upgrade some branches on LP but am having some issues
[21:48] <beuno> mdke, what seems to be the problem?
[21:49] <mdke> beuno: http://paste.ubuntu.com/7616/
[21:50] <beuno> mdke, you should use sftp for upgrades
[21:50] <beuno> give that a try
[21:50] <mdke> bzr info on the same url gives "format: unnamed"
[21:50] <mdke> beuno: ah, it doesn't work at all with bzr+ssh?
[21:50] <beuno> mdke, IIRC, upgrading doesn't work with bzr+ssh on LP, np
[21:50] <beuno> *no
[21:51] <mdke> is there anything else besides sftp? the server doesn't have paramiko installed
[21:51] <beuno> I don't think you can write to LP anyway else
[21:53] <mdke> beuno: ok, thanks anyway
[21:54] <beuno> mdke, np  :)
[21:54] <beuno> of course
[21:54] <beuno> another alternative might be
[21:54] <beuno> upgrade locally
[21:54] <beuno> remove the current one
[21:55] <beuno> and upload the upgraded one
[21:55] <beuno> to some extent, that might be faster
[21:55] <beuno> (upgrading in LP makes several round trips)
[21:55] <mdke> beuno: I might do that. is it possible to delete branches in launchpad?
[21:56] <spacepluk> hi, can I have packages in PPA which depend on universe, multiverse, etc.?
[21:56] <beuno> mdke, yup, there's a "Delete Branch" option on there
[21:56] <mdke> beuno: hmm. i can't use it - it would delete subscriptions and bug links
[21:57] <mdke> beuno: I'll try and get paramiko installed on the server and do it with sftp
[21:57] <spacepluk> I've just uploaded the source package and I'm having a "Chroot problem"
[21:57] <beuno> mdke, alright, good luck with that then  :)
[22:15] <awmcclain> Hey all... is there an easy way to specify a list of custom repositories for pbuilder? I've tried specifying lines in my source.list by setting the OTHERMIRRORS variable in my rc file and by passing them in via --othermirrors. Am I missing something?
[22:17] <awmcclain> Or: is there an ubuntu package developer IRC? Similar to debian-mentors?
[22:24] <spacepluk> awmcclain: have you tried sudo pbuilder login, and then edit the source.list inside?
[22:24] <awmcclain> spacepluk: Oh! No! Will that take effect for all default builds?
[22:24] <spacepluk> awmcclain: I think so
[22:24] <awmcclain> spacepluk: I'll try that. Thank you!
[22:25] <spacepluk> awmcclain: np :)
[22:32] <awmcclain> spacepluk: Oh, actually, I just found a good way to do it: https://wiki.ubuntu.com/PbuilderHowto, where you can copy over your existing apt directory to pbuilder
[22:33] <spacepluk> awmcclain: I was about to point you to that howto :P
[22:34] <awmcclain> Hrm, though, it's not working with my .pbuilderrc. Probably because I'm running it as sudo?
[22:34] <awmcclain> s/as/with
[22:41] <Zelut> stdin: probably a week ago..
[22:47] <Zelut> stdin: ...and that's odd.  I just uploaded another .changes and this one generated a .deb.
[22:47] <Zelut> stdin: fluke I guess.