Problem Description
After upgrade from 11 to 12, I’m getting an hourly email message “Key is stored in
legacy trusted.gpg keyring” from sympl-php-configure
Any Error Messages
The full email contents:
/etc/cron.hourly/sympl-php-configure:
W: http://packages.mythic-beasts.com/mythic/dists/bookworm/InRelease: Key is stored in
legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in
apt-key(8) for details.
Additional Information
As I’m hosting this on a Bitfolk VPS, I’m using Bitfolk’s Debian repository cache. Sample line from sources.list:
deb http://apt-cacher.lon.bitfolk.com/debian/deb.debian.org/debian bookworm main
…and similar. I realise this is an unsupported configuration, but I don’t know whether I should be asking here or at Bitfolk, and if the latter, what question should I be asking?
Signing, certificates, public and private keys are beyond my pay grade other than understanding the basic principles, so after reading the man pages for apt-key and sources.list I’m still not clear what I have to do.
Environment
- Sympl Version : 12
- Sympl Testing Version? No
- Debian Version : bookworm
- Hardware Type? Virtual
- Hosted On? Bitfolk
Debian changed the format that Apt wants the keys in, and it’s a bit verbose when warning about them being in the older format.
If you run this, it will download the Mythic key and place it in the new location in the relevant format:
wget -q https://mirror.mythic-beasts.com/mythic/support@mythic-beasts.com.gpg.key -O /etc/apt/trusted.gpg.d/support@mythic-beasts.com.asc
The current upgrade instructions cover this. But if you upgraded before then you may have not added this relatively small change.
Thank you!
I printed out the upgrade instructions, but must have missed that line in the middle of all the editing of the apt list files, which I was not doing exactly as shown because my files were different.
Key now installed, let’s hope my mailbox has a quieter life now.
Something else now!
Email with lots of lines all saying
/var/cache/cracklib/cracklib_dict.pwd: No such file or directory
Something to do with cracklib was removed manually in the install process - anything to do with that?
(It’s the ftp password strength checker sending the email)
OK - I re-installed cracklib-runtime and sympl-password-test now runs fine.
So not sure why instructed to
apt -y purge cracklib-runtime
as part of the upgrade … but it works for me now!
I’ll check and update the documentation - I think there was somewhat of a conflict with the replacement package, although not got my notes handy at the moment.