[05:06] <glachas> E: Failed to fetch http://ppa.launchpad.net/v-launchpad-jochen-sprickerhof-de/pcl/ubuntu/dists/xenial/main/binary-amd64/Packages  404  Not Found
[05:06] <glachas> E: Some index files failed to download. They have been ignored, or old ones used instead.
[05:07] <glachas> got the above error while running sudo apt-get update
[05:32] <wgrant> glachas: That PPA doesn't provide any packages for xenial (see https://launchpad.net/~v-launchpad-jochen-sprickerhof-de/+archive/ubuntu/pcl)
[05:32] <wgrant> You probably want to remove it.
[05:34] <glachas> I don't know but I just followed http://pointclouds.org/downloads/linux.html in order to install pcl on my system (ubuntu 16.04 lts)
[05:35] <glachas> I removed that too but I am not able to install pcl
[05:36] <wgrant> glachas: They haven't updated that PPA since Ubuntu 14.10.
[05:36] <wgrant> glachas: You probably want to contact the developer of the software and ask them what 16.04 users should do.
[05:36] <glachas> wgrant: ohk
[12:24] <tvansteenburgh> wgrant: hi, i have a question about OOPS-7eb6a6506531c94928fd7c1fc2cedd2d
[12:25] <tvansteenburgh> wgrant: i don't suppose that is likely to be temporary?
[12:26] <tvansteenburgh> Mmike: the 503 is being caused by a query timeout: OOPS-7eb6a6506531c94928fd7c1fc2cedd2d
[13:50] <wgrant> tvansteenburgh, Mmike: The problem occurs because of the large number of private teams that the user is a member of. If you don't care about private team memberships, making the same request anonymously should work.
[13:50] <wgrant> Due to the way private teams work it's not an easy fix, unfortunately.
[13:52] <cjwatson> Is that the same sort of thing that causes https://bugs.launchpad.net/launchpad/+bug/1692120 ?  The queries are structurally somewhat similar.
[13:53] <wgrant> cjwatson: Hm, I don't think so?
[13:54] <wgrant> Well, a bit, I guess.
[13:54] <wgrant> The problem is that private teams are visible to you if you can see any bugs related to them, which is a very large intermediate set that can't be efficiently calculated from either end.
[14:50] <Mmike> wgrant, so, what do I do then? :) Ask to be removed from all those teams?
[14:50] <Mmike> I'll try what tvansteenburgh suggested, ask for a review from the mongodb-charmers team, and not as myself
[15:50] <tvansteenburgh> wgrant: thanks for looking. unfortunately, getting a list of the team memberships is the sole purpose of the api call we're making :P
[15:57] <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/324625
[15:57] <smoser> launchpad doesn't like that MP
[15:57] <smoser>  OOPS-22167f54777fabf3361afabbffb9ead3
[16:01] <cjwatson> smoser: can you file a bug please?
[16:02] <cjwatson> I don't understand why we're only seeing these bugs related to updating related bugs from commit metadata now; that code's been in for months
[16:02] <cjwatson> but anyway, should be an easy fix
[16:02] <cjwatson> I guess it's relatively unusual for LP not to have seen a given author before
[16:03] <smoser> cjwatson, hm... maybe because it *had* seen the author before
[16:03] <smoser> at https://code.launchpad.net/~jingni.wjj/cloud-init/+git/cloud-init/+merge/323306
[16:03] <smoser> but i changed the spelling of the 'Author' name in my commit
[16:04] <smoser> to give capitalization
[16:06] <cjwatson> -> new RevisionAuthor row
[16:07] <cjwatson> still linked to the same Person
[16:07] <smoser> i dont know. but youmentioned author, and i knew that i'd done that
[16:07] <cjwatson> look, it doesn't matter, I know what the fix is :)
[16:07] <cjwatson> I just want a bug to hang the commit off
[16:08] <smoser> https://bugs.launchpad.net/launchpad/+bug/1693543
[16:08] <cjwatson> ta
[16:38] <wgrant> tvansteenburgh: The particular problem you're running into is caused by an authenticated user trying to list a set of teams including private ones that the user can't see. The slow codepath is skipped if the user isn't authenticated -- you'd still get to see team memberships, just not private ones.
[19:32] <dupondje_> mmmm
[19:34] <dupondje> dev.launchpad.net uses an invalid security certificate.
[19:34] <dupondje> The certificate expired on 22 mei 2017 om 14:00. The current time is 25 mei 2017 om 21:27.
[19:34] <dupondje> guess somebody needs to fix this :)
[21:08] <cjwatson> dupondje: Yeah, I noticed earlier today and filed a ticket with our sysadmins