=== drkokandy_ is now known as drkokandy === elmo_ is now known as elmo === JoseeAntonioR is now known as jose [16:03] 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] 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] is it important that it be viewable in the web UI? [16:13] it seems to at least have been scanned by Launchpad itself, so you should be able to branch it normally etc. [16:16] 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] 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] it's not clear that codebrowse problems are related to that though [16:17] looking into logs [16:20] 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] indeed [16:23] this isn't an area I know well yet, though [16:24] do you know how the help.ubuntu.com update is triggered? [16:24] 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] the REVISIONS_ADDED_MAIL job for this branch OOPSed [16:24] so that explains the lack of mail [16:25] OOPS-a063e5292d781f083e06db3c2cf8c7df but it's not on oops.c.c [16:25] https://oops.canonical.com/?oopsid=OOPS-a063e5292d781f083e06db3c2cf8c7df [16:25] Correction: I think help.ubunut.com actually did update. [16:25] ... still checking. [16:26] Yes, help.ubuntu.com did update. [16:26] 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] Or similar. [16:28] 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] I think so. Bazaar has some scaling limitations ... [16:30] 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] Thanks all. [16:33] dsmythies: I just started "bzr pull". Let's see what happens. [16:34] GunnarHj: It is big. [16:34] dsmythies: I know. :) [16:38] dsmythies: Can we move to #ubuntu-doc? [16:41] 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] dsmythies: It's probably just a cron job, then. [16:41] I would assume, yes. [16:42] GunnarHj: I will join #ubuntu-doc [16:56] dobey: Re: "large commit can cause issues with pulling the branch as well": GunnarHj's pull was O.K. [17:06] 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] dobey, dsmythies: Actually I got the message ""Connection Timeout: disconnecting client after 300.0 seconds", but it still continued and finalized successfully. === wedgwood is now known as Guest68861 === JanC_ is now known as JanC [20:39] I'm having problem with gcc 4.8, gcc-4.8: error: unrecognized command line option ‘-fstack-protector-strong’ [20:39] any idea? [20:40] yes, gcc-4.8 didn't have that option, so don't use it with it. [20:40] ubuntu 14.10 [20:40] 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 === JoseeAntonioR is now known as jose [20:40] hum, any tip to override them? [20:41] dpkg-buildflags=xxxxx, something like this? [20:41] see dpkg-buildflags(1) [20:41] hmm, how did some of my launchpad (api) cache get owned by root? [20:41] simplest way is probably, in debian/rules: export DEB_BUILD_MAINT_OPTIONS := hardening=-stackprotectorstrong [20:42] hum, let me see [20:43] great, it works [21:37] is there a bug to track deleted ppas being listed in profile? e.g. https://launchpad.net/~renatosilva/+related-packages [21:44] mark06: how many PPAs do you see there? [21:46] 6, you? http://i.imgur.com/ZpbHPUM.png [21:50] 1 [21:50] deleted PPAs are visible to the owner in case they wish to restore, i guess [21:51] * mark06 hates artificial deletion [21:53] I see no restore option [21:53] sounds like a bug [21:55] restoring not mentioned in docs either https://help.launchpad.net/Packaging/PPA?action=show&redirect=PPA#Deleting_a_PPA [21:55] anyone knows an existing bug to handle this? [21:56] if you want to file a bug, just file one [21:56] lp developers are all gone for the weekend [22:11] * mark06 filed bug 1421853 [22:11] bug 1421853 in Launchpad itself "Deleted PPAs displayed in profile when logged in" [Undecided,New] https://launchpad.net/bugs/1421853 [22:12] This may be random, but I was looking at this: https://answers.launchpad.net/launchpad/+question/218551 [22:12] What does launchpad actually send, header wise?