[SOLVED] Problem with slackrepo and slackpkg+?

bilbod · 05-05-2017, 01:55 PM

I created a personal SBo repository using slackrepo.

I am trying to access it using slackpkg with slackpkg+ plugin.

1st I run

Code:

slackpkg update gpg

and it imports the gpg key for a Slackware website mirror, the slackpkg+ website, and my personal repository.

Then I run

Code:

slackpkg update

It starts downloading files (I think it is metadata) from the repositories.

Part way through I get this error:

Code:

                        !!! F A T A L !!!
    Repository 'mySlackRepo' FAILS the CHECKSUMS.md5 signature check
    The file may be corrupted or the gpg key may be not valid.
    Remember to import keys by launching 'slackpkg update gpg'.

Then it continues downloading more metadata files. At the finish:

Code:

  WARNING! One or more errors occurred while slackpkg was running
------------------------------------------------------------------------------
Repository 'mySlackRepo' FAILS the CHECKSUMS.md5 signature check.
Try to run 'slackpkg update gpg'

I ran

Code:

slackrepo lint

There were 2 Warnings.

Code:

================================================================================
SUMMARY                                                                 14:45:22
================================================================================

Logfile:     /var/log/slackrepo/SBo/slackrepo_2017-05-05_14:40:50.log
Runtime:     0h 4m 32s
Warnings:    2
  development/jdk: Source has been modified upstream.
  multimedia/pepperflash-plugin: Inappropriate directory. pepperflash-plugin-25.0.0.148-x86_64-2_SBo.tgz

I rebuilt the 2 offending packages ran

Code:

slackrepo lint

again but got the same 2 warnings.

Is there some way to get slackrepo to recreate all the metadata with the correct gpg key without rebuilding the entire repository (which takes many hours)?

Panagiotis Nik · 05-05-2017, 02:32 PM

Did you have enable the Variables for calling gen_repos_files.sh in your slackrepo_ID.conf ?
...
# Change this to '1' if you want to enable gen_repos_files.sh
# If enabled, you *must* set correct values for all the variables below!
...

Also you can use alien bob script separately for your repo metadata
without involve slackrepo:
http://www.slackware.com/~alien/tool...repos_files.sh

bassmadrigal · 05-05-2017, 02:47 PM

It should regenerate all the repository files every time a single package is created/updated. Is slackrepo generating .asc files for your new packages?

Code:

================================================================================
SUMMARY                                                                 15:40:32
================================================================================

Logfile:     /var/log/slackrepo/SBo/slackrepo_2017-05-05_15:39:59.log
Runtime:     0h 0m 33s
Added:       1
  system/virtualbox-kernel/virtualbox-kernel-5.0.30_4.4.38-x86_64-1_SBo.tgz
Updated:     1
  multimedia/x265/x265-2.4-x86_64-1_SBo.tgz
Rebuilt:     1
  multimedia/ffmpeg/ffmpeg-3.2.4-x86_64-2_SBo.tgz
================================================================================
gen_repos_files.sh                                                      15:40:32
================================================================================

# -------------------------------------------------------------------#
# $Id: gen_repos_files.sh,v 1.92 2014/07/31 20:27:53 root Exp root $ #
# -------------------------------------------------------------------#
--- Generating repository metadata for /var/lib/slackrepo/SBo/packages/14.2/x86_64 ---
--- Repository owner is Jeremy Brent Hansen (bassmadrigal) <jebrhansen+SBo@gmail.com> ---

--> Generating .asc file for ffmpeg-3.2.4-x86_64-2_SBo.tgz
--> Generating .asc file for x265-2.4-x86_64-1_SBo.tgz
--> Generating .asc file for virtualbox-kernel-5.0.30_4.4.38-x86_64-1_SBo.tgz

Finished gen_repos_files.sh at 15:43:24

And I don't know if this would even help (possibly not this specific issue), but there's a thread I created with some setup procedures I used and then a bunch of questions I had. It turned into some great discussion and there might be some information in there that you could benefit from. Feel free to check it out.

bilbod · 05-05-2017, 03:27 PM

Quote:

Originally Posted by Panagiotis Nik

Did you have enable the Variables for calling gen_repos_files.sh in your slackrepo_ID.conf ?
...
# Change this to '1' if you want to enable gen_repos_files.sh
# If enabled, you *must* set correct values for all the variables below!
...

Also you can use alien bob script separately for your repo metadata
without involve slackrepo:
http://www.slackware.com/~alien/tool...repos_files.sh

Code:

USE_GENREPOS='1'

I have that set up correctly.

I tried running the script directly but it failed. It was looking for RSS_UUID. That is in my slackrepo_ID.conf file but it does not read that file and I could find no docs on a config file for for gen_repos_files.sh.

bilbod · 05-05-2017, 03:43 PM

Quote:

Originally Posted by bassmadrigal

It should regenerate all the repository files every time a single package is created/updated. Is slackrepo generating .asc files for your new packages?

And I don't know if this would even help (possibly not this specific issue), but there's a thread I created with some setup procedures I used and then a bunch of questions I had. It turned into some great discussion and there might be some information in there that you could benefit from. Feel free to check it out.

I did read your tutorial and it helped me get slackrepo configured.

slackrepo is generating .asc files for my packages.

Code:

Repository 'mySlackRepo' FAILS the CHECKSUMS.md5 signature check.

The offending file is CHECKSUMS.md5. If I delete that file, will slackrepo recreate it when I run

Code:

slackrepo lint

Also, something I forgot to mention. When I was setting up slackrepo, I generated several gpg keys. It is possible that a couple of packages were signed with a different gpg key than is currently in use. Is there a way to check that?

bassmadrigal · 05-05-2017, 09:26 PM

It should recreate CHECKSUMS.md5 every time a package is added/updated/removed.

As for checking what key signed what, that's beyond my knowledge. I created a gpg key for the first time when using slackrepo and my knowledge is mainly limited to that (which I've likely mostly forgotten at this point). My first thought would be to write a bash script using a for loop to run gpg -verify (it goes gpg -verify packagename.tgz.asc packagename.tgz) against all the packages in your repo. There's probably a better way to do it, but I'm not aware of one.

bilbod · 05-05-2017, 11:24 PM

Quote:

Originally Posted by bassmadrigal

It should recreate CHECKSUMS.md5 every time a package is added/updated/removed.

As for checking what key signed what, that's beyond my knowledge. I created a gpg key for the first time when using slackrepo and my knowledge is mainly limited to that (which I've likely mostly forgotten at this point). My first thought would be to write a bash script using a for loop to run gpg -verify (it goes gpg -verify packagename.tgz.asc packagename.tgz) against all the packages in your repo. There's probably a better way to do it, but I'm not aware of one.

I looked at the date stamp for GPG-KEY file and rebuilt all packages built on that date or earlier. There were only a hand full and it took about 3 minutes.

I tried slackpkg+ again and it gives the same error so that is not the problem.

I tried gpg -verify on CHECKSUMS.md5 on the repo server and it passed. So I looked at the gpg keys and the server is using a different key than is in the GPG-KEY file on the server. So I recreated the GPG-KEY file

Code:

gpg --list-keys "$REPOSOWNERGPG" > GPG-KEY
gpg -a --export "$REPOSOWNERGPG" >> GPG-KEY

The second command creates ascii armored output and exports it to a GPG-KEY file (I got those commands from gen_repos_files.sh).

I ran

Code:

slackpkg update gpg
slackpkg update

No errors, Problem Solved.