Thank you for explanatiaon. :)
Printable View
Thank you for explanatiaon. :)
Thanks :) That's what I was looking to hear... before knowing this i just haven't bothered with it because I didn't want to touch the custom Kernel...
Sidenote though... I noticed gslapt doesn't direct to it anymore after upgrading slapt-get via the info on the forum. What do I have to edit to fix that?
I created lzm modules to put in my BT3/base usb install which appears to fix the problem for me.
http||ftp.belnet.be/packages/slackware/slackware-current/slackware/n/gnupg-1.4.9-i486-1.tgz
http||software.jaos.org/slackpacks/12.0/slapt-get-0.9.12d-i386-1.tgz
OK. I've tried all of these things, including running FastTrack's slapt updater and I am having an issue that I did not see discussed here.
When I run Gslapt and hit "update" it simply closes itself when it gets to "Retrieving checksum list". No error message or anything. Gslapt just goes away.
Are there alternative guis to gslapt for package management on BackTrack 3?
Yes. I am a n00b. But, I am a fast learning n00b and I spread the kn00wledge. So, how about a little help?
Ok so i have read this thread several times and i still dont get what im doing wrong because im getting the error when i try to retrieve the GPG keys from the mirrors..
Retrieving GPG key [http://linuxpackages.inode.at/Slackware-12.0/]...Not Found
Retrieving GPG key [ftp://ftp.slackware.com/pub/slackwar...2.0/]...Cached
GPGME: Invalid crypto engine
GPG key could not be imported.
Retrieving GPG key [http://software.jaos.org/slackpacks/12.0/]...Cached
GPGME: Invalid crypto engine
GPG key could not be imported.
also i have downloaded libassuan,gpgme,gnupg latest versions from the website
im running slapt-get 0.9.12.d-i386-1 installed all the packages i can for gnupg2 and everything else i can see on here im hoping someone feels generous on friday and wants to help me out and tell me what im missing
There is a fix on the wiki. Go have a look there mate.
http://airdump.net/papers/backtrack-...get-correcting
This actually works just as well and may be easier to follow than all the different fixes we posted in this thread.