[SOLVED] sbopkg resync fails GPG key after latest security upgrades

magicm · 04-22-2015, 06:41 PM

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.

mancha · 04-23-2015, 01:11 AM

Hi magicm.

GnuPG 1.4.19's armor check prints extraneous debug output that doesn't appear to impact sbopkg (beyond littering the screen). I don't
use sbopkg so please confirm if this is not the case.

If you're interested, GnuPG fixed this in commit f34d88364a98494. Rebuilding GnuPG 1.4.19 with that patch should get rid of the junk.

--mancha

magicm · 04-23-2015, 09:14 AM

mancha -

Thank you. It does seem like I was fooled by a "false negative". I'll mark this as "solved".

mancha · 04-25-2015, 10:21 PM

You're welcome magicm.

There's a bit of good news in the latest current upgrades - seems Willy Sudiarto passed our analysis on to Pat.

Code:

Sat Apr 25 23:13:15 UTC 2015
n/gnupg2-2.0.27-i486-2.txz:  Rebuilt.
  Patched to fix spurious debug messages that may break sbopkg and slackpkg.
  Thanks to Willy Sudiarto Raharjo.

Unfortunately, only GnuPG-2 was fixed and I believe sbopkg and slackpkg use GnuPG-1.

--mancha

mister_b · 04-25-2015, 10:28 PM

Quote:

Originally Posted by mancha

Unfortunately, only GnuPG-2 was fixed and I believe sbopkg and slackpkg use GnuPG-1.

--mancha

It was patching and rebuilding GnuPG-1 only that fixed the sbopkg error for me.

willysr · 04-25-2015, 11:50 PM

Yes, i asked Pat to do the same for gnupg as well after i saw that it was only rebuilt for GnuPG2

MadMaverick9 · 04-26-2015, 12:54 AM

Quote:

Originally Posted by willysr

Yes, i asked Pat to do the same for gnupg as well after i saw that it was only rebuilt for GnuPG2

Only for -current or will/can this be done for 14.0/14.1 as well? Thanks.

willysr · 04-26-2015, 02:52 AM

it should be backported to -stable as well since i got this on 14.1 machine when running sbopkg -r

Code:

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.

mats_b_tegner · 04-26-2015, 06:11 AM

If you run -current it's possible to use the patch provided in /source/n/gnupg2 on gnupg and add the appropriate to line the gnupg.SlackBuild e.g:

Code:

zcat $CWD/gnupg.remove.left.over.debug.messages.diff.gz | patch -p1 --verbose || exit 1

kikinovak · 04-26-2015, 07:51 AM

Quote:

Originally Posted by willysr

it should be backported to -stable as well since i got this on 14.1 machine when running sbopkg -r

Code:

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.

+1. Same problem here on 14.1.

mancha · 04-26-2015, 01:31 PM

Quote:

Originally Posted by mats_b_tegner

If you run -current it's possible to use the patch provided in /source/n/gnupg2 on gnupg and add the appropriate to line the gnupg.SlackBuild

That's because the patch being applied to GnuPG-2 in -current is actually the patch against GnuPG-1 that I provided in post #2. It
happens to apply to GnuPG-2 (with offsets) because of the shared code-base but the clean patch against GnuPG-2 is actually
936416690e6c.

--mancha

willysr · 04-29-2015, 05:39 AM

it has been applied to gnupg (1.x) and also backported to -stable as well

magicm · 04-29-2015, 07:24 AM

XLNT ! - downloaded, applied, verified - 14.1 32-bit - thanx all

mister_b · 04-29-2015, 09:12 AM

Quote:

Originally Posted by willysr

it has been applied to gnupg (1.x) and also backported to -stable as well

Great news. It's a sweet moment when you see the payoff of choosing not to blacklist a package rebuilt from -current for -stable.