You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Laszlo Gaal (Jira)" <ji...@apache.org> on 2020/07/27 22:43:00 UTC
[jira] [Created] (IMPALA-10011) Building the Debian 8 container in
the toolchain fails on an expired key
Laszlo Gaal created IMPALA-10011:
------------------------------------
Summary: Building the Debian 8 container in the toolchain fails on an expired key
Key: IMPALA-10011
URL: https://issues.apache.org/jira/browse/IMPALA-10011
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 4.0
Reporter: Laszlo Gaal
Investigating and fixing IMPALA-9985 required a toolchain rebuild reaching down to rebuilding the Docker images used for the toolchian build (this happens using the Dockerfiles in the docker subdirectory of the native-toolchain repo).
During the rebuild the Debian 8 container failed with this error:
{code}
....
GPG error: http://archive.debian.org jessie Release: The following signatures were invalid: KEYEXPIRED 1587841717
.....
WARNING: The following packages cannot be authenticated!
libgdbm3 libpopt0 libedit2 libgpm2 libkeyutils1 python-minimal mime-support
[....list of about 100 packages....]
[91mE: There are problems and -y was used without --force-yes
[0mThe command '/bin/sh -c apt-get update && apt-get install -y autoconf bison build-essential ccache curl flex git groff-base libffi-dev libkrb5-dev libncurses5-dev libreadline-dev libsasl2-dev libssl-dev libtool-bin libz-dev lsb-release pigz pkg-config python-dev rsync texinfo unzip vim-common wget' returned a non-zero code: 100
{code}
Debian 8 is past its end-of-life, which happened on June 30th, 2020; the expiration of repo keys is probably one of the side effects of this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org