[16:03] <dsmythies> Hi launchpad people. I have an issue. 14 hours ago I pushed revisions to the Ubuntu Officical documentation that ends up on help.ubuntu.com. I never got an e-mail (the team normally does), and I still am unable to open http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-docs/help.ubuntu.com/revision/176 . Note that I have done large revisions before, but I do not think ever one this big. The page I end up on says if the problem persists 
[16:12] <dobey> dsmythies: looks like it is timing out. do you get an OOPS-ID in the page? if so, you can file a bug and include that OOPS-ID value in the report.
[16:13] <cjwatson> is it important that it be viewable in the web UI?
[16:13] <cjwatson> it seems to at least have been scanned by Launchpad itself, so you should be able to branch it normally etc.
[16:16] <dsmythies> There is no OOPs-ID. The page start with "Uh Oh" and says there is a "Technically, the load balancer took too long to connect to an application server."
[16:16] <dsmythies> If it worked, and completed properly, then I should have got an e-mail and this morning help.ubuntu.com should have been updated. Neither occured.
[16:17] <cjwatson> it's not clear that codebrowse problems are related to that though
[16:17] <cjwatson> looking into logs
[16:20] <dsmythies> cjwatson: I recall you saying one time that you were heading over to launchpad (I don't recall the context of the exchange).
[16:21] <cjwatson> indeed
[16:23] <cjwatson> this isn't an area I know well yet, though
[16:24] <cjwatson> do you know how the help.ubuntu.com update is triggered?
[16:24] <dobey> well, if the branch history is significantly large as a result of the changes in the commit, it can cause issues with pulling the branch as well (i've had issues pulling very large branches before)
[16:24] <cjwatson> the REVISIONS_ADDED_MAIL job for this branch OOPSed
[16:24] <cjwatson> so that explains the lack of mail
[16:25] <cjwatson> OOPS-a063e5292d781f083e06db3c2cf8c7df but it's not on oops.c.c
[16:25] <dsmythies> Correction: I think help.ubunut.com actually did update.
[16:25] <dsmythies> ... still checking.
[16:26] <dsmythies> Yes, help.ubuntu.com did update.
[16:26] <cjwatson> That makes sense.  So you just didn't get mail because the job oopsed, probably because it tried to get the revision history and timed out.
[16:26] <cjwatson> Or similar.
[16:28] <dsmythies> O.K. so it seems I'll never be able to open the revision page because it is too huge. the e-mail also failed for the same reason. But the update itself is O.K.
[16:29] <cjwatson> I think so.  Bazaar has some scaling limitations ...
[16:30] <dsmythies> GunnarHj: I made a mistake in my e-mail, it did update, I was looking for relative addresses, which of course on the real help.ubuntu.com are the same as the old absolute address. Duh.
[16:30] <dsmythies> Thanks all.
[16:33] <GunnarHj> dsmythies: I just started "bzr pull". Let's see what happens.
[16:34] <dsmythies> GunnarHj: It is big.
[16:34] <GunnarHj> dsmythies: I know. :)
[16:38] <GunnarHj> dsmythies: Can we move to #ubuntu-doc?
[16:41] <dsmythies> cjwatson: Imissed your "how the help.ubuntu.com update is triggered?" earlier: All I know is that if the push is done by about 2 to 3 hours ago (5 to 7 A.M. my time) it will get picked up and hlep.ubuntu.com will be updated. I believe the pickup is once every 24 (ish) hours.
[16:41] <cjwatson> dsmythies: It's probably just a cron job, then.
[16:41] <dsmythies> I would assume, yes.
[16:42] <dsmythies> GunnarHj: I will join #ubuntu-doc
[16:56] <dsmythies> dobey: Re: "large commit can cause issues with pulling the branch as well": GunnarHj's pull was O.K.
[17:06] <dobey> dsmythies: sure, i was just pointing out that branches can become too large for bzr to be able to check out on some machines.
[17:09] <GunnarHj> dobey, dsmythies: Actually I got the message ""Connection Timeout: disconnecting client after 300.0 seconds", but it still continued and finalized successfully.
[20:39] <sergio-br22> I'm having problem with gcc 4.8,  gcc-4.8: error: unrecognized command line option ‘-fstack-protector-strong’
[20:39] <sergio-br22> any idea?
[20:40] <cjwatson> yes, gcc-4.8 didn't have that option, so don't use it with it.
[20:40] <sergio-br22> ubuntu 14.10
[20:40] <cjwatson> if you're explicitly using gcc-4.8 for some reason in a build, you may need to override the default hardening flags emitted by dpkg-buildflags
[20:40] <sergio-br22> hum, any tip to override them?
[20:41] <sergio-br22> dpkg-buildflags=xxxxx, something like this?
[20:41] <cjwatson> see dpkg-buildflags(1)
[20:41] <darkxst> hmm, how did some of my launchpad (api) cache get owned by root?
[20:41] <cjwatson> simplest way is probably, in debian/rules: export DEB_BUILD_MAINT_OPTIONS := hardening=-stackprotectorstrong
[20:42] <sergio-br22> hum, let me see
[20:43] <sergio-br22> great, it works
[21:37] <mark06> is there a bug to track deleted ppas being listed in profile? e.g. https://launchpad.net/~renatosilva/+related-packages
[21:44] <dobey> mark06: how many PPAs do you see there?
[21:46] <mark06> 6, you? http://i.imgur.com/ZpbHPUM.png
[21:50] <dobey> 1
[21:50] <dobey> deleted PPAs are visible to the owner in case they wish to restore, i guess
[21:51]  * mark06 hates artificial deletion
[21:53] <mark06> I see no restore option
[21:53] <mark06> sounds like a bug
[21:55] <mark06> restoring not mentioned in docs either https://help.launchpad.net/Packaging/PPA?action=show&redirect=PPA#Deleting_a_PPA
[21:55] <mark06> anyone knows an existing bug to handle this?
[21:56] <dobey> if you want to file a bug, just file one
[21:56] <dobey> lp developers are all gone for the weekend
[22:11]  * mark06 filed bug 1421853
[22:12] <belak> This may be random, but I was looking at this: https://answers.launchpad.net/launchpad/+question/218551
[22:12] <belak> What does launchpad actually send, header wise?