magicm |
04-22-2015 06:41 PM |
sbopkg resync fails GPG key after latest security upgrades - advice?
After the massive updates to -current (truly amazing amount of work!), and the subsequent updates to the security patches that followed, I upgraded all via slackpkg. Everything seemed to go swimmingly.
Then, because I sometimes exhibit anal-retentive characteristics (and to be thorough), I decided to resync (and take any needed actions) the various SlackBuilds that I have using sbopkg (excellent tool).
When I attempt that, I get the following:
Code:
root@yurt:~# sbopkg -r
Syncing with the remote repository into /var/lib/sbopkg/SBo/14.1.
receiving incremental file list
sent 5,461 bytes received 972,349 bytes 130,374.67 bytes/sec
total size is 71,404,974 speedup is 73.03
Rsync with the SBo repository for Slackware 14.1 complete.
Importing SBo repository for Slackware 14.1 GPG Key...
gpg: DBG: armor-keys-failed (KEY 0x0000000000000000 BEGIN
) ->0
gpg: DBG: armor-keys-failed (KEY 0x0000000000000000 END
) ->0
Import done.
***SYNC COMPLETE***
I'm sure this is a side-effect of the security update to gpg, but am not sure how to correct this.
Thanks in advance for any help.
|