[00:01] <Darxus> $ bzr push lp:~darxus/+junk/spamassassin-unpackaging
[00:01] <Darxus> ssh: connect to host bazaar.launchpad.net port 22: No route to host
[00:01] <Darxus> Woo.
[00:01] <mwhudson> Darxus: yeah, the sysadmins are investigating
[00:17] <chadadavis> Are there issues with Launchpad at the moment? I'm trying to file a bug, I keep getting an Oops error from Launchpad.
[00:17] <poolie> chadadavis: yes
[00:17] <poolie> apparently some network hardware has failed; we're working on it
[00:17] <chadadavis> poolie, Thanks, I'll write them down and file them in the morning ...
[00:21] <lifeless> chadadavis: if you're attaching a file to the bug that will happen
[00:22] <chadadavis> lifeless, thanks for the tip. It worked fine without the attachments. Just wanted the bug number. I'll attach them later.
[00:34] <ripps> Is something wrong with bazaar.launchpad.net? I can't seem to connect. Ping shows this: From eth0.peumo.canonical.com (91.189.88.10) icmp_seq=8 Destination Host Unreachable
[00:35] <lifeless> yes
[00:35] <ScottK> ripps: Look at the start of /topic.
[00:35] <lifeless> we have a switch which has gone awol and isn't recoverable remotely; engineers are going onsite as we speak
[01:07] <lifeless> (*) builds will be slightly delayed as the final services are restored
[01:08] <lifeless> and there may be a cluster of rejections
[01:25] <Darxus> So did the switch just need power cycling or something?  Or did it get replaced?
[01:34] <lifeless> AIUI we've moved the wires to a different switch module and the failed component is being investigated
[01:34] <lifeless> Darxus: we have remote power cycling facilities etc, so I don't think it was that simple :)
[01:53] <ScottK> lifeless: Looks like the network issue got soyuz and the keyserver on bad terms again.
[01:54] <lifeless> spm: ^
[01:54] <spm> ugh
[01:58] <wgrant> ScottK: cocoplum again?
[01:58] <ScottK> wgrant: Yes.
[01:58] <ScottK>   Uploading plasma-mobile_0.0~svn20110101-0ubuntu2_source.changes: 1k/2k550 Changes file must be signed with a valid GPG signature: Verification failed 3 times: ["(7, 9, u'No public key')", "(7, 9, u'No public key')", "(7, 9, u'No public key')"] : Permission denied.
[01:58] <wgrant> Thanks.
[01:59] <ScottK> Would you also please check if that actually got accepted?
[02:01] <ScottK> Fun.  (Error ID: OOPS-1930H76) on https://launchpad.net/builders.
[02:01] <wgrant> Hmm.
[02:01]  * wgrant pokes cocoplum.
[02:01] <wgrant> Hello cocoplum... are you there?
[02:01] <zachtib> is the ppa service having trouble? it's rejecting my gpg key, which it liked yesterday
[02:03] <wgrant> zachtib: We had a networking hardware failure earlier... possibly still fallout from that. Investigating.
[02:11] <zachtib> wgrant, huh... well, I just got a package accepted email for the lucid and natty packages... nothing on the maverick one, though
[02:14] <spiv> Hmm, I'm having trouble sending crash reports.
[02:16] <ScottK> The /builders page is working again.
[02:17] <ScottK> wgrant: Once you have a spare moment from the current 'fun', I'd appreciate it if you would check and see if the kdebase and kdetoys builds on powerpc are really stuck (as it appears in the web U/I)?
[02:18] <zachtib> oh, duh, the maverick package never uploaded
[02:18] <zachtib> ok, it seems to be building, though dput still throws an error anyways
[02:28] <wgrant> zachtib: Right, the error is mostly a warning.
[02:29] <wgrant> ScottK: buildd-manager is still a little bit upset from the earlier networking fun, I think.
[02:29] <wgrant> Something else seems to be wrong now, since I can't talk to cocoplum from some internal hosts :/
[02:29] <ScottK> OK.
[02:58] <MTecknology> a $40 bottle of tequila just broke on my floor........
[02:58] <MTecknology> I grabbed it, then I was holding  on my way to put it in the fridge, and the whole bottle separated from the top (that I was holding)
[02:58] <MTecknology> a tad bit pissed off
[02:58] <MTecknology> grrrr
[03:09] <poolie> apport bug filing seems really slow at the moment; this might just be still fallout
[03:09] <poolie> iow it's stuck on "please wait wihle bug data is processed"
[03:11] <wgrant> poolie: Just got an alert about that 5 minutes ago.
[03:11] <wgrant> Looking.
[03:57] <ripps> dput has suddenly stopped working for me. It's giving gpg verification errors suddenly.   Uploading mplayer2-build_2.0+git20110413.0bec988-0ubuntu1~ripps1_source.changes: 2k/3k550 Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['General error', 'General error', 'General error'] : Permission denied.
[03:57] <ScottK> ripps: Known breakage from the recent outage.  It probably was uploaded anyway.
[03:57] <wgrant> ripps: We're still resolving widespread network fallout from the hardware failure earlier... it *may* still process okay.
[03:58] <wgrant> But the buildds are still out, so it won't build for a while.
[04:38] <poolie> wgrant: i filed bug 760393 for the problem i hit before with apport getting stuck, just so you know
[04:39] <wgrant> poolie: It's not really a bug, but yeah.
[04:40] <poolie> just an operational thing
[04:40] <poolie> i'm happy if it's just rejected or whatever, i just thought i'd give it a handle
[04:41] <wgrant> Sure.
[07:18] <kl_> Hi is there something wrong with launchpad? I cannot report a bug. Stuck on gathering info
[07:20] <geser> kl_: see /topic
[07:24] <kl_> geser: Was not that fixed 6 hours ago?
[07:24] <lifeless> we got mostly operational 6 hours ago
[07:25] <lifeless> however the failed bit of kit was fairly large so we didn't have a spare idling around, a comprehensive shuffle has had to take place, and is still ongoing
[07:25] <lifeless> we hope to be fully operational soon
[07:26] <kl_> lifeless: ok
[08:55] <mabac> It seems I can't access any merge requests. Is this a known issue?
[08:55] <mabac> OOPS-1930W393
[08:55] <ttx> yes it's known
[08:56] <mabac> oh ok, thanks
[08:56] <ttx> don't have any clear ETA on fix though
[08:56] <ttx> (see channel topic)
[08:56] <wgrant> mabac: We had a major networking hardware failure a few hours ago. Most services were restored quickly, but it was bad enough that the last few are going to take a while longer.
[08:57] <mabac> ttx, thanks didn't notice that
[08:57] <mabac> wgrant, that's tough. I fully understand that it takes a while to recover.
[08:58] <ttx> wgrant: any idea what "a while longer" should be ? I have a release cooking...
[08:59] <wgrant> ttx: I'm not sure :/
[08:59] <ttx> wgrant: ok, thanks
[09:01] <poolie> codehost is down again?
[09:02] <wgrant> poolie: Looks alive to me.
[09:02] <poolie> wgrant: you can ssh in?
[09:02] <poolie> for me it seems to be hanging after 'offering dsa key'
[09:03] <wgrant> Not hanging, but rejecting my key :/
[09:03] <poolie> actually i also get a long pause, then rejection
[09:03] <fagan> we are having problems too
[09:04] <fagan> it happened last night about 11 last night UK time
[09:04] <fagan> and its still down :/
[09:04] <fagan> same as wgrant
[09:05] <poolie> fagan: i guess this is also network hardware failure fallout
[09:05] <fagan> poolie: is it going to last long we are at the windows sprint and we are blocked
[09:06] <lifeless> fagan: folk are working as fast as they can, sorry but no ETA yet
[09:06] <poolie> IS are working as fast as they can
[09:07] <fagan> lifeless: sure its cool we can try work around it
[09:08] <poolie> fagan: pulling from http://bazaar.launchpad.net/whatever may still wokr
[09:09] <fagan> poolie: does it work with pushing
[09:09] <poolie> sorry we're readonly until this is fixed
[09:10] <poolie> this particular bit may be fixed quite soon
[09:10] <fagan> ah ok
[09:12] <fagan> we are just going to ssh to a server until we can use lp again
[09:13] <poolie> good idea
[09:16] <philip_stoev> hi, branching from LP also seems to not work -- I am able to load pages such as http://bazaar.launchpad.net/~maria-captains/maria/maria-5.3-pstoevbuildbottesting/ in my browser but I can not bzr branch or bzr checkout from them
[09:16] <cdbs> Moreover, I can't view bug attachments
[09:16] <cdbs> I get a 502 proxy error
[09:16] <cdbs> https://launchpadlibrarian.net/69307138/Screenshot1.png for example
[09:17] <cdbs> https://bugs.launchpad.net/unity/+bug/760210 is the bug for the above example
[09:17] <lifeless> see topic
[09:17] <lifeless> we have a major outage in progress
[09:17] <lifeless> engineers on site, recovering things
[09:17] <cdbs> lifeless: LP Librarian isn't mentioned in that
[09:18] <cdbs> lifeless: would be good if you posted it on identi.ca lpstatus?
[09:18] <lifeless> I'm just updating that
[09:26] <poolie> codehost is ok for me now
[09:26] <poolie> fagan, philip_stoev^
[09:26] <philip_stoev> poolie: thanks
[09:26] <lifeless> codehosting back
[09:27] <fagan> poolie, lifeless cool thanks
[09:29]  * cdbs can finally get back to Unity work
[09:30] <ttx> merge proposals still oopses though.
[09:31] <dpm> hi launchpadders, I'm getting consistent OOPSes trying to moderate an LP mailing list. E.g. OOPS-1930W429
[09:31] <dpm> could someone look at it?
[09:32] <dpm> ok, no worries, I've just read the channel's topic :)
[09:37] <fagan> dpm: yeah I already thought I blew up lp when I saw that
[09:39] <dpm> :-)
[09:46] <bullgard4> How long will be  https://bugs.launchpad.net/ubuntu/ blocked yet?
[09:49] <wgrant> bullgard4: It should be working OK now.
[09:51] <bullgard4> wgrant: Not with me. I obtain: "Please wait while bug data is being processed." since 06:24 MESZ = GMT+2.
[09:53] <wgrant> bullgard4: Oh, that's not the URL you gave.
[09:53] <wgrant> bullgard4: The backlog is processing.
[09:54] <wgrant> They started processing about 15 minutes ago.
[09:54] <wgrant> Not sure how long it will take.
[09:56] <bullgard4> wgrant: The precise URL is very long (and thus error prone): https://bugs.launchpad.net/ubuntu/+sourcebase/banshee/+filebug/1ed4e3ba-666c-11e0-83cc-002481e7f48a
[09:58] <bullgard4> wgrant: The precise URL is very long (and thus error prone): https://bugs.launchpad.net/ubuntu/+source/banshee/+filebug/1ed4e3ba-666c-11e0-83cc-002481e7f48a
[09:59] <wgrant> bullgard4: Right. It'll take a while to process all the apport uploads from the last few hours.
[10:00] <bullgard4> wgrant: Thank you for your information.
[10:03] <ttx> looks like mergeproposals are back.
[10:05] <wgrant> ttx: Yeah, they should be OK now. Just sorting out the few remaining issues...
[10:48] <tim> hi, i have debianized a package and tried to upload it to my ppa. however it is rejected, because of a missing signature. how do i create it? http://pastebin.com/aT7yMB7s
[10:48] <bigjools> lifeless: time to update the topic?
[10:48] <lifeless> I think so
[10:49] <bigjools> lifeless: is poppy still affected or is this guy's error real?
[10:50] <lifeless> bigjools: thats the gpghandler tempdir thing
[10:50] <lifeless> we just need to bounce it
[10:50] <bigjools> awesome
[10:51] <bigjools> lifeless: why do we have a tempdir reaper again? :/
[10:51] <lifeless> bigjools: because otherwise we run out of space and diaf
[10:51] <bigjools> tim: you should be ok, wait for an acceptance email.  If you don't get one in 5 minutes ask again
[10:51] <lifeless> bigjools: can you liase with mthaddon on this one; I am about to head
[10:52] <bigjools> lifeless: I guess
[10:52] <SteveA> good morning
[10:53] <lifeless> bigjools: bug 757248
[10:53] <lifeless> SteveA: hola!
[10:53] <SteveA> hi robert
[10:53] <lifeless> SteveA: how goes amsterdam ?
[10:54] <SteveA> it's great :-)
[10:56] <SteveA> how's new zealand? I hope things are getting back to normal there
[10:56] <lifeless> yeah
[10:56] <lifeless> better off than japan
[10:57] <bigjools> hey there SteveA
[10:57] <SteveA> hi julian!
[10:57] <lifeless> SteveA: I'm in rangiora, nearly no disruption
[10:57] <lifeless> critical services and most normal services are fine
[10:58] <bigjools> this is a coincidence!  I was just debugging some code that says: if steveIsFixingThis:
[10:58] <lifeless> actual death toll was -very small- 0.25% of population
[10:58] <lifeless> the property damage and infrastructure was huge
[10:59] <SteveA> bigjools: thanks for fixing it! :-)
[10:59] <bigjools> :)
[11:27] <verwilst> Uploading php-mongo_1.1.4-0ppa1_source.changes: 1k/2k550 Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['General error', 'General error', 'General error'] : Permission denied. Note: This error might indicate a problem with your passive_ftp setting.      Please consult dput.cf(5) for details on this configuration option.
[11:27] <verwilst> any ideas about this?
[11:27] <verwilst> "Successfully signed dsc and changes files" while making my packages
[11:30] <geser> verwilst: the LP FTP server checks now the signature during upload and sometimes the FTP server and the Ubuntu keyserver don't like each other and don't communicate (but your upload might got accepted despite the error)
[11:31] <verwilst> i havent gotten a mail so i guess it didnt go through
[11:31] <verwilst> geser, but it's a server error i guess?
[11:31] <geser> yes
[11:32] <verwilst> last week i uploaded another package
[11:32] <verwilst> dput was all fine
[11:32] <verwilst> but i never got an email and the package never got on my ppa
[11:32] <verwilst> it just vanished as if i never uploaded it
[11:32] <verwilst> tried 3 times, dput was successful every time
[11:33] <geser> verwilst: does LP know about the key (that it belongs to your account) you used for signing?
[11:33] <verwilst> geser, i've uploaded a lot of packages
[11:33] <verwilst> so i guess so :)
[11:33] <geser> ah, so this only started happening recently?
[11:34] <verwilst> yeah
[11:34] <nigelb> hi, what can I do request a pad.lv for blueprints?
[11:34] <geser> then the new FTP server is to blaime
[11:34] <verwilst> https://launchpad.net/~verwilst/+archive/ppa < as you can see i packaged stuff 5 days ago
[11:34] <verwilst> from the exact same server
[11:37] <verwilst> geser, do you have the power to fix this? :D
[11:39] <bigjools> verwilst: there was a problem with the ftp server, it was bounced around 50 minutes ago to rectify that, do you get the same problem now?
[11:40] <verwilst> Successfully uploaded packages.
[11:40] <verwilst> :)
[11:40] <geser> verwilst: no, I'm just a mere LP user
[11:42] <verwilst>   Uploading php-gearman_0.7.0-0ppa1_source.changes: done. Successfully uploaded packages. < this is what i got last week as well for this other package
[11:42] <verwilst> but it never appeared in ppa and never gotten a mail from it
[11:42] <verwilst> maybe i will get one now
[11:42] <bigjools> verwilst: https://answers.edge.launchpad.net/launchpad/+faq/227
[12:02] <onox> is it possible to make the text below a bug report page in color red and large font?
[12:54] <verwilst> bigjools, so how am i supposed to know what is wrong with my changes or control file? :P
[12:54] <verwilst> an error mail for example would be handy :)
[12:56] <verwilst> hm, maintainer is empty
[12:56] <verwilst> might be that
[12:56] <wgrant> That's probably it.
[12:57] <wgrant> verwilst: The difficulty is that we can't parse the changes file to identify who to send the email to.
[12:57] <verwilst> dh-make-pecl's fault! :)
[12:57] <verwilst> wgrant, but i get a mail when it's rejected or accepted :)
[12:57] <verwilst> just use that email address :d
[12:57] <wgrant> verwilst: Yeah, but that's when the changes file is parsable :(
[13:01] <verwilst> 	[PPA verwilst] [ubuntu/lucid] php-gearman 0.7.0-0ppa1 (Accepted)
[13:01] <verwilst> hurray!
[13:02] <verwilst> thanks for the help dudes ;)
[13:42] <FloSoft> are the buildservers still offline?
[13:44] <wgrant> FloSoft: They should be just about back to normal now, once the queue's processed.
[13:44] <wgrant> FloSoft: Are you seeing any problems?
[13:44] <FloSoft> hmm okay, then I'll have to wait: "Start in 12h" -.-
[13:44] <wgrant> Which build?
[13:45] <FloSoft> aah now it changed, now its "8min" - for 2 minutes it was 12h ^^
[13:47] <FloSoft> wgrant: okay good, now all my builds will start in max 20min, thats okay *g*
[13:47] <wgrant> FloSoft: Great!
[13:51] <FloSoft> 12h would be a bit long *g*
[14:06] <verwilst> rah
[14:07] <verwilst> php5-gearman_0.7.0-0ppa1_i386.deb: has 10 file(s) with a time stamp too far in the past (e.g. usr/share/doc/php5-gearman/examples/reverse_client.php [Thu Jan  1 09:13:08 1970]).
[14:07] <verwilst> not again :(
[14:07] <verwilst> so now i can no longer re-upload the source package because the contents have changed if i touch the source files :(
[15:02] <Philip5> could i get the attention from any of the launchpad PPA admins to look at my question i just posted in "Questions for Launchpad itself" on launchpad.
[15:03] <bigjools> Philip5: that's a faq
[15:03]  * bigjools links
[15:05] <Philip5> bigjools: oh? i don't thinks that's in any faq
[15:05] <bigjools> see my answer
[15:10] <Philip5> bigjools: hmm, but in my case i uploaded it wrong and made a delete of it before it finished all the builds and never got published
[15:10] <bigjools> Philip5: doesn't matter, you cannot ever re-upload the same files/versions
[15:13] <Philip5> but first i upploded 2.1.0-maverick~ppa1 which was built and fine and then uploaded 2.2.0-maverick~ppa1 that i deleted before it got published as it should have been 2.1.0-maverick~ppa2
[15:13] <Philip5> now i'm stuck on 2.2.0-maverick~ppa1 you say?
[15:14] <Philip5> as i broke out 2.2 to be it's own set of packages so 2.1 will never be called 2.2
[15:15] <Philip5> i med the error by not changing "Source Package" in my controll file
[15:15] <Philip5> med=made
[15:16] <bigjools> yes you are stuck on 2.2.0
[15:17] <Philip5> hmm, that's not good
[15:17] <Philip5> and no way to delete that in my ppa history?
[15:17] <bigjools> no
[15:18] <bigjools> other people have done a ~really2.1.0~ppa1 style version
[15:19] <Philip5> that might solve it
[15:19] <Philip5> a little ugly though
[15:22] <bigjools> unfortunately yes :(
[15:28] <jcsackett> adeuring: r=me.
[15:28] <adeuring> jcsackett: thanks!
[15:28] <jcsackett> adeuring: glad you were in this channel too. :-P
[15:38] <Philip5> is ~ a higher bump than a number?
[15:39] <wgrant> '~' is less than everything. Even ''
[15:39] <wgrant> You can use dpkg --compare-versions to check your versions.
[15:39] <wgrant> eg. dpkg --compare-versions 1 lt 2 && echo "true"
[15:39] <Philip5> thanks
[15:47] <Philip5> well that was the ugliest thing i have ever done on my PPA
[15:47] <Philip5> when you hit the low you can only do better :)
[15:51] <Ampelbein> Philip5: you could add an epoch to the version to avoid the ~really... stuff.
[15:52] <wgrant> You want to be *really* sure about that.
[15:52] <tsimpson> you can never undo an epoch
[15:52] <wgrant> For a small mistake like this it's almost definitely overkill.
[15:52] <wgrant> Permanent overkill.
[15:53] <Ampelbein> yes, that's true.
[15:53] <maxb> Technically you *can* make PPAs go back to lower versions, but if you do, you screw things up for users who have your packages installed. So it's only an option if you know your installed userbase is zero
[15:53] <Philip5> i didn't do an epoch just an ugly version naming
[15:53] <Philip5> maxb: how?
[15:53] <Philip5> no users have that packges as they never got published
[15:54] <maxb> If you delete the old package in the web UI, you can upload a version that is lower
[15:54] <maxb> But you can't upload a version which is the same as one used before, even if it is deleted
[15:54] <Philip5> maxb: no then the upload get rejected
[15:54] <Philip5> aha
[15:54] <Philip5> but that was what i did
[15:55] <Philip5> abd got into this mess in the first place
[15:58] <maxb> really~2.1.0-maverick~ppa2 ?!
[15:58] <maxb> Yuck
[15:58] <maxb> that's hideous, and just as permanent as an epoch
[15:58] <Philip5> exactly, yuck
[15:59] <tsimpson> it's not as permanent as an epoch
[15:59] <maxb> You should delete it and upload a 2.1.0-maverick~ppa5
[16:00] <maxb> You might need to wait for a publisher run to occur between deleting and uploading a replacement
[16:00] <maxb> tsimpson: For all practical purposes it is, as no realistic upstream version will ever exceed it
[16:00] <Philip5> maxb: thats what i did but i got error when it was going to be uploaded for publication but it all built fine
[16:01] <maxb> If you delete all of the stuff with bizarre versions, wait at least 10 minutes, and upload a sane one, it should work
[16:02] <Philip5> i think i'll do that bebore i do this ugly thing
[16:10] <wgrant> (it may take up to an hour, but 10 minutes is likely)
[16:10] <Philip5> then i wait an hour to be sure
[16:11] <Philip5> maybe that was my misstake in the first place. that i uploaded the new one too fast after i delete the first one that was wrong
[16:13] <wgrant> Philip5: It's a bit of an unintended feature that that works.
[16:13] <wgrant> So timelines are not obvious nor guaranteed.
[16:16] <Philip5> well i'll see... i'll go out for a bit and try a new upload when i get back
[16:17] <Philip5> thanks so far...
[17:30] <FloSoft> hmm those buildservers: i have here one build which will start in 6h - is that okay? (buildjob 2475857)
[17:31] <TheEvilPhoenix> FloSoft:  yes, not all packages are built immediately
[17:31] <FloSoft> TheEvilPhoenix: okay than only the lpia-architecture has a very laaarrge queue ?
[17:31] <FloSoft> *then
[17:33] <TheEvilPhoenix> FloSoft:  dont know, i'm not a builder manager, i just know that several times I had to wait for over 5 hours to get a package built (and that package was architecture-independent)
[17:39] <micahg> FloSoft: lpia is only for karmic and hardy
[17:40] <TheEvilPhoenix> ^
[18:01] <ScottK> lifeless: More fun with your favorite package accept page.  (Error ID: OOPS-1930J1284) - It may be related to the fact that there's a previous upload still unaccepted.
[18:01] <ScottK> (Error ID: OOPS-1930F1319) too
[18:03] <ScottK> Third try was the charm...
[18:47] <Philip5> maxb & wgrant: btw, it worked with my rebuild after i deleted the wrong packages and waited. uploaded new bumped nice looking version :)  so thanks for the support guys
[18:47] <maxb> :-)
[18:49] <Philip5> maxb:  i'm so relieved that i didn't have to make that ugly version number for my packages. *sigh*
[19:29] <ScottK> lifeless and wgrant: The builders page timed out again: (Error ID: OOPS-1930H1457)
[21:46] <FloSoft> hi, i've deleted a ppa but it's not removed from the system? only grayed out - but i can't reactivate that name
[21:47] <maxb> that is correct (unfortunately)
[21:48] <FloSoft> hmm
[21:48] <FloSoft> what does happen if the 2gb limit of the ppa is reached?
[22:17] <maxb> What steps exist between a package being shown as published in the Launchpad UI, and it actually appearing on archive.ubuntu.com ?
[22:34] <lifeless> maxb: there is an rsync job that takes the archive launchpad produces, and mirrors it to the static web servers; along the way it gets split into a.u.c, p.u.c, s.u.c
[22:37] <maxb> Is it abnormal for that to have not happened yet 30 minutes after publication?
[22:37] <lifeless> beta release stuff is happening
[22:37] <lifeless> so it might be related
[22:38] <lifeless> as for timelineness, I think 1 hour is the window
[22:38] <lifeless> would like to make that smaller e.g. with lmirror but its not on the immediate agenda