Workaround for Chrome found:
> there is difrent URL and GPG key paths on Fedora repo file than what i found
> online and editing the google-chrome.repo on details down i can layer google
> chrome and dont get any gpg signature errors and this is tested on F39
> silverblue and F40 beta silverblue
>
> ```[google-chrome]
> name=google-chrome
> baseurl=http://dl.google.com/linux/chrome/rpm/stable/$basearch
> enabled=1
> gpgcheck=1
> gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
> ```
>
> also at first installation […] edit the repo file and take gpg check 0
> install chrome and then put gpg check back to 1 and again all works so i
> guess using default repo files are still valid, but on first install gpg
> check need to be off and after that seems fine again to use
via:
https://discussion.fedoraproject.org/t/google-chrome-failed-update-due-to-signature-not-ok/83540/38
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2577#issuecomment-2027229021
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2577/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
