Skip to content
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

GPG error: https://dl.yarnpkg.com/debian stable InRelease NO_PUBKEY E074D16EB6FF4DE3 #4453

Closed
boscowitch opened this issue Sep 14, 2017 · 41 comments

Comments

@boscowitch
Copy link

fails at apt-get update since this morning(European time) with:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Some index files failed to download. They have been ignored, or old ones used instead.

Tried readding the key from:
https://dl.yarnpkg.com/debian/pubkey.gpg

no change...

guess some key timedout or got thrown out.

OS:
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

atm installed Package version:
dpkg -s yarn
Package: yarn
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 3824
Maintainer: Yarn Developers yarn@dan.cx
Architecture: all
Version: 1.0.1-1
Recommends: nodejs
Conflicts: nodejs (<< 4.0.0)

@itskingori
Copy link

I'm having the same issue:

# Added the key
root@a7b7b8f09d84:/# apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 1646B01B86E50310
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.1YxGw8HlmN --no-auto-check-trustdb --trust-model always --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 1646B01B86E50310
gpg: requesting key 86E50310 from hkp server keyserver.ubuntu.com
gpg: key 86E50310: public key "Yarn Packaging <yarn@dan.cx>" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

# Confirming the key exists
root@a7b7b8f09d84:/# apt-key list
/etc/apt/trusted.gpg
--------------------
pub   4096R/86E50310 2016-10-05
uid                  Yarn Packaging <yarn@dan.cx>
sub   4096R/D50AF136 2016-10-05
sub   4096R/9D41F3C3 2016-10-05 [expires: 2017-10-05]
sub   4096R/FD2497F5 2016-10-30

# Updated my sources
root@a7b7b8f09d84:/# echo 'deb https://dl.yarnpkg.com/debian/ stable main' > /etc/apt/sources.list.d/yarn.list

# Updating package index fails
root@a7b7b8f09d84:/# apt-get update -y
Hit http://security.debian.org jessie/updates InRelease
Get:1 https://dl.yarnpkg.com stable InRelease [11.5 kB]
Get:2 http://security.debian.org jessie/updates/main amd64 Packages [546 kB]
Ign http://deb.debian.org jessie InRelease
Hit http://deb.debian.org jessie-updates InRelease
Hit http://deb.debian.org jessie Release.gpg
Ign https://dl.yarnpkg.com stable InRelease
Get:3 https://dl.yarnpkg.com stable/main amd64 Packages [5912 B]
Hit http://deb.debian.org jessie Release
Get:4 http://deb.debian.org jessie-updates/main amd64 Packages [23.1 kB]
Get:5 http://deb.debian.org jessie/main amd64 Packages [9063 kB]
Fetched 9649 kB in 5s (1618 kB/s)
Reading package lists... Done
W: GPG error: https://dl.yarnpkg.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3

@rzo1
Copy link

rzo1 commented Sep 14, 2017

confirmed. Same here.

@todeveni
Copy link

The signing key changed in yarnpkg/releases@d926b59

But that key isn't available (yet?) in keyservers.

gpg: requesting key B6FF4DE3 from hkp server keyserver.ubuntu.com
gpgkeys: key E074D16EB6FF4DE3 not found on keyserver

To add the latest key:
wget -qO - https://raw.githubusercontent.com/yarnpkg/releases/gh-pages/debian/pubkey.gpg | sudo apt-key add -

@viktorku
Copy link

Doing curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - again was enough.

@boscowitch
Copy link
Author

boscowitch commented Sep 14, 2017

Confirmed they fixed it. But this moring even readding it def. didn't work! I readded it in the morning and checked it now with ansible same server.
Readding the key now reported no change (now in the afternoon)
but it works now with the readed the key from the morning, so i guess there was a change in the key file but it took a while for the releases to be adjusted ?:

ansible ad hoc command used:
ansible -m apt_key -a "url=https://dl.yarnpkg.com/debian/pubkey.gpg state=present" TESTHOST

