installation in ubuntu is not working

[AbhishekVermaKT]

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]

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]

Seeing the issue as well on ubuntu 16.04

[bk2204]

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]

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

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

[bk2204]

Okay, great. Sorry about the inconvenience.

[ffes]

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]

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]

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

[stevencrader]

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]

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.

[gkapfham]

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!