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 key error ~ NO_PUBKEY #263

Closed
LouDnl opened this issue Jan 5, 2024 · 9 comments
Closed

GPG key error ~ NO_PUBKEY #263

LouDnl opened this issue Jan 5, 2024 · 9 comments

Comments

@LouDnl
Copy link
Contributor

LouDnl commented Jan 5, 2024

Issue when using nanasess/setup-chromedriver@v2

  | ##setup chromedriver
  | [command]/run/act/actions/nanasess-setup-chromedriver@v2/lib/setup-chromedriver.sh  linux64
  | dpkg-query: package 'google-chrome' is not installed and no information is available
  | Use dpkg --info (= dpkg-deb --info) to examine archive files.
  | Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
  | Executing: /tmp/apt-key-gpghome.5vFEFduHjd/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys A040830F7FAC5991
  | gpg: key A040830F7FAC5991: public key "Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com>" imported
  | gpg: Total number processed: 1
  | gpg:               imported: 1
  | Installing google-chrome-stable...
  | Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
  | Get:2 https://dl.google.com/linux/chrome/deb stable InRelease [1825 B]
  | Get:3 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease [3631 B]
  | Get:4 https://ppa.launchpadcontent.net/git-core/ppa/ubuntu jammy InRelease [23.8 kB]
  | Get:5 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
  | Err:2 https://dl.google.com/linux/chrome/deb stable InRelease
  |   The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4EB27DB2A3B88B8B

Repro:
Any version of nanasess/setup-chromedriver@v2

Proposed fix:
Update A040830F7FAC5991 to 4EB27DB2A3B88B8B in setup-chromedriver.sh

${sudo} apt-key adv --keyserver keyserver.ubuntu.com --recv-keys A040830F7FAC5991

@nanasess
Copy link
Owner

nanasess commented Jan 5, 2024

@LouDnl
Thanks for the detailed issue.
I just now tried running GitHub Actions and could not reproduce it.
Please let me know what environment can reproduce this.
see https://github.com/nanasess/setup-chromedriver/actions/runs/7380602768/job/20203005029#step:13:13

@LouDnl
Copy link
Contributor Author

LouDnl commented Jan 5, 2024

@LouDnl Thanks for the detailed issue. I just now tried running GitHub Actions and could not reproduce it. Please let me know what environment can reproduce this. see https://github.com/nanasess/setup-chromedriver/actions/runs/7380602768/job/20203005029#step:13:13

I'm running it in WSL2 ~ Ubuntu with Nectos Act: https://github.com/nektos/act

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy

@LouDnl
Copy link
Contributor Author

LouDnl commented Jan 5, 2024

I added a modified version (GPG KEY) of setup-chromedriver.sh to my workflow instead of your Action and just ran it on Github after a new push.

Output:

Run bash .github/workflows/chromedriver.sh
dpkg-query: package 'google-chrome' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key([8](https://github.com/thorax92/aorta/actions/runs/7424307096/job/20203637174#step:7:9))).
Executing: /tmp/apt-key-gpghome.tFTzoa21WB/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 4EB27DB2A3B88B8B
gpg: key 7721F63BD38B47[9](https://github.com/thorax92/aorta/actions/runs/7424307096/job/20203637174#step:7:10)6: 2 duplicate signatures removed
gpg: key 7721F63BD38B4796: "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" 1 new signature
gpg: Total number processed: 1
gpg:         new signatures: 1
CHROME_VERSION=120
VERSION=120.0.6099.[10](https://github.com/thorax92/aorta/actions/runs/7424307096/job/20203637174#step:7:11)9
Downloading https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json...
Installing ChromeDriver [12](https://github.com/thorax92/aorta/actions/runs/7424307096/job/20203637174#step:7:13)0.0.6099.109 for linux64
Downloading https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/120.0.6099.109/linux64/chromedriver-linux64.zip...
Installing chromedriver to /usr/local/bin
Chrome version:
Google Chrome 120.0.6099.109 
Chromedriver version:
ChromeDriver 120.0.6099.109 (3419140ab665596f21b385ce[13](https://github.com/thorax92/aorta/actions/runs/7424307096/job/20203637174#step:7:14)6419fde0924272-refs/branch-heads/6099@{#[14](https://github.com/thorax92/aorta/actions/runs/7424307096/job/20203637174#step:7:15)83})

@nanasess
Copy link
Owner

nanasess commented Jan 5, 2024

@LouDnl
Thank you so much!
Is it possible to Pull Request?

@LouDnl
Copy link
Contributor Author

LouDnl commented Jan 5, 2024

@LouDnl Thank you so much! Is it possible to Pull Request?

Will see what I can do for you

LouDnl added a commit to LouDnl/setup-chromedriver that referenced this issue Jan 5, 2024
@LouDnl
Copy link
Contributor Author

LouDnl commented Jan 7, 2024

@LouDnl Thank you so much! Is it possible to Pull Request?

you gonna use the pull request?

@nanasess
Copy link
Owner

nanasess commented Jan 7, 2024

@LouDnl
We are testing it now, so please be patient.

@nanasess
Copy link
Owner

nanasess commented Jan 7, 2024

@LouDnl
#264 has been merged.
Thanks for your contribution!

@nanasess nanasess closed this as completed Jan 7, 2024
@LouDnl
Copy link
Contributor Author

LouDnl commented Jan 9, 2024

Updated workflow to @master, works like a charm. Thanks for merging!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants