Some packages with _invalid key ID_ on Lx3.0

Here is from latest update log:

/var/cache/urpmi/rpms/gnuplot-5.2.2-2-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Tue Mar  6 17:13:52 2018, Key ID 8b355e10273b1147))
/var/cache/urpmi/rpms/gnuplot-doc-5.2.2-2-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Tue Mar  6 17:13:54 2018, Key ID 8b355e10273b1147))
/var/cache/urpmi/rpms/gnuplot-mode-5.2.2-2-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Tue Mar  6 17:13:53 2018, Key ID 8b355e10273b1147))
/var/cache/urpmi/rpms/gnuplot-nox-5.2.2-2-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Tue Mar  6 17:13:53 2018, Key ID 8b355e10273b1147))
/var/cache/urpmi/rpms/lib64archive16-3.3.2-3-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Sat Mar 10 10:49:23 2018, Key ID 53452bb24e09750e))
/var/cache/urpmi/rpms/cpio-3.3.2-3-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Sat Mar 10 10:49:23 2018, Key ID 53452bb24e09750e))
/var/cache/urpmi/rpms/lib64evdev2-1.5.9-1-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Sat Mar 10 10:35:57 2018, Key ID 83e54831213935d1))
/var/cache/urpmi/rpms/lib64input10-1.10.2-1-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Sat Mar 10 10:37:17 2018, Key ID a5145270929c1af6))
/var/cache/urpmi/rpms/libinput-1.10.2-1-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Sat Mar 10 10:37:17 2018, Key ID a5145270929c1af6))
/var/cache/urpmi/rpms/tar-3.3.2-3-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Sat Mar 10 10:49:23 2018, Key ID 53452bb24e09750e))
1 Like

I saw the same behaviour here.

Chris

1 Like

I had same with flash-player-plugin, flash-player-plugin-kde, and chromium-pepper-flash earlier today.

Wonder if something has gone wrong with ABF or elsewhere? Anyway just updated another system and the list is considerably expanded:

Invalid-key-list.txt (6.6 KB)

Edit: Went back and posted the list as a file rather than code as a reminder to myself of “Best practices” and to establish better habits. :broccoli:

yes looks like since the abf changes for new rpm the rpms are not getting re-signed when published.

2 Likes

Thanks, I was wondering. Not particularly concerning for me but we’re likely to hear from users here soon.

Anyway it’s reported.

You are installing packages from /var/cache/urpmi/rpms this means you have downloaded these already. I may asume you have downloaded packages from /testing and when they got moved to /updates you still installed these from your local cache.

Anyways i’ll check if these files are signed on ABF side.

2 Likes

To be on the safe side, check /var/cache/urpmi/rpms/ every time you run an update and clear it all - unless you have any reason for saving some packages in such a case you can move them elsewhere from this directory previously.

2 Likes

Thanks.

No they are from the time and date listed. It is because I use urpmi --auto-updates --test which downloads all packages first (to /var/cache/urpmi/rpms). Same as would happen if I used urpmi --auto-update --download-all. But the steps are done at the same time one after the other. Unless I made a mistake or forgot something:cold_sweat:

I use urpmi --clean -av

Edit: If you use testing repos they need to be enabled when you run this.

1 Like

Mine would be an evergreen suggestion, if I may :wink:
Sometimes you may find there .rpm files which were not installed although downloaded (by --test option) for whatever reason (conflicts or such) and they would keep staying in /var/cache/urpmi/rpms/ limbo.
Not sure if --clean option does the trick, I admit that I never run it. Will test next time.

2 Likes

Worth us testing but I am pretty sure it does. If you run it with verbose output (-v) it tells us:

# urpmi --clean -av
...
cleaning /var/cache/urpmi/partial and /var/cache/urpmi/rpms
1 Like

If you say, I don’t doubt then.

:+1:

Postedit

I wrongly understood before that you add --clean to urpmi --auto-update command. Now I learn that it’s standalone command. Thanks

2 Likes

Here is a log.
You will see I don’t have any testing repo and it occurs while first run of
urpmi --auto-update --test
after command
urpmi --clean -av

konsole-agg20180315.txt (131,8 KB)

1 Like

Packages are from cache because I tested twice before to open this post. Each time I removed all packages in cache with rm -f /var/cache/urpmi/rpms/*rpm, finally I kept them in cache to copy and paste log here. No packages from testing is installed in that machine, I use only official repositories and my personal, of course, but none of these packages are from my personal.

Postedit: here is from today update:

# rm -f /var/cache/urpmi/rpms/*rpm
# urpmi --auto-update
medium "main" is up-to-date
medium "main updates" is up-to-date
medium "main32" is up-to-date
medium "main32 updates" is up-to-date
medium "contrib" is up-to-date
medium "contrib updates" is up-to-date
medium "contrib32" is up-to-date
medium "contrib32 updates" is up-to-date
medium "restricted" is up-to-date
medium "restricted updates" is up-to-date
medium "restricted32" is up-to-date
medium "restricted32 updates" is up-to-date
medium "mandian_personal" is up-to-date
To satisfy dependencies, the following packages are going to be installed:
 Package                        Version      Release       Dist  DEpoch Arch 
(medium "main updates")
 kcontacts                      17.12.2      3             omv   2015.0 x86_64 
 kdialog                        17.12.2      1             omv   2015.0 x86_64 
 lib64KF5Contacts-devel         17.12.2      3             omv   2015.0 x86_64 
 lib64KF5Contacts5              17.12.2      3             omv   2015.0 x86_64 
26KB of additional disk space will be used.
334KB of packages will be retrieved.
Proceed with the installation of the 4 packages? (Y/n) y
    http://downloads.openmandriva.org/mirrors/openmandriva.3.0.x86_64.list: media/main/updates/lib64KF5Contacts5-17.12.2-3-omv2015.0.x86_64.rpm
    http://downloads.openmandriva.org/mirrors/openmandriva.3.0.x86_64.list: media/main/updates/kdialog-17.12.2-1-omv2015.0.x86_64.rpm                   
    http://downloads.openmandriva.org/mirrors/openmandriva.3.0.x86_64.list: media/main/updates/lib64KF5Contacts-devel-17.12.2-3-omv2015.0.x86_64.rpm    
    http://downloads.openmandriva.org/mirrors/openmandriva.3.0.x86_64.list: media/main/updates/kcontacts-17.12.2-3-omv2015.0.x86_64.rpm                 
                                                                                                                                                        

The following packages have bad signatures:
/var/cache/urpmi/rpms/kcontacts-17.12.2-3-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Thu Mar  8 09:29:37 2018, Key ID 3b360bec8403dc21))
/var/cache/urpmi/rpms/kdialog-17.12.2-1-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Thu Mar  8 10:49:22 2018, Key ID cd79870d83e19903))
/var/cache/urpmi/rpms/lib64KF5Contacts-devel-17.12.2-3-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Thu Mar  8 09:29:38 2018, Key ID 3b360bec8403dc21))
/var/cache/urpmi/rpms/lib64KF5Contacts5-17.12.2-3-omv2015.0.x86_64.rpm: Invalid Key ID (OK (RSA/SHA1, Thu Mar  8 09:29:38 2018, Key ID 3b360bec8403dc21))
Do you want to continue installation ? (y/N)
1 Like

This issue is RESOLVED/FIXED. Thanks @TPG. See this thread.

3 Likes