Skypeforlinux GPG key blocks other packages?

Hello All,

I have Skye for Linux installed on the system and every time there’s a new package available and try to update the system I get the following error message:

The GPG keys listed for the “skype (stable)” repository are already installed but they are not correct for this package.
GPG Keys are configured as: <link below in the repo file, forum doesn’t allow me to post more than 2>

I downloaded the SKYPE-GPG-KEY installed it with gpg --import but it’s still the same error.

$ cat /etc/yum.repos.d/skype-stable.repo
name=skype (stable)
baseurl=Index of /rpm/stable

I’d prefer to keep the gpgcheck enabled and solve the key issue.

Also if it skypforlinux update comes with other package updates than “dnf update” won’t install those packages because of the Skype GPG error?

dnf update

Transaction Summary

Install 2 Packages
Upgrade 31 Packages <----------------------------------

(31/33): skypeforlinux_8.89.0.403-1.x86_64.rpm 1.5 MB/s | 120 MB 01:18

The GPG keys listed for the “skype (stable)” repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository… Failing package is: skypeforlinux-
GPG Keys are configured as: <same as above, forum doesn’t allow me to put more than 2 in a post>
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.

dnf clean packages

33 files removed <------------------------------

Thank you.

An invalid GPG key will halt an entire dnf operation. If you don’t want it to, you have a few options:

  1. Disable gpg checking from the skype repo (not recommended)
  2. Disable gpg checking from the skype repo and also keep it disabled and temporarily enable it when you want to update (also not recommended, but it would stop dnf from halting regular updates)
  3. Use the flatpak version of skype

I would recommend that the invalid GPG key be reported to the Skype maintainers either way.

OK, but how did it get there, where did the GPG keys come from, is it 100% open source, did you install it as root?

Thank you guys. My biggest concern is why a package with invalid GPG key is blocking the installation of other legit updates until I figured what to do with that single one and than I have to re-run the full update again.

Is this behaviour is by design or can it be changed somewhow and leave only the package with the issue uninstalled?
After I disabled GPG check and re-run dnf update all 46 update package gets installed:

Total size: 228 M
Downloading Packages:
[SKIPPED] cockpit-packagekit-264.2-1.el9_0.noarch.rpm: Already downloaded                                                                                                                      
[SKIPPED] ostree-libs-2022.5-1.el9_0.x86_64.rpm: Already downloaded                                                                                                                            
[SKIPPED] ostree-2022.5-1.el9_0.x86_64.rpm: Already downloaded                                                                                                                                 
[SKIPPED] kernel-headers-5.14.0-70.30.1.el9_0.x86_64.rpm: Already downloaded                                                                                                                   
[SKIPPED] zlib-devel-1.2.11-32.el9_0.x86_64.rpm: Already downloaded                                                                                                                            
[SKIPPED] faad2-libs-2.10.1-1.el9.x86_64.rpm: Already downloaded                                                                                                                               
[SKIPPED] skypeforlinux_8.90.0.405-1.x86_64.rpm: Already downloaded                                                                                                                            
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                                        1/1 
  Upgrading        : zlib-1.2.11-32.el9_0.x86_64                                                                                                                                          1/109 
  Upgrading        : openssl-libs-1:3.0.1-43.el9_0.x86_64                                                                                                                                 2/109 
  Upgrading        : lua-libs-5.4.2-4.el9_0.3.x86_64                                                                                                                                      3/109 
  Upgrading        : rpm-                                                                                                                                       4/109 
  Upgrading        : rpm-libs-

Thank you.