@millette
Copy link

New key should be good until 2019-01-01 according to #4253

@Daniel15
Copy link
Member

Sorry about this! I'm not sure how to improve the process at the moment, so I'll have to get some advice on it. The best practice is to rotate your signing keys periodically (eg. every year, or every two years), but I might need to get advice from other people that maintain package repositories to see how they handle it. Debian and Ubuntu both rotate their keys on each release, but that works well for those projects as they have a separate repo per release.

@dmke
Copy link

dmke commented Oct 5, 2017

@Daniel15, the deb-multimedia.org repository ships a deb-multimedia-keyring package, which contains and updates the keys.

Maybe you should get in contact with Christian Marillat (marillat at deb-multimedia.org), or better yet, drop a line into the dmo-discussion mailing list and ask for advice from someone who has done this in the past.

@hilbix
Copy link

hilbix commented Nov 1, 2017

This might be late to this "bug", but can you please:

  • Provide a signature of the new key, signed with the old key.
  • Give some advice how to check this against the old key.
  • And please show this procedure on your webpage, too.

Because without, the whole purpose of signed repositories is voided, as any hacker can provide the exact same information as you, but with some forged key.

Thanks.

PS: I think of some simple client procedure like following:

  • First, create some scratchdir:

      mkdir scratchdir
      cd scratchdir
    
  • Then download the new key along with it's sig:

     wget https://dl.yarnpkg.com/debian/pubkey.gpg
     wget https://dl.yarnpkg.com/debian/pubkey.gpg.sig
    
  • Now check integrity:

     gpg --keyring /etc/apt/trusted.gpg pubkey.gpg.sig
    
  • Then, do only if satisfied:

      sudo apt-key add pubkey.gpg
    

FYI: You are the only trustworthy source to authenticate the new key! So please provide some clear and secure upgrade path. Downloading the key from some "obscure" website (which might got hacked in the meanwhile, as https is no trustworthy source by itself, it only authenticates the transport, not the source) re-introduces the initial hen-egg-problem again, which already should have been solved, thanks to the existing (old and expired, but this is not really the problem here) key.

@Daniel15
Copy link
Member

Daniel15 commented Nov 1, 2017

Provide a signature of the new key, signed with the old key.

@hilbix - I can do this, but is it actually necessary? The new key is a subkey under exactly the same master key as the old one, so there's already implicit trust between the two. Anyone that can sign a message using the key can also add a subkey.

For future key rotations, I can post a Github issue containing the fingerprint of the new key, signed with the old one. Would that be sufficient?

. Downloading the key from some "obscure" website (which might got hacked in the meanwhile, as https is no trustworthy source by itself, it only authenticates the transport, not the source)

