Hi

Following the tips from a few thread here at LQ and AlienBob's blog, I set up a repository for my own slackware packages, using AlienBob gen_repos_files.sh script.

Unfortunately, slackpkg kept complaining about my repo failing the CHECKSUMS gpg check.

I dig a little and I found out that although the script generates the repo's GPG-KEY from the REPOSOWNERGPG variable, it did not use to it to sign the packages and the CHECKSUMS.md5 file.
When you don't specify the key to use, gpg uses the first one in your keyring. If that's your repo's gpg key, all is fine. But my repo's gpg key is actually second in my keyring...

Here's my proposed patch to add -u "$REPOSOWNERGPG" to the gpg command.

Cheers

Attached Files

gen_repos_files-gpg_sign.patch.txt (638 Bytes, 53 views)

Use slackpkg+ that allow you to use repositories not signed with slackware key

Hi

I do use slackpkg+
Since both AlienBob's gen_repos_files.sh can sign the repository and slackpkg+ can check it, I wish to fully set up my repository, including signing it with my own gpg key to pass the slackpkg+ check.
The only glitch I encountered was that the key used by gen_repos_files.sh to sign the packages wasn't the one I want to use because it isn't the first in my gpg keyring.
On a second system where the gpg key for my repository is the first in the keyring, I didn't encountered this problem.

Cheers

ah, ok.

You can specify a different key by passing a parameter. I used it for MSB repo and it worked

Still I think it is a good proposal so I will implement it.

Eric

Ohh i have used that actually..

Sorry, i didn't look at the patch previously

Hi

"Solved" in Revision 1.92

Thanks Eric!

Cheers