MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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.
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.
When I go to install using rpmdrake, any installation fails giving me the message "Bad signatures" cannot open file xxxxxxx.rpm. I am using an ftp site called: ftp://ftp.mirrorservice.org/pub/Mand.../main_updates. I have tried other sites also and get the same error message. I am using the download version of Mandrake 10.1, the non-64 bit version. I get the same message on an entirely different system.
I am sure there must be something I am doing wrong. Has anybody else had this problem, and how did you fix it?
I appreciate your response. The files will not install, and I have tested a handful of different packages, and different servers, but none will work. These are mirror servers. Is there a specific server I should be going to? Shouldn't all the mirror servers on Mandrakes list be authorized sources for RPM's? Thank you for your help also.
I think that message also shows up when your repository sources are not properly synched up with your urpmi database. In rpmdrake, there should be a button labeld "Update", or "Update sources", or some such (I am at work on a Win box, can't check my Mdk box right now ).
Or from the command line, "urpmi.update -all" should update your sources. (I think - IIRC)
first off, use the "gpg --recv-keys --keyserver pgp.mit.edu 0x22458A98" command as root to import the mandrake security team's gpg keys to your pc. Like so:
Code:
[don@x1-6-00-0a-e6-91-be-32 don]$ su
Password:
[root@x1-6-00-0a-e6-91-be-32 don]# gpg --recv-keys --keyserver pgp.mit.edu 0x22458A98
gpg: /root/.gnupg: directory created
gpg: new configuration file `/root/.gnupg/gpg.conf' created
gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key 22458A98: public key "Mandrake Linux Security Team <security@mandrakesoft.com>" imported
gpg: Total number processed: 1
gpg: imported: 1
[root@x1-6-00-0a-e6-91-be-32 don]#
Then try installing your updates again and see if the bad signature message is gone and all works well.
I tried both of your suggestions, and I still get the message bad signatures. If I install off the CD, I don't get this message. I also updated the signature for the ftp source I was pointed to after using gpg command, and installs still will not work. Oh well, I'll eventually figure this out, probably finding out it is something very simple!!
I did look through the Mandrake doc, but it just says to put in the ftp address of the mirror server.
Some suggested you update your urpmi sources, try that and see if this resolves your problems. You may have to wait a few hours for the mirror you are using to sync with the main ftp site before all packages are available.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.