What about loading it from a key server (like https://pgp.mit.edu)? You could do that if you prefer.

@hilbix
Copy link

hilbix commented Nov 2, 2017

Thank you for noting the SubKey-Feature of OpenPGP which I was not aware of until today. I now read about it from https://wiki.debian.org/Subkeys (Beware! Here be Dragons!) and I can agree, you are completely right in what you say. The new subkey can be authenticated by the master-key of the expired old subkey.

But this is not very obvious (not to tell: Very well hidden in the most secret basement ever) for people, who know everything behind the Mathematics of PKI but so far nothing about GnuPG in special (is this only me in the entire universe?).

For other, who want to know, too, here is what I came up for Debian after several hours of googling around and reading manuals about GPG and so on, but for no much avail. Hence I did trial and error, so beware again: Here be dragons, too!

This solution:

  • Does not use the intransparent /etc/apt/trusted.gpg, as I think, this should be avoided at all cost if possible.
  • Instead it installs the pubkey into /etc/apt/trusted.gpg.d/ where it truely belongs in a portable and easy to manage way.
  • This also makes etckeeper very happy. You all use etckeeper already, right?

First, get everything in a scratch directory:

$ mkdir scratch
$ cd scratch
$ curl -o yarnpkg.gpg.pub https://dl.yarnpkg.com/debian/pubkey.gpg

Now verify it:

$ gpg yarnpkg.gpg.pub
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2016-10-05 [SC]
      72ECF46A56B4AD39C907BBB71646B01B86E50310
uid           Yarn Packaging <yarn@dan.cx>
sub   rsa4096 2016-10-05 [E]
sub   rsa4096 2016-10-05 [S] [expired: 2017-10-05]
sub   rsa4096 2016-10-30 [S]
sub   rsa4096 2017-09-10 [S] [expires: 2019-01-01]

$ gpg /etc/apt/trusted.gpg
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2016-10-05 [SC]
      72ECF46A56B4AD39C907BBB71646B01B86E50310
uid           Yarn Packaging <yarn@dan.cx>
sub   rsa4096 2016-10-05 [E]
sub   rsa4096 2016-10-05 [S] [expired: 2017-10-05]
sub   rsa4096 2016-10-30 [S]

Check, that both fingerprints of the master key are the same (here 72ECF46A56B4AD39C907BBB71646B01B86E50310).

If so, remove the old key and install the new one and commit etckeeper (please note that the sequence of the two apt-key-calls matters):

sudo apt-key del 72ECF46A56B4AD39C907BBB71646B01B86E50310
sudo apt-key --keyring /etc/apt/trusted.gpg.d/yarnpkg.gpg add yarnpkg.gpg.pub
sudo etckeeper commit 'updated key of yarnpkg.com'

Now the issues of apt-get update should be gone.

For me my question is answered, thank you very much ;)

notthatbreezy added a commit to raster-foundry/raster-foundry-docs that referenced this issue Dec 19, 2017
notthatbreezy added a commit to raster-foundry/raster-foundry-docs that referenced this issue Dec 19, 2017
* Update dependency pinning to be slightly more restrictive

* Update readme instructions

* Add yarn GPG key manually

See: yarnpkg/yarn#4453
@wjordan
Copy link

wjordan commented Apr 28, 2018

To automatically refresh all current apt-secure repository PGP keys with the gpg --refresh-keys command, invoked via apt-key adv:

(as root or via sudo, replacing ha.pool.sks-keyservers.net with the PGP keyserver of choice)

apt-key adv --refresh-keys --keyserver ha.pool.sks-keyservers.net

@mrgab0
Copy link

mrgab0 commented May 8, 2018

just an wget...

it was fun...! thank you

rclarkburns added a commit to castiron/puppet-yarn that referenced this issue May 15, 2018
Because everyone is sick of yarnpkg/yarn#4453
@Koli14
Copy link

Koli14 commented Jan 1, 2019

I solved the problem with the alternative installation script:
curl -o- -L https://yarnpkg.com/install.sh | bash
Then followed the suggestions in it.

@nitrag
Copy link

nitrag commented Jan 1, 2019

Latest keys are expired:

# curl -o yarnpkg.gpg.pub https://raw.githubusercontent.com/yarnpkg/releases/gh-pages/debian/pubkey.gpg
# gpg yarnpkg.gpg.pub
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2016-10-05 [SC]
      72ECF46A56B4AD39C907BBB71646B01B86E50310
uid           Yarn Packaging <yarn@dan.cx>
sub   rsa4096 2016-10-05 [E]
sub   rsa4096 2016-10-05 [S] [expired: 2017-10-05]
sub   rsa4096 2016-10-30 [S] [expired: 2019-01-01]
sub   rsa4096 2017-09-10 [S] [expired: 2019-01-01]

@Daniel15
Copy link
Member

Daniel15 commented Jan 1, 2019

That's being tracked in #6865

danigunawan added a commit to danigunawan/Computer-Vision-and-Deep-Learning-Setup that referenced this issue Jan 5, 2019
Development Area(s) of Interest*
Accelerated Computing
Autonomous Machines
Deep Learning
Design & Visualization
Game Development
Self Driving Cars
Smart Cities
Virtual Reality 


