[SOLVED] Strange checksum and/or GPG error on third-party Slackware repository

kikinovak · 09-08-2014, 03:15 AM

Hi,

I'm currently uploading a huge batch of updates for MLED and MLES, my own Slackware repositories.

I've been using Eric Hameleers' gen_repos_files.sh script to generate checksums, signatures and everything. But it seems like I'm having trouble getting things right. For a start, I configured the MLES-14.0-32bit repository:

http://www.microlinux.fr/slackware/MLES-14.0-32bit/

This script was used to generate repository metadata:

https://github.com/kikinovak/slackwa...repos_files.sh

I uploaded everything and tried to test this repo on a sandbox machine, with slackpkg+. I ran 'slackpkg update gpg' which fetched the GPG key fine. Then I ran 'slackpkg update', but I keep getting FATAL errors, and slackpkg complains about either wrong checksums and/or wrong GPG key.

I checked and double-checked everything and can't seem to find my mistake.

Any suggestions?

Didier Spaier · 09-08-2014, 03:57 AM

Quote:

Originally Posted by kikinovak

Hi,

I'm currently uploading a huge batch of updates for MLED and MLES, my own Slackware repositories.

I've been using Eric Hameleers' gen_repos_files.sh script to generate checksums, signatures and everything. But it seems like I'm having trouble getting things right. For a start, I configured the MLES-14.0-32bit repository:

http://www.microlinux.fr/slackware/MLES-14.0-32bit/

This script was used to generate repository metadata:

https://github.com/kikinovak/slackwa...repos_files.sh

I uploaded everything and tried to test this repo on a sandbox machine, with slackpkg+. I ran 'slackpkg update gpg' which fetched the GPG key fine. Then I ran 'slackpkg update', but I keep getting FATAL errors, and slackpkg complains about either wrong checksums and/or wrong GPG key.

I checked and double-checked everything and can't seem to find my mistake.

Any suggestions?

It seems that slackpkg fetch the files GPG-KEY and CHECKSUMS.md5 (among others) from the un-commented mirror in /etc/slackpkg/mirrors. So if this mirror is an official Slackware mirror it won't find your own files. Caveat: I just had a quick look, so I'm not sure of what I just wrote.

PS if you really meant "slackpkg+ update" (is there a slackpkg+ "update" option?) I have no clue as I never used slackpkg+ yet.

Alien Bob · 09-08-2014, 04:00 AM

Hi Niki

My mirror of your repository (http://taper.alienbase.nl/mirrors/people/kikinovak/) looks OK.
In "MLED-14.1-64bit" I ran this check:

Code:

tail +13 CHECKSUMS.md5 | md5sum --check | grep -v OK

and this resulted in empty output, which means that all md5 checksums were OK.

Note that you seem to be using a version of my script that is a bit old. The current script writes this in the header of the CHECKSUMS.md5 script:

Code:

These are the MD5 message digests for the files in this directory.
If you want to test your files, use 'md5sum' and compare the values to
the ones listed here.

To test all these files, use this command:

tail +13 CHECKSUMS.md5 | md5sum --check | less

'md5sum' can be found in the GNU coreutils package on ftp.gnu.org in
/pub/gnu, or at any GNU mirror site.

MD5 message digest                Filename

while your copy of it writes:

Code:

These are the MD5 message digests for the files in this directory.
If you want to test your files, use 'md5sum' and compare the values to
the ones listed here.

To test all these files, use this command:

md5sum -c CHECKSUMS.md5 | less

'md5sum' can be found in the GNU coreutils package on ftp.gnu.org in
/pub/gnu, or at any GNU mirror site.

MD5 message digest                Filename

a subtle difference.
Anyway, your repository seems to be OK so the issue must be a local one, on your own computer.

Eric

kikinovak · 09-08-2014, 12:11 PM

Thanks for the heads-up, Didier and Eric.

I cleared all the metadata and replaced the old gen_repos_files.sh with the last version, which I edited for every single one of the seven different repositories. Then I cleared all the existing metadata and recreated it with the new scripts. Now everything is working fine.

Cheers & marking as SOLVED.

Alien Bob · 09-08-2014, 02:13 PM

Why d you have seven different copies of the script? You can create seven configuration files and use a single script - much easier to keep uptodate.

Eric

kikinovak · 09-08-2014, 02:29 PM

Quote:

Originally Posted by Alien Bob

Why d you have seven different copies of the script? You can create seven configuration files and use a single script - much easier to keep uptodate.

Eric

Must be a combination of copy & paste combined with the thought that this script doesn't get updated very often. Quick & dirty, but hey, it works.