Oh boy, I totally overlooked that part. I think I owe you both my apologies, you’ve been really helpful and I have wasted a lot of your time.
However, with this piece of info added to the picture I have solved the issue. Under GPG home there was an empty trustdb:
[root@firewall .gnupg]# ll
total 8
-rw------- 1 root root 3444 Dec 6 17:11 pubring.gpg
-rw------- 1 root root 1161 Dec 6 16:37 pubring.gpg~
-rw------- 1 root root 0 Dec 6 16:36 secring.gpg
-rw------- 1 root root 0 Dec 6 16:36 trustdb.gpg
file date/time are those of first installation. I can’t guess why it ended up empty, but GPG doesn’t like an empty trustdb file, as it seems (it complains “wrong format” or something like that). So I simply deleted the trustdb and imported keys anew:
[root@firewall .gnupg]# rm trustdb.gpg
rm: remove regular empty file 'trustdb.gpg'? y
[root@firewall .gnupg]# /etc/rc.d/init.d/pakfire start
Setting up Pakfire Package Manager... [ OK ]
and just for good measure, I’ve also checked with the single command:
[root@firewall .gnupg]# gpg --import /opt/pakfire/pakfire-2018.key /opt/pakfire/pakfire-2022.key
gpg: key D713594B: "IPFire Pakfire Package Signing Key <pakfire@ipfire.org>" not changed
gpg: key C8DCE211: "IPFire Pakfire Package Signing Key <pakfire@ipfire.org>" not changed
gpg: Total number processed: 2
gpg: unchanged: 2
and from this, everything looks good:
[root@firewall .gnupg]# gpg --list-keys
gpg: /opt/pakfire/etc/.gnupg/trustdb.gpg: trustdb created
/opt/pakfire/etc/.gnupg/pubring.gpg
-----------------------------------
pub 4096R/D713594B 2018-03-16
uid IPFire Pakfire Package Signing Key <pakfire@ipfire.org>
pub 4096R/C8DCE211 2022-03-21
uid IPFire Pakfire Package Signing Key <pakfire@ipfire.org>
sub 4096R/24695A3E 2022-03-21
[root@firewall .gnupg]# ls -la
total 12
drwx------ 2 root root 83 Jan 17 09:34 .
drwx------ 3 root root 78 Jan 16 21:45 ..
-rw------- 1 root root 3444 Dec 6 17:11 pubring.gpg
-rw------- 1 root root 1161 Dec 6 16:37 pubring.gpg~
-rw------- 1 root root 0 Jan 17 09:33 secring.gpg
-rw------- 1 root root 1200 Jan 17 09:34 trustdb.gpg
…and pakfire works like a charm:
[root@firewall .gnupg]# pakfire update
server-list.db 100.00% |=============================>| 2.24 KB
packages_list.db 100.00% |=============================>| 4.94 KB
core-list.db 100.00% |=============================>| 903.00 B
[root@firewall .gnupg]# pakfire install nmap
PAKFIRE RESV: nmap: Resolving dependencies...
PAKFIRE INFO: Packages to install:
PAKFIRE INFO: nmap - 4.67 MB
PAKFIRE INFO: Total size: ~ 4.67 MB
PAKFIRE INFO: Is this okay? [y/N]
y
nmap-7.95-19.ipfi... 100.00% |=============================>| 4.63 MB
PAKFIRE INST: nmap: Decrypting...
PAKFIRE INST: nmap: Copying files and running post-installation scripts...
PAKFIRE INST: nmap: Finished.
case closed guys, and again, many thanks for your really precious support!
Ciao,
Fabrizio