Application Domain :
- Image Classification
- Facial Recognition
- Action Recognition
- Big Data
- Natural Language Processing
- Medical
- Speech Recognition
- Object Recognition
- Machine Learning Algorithms/Research

Deep Learning Framework * :
- Caffe
- Caffe2
- Chainer
- CNTK(Microsoft Cognitive Toolkit)
- Deeplearning4j
- Keras
- MATLAB
- MxNet
- TensorFlow
- Theano
- Torch/PyTorch


TRELLO : https://trello.com/b/wKBiqfM7/data-scientist

### ROADMAP DATA SCIENTIST ###
https://github.com/MrMimic/data-scientist-roadmap
https://github.com/bulutyazilim/awesome-datascience

REFF: 
https://www.petanikode.com/python-virtualenv/

TOOLS :
MINICONDA
ANACONDA # https://conda.io/docs/user-guide/install/linux.html, #https://github.com/danigunawan/Fullstack-Python-Django-Dev/blob/master/16_djangolevelone/dev%20tools/1.django%20level%20one.txt

ENV : 
- PIP
- VIRTUALENV

DEEP LEARN :
- YOLO
- TENSORFLOW
- OPENCV

INSTALL PYTHON UBUNTU 16.04
============================
sudo apt-get -y install python
sudo apt-get -y install python3
which python
ls -l /usr/bin/python

1. PIP
REFF :
https://www.rosehosting.com/blog/how-to-install-pip-on-ubuntu-16-04/
https://www.abiraf.com/blog/modules-python-yang-wajib-dimiliki---virtualenv-dan-pip
https://www.petanikode.com/python-virtualenv/

sudo apt-get update && sudo apt-get -y upgrade
sudo apt-get install python-pip
pip -V # PY2
pip3 -V # PY3
pip search package_name
pip install package_name
pip uninstall package_name
pip --help

#ALTERNATE
sudo easy_install pip # PY2
sudo easy_install pip3 # PY3
	

2. VIRTUAL ENV
apt install virtualenv
apt install python-virtualenv # PY 2
apt install python3-virtualenv # PY 3

# Alternate
sudo pip install virtualenv # install ENV LEWAT PIP

# Latest Version Beta No Stable
sudo pip install https://github.com/pypa/virtualenv/tarball/develop

# With Curl
curl -O https://pypi.python.org/packages/source/v/virtualenv/virtualenv-X.X.tar.gz
tar xvfz virtualenv-X.X.tar.gz
cd virtualenv-X.X
sudo python setup.py install

# CEK VIRTUAL ENV
which virtualenv
virtualenv --version

# Membuat Virtual ENV
mkdir my-project
cd my-project
virtualenv my-env

Saat kita mengetik perintah virtualenv my-env, virtualenv akan otomatis membuat lingkungan virtual dan direktori baru bernama my-env.

my-project/
└── my-env/
    ├── bin
    ├── include
    ├── lib
    ├── local
    └── pip-selfcheck.json

# Aktifkan Virtual Env
source my-env/bin/activate 

atau

. my-env/bin/activate

# install Flask With PIP
pip install Flask
flask --version

jika error : 
. my-env/bin/activate # masuk dulu ke env agar flask bisa
flask --version


######## DEEP LEARNING AND COMPUTER VISION #########

# Awesome Deep Learning (RECOGNITION)
https://github.com/daicoolb/Awesome-Object-Detections
https://github.com/amusi/awesome-object-detection
https://github.com/kjw0612/awesome-deep-vision
https://www.pyimagesearch.com

# Video Analytics
- Yolo # Realtime Object Detection Darknet
- OpenFace # Face Recognition 

# REQUIRMENT SPEC DEEP LEARNING :
- NVDIA GPU, Drivers
- CUDA
- cuDDN Libraries
- Tensorflow
- Darknet YOLO
- Theano
- Linux Ubuntu 16.04, 17.10, 18.04
- Keras
- OpenCV
- Raspberry + Camera

