slackpkg gpg error

KIngofKIngs · 12-20-2011, 07:18 PM

when I typed slackpkg update I get the following error
ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of date
or has been tampered with.

I have tried a variety of mirrors
I am running slackware 64
I updated the Kernel to 3.1.5
I checked the date and it is accurate
I ran slackpkg update gpg
Thanks for any help you can give me

ottavio · 12-21-2011, 03:51 AM

Well, either the file is out of date or it has been tampered with.

Don't rely on slackpkg too much.

KIngofKIngs · 12-21-2011, 05:40 AM

I need to use it to upgrade to slackware-current because that is a prereq for a few programs I am going to run. Slackware 13.37 doesn't have all the necessary files without updating it.

ottavio · 12-22-2011, 04:05 AM

Upgrading the system with slackpkg is a bad idea. This has been discussed at lenght before. Slackpkg is ok to keep an existing stable installation updated but when -current is put into the equation it's better to upgrade/update using the changelog.

brianL · 12-22-2011, 05:46 AM

If you want to do a fresh install of current, rather than an upgrade, use Eric's mirror-slackware-current script:
http://connie.slackware.com/~alien/tools/

KIngofKIngs · 12-22-2011, 08:09 PM

I fixed it by installing the script I needed from a current ftp. Still can't use slackpkg, but hey my other program installed.

asipper · 12-23-2011, 05:52 AM

Are you using a beta? I never get that error unless I'm using slackpkg beta.

KIngofKIngs · 12-23-2011, 08:03 AM

Nope. Was using the one that came on the DVD in the first place.

hitest · 12-23-2011, 08:57 AM

Quote:

Originally Posted by KIngofKIngs

I fixed it by installing the script I needed from a current ftp. Still can't use slackpkg, but hey my other program installed.

I'm not sure if this will work, especially if you cannot update slackpkg. You could try to reinstall slackpkg and then try again to update it. Perhaps your slackpkg program is corrupted. It might work

# slackpkg reinstall slackpkg

# slackpkg update

KIngofKIngs · 12-23-2011, 09:26 AM

I tried this before I posted here. I forgot to mention that. Thanks for the idea though hitest.

hitest · 12-23-2011, 10:15 AM

Quote:

Originally Posted by KIngofKIngs

I tried this before I posted here. I forgot to mention that. Thanks for the idea though hitest.

Total bummer!
I would then try to build a slackware-current ISO(s) using Alien Bob's -current build script which brianL linked to previously. I very recently built ISOs for slackware-current (32 bit) using Alien Bob's script. You can of course change the Arch to 64 bit, and change it so it builds a DVD instead of three CDs. Eric's script is very nifty in that once the ISO(s) are built the script then checks the integrity of the images (md5). Eric's script has never failed me.

KIngofKIngs · 12-23-2011, 11:02 AM

curious, if you're going to install arch as 64bit why not install a 64bit system and make it multilib?

hitest · 12-23-2011, 11:24 AM

Quote:

Originally Posted by KIngofKIngs

curious, if you're going to install arch as 64bit why not install a 64bit system and make it multilib?

Not sure I understand your post. Eric's script will build 64 bit ISO(s) of Slackware64-current if you edit the build script. Here is a snippet of Eric's script:

Code:

# What architecture will we be mirroring? The default is 'x86' meaning 32bit.
# Alternatively you can specify 'x86_64' meaning 64bit. The value of ARCH
# determines the name of the slackware directories.
# This value can be overruled via the '-a' commandline parameter;
ARCH=${ARCH:-"x86"}

Once you do a clean install of Slackware64-current I'm sure you can install the multilib libraries.

KIngofKIngs · 12-23-2011, 11:27 AM

Quote:

Originally Posted by hitest

Not sure I understand your post. Eric's script will build 64 bit ISO(s) of Slackware64-current if you edit the build script. Here is a snippet of Eric's script:

Code:

# What architecture will we be mirroring? The default is 'x86' meaning 32bit.
# Alternatively you can specify 'x86_64' meaning 64bit. The value of ARCH
# determines the name of the slackware directories.
# This value can be overruled via the '-a' commandline parameter;
ARCH=${ARCH:-"x86"}

Once you do a clean install of Slackware64-current I'm sure you can install the multilib libraries.

never mind, I see what you're saying. Next time I screw something up bad enough I decide to just start over I'll probably do current. For now though, I got KDE 4.7.4 and all its dependencies in. Now if I can just figure out how to get plasma to work...

hitest · 12-23-2011, 11:29 AM

Quote:

Originally Posted by KIngofKIngs

never mind, I see what you're saying. Next time I screw something up bad enough I decide to just start over I'll probably do current. For now though, I got KDE 4.7.4 and all its dependencies in. Now if I can just figure out how to get plasma to work...

Good luck with your issue, man! Happy Holidays.