Hy!
I just updated a 15.1 KDE (manually changing repos to 15.3, then zypper dup --allow-vendor-change) as I did before on some machines (10 days ago or so…) and got a lot of warnings:
# 2021-05-19 15:05:54 GeoIP-data-1.6.12-6.3.1.noarch.rpm installed ok
# Additional rpm output:
# warning: /var/cache/zypp/packages/openSUSE-Leap-15.2/noarch/GeoIP-data-1.6.12-6.3.1.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY
#
2021-05-19 15:05:54|install|GeoIP-data|1.6.12-6.3.1|noarch||openSUSE-Leap-15.2|e7164b0deb17fe00d1e6dc6cb6cb7d68b122c8d9d7e7615a5d021cd7cb5dd8ed|
2021-05-19 15:05:55|install|MozillaFirefox-branding-openSUSE|68-lp153.4.22|x86_64||openSUSE-Leap-15.2|a58ef854cbed93fe5345365515cc7d0e95d529d0f8bd2f34682bfef1589da324|
# 2021-05-19 15:05:59 akonadi-mime-20.04.2-bp153.1.34.x86_64.rpm installed ok
# Additional rpm output:
# warning: /var/cache/zypp/packages/openSUSE-Leap-15.2/x86_64/akonadi-mime-20.04.2-bp153.1.34.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 65176565: NOKEY
#
2021-05-19 15:05:59|install|akonadi-mime|20.04.2-bp153.1.34|x86_64||openSUSE-Leap-15.2|3876281a7e7e281e2850e8ca124a7d580344b4b7781cbd57e684e949cb64b22e|
# 2021-05-19 15:06:02 alsa-ucm-conf-1.2.4-4.13.noarch.rpm installed ok
# Additional rpm output:
# warning: /var/cache/zypp/packages/openSUSE-Leap-15.2/noarch/alsa-ucm-conf-1.2.4-4.13.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY...
Tried it again on a second machine, again for a lot of packages I see these warnings.
I found a thread here from 2014, apparently not a big issue, but I would like to confirm
https://forums.opensuse.org/showthread.php/496213-zypper-up-found-no-key-but-still-installed-packages ------------------------------
PS:
zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
---+---------------------------+-----------------------------------------+---------+-----------+---------+-------------------------------------------------------------------------
1 | dvd | openSUSE_Leap_15.3 | No | ---- | ---- | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/
2 | openSUSE-Leap-15.2 | openSUSE-Leap-15.3 | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
3 | openSUSE_Leap_15.2 | Mozilla | No | ---- | ---- | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/
4 | openSUSE_Leap_15.2_1 | packman2 | No | ---- | ---- | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/
5 | repo-debug | openSUSE-Leap-15.3-Debug | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.3/repo/oss/
6 | repo-debug-non-oss | openSUSE-Leap-15.3-Debug-Non-Oss | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/
7 | repo-debug-update | openSUSE-Leap-15.3-Update-Debug | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.3/oss/
8 | repo-debug-update-non-oss | openSUSE-Leap-15.3-Update-Debug-Non-Oss | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.3/non-oss/
9 | repo-non-oss | openSUSE-Leap-15.3-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/
10 | repo-source | openSUSE-Leap-15.3-Source | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/
11 | repo-source-non-oss | openSUSE-Leap-15.3-Source-Non-Oss | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.3/repo/non-oss/
12 | repo-update | openSUSE-Leap-15.3-Update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss/
13 | repo-update-non-oss | openSUSE-Leap-15.3-Update-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/non-oss/
Sorry, TYPO! I updated from 15.2, not 15.1…
hcvv
May 19, 2021, 4:59pm
3
Your report on what you exactly did to upgrade is a bit scarce. It could be that you did correct, but shouldn’t one do a zypper clean and zypper ref?
I am not sure. but I see those message talk about packages from 15.2 repos. Looks like artifacts.
Hi
Perhaps consider the releasever option in upgrading…
https://en.opensuse.org/SDB:System_upgrade
This is a known bug. There’s a bug report on it, but I have not been following that bug report.
It happened to me when I did a test update (from Leap 15.0).
hcvv
May 19, 2021, 5:21pm
6
In any case, you could edit the Aliases of your repos. As long as they show 15.2, they are probably confusing.
BTW, I assume this better would have been a 15.3 problem instead of a 15.2 problem as you have chosen.
hcvv:
In any case, you could edit the Aliases of your repos. As long as they show 15.2, they are probably confusing.
BTW, I assume this better would have been a 15.3 problem instead of a 15.2 problem as you have chosen.
I don’t see any 15.2 in the repo names. Again:
zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
---+---------------------------+-----------------------------------------+---------+-----------+---------+-------------------------------------------------------------------------
1 | dvd | openSUSE_Leap_15.3 | No | ---- | ---- | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/
2 | openSUSE-Leap-15.2 | openSUSE-Leap-15.3 | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
3 | openSUSE_Leap_15.2 | Mozilla | No | ---- | ---- | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/
4 | openSUSE_Leap_15.2_1 | packman2 | No | ---- | ---- | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/
5 | repo-debug | openSUSE-Leap-15.3-Debug | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.3/repo/oss/
6 | repo-debug-non-oss | openSUSE-Leap-15.3-Debug-Non-Oss | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/
7 | repo-debug-update | openSUSE-Leap-15.3-Update-Debug | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.3/oss/
8 | repo-debug-update-non-oss | openSUSE-Leap-15.3-Update-Debug-Non-Oss | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.3/non-oss/
9 | repo-non-oss | openSUSE-Leap-15.3-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/
10 | repo-source | openSUSE-Leap-15.3-Source | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/
11 | repo-source-non-oss | openSUSE-Leap-15.3-Source-Non-Oss | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.3/repo/non-oss/
12 | repo-update | openSUSE-Leap-15.3-Update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss/
13 | repo-update-non-oss | openSUSE-Leap-15.3-Update-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/non-oss/
And the problem occured while I was on 15.2, updating to 15.3. I don’t assume this to happen in a native 15.3.
They were referring to the names in /etc/zypp/repos.d they contain the 15.2 reference
You can just rename them with a mv command.
hcvv
May 19, 2021, 5:43pm
9
suse_rasputin:
I don’t see any 15.2 in the repo names. Again:
zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
---+---------------------------+-----------------------------------------+---------+-----------+---------+-------------------------------------------------------------------------
1 | dvd | openSUSE_Leap_15.3 | No | ---- | ---- | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/
2 | openSUSE-Leap-15.2 | openSUSE-Leap-15.3 | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
3 | openSUSE_Leap_15.2 | Mozilla | No | ---- | ---- | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/
4 | openSUSE_Leap_15.2_1 | packman2 | No | ---- | ---- | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/
5 | repo-debug | openSUSE-Leap-15.3-Debug | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.3/repo/oss/
6 | repo-debug-non-oss | openSUSE-Leap-15.3-Debug-Non-Oss | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/
7 | repo-debug-update | openSUSE-Leap-15.3-Update-Debug | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.3/oss/
8 | repo-debug-update-non-oss | openSUSE-Leap-15.3-Update-Debug-Non-Oss | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.3/non-oss/
9 | repo-non-oss | openSUSE-Leap-15.3-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/
10 | repo-source | openSUSE-Leap-15.3-Source | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/
11 | repo-source-non-oss | openSUSE-Leap-15.3-Source-Non-Oss | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.3/repo/non-oss/
12 | repo-update | openSUSE-Leap-15.3-Update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss/
13 | repo-update-non-oss | openSUSE-Leap-15.3-Update-Non-Oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/non-oss/
I did not say (in fact typed) name , I typed Aliase s.
To help you in reading, I marked them red above in the quote.
I triple-checked again…
https://paste.opensuse.org/2686f674
no 15.2 left over…
And I just for the lulz tried again
sudo zypper ref
[sudo] password for root:
Repository 'openSUSE-Leap-15.3' is up to date.
Repository 'openSUSE-Leap-15.3-Non-Oss' is up to date.
Repository 'openSUSE-Leap-15.3-Update' is up to date.
Repository 'openSUSE-Leap-15.3-Update-Non-Oss' is up to date.
All repositories have been refreshed.
-----------------
sudo zypper dup --allow-vendor-change
Loading repository data...
Warning: Repository 'openSUSE-Leap-15.3-Update-Non-Oss' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
The following item is locked and will not be changed by any action:
Available:
amarok
Nothing to do.
Does this make sense at all?
hcvv
May 19, 2021, 7:09pm
11
suse_rasputin:
I triple-checked again…
SUSE Paste
no 15.2 left over…
Sorry, I give up. When you can not see 15.2 in the repo list you posted, I can not help you.
And the screenshot of YaST is useless for this, because it does not show Aliases at all.
In any case, forget it, as I said it is only confusing, but it can be any string, only the URL is relly important.
Miuku
May 19, 2021, 7:26pm
12
My guess; SUSE build key expired in October 2020 and was renewed. Your 15.1 did not have the new key and thus you are getting NOKEY since you skipped 15.2 which received the updated suse-build-key.
Note; this is just uneducated guessing here.
hcvv
May 19, 2021, 7:41pm
13
Miuku:
My guess; SUSE build key expired in October 2020 and was renewed. Your 15.1 did not have the new key and thus you are getting NOKEY since you skipped 15.2 which received the updated suse-build-key.
Note; this is just uneducated guessing here.
In his first post he reported going from 15.1 to 15.3.
In his second post he corrected this in going from 15.2 to 15.3
I am not sure that your theory is still valid knowing this.
hcvv:
Sorry, I give up. When you can not see 15.2 in the repo list you posted, I can not help you.
And the screenshot of YaST is useless for this, because it does not show Aliases at all.
In any case, forget it, as I said it is only confusing, but it can be any string, only the URL is relly important.
Yeah, I see it, but I have no idea where it comes from.
I changed the repos and the names in Yast, from 15.1 to 15.2 I edited some text files (/etc/zypp/something maybe? I don’t really remember and can’t find a howto for this, therefore I did it in Yast).
hcvv
May 19, 2021, 8:32pm
15
suse_rasputin:
Yeah, I see it, but I have no idea where it comes from.
I changed the repos and the names in Yast, from 15.1 to 15.2 I edited some text files (/etc/zypp/something maybe? I don’t really remember and can’t find a howto for this, therefore I did it in Yast).
O, you saw it.
I also do not know where it comes from. What I know is that the several mechanisms that create repo files have no common idea about what to use as Alias (and as larryr already explained, these are the names of the .repo files in /etc/zypp/repos.d).
IMO it should be a short lower case only (Unix/Linux people hate using capitals in commands) word that identifies the repo to the system manager, so he can use them easy in commands without much thought.
What we see in fact are all sorts of long names with all sorts of characters, possibly created by installations, upgrades, one-click installs and what else. In short to look at them makes an organized person shiver. Now, one can of course say “but it works”. OK, not my way of managing systems, but having an Alias that says 15.2 where the Name and the URI all say 15.3 is a bit too much for me.
So it is up to you to do something there or not. It will “just work” in both cases. But you might confuse yourself and others when posting such a list in the forums somewhere in the future (after you forgot this whole incident).
hcvv:
O, you saw it.
I also do not know where it comes from. What I know is that the several mechanisms that create repo files have no common idea about what to use as Alias (and as larryr already explained, these are the names of the .repo files in /etc/zypp/repos.d).
IMO it should be a short lower case only (Unix/Linux people hate using capitals in commands) word that identifies the repo to the system manager, so he can use them easy in commands without much thought.
What we see in fact are all sorts of long names with all sorts of characters, possibly created by installations, upgrades, one-click installs and what else. In short to look at them makes an organized person shiver. Now, one can of course say “but it works”. OK, not my way of managing systems, but having an Alias that says 15.2 where the Name and the URI all say 15.3 is a bit too much for me.
So it is up to you to do something there or not. It will “just work” in both cases. But you might confuse yourself and others when posting such a list in the forums somewhere in the future (after you forgot this whole incident).
File names might be the point:
On an older install (now on 15.3) I have
/etc/zypp/repos.d # ls -al
total 60
drwxr-xr-x 2 root root 4096 Apr 29 17:50 .
drwxr-xr-x 12 root root 4096 Jan 8 12:03 ..
-rw-r--r-- 1 root root 147 May 19 14:33 dvd.repo
-rw-r--r-- 1 root root 173 May 19 14:33 openSUSE-Leap-15.2.repo
-rw-r--r-- 1 root root 182 May 19 14:33 openSUSE_Leap_15.2.repo
-rw-r--r-- 1 root root 183 May 19 14:33 openSUSE_Leap_15.2_1.repo
-rw-r--r-- 1 root root 197 May 19 14:33 repo-debug-non-oss.repo
-rw-r--r-- 1 root root 200 May 19 14:33 repo-debug-update-non-oss.repo
-rw-r--r-- 1 root root 180 May 19 14:33 repo-debug-update.repo
-rw-r--r-- 1 root root 177 May 19 14:33 repo-debug.repo
-rw-r--r-- 1 root root 179 May 19 14:33 repo-non-oss.repo
-rw-r--r-- 1 root root 200 May 19 14:33 repo-source-non-oss.repo
-rw-r--r-- 1 root root 180 May 19 14:33 repo-source.repo
-rw-r--r-- 1 root root 182 May 19 14:33 repo-update-non-oss.repo
-rw-r--r-- 1 root root 162 May 19 14:33 repo-update.repo
On an install from SEP-2019 (now on 15.3) I have
/etc/zypp/repos.d # ls -al
total 60
drwxr-xr-x 2 root root 4096 Apr 29 17:50 .
drwxr-xr-x 11 root root 4096 Jan 8 12:03 ..
-rw-r--r-- 1 root root 135 May 19 17:09 dvd.repo
-rw-r--r-- 1 root root 173 May 19 17:09 openSUSE-Leap-15.2.repo
-rw-r--r-- 1 root root 171 May 19 17:09 packman2.repo
-rw-r--r-- 1 root root 179 May 19 17:09 repo-debug-non-oss.repo
-rw-r--r-- 1 root root 183 May 19 17:09 repo-debug-update-non-oss.repo
-rw-r--r-- 1 root root 162 May 19 17:09 repo-debug-update.repo
-rw-r--r-- 1 root root 157 May 19 17:09 repo-debug.repo
-rw-r--r-- 1 root root 171 May 19 17:09 repo-non-oss.repo
-rw-r--r-- 1 root root 160 May 19 17:09 repo-oss.repo
-rw-r--r-- 1 root root 182 May 19 17:09 repo-source-non-oss.repo
-rw-r--r-- 1 root root 160 May 19 17:09 repo-source.repo
-rw-r--r-- 1 root root 176 May 19 17:09 repo-update-non-oss.repo
-rw-r--r-- 1 root root 159 May 19 17:09 repo-update.repo
I’m not aware of any changes to these file names (lower/upper case)…
PS: Proof, that the machine is on 15.3
cat /etc/*-release
NAME="openSUSE Leap"
VERSION="15.3"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.3"
PRETTY_NAME="openSUSE Leap 15.3"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.3"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/
mwilck
June 24, 2021, 10:58am
17
The issue is described in the Leap 15.3 release notes , §2.1. In short, this wouldn’t occur if an update to the latest Leap 15.2 state was done immediately before doing the distro update to 15.3. If the NOKEY issue occurs (e.g. because the update had been forgotten), you can import the key manually from the openSUSE-build-key package:
rpm -import /usr/lib/rpm/gnupg/keys/gpg-pubkey-39db7c82-5847eb1f.asc
marel
June 27, 2021, 12:09pm
18
Based on this output it does not make sense.
Please run “sudo zypper -vv ref” that way we can maybe figure out what is going on.