## INSTALL ENVIRONMENT DEEP LEARNING & COMPUTER VISION

# INSTALL NVDIA + CUDA 9 UBUNTU 16.04 ON LAPTOP 
https://gist.github.com/zhanwenchen/e520767a409325d9961072f666815bb8#install-nvidia-graphics-driver-via-apt-get
https://www.linuxsec.org/2018/05/cara-install-driver-nvidia-terbaru-di.html
https://medium.com/@omar.merghany95/how-to-install-tensorflow-gpu-with-cuda-toolkit-9-0-and-cudnn-7-2-1-on-aws-ec2-ubuntu-16-04-c46b469a7358
https://medium.com/@yifanguo1129/install-cuda-9-0-and-cudnn-7-2-on-ubuntu-18-04-d9a7aeb89105
https://askubuntu.com/questions/967332/how-can-i-install-cuda-9-on-ubuntu-17-10
https://askubuntu.com/questions/995542/installing-cuda-8-on-ubuntu-16-unable-to-locate-package-cuda
https://www.pyimagesearch.com/2017/09/27/setting-up-ubuntu-16-04-cuda-gpu-for-deep-learning-with-python/
https://www.pytorials.com/how-to-install-tensorflow-gpu-with-cuda-10-0-for-python-on-ubuntu/2/
http://www.advancedclustering.com/act_kb/installing-nvidia-drivers-rhel-centos-7/ # INSTALL ON CENTOS
https://davidwpearson.wordpress.com/2017/12/21/installing-nvidias-cuda-9-1-on-fedora-27/ # INSTALL ON FEDORA 
https://ddkang.github.io/2018/11/05/installing-cuda.html
http://security-plus-data-science.blogspot.com/2018/01/setting-up-cuda-9-on-fedora-27.html
https://nicolas-bettenburg.com/2018-08-18-ubuntu-18-04-deep-learning-box/
https://qiita.com/ishizakiyu/items/bcf1b76f1f4f02b0ac57

Install CUDA 9.2, cuDNN 7.2.1, Anaconda and PyTorch on Ubuntu 16.04 :

https://gist.github.com/kylemcdonald/3ae0b88a1bf91afc00ba441fe6823a17



- INSTALL DRIVER NVDIA (AUTOMATIS RECOMMENDED)

sudo ubuntu-drivers autoinstall # akan menginstall CUDA AUTOMATIS

- INSTALL DRIVER NVDIA MANUAL (MANUAL)
ubuntu-drivers devices # CEK 
sudo apt install nvidia-driver-390 # 390 seri di ubuntu driver cek atau kadang 396 tergantung di pengeckan

- INSTALL DRIVER NVDIA VERSI BETA (MANUAL)
sudo add-apt-repository ppa:graphics-drivers/ppa
ubuntu-drivers devices # CHECK KEMBALI

# INSTALL ENV DEEP LEARNING

https://github.com/heethesh/Computer-Vision-and-Deep-Learning-Setup

- INSTALL CUDA TOOLKIT
sudo apt install nvidia-cuda-toolkit
nvcc --version

- INSTALL TENSORFLOW

######## END DEEP LEARNING AND COMPUTER VISION #########



######## DEEP LEARNING (CHATBOT) #########

######## END DEEP LEARNING (CHATBOT) #########



##### BIG DATA #####
- Hadoop


###### IMPROVISATION AND EXPLORE ######

## YOLO EXPLORE ##
# SUPERVISELY CLUSTER
https://www.youtube.com/watch?v=el07zd4Dzsg

# MEDIA STREAMING SERVER

@ REFF AWESOME : 
https://github.com/topics/media-server
https://github.com/Kickball/awesome-selfhosted
https://github.com/ebu/awesome-broadcasting
https://github.com/manuzhang/awesome-streaming

