setup-r action failing on Ubuntu

[mattwarkentin]

Hi @jimhester,

Seemingly out of nowhere my setup-r action stopped working for any version of Ubuntu I've tried, with the following error:

Reading package lists...
E: Failed to fetch https://packagecloud.io/github/git-lfs/ubuntu/dists/bionic/InRelease  402  Payment Required [IP: 54.193.34.251 443]
E: The repository 'https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease' is no longer signed.
Error: Failed to get R 4.0.3: Failed to get R 4.0.3: Failed to install R: Error: The process '/usr/bin/sudo' failed with exit code 100

Any insight into what this means?

For additional context, I'm not doing anything fancy:

jobs:
  foo:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v2
      - uses: r-lib/actions/setup-r@v1

[mattwarkentin]

Re-ran and got a slightly different error:

Reading package lists...
E: Failed to fetch https://packagecloud.io/github/git-lfs/ubuntu/dists/focal/InRelease  402  Payment Required [IP: 54.183.38.243 443]
E: The repository 'https://packagecloud.io/github/git-lfs/ubuntu focal InRelease' is no longer signed.
Error: Failed to get R 4.0.3: Failed to get R 4.0.3: Failed to install R: Error: The process '/usr/bin/sudo' failed with exit code 100

Seems like the issue is with the packagecloud service?

[buvinghausen]

@mattwarkentin I am getting this error too

[andres]

http request to https://packagecloud.io/github/git-lfs/ubuntu/dists/bionic/InRelease
gives: Payment required
so the problem must be at packagecloud.io

[bmendonca]

I'm also hitting this error on unrelated Docker images trying to call out to the https://packagecloud.io/github/git-lfs website.

Get:1 http://security.debian.org/debian-security stretch/updates InRelease [53.0 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Get:3 https://packages.sury.org/php stretch InRelease [6760 B]
Get:4 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [613 kB]
Get:5 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]
Get:6 http://deb.debian.org/debian stretch Release [118 kB]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2410 B]
Get:8 https://packages.sury.org/php stretch/main amd64 Packages [152 kB]
Get:9 http://deb.debian.org/debian stretch-updates/main amd64 Packages [2596 B]
Get:10 http://deb.debian.org/debian stretch/main amd64 Packages [7080 kB]
Ign:11 https://packagecloud.io/github/git-lfs/debian stretch InRelease
Err:12 https://packagecloud.io/github/git-lfs/debian stretch Release
  402  Payment Required
Reading package lists...
E: The repository 'https://packagecloud.io/github/git-lfs/debian stretch Release' does not have a Release file

[c-py]

There is also an issue open in actions/virtual-environments for this actions/runner-images#1983

[kyle-assurely]

as a temporary work around I recommend removing the git-lfs package unless you are using it via:

      - name: remove git-lfs
        shell: bash
        run: |
          sudo rm /etc/apt/sources.list.d/github_git-lfs.list 
          sudo rm /etc/apt/sources.list.d/github_git-lfs.list.save

also note this appears to be because the git-lfs project has issues itself, as I cannot even obtain their gpg key.

[bmendonca]

as a temporary work around I recommend removing the git-lfs package unless you are using it via:

      - name: remove git-lfs
        shell: bash
        run: |
          sudo rm /etc/apt/sources.list.d/github_git-lfs.list 
          sudo rm /etc/apt/sources.list.d/github_git-lfs.list.save

also note this appears to be because the git-lfs project has issues itself, as I cannot even obtain their gpg key.

Thank you so much, @kyle-assurely ! Your solution seemed to work for me when using my unrelated Docker build images that are not related to this project but were suffering from this same problem. Frantically Googling after work brought me to this thread and I imagine others will find their way here as well.

RUN rm /etc/apt/sources.list.d/github_git-lfs.list

The /etc/apt/sources.list.d/github_git-lfs.list.save file didn't exist for me, but I imagine it varies depending on distribution.

[buvinghausen]

FYI the keys are back online

[jimhester]

This was an upstream issue unrelated to the custom actions here, so I will close this issue.

[github-actions]

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue