virtualstaticvoid/heroku-buildpack-r

GPG error

diegocl02 opened this issue · 3 comments

diegocl02 commented

Hi, we are getting this error when deploying using the buildpack. I read it was fixed in the Heroku R Docker Image repository, is there something we need to update when using the buildpack?

-----> R app detected

-----> Installing R

       Version 4.0.0 will be installed.

-----> Downloading buildpack archives from AWS S3

       Downloading https://heroku-buildpack-r.s3.amazonaws.com/latest/heroku-buildpack-r-18-4.0.0-deploy.tar.gz

       Setting up build environment

       Downloading https://heroku-buildpack-r.s3.amazonaws.com/latest/heroku-buildpack-r-18-4.0.0-chroot.tar.gz

-----> Configuring build environment...

       WARNING: Use of the Aptfile file is NOT recommended and will be deprecated in future.

       For greater control and flexibility consider using the Heroku

       container stack together with the heroku-docker-r implementation.

       See https://github.com/virtualstaticvoid/heroku-docker-r for more information.

       W: GPG error: https://cloud.r-project.org/bin/linux/ubuntu bionic-cran40/ InRelease: The following signatures were invalid: EXPKEYSIG 51716619E084DAB9 Michael Rutter <marutter@gmail.com>

       E: The repository 'https://cloud.r-project.org/bin/linux/ubuntu bionic-cran40/ InRelease' is not signed.

 !     Push rejected, failed to compile R app.

 !     Push failed
virtualstaticvoid commented

I've triggered a new build of the buildpack artifacts, which will include the new GPG key.

I'll close the issue once the new artifacts have been published to AWS S3.

virtualstaticvoid commented

The updated artifacts have been published. Please confirm that your deployment is working.

  • 👍1
diegocl02 commented

The updated artifacts have been published. Please confirm that your deployment is working.

Thanks! Just deployed a test app a few minutes ago using the buildpack and it worked fine!

  • 👍1