@ List Media Server Streaming :
~ Comparison : https://en.wikipedia.org/wiki/Comparison_of_streaming_media_systems
- wowza
- kurento
- red5
- nginxRTMP
- Ant Media Server
- OpenVidu
- Jitsi
- Flussonic
- Kaltura
- Node RTSP RTMP Server
- https://github.com/R0GGER/mistserver
- helixproduction
- https://github.com/daniulive/SmarterStreaming
- https://hackernoon.com/build-live-video-streaming-server-use-ffmpeg-nginx-rtmp-module-nodejs-82e1bb58949e

@ Referensi Spec Server Streaming Yang Bagus
- Low Latency WebRTC 
- Adaptive Bitrate 
- Hardware Encoding(GPU) 
- Cluster 
- Live Publishing to Periscope, Facebook & Youtube 
- All Community Edition Features
- RTMP, RTSP, MP4, HLS
- WebRTC to RTMP Adapter
- Live Publishing To Periscope
- 360 Degree Live & VoD Streams
- Management Dashboard

@ Adaptive Streaming With Nginx
https://licson.net/post/setting-up-adaptive-streaming-with-nginx/ 

@ Tools :
- Openbroadcaster
- CasparCG # https://casparcgforum.org/t/simple-video-playout/61, #https://drive.google.com/drive/u/1/folders/12xcrh-LiAatzf6ppW4pyQthokhi55qSN
- Wirecast
- VLC
- FFMPEG
- handbrake # Transcoding

@ Transcoding : 
-

# How Streaming RTSP / RTMP on client side ex: vlc client with rtmpt://ipdaddress:port 

# POSTING IMAGE YOLO ON PHP INSERT DB
https://stackoverflow.com/questions/45792720/cant-execute-yolo-darknet-from-php-exec-predictions-png-never-appears

# MESSAGE QUEUE (ANTRIAN)
- KAFKA
- REDIS

## END YOLO EXPLORE ##

## ABSENCE FACE RECOGNITION ## 
https://github.com/topics/attendance-system
https://github.com/yodist/face-recognition-lbph
## END ABSENCE FACE RECOGNITION ## 


###### TROUBLE SHOOTING ######
1. Pip is not working: ImportError: No module named 'pip._internal'
REFF : https://askubuntu.com/questions/1025189/pip-is-not-working-importerror-no-module-named-pip-internal

2. GPG error: https://dl.yarnpkg.com/debian stable InRelease NO_PUBKEY E074D16EB6FF4DE3 #4453 
yarnpkg/yarn#4453

- Solution : 
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - 

###### BENCHMARK PLATFORM ######
https://lewatmana.com/kota/jakarta-pusat/
@a-lang
Copy link

a-lang commented Jan 6, 2019

The gpg key at the official site has been updated, just follow the commands below to add it.

wget -O yarnpkg.gpg.pub https://dl.yarnpkg.com/debian/pubkey.gpg
gpg yarnpkg.gpg.pub #just check the expired date of the key
sudo apt-key add yarnpkg.gpg.pub

@Tpojka
Copy link

Tpojka commented Jan 11, 2019

This solution is working. Thanks @viktorku

@benwiley4000
Copy link

@millette your comment about the key expiring january 1 probably helps explain why my OS just exploded.. thanks! all fixed now (thanks @viktorku)

@zzvara
Copy link

zzvara commented Jan 17, 2019

None of the solutions posted above work for me on Linux 4.4.0-17763-Microsoft #253-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux.

W: GPG error: https://dl.bintray.com/sbt/debian  Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 99E82A75642AC823
E: The repository 'https://dl.bintray.com/sbt/debian  Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Target Packages (Packages) is configured multiple times in /etc/apt/sources.list.d/sbt.list:1 and /etc/apt/sources.list.d/sbt.list:2
W: Target Translations (en) is configured multiple times in /etc/apt/sources.list.d/sbt.list:1 and /etc/apt/sources.list.d/sbt.list:2

@Daniel15
Copy link
Member

Daniel15 commented Jan 17, 2019

@zzvara That's a completely different repo (dl.bintray.com/sbt/) that's unrelated to Yarn. Speak to the owner of that repo. :)

