New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installation in ubuntu is not working #3474

Closed
AbhishekVermaKT opened this Issue Jan 14, 2019 · 16 comments

Comments

Projects
None yet
@AbhishekVermaKT
Copy link

AbhishekVermaKT commented Jan 14, 2019

Trying the instruction:

abhishek@abhishek:~/ds_development$ sudo add-apt-repository ppa:git-core/ppa
 The most current stable version of Git for Ubuntu.

For release candidates, go to https://launchpad.net/~git-core/+archive/candidate .
 More info: https://launchpad.net/~git-core/+archive/ubuntu/ppa
Press [ENTER] to continue or Ctrl-c to cancel adding it.

yields eventually:

Get:13 https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease [23.2 kB]                                                                 
Err:13 https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B05F25D762E3157
Fetched 299 kB in 2s (143 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B05F25D762E3157
W: Failed to fetch https://packagecloud.io/github/git-lfs/ubuntu/dists/bionic/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B05F25D762E3157
W: Some index files failed to download. They have been ignored, or old ones used instead.

Also I have had git lfs in my computer already installed however I was getting same error while sudo apt update so tried to uninstall and install again.

@philibar

This comment has been minimized.

Copy link

philibar commented Jan 14, 2019

Attempting to do an apt update when the repo is already added will return the following:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://10.55.0.38/git-lfs xenial InRelease: The following signatures were invalid: KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640
W: Failed to fetch http://10.55.0.38/git-lfs/dists/xenial/InRelease  The following signatures were invalid: KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640  KEYEXPIRED 1547333640

The key seems to have expired over the weekend:

 /etc/apt/trusted.gpg.d/git-lfs.gpg
----------------------------------
pub   4096R/D59097AB 2014-01-13 [expired: 2019-01-12]
uid                  packagecloud ops (production key) <ops@packagecloud.io>

EDIT:
@bk2204 , comment has fixed the issue for us.

@bertrand-camus

This comment has been minimized.

Copy link

bertrand-camus commented Jan 14, 2019

Seeing the issue as well on ubuntu 16.04

@bk2204

This comment has been minimized.

Copy link
Contributor

bk2204 commented Jan 14, 2019

Hey, sorry to hear y'all are having trouble.

As far as I can tell, the key we're using for signatures in the packagecloud repository is different. We don't manually manage that key, so it's possible that they've changed it without us knowing. Unfortunately, without packagecloud providing some sort of archive keyring, there's no way to automatically rotate keys.

I tried to download the key from https://packagecloud.io/app/github/git-lfs/gpg#gpg-apt and then install the repo in an Ubuntu bionic container, and it appears to work for me. Can you confirm that following the steps on that page makes it possible for you to run apt update successfully?

@ScottMcCormack

This comment has been minimized.

Copy link

ScottMcCormack commented Jan 15, 2019

Running the following command looks to have fixed this issue for me:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6B05F25D762E3157
@bk2204

This comment has been minimized.

Copy link
Contributor

bk2204 commented Jan 15, 2019

Okay, great. Sorry about the inconvenience.

@bk2204 bk2204 closed this Jan 15, 2019

@ffes

This comment has been minimized.

Copy link

ffes commented Jan 17, 2019

I run into the same problem. I tried the apt-key command above and the update still fails. It appears that their key has expired:

root@mypc:~# apt-key list
/etc/apt/trusted.gpg
--------------------
pub   rsa4096 2014-01-13 [SCEA] [expired: 2019-01-12]
      418A 7F2F B0E1 E6E7 EABF  6FE8 C2E7 3424 D590 97AB
uid           [ expired] packagecloud ops (production key) <ops@packagecloud.io>

I snipped all the irrelevant keys that work as expected.

@bk2204 bk2204 reopened this Jan 17, 2019

@bk2204

This comment has been minimized.

Copy link
Contributor

bk2204 commented Jan 17, 2019

Can you provide the deb or deb-src line for the repository you're using? It's likely somewhere in /etc/apt/sources.list.d.

@AbhishekVermaKT

This comment has been minimized.

Copy link
Author

AbhishekVermaKT commented Jan 17, 2019

@ScottMcCormack fix worked for me. Just putting it here for anyone who might benefit.

@stevencrader

This comment has been minimized.

Copy link

stevencrader commented Jan 17, 2019

I am seeing this issue on Ubuntu 14.04

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io trusty InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)

W: Failed to fetch https://packagecloud.io/github/git-lfs/ubuntu/dists/trusty/InRelease

I tried the command from @ScottMcCormack and adding the GPG key command shown on https://packagecloud.io/app/github/git-lfs/gpg#gpg-apt but neither works.

Here is the output of /etc/apt/sources.list.d/github_git-lfs.list

# this file was generated by packagecloud.io for
# the repository at https://packagecloud.io/github/git-lfs

deb https://packagecloud.io/github/git-lfs/ubuntu/ trusty main
deb-src https://packagecloud.io/github/git-lfs/ubuntu/ trusty main
@ffes

This comment has been minimized.

Copy link

ffes commented Jan 18, 2019

Here it is:

frank@mypc:/etc/apt/sources.list.d$ cat git-lfs.list
# this file was generated by packagecloud.io for
# the repository at https://packagecloud.io/github/git-lfs

deb https://packagecloud.io/github/git-lfs/ubuntu/ bionic main
deb-src https://packagecloud.io/github/git-lfs/ubuntu/ bionic main

When I installed git-lfs (somewhere in the summer) I used the description on the git-lfs website. Once done, I only renamed the file in /etc/apt/sources.list.d. I has worked as expected until very recently. As I mentioned above apt-key list says the keys has expired on the 12th of January.

@ashiklom ashiklom referenced this issue Jan 24, 2019

Closed

Change R version to 3.5 in .travis.yml {WIP} #2258

2 of 12 tasks complete
@gkapfham

This comment has been minimized.

Copy link

gkapfham commented Jan 28, 2019

Since there has been some confusion as to whether or not the approach by @ScottMcCormack would work or not, I am writing to report that, for Ubuntu 16.04 LTS this worked correctly for me. I can confirm that after running the suggested command the sudo apt update command worked correctly without warning! Many thanks to the creators of this tool and to @ScottMcCormack for suggesting the fix!

@ttaylorr ttaylorr closed this Feb 1, 2019

sschuberth added a commit to heremaps/tin-terrain that referenced this issue Feb 1, 2019

sschuberth added a commit to heremaps/tin-terrain that referenced this issue Feb 1, 2019

Travis: Avoid apt complaining about public key 6B05F25D762E3157
Also see

git-lfs/git-lfs#3474 (comment)
Signed-off-by: Sebastian Schuberth <sebastian.schuberth@here.com>

sschuberth added a commit to heremaps/tin-terrain that referenced this issue Feb 1, 2019

Travis: Avoid apt complaining about public key 6B05F25D762E3157
Also see

git-lfs/git-lfs#3474 (comment)
Signed-off-by: Sebastian Schuberth <sebastian.schuberth@here.com>

sschuberth added a commit to heremaps/tin-terrain that referenced this issue Feb 1, 2019

Travis: Avoid apt complaining about public key 6B05F25D762E3157
Also see

git-lfs/git-lfs#3474 (comment)
Signed-off-by: Sebastian Schuberth <sebastian.schuberth@here.com>

sschuberth added a commit to heremaps/tin-terrain that referenced this issue Feb 1, 2019

Travis: Avoid apt complaining about public key 6B05F25D762E3157
Also see

git-lfs/git-lfs#3474 (comment)

Signed-off-by: Sebastian Schuberth <sebastian.schuberth@here.com>
@Gilkshell

This comment has been minimized.

Copy link

Gilkshell commented Feb 1, 2019

Running 'sudo apt-get update' issues: W: GPG error: https://packagecloud.io/github/git-lfs/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B05F25D762E3157
W: The repository 'https://packagecloud.io/github/git-lfs/ubuntu xenial InRelease' is not signed. I've tried the @ScottMcCormack command but it issues: gpg: requesting key 762E3157 from hkp server keyserver.ubuntu.com
?: [fd 4]: read error: Connection reset by peer
gpgkeys: HTTP fetch error 7: couldn't connect: eof
gpg: no valid OpenPGP data found.
From reading comments above it seems like this has been solved for most - what's the secret sauce?

@Gilkshell

This comment has been minimized.

Copy link

Gilkshell commented Feb 1, 2019

I was able to solve my problem with command: sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 6B05F25D762E3157. Note the addition of port 80. Having got the key the apt-get update works fine. Reference: https://tinyurl.com/yb5cmvvh

@rrmhearts

This comment has been minimized.

Copy link

rrmhearts commented Feb 7, 2019

Running the following command looks to have fixed this issue for me:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6B05F25D762E3157

This worked for me. I'm on Ubuntu 16.04.5 LTS

@abferm

This comment has been minimized.

Copy link

abferm commented Feb 8, 2019

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 6B05F25D762E3157

I had to use this format on Ubuntu 18.04.1 LTS (bionic).

@ffes

This comment has been minimized.

Copy link

ffes commented Feb 11, 2019

On WSL it fails, but that seems to be a WSL problem in (at least) 1803. As mentioned in Microsoft/WSL#3696 (dup of MicrosoftDocs/azure-docs-cli#1181) it should be fixed in 1809.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment