chroot problem with various Xenial builds

Asked by Rob Savoury

Hi, today various builds for Xenial are failing for me with "chroot problem" and the following types of errors:

Err:42 https://ppa.launchpadcontent.net/savoury1/digikam/ubuntu xenial/main amd64 Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

W: The repository 'https://ppa.launchpadcontent.net/savoury1/digikam/ubuntu xenial Release' does not have a Release file.

Builds were working fine for me last night, so this is new from this morning. Examples of this failure:

https://launchpad.net/~savoury1/+archive/ubuntu/digikam/+build/23095227
https://launchpad.net/~savoury1/+archive/ubuntu/ffmpeg5/+build/23095745

Is there an issue currently with the Launchpad servers? Any help appreciated.

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said :
#1

This is due to a combination of the work in https://bugs.launchpad.net/launchpad/+bug/1473091 and the fact that xenial builds start out with a very old chroot that's lacking support for slightly more modern certificate chains. Thanks - we're looking into this.

Revision history for this message
Best Colin Watson (cjwatson) said :
#2

Thanks for the heads-up. We've fixed this (reverting to plain HTTP for the purposes of builds, since that's the simplest approach and is no worse than before), and I've just retried all the failed builds where possible.

Revision history for this message
Rob Savoury (savoury1) said :
#3

Thanks for the background info about the switch to HTTPS which is very good to do of course. Appreciate you reverting to HTTP for the builds for now to get them working on "vintage" (!) releases such as Xenial, and thanks for kicking off the failed builds again which all look like they're progressing well.

Cheers!