@zzvara
Copy link

zzvara commented Jan 17, 2019

This is the second biggest embarrassment of my life probably. (However, the package still not found, I have to look into it some more.)

@i-fail
Copy link

i-fail commented Mar 3, 2019

I'm having a trouble with this on Ubuntu 16.04.6.
All the above solutions failed.

@Daniel15
Copy link
Member

Daniel15 commented Mar 3, 2019

@i-fail Please post the exact output.

@i-fail
Copy link

i-fail commented Mar 3, 2019

# apt-get update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Hit:2 http://archive.canonical.com/ubuntu xenial InRelease
Hit:3 http://ppa.launchpad.net/ondrej/apache2/ubuntu xenial InRelease
Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:5 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Fetched 218 kB in 1s (176 kB/s)
Reading package lists... Done
...
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?
E: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease
E: Some index files failed to download. They have been ignored, or old ones used instead.
...

@Daniel15
Copy link
Member

Daniel15 commented Mar 3, 2019

The error message literally tells you what's wrong :)

E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

apt install apt-transport-https will fix that.

@i-fail
Copy link

i-fail commented Mar 3, 2019

Thank you! That worked, but now I'm getting this error:
#6900

@WebAhmed
Copy link

WebAhmed commented Feb 4, 2020

Doing curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - again was enough.

@viktorku thank you! that was the only thing that worked for me.

@Daniel15
Copy link
Member

Daniel15 commented Feb 4, 2020

Yes, this is currently mentioned in #7866 which is (temporarily) pinned in the repo.

@jaeminkim87
Copy link

@viktorku Thank you!!

@lohhans
Copy link

lohhans commented Feb 19, 2020

The gpg key at the official site has been updated, just follow the commands below to add it.

wget -O yarnpkg.gpg.pub https://dl.yarnpkg.com/debian/pubkey.gpg
gpg yarnpkg.gpg.pub #just check the expired date of the key
sudo apt-key add yarnpkg.gpg.pub

It's worked!! thks

@Jonathan0wh
Copy link

For anyone who saw this:

I also encountered this problem on Windows 10 version 1909, wsl 1.
Following this guide https://docs.microsoft.com/en-us/windows/wsl/install-win10 to upgrade to Windows 10 version 2004 and wsl2 resolved it.

@defigor
Copy link

defigor commented Jan 24, 2021

Hi All,
I wonder, if anyone experiencing the same issue, but we started (today, yesterday everything was working correctly) we are getting the following error message when executing curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -:

gpg: [don't know]: partial length invalid for packet type 63
gpg: read_block: read error: Invalid packet
gpg: import from '[stdin]' failed: Invalid keyring

We use ubuntu 18.04

@Daniel15
Copy link
Member

Sorry @defigor, I was trying to bump the expiry date of the key and I think I hit https://dev.gnupg.org/T3194 (the exported key worked fine on Windows but not Linux). I'll re-export the public key, which should fix it.

@Daniel15
Copy link
Member

@defigor Can you please try it again? I just tested on a fresh virtual machine and the public key file looks good now.

@defigor
Copy link

defigor commented Jan 24, 2021

@Daniel15 it works now, many many thanks!

@serge-salamanka
Copy link

Good day!

Having issue. Trying to resolve.


W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.

@serge-salamanka
Copy link

resolved by

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -

@alana314
Copy link

alana314 commented Feb 3, 2021

Also running into this issue in Codebuild using Ubuntu, and curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - is already in our buildspec.yml file and it doesn't resolve

@alana314
Copy link

alana314 commented Feb 3, 2021

Actually curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - did work for me but I had to place it above any apt-get commands or they will fail

@yarnpkg yarnpkg locked as resolved and limited conversation to collaborators Feb 4, 2021
@merceyz
Copy link
Member

merceyz commented Feb 4, 2021

See #7866

kingpinzs referenced this issue in yarnpkg/releases Jan 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests