Following up the previous post on this topic, the issue with missing pubkey files leading to NOKEY errors is now resolved on the majority of mirror servers. The following servers from the list used by the Mandriva tools have been tested and found to be GOOD: ftp://ftp.mandrake.ikoula.com/Mandrakelinux/official/2008.0 ftp://ftp.iasi.roedu.net/mirrors/ftp.mandrake.com/official/2008.0 ftp://ftp.free.fr/mirrors/ftp.mandriva.com/MandrivaLinux/official/2008.0 ftp://ramses.wh2.tu-dresden.de/pub/mirrors/mandrake/official/2008.0 ftp://ftp.uwsg.indiana.edu/linux/mandrake/official/2008.0 ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2008.0 http://gd.tuwien.ac.at/pub/linux/Mandrakelinux/official/2008.0 ftp://ftp.lip6.fr/pub/linux/distributions/Mandrakelinux/official/2008.0 ftp://carroll.cac.psu.edu/pub/linux/distributions/mandrivalinux/official/2008.0 ftp://ftp.surfnet.nl/pub/os/Linux/distr/Mandrakelinux/official/2008.0 http://mandriva.dcc.fc.up.pt/official/2008.0 ftp://ftp.pbone.net/pub/mandrakelinux/official/2008.0 ftp://ftp.esat.net/pub/linux/mandrakelinux/official/2008.0 ftp://mirrors.secsup.org/pub/linux/mandrakelinux/official/2008.0 ftp://ftp.ps.pl/mirrors/mandrake/official/2008.0 ftp://ftp.tuniv.szczecin.pl/pub/linux/mandrakelinux/official/2008.0 The following servers have been tested and found to be BAD: http://www.gtlib.cc.gatech.edu/pub/mandrake/official/2008.0 ftp://ftp.rhnet.is/pub/Mandrakelinux/official/2008.0 ftp://ftp.cica.es/pub/Linux/Mandrakelinux/official/2008.0 ftp://ftp.ciril.fr/pub/linux/mandrakelinux/official/2008.0 ftp://sunsite.cnlab-switch.ch/mirror/mandrake/official/2008.0 ftp://mirror.switch.ch/mirror/mandrake/official/2008.0 ftp://ftp.heanet.ie/pub/mandrake/Mandrakelinux/official/2008.0 ftp://ftp.nara.wide.ad.jp/pub/Linux/Mandrakelinux/official/2008.0 The following servers could not be tested as they were full: ftp://ftp.u-strasbg.fr/pub/linux/distributions/Mandriva/official/2008.0 ftp://fr2.rpmfind.net/linux/Mandrakelinux/official/2008.0 If you are using one of the servers listed as GOOD, you may be able to resolve the problem by running this command: urpmi.update --force-key If you are using one of the servers listed as BAD, or if the --force-key command does not work to resolve the problem, you can resolve the problem by removing your repositories and re-adding them using one of the servers listed as GOOD. Tomorrow we will test all servers again, and remove those that have still not properly synchronized the fix from the official server list. Again, we apologize for any inconvenience caused by this issue.