Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
12-20-2011, 07:18 PM
|
#1
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Rep: 
|
slackpkg gpg error
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
|
|
|
12-21-2011, 03:51 AM
|
#2
|
Member
Registered: Nov 2007
Posts: 312
Rep:
|
Well, either the file is out of date or it has been tampered with.
Don't rely on slackpkg too much.
|
|
|
12-21-2011, 05:40 AM
|
#3
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Original Poster
Rep: 
|
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.
|
|
|
12-22-2011, 04:05 AM
|
#4
|
Member
Registered: Nov 2007
Posts: 312
Rep:
|
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.
|
|
|
12-22-2011, 05:46 AM
|
#5
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Rep: 
|
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/
|
|
|
12-22-2011, 08:09 PM
|
#6
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Original Poster
Rep: 
|
I fixed it by installing the script I needed from a current ftp. Still can't use slackpkg, but hey my other program installed.
|
|
|
12-23-2011, 05:52 AM
|
#7
|
Member
Registered: Oct 2011
Distribution: Fedora 17
Posts: 138
Rep:
|
Are you using a beta? I never get that error unless I'm using slackpkg beta.
|
|
|
12-23-2011, 08:03 AM
|
#8
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Original Poster
Rep: 
|
Nope. Was using the one that came on the DVD in the first place.
|
|
|
12-23-2011, 08:57 AM
|
#9
|
Guru
Registered: Mar 2004
Location: Canada
Distribution: Slackware64-current
Posts: 7,500
|
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
|
|
|
12-23-2011, 09:26 AM
|
#10
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Original Poster
Rep: 
|
I tried this before I posted here. I forgot to mention that. Thanks for the idea though hitest.
|
|
|
12-23-2011, 10:15 AM
|
#11
|
Guru
Registered: Mar 2004
Location: Canada
Distribution: Slackware64-current
Posts: 7,500
|
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. 
|
|
|
12-23-2011, 11:02 AM
|
#12
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Original Poster
Rep: 
|
curious, if you're going to install arch as 64bit why not install a 64bit system and make it multilib?
|
|
|
12-23-2011, 11:24 AM
|
#13
|
Guru
Registered: Mar 2004
Location: Canada
Distribution: Slackware64-current
Posts: 7,500
|
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.
Last edited by hitest; 12-23-2011 at 11:26 AM.
|
|
|
12-23-2011, 11:27 AM
|
#14
|
LQ Newbie
Registered: Dec 2011
Posts: 8
Original Poster
Rep: 
|
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...
|
|
|
12-23-2011, 11:29 AM
|
#15
|
Guru
Registered: Mar 2004
Location: Canada
Distribution: Slackware64-current
Posts: 7,500
|
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. 
|
|
|
All times are GMT -5. The time now is 03:31 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|