On Wed, 2006-02-15 at 08:02 -0300, Adriano Frare wrote: > Best soluction is > > yum exclude=nmap* update > > Peter Kjellström wrote: > > On Tuesday 14 February 2006 22:14, William L. Maltby wrote: > > > >>Sorry to reply to myself, but ... > >> > >>On Tue, 2006-02-14 at 13:45 -0500, William L. Maltby wrote: > >> > >>>On Tue, 2006-02-14 at 10:55 -0500, Jim Perrin wrote: > >>> > >>>>><snip> > >>>> > >>>>Try running 'yum clean all' then 'yum update' and see what you get. > >>>>rpmforge should include all of dag's packages anyway so there > >>>>shouldn't be a problem. All I can tell you is it "WorksForMe". > >>> > >>>All the other's updated fine. I'm going to ribit and do a forced fsck to > >>>make sure I'm not getting victimized by a creeping calamitous failure on > >>>my HD. Then I'll try some manual junk. > >> > >>Ummm... I'd try some manual junk if I had any idea where to start. I did > >>the reboot, fsck, and even tried a yum update while in single user mode. > >>ImageMagick updated ok, but the two files here failed again. > >> > >> nmap-frontend.i386 2:4.01-1.2.el4.rf > >> nmap.i386 2:4.01-1.2.el4.rf > >> > >>Since I'm under the aegis of WFM now, if someone could give a starting > >>point for me to follow and resolve, I'd appreciate it and stop pestering > >>you all. I can't figure why only this one should be a problem only for > >>my installation. *sigh*. > > > > > > FWIW, I see the exact same problem here with all of my centos-4 machines that > > have nmap from rpmforge.net. I consider it a broken rpm package (but havn't > > looked into it yet. I dropped dag a line about it. > > > > You can allways update and, for the time, ignore nmap like this: > > yum --exclude=nmap update > > > > /Peter > > > > > >>TIA > >> > >>A few tidbits from the most recent attempt ============ > >>Total download size: 775 k > >>Is this ok [y/N]: y > >>Downloading Packages: > >>(1/2): nmap-frontend-4.01 100% |=========================| 29 kB > >>00:00 > >>http://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno -1] Package does not match > >>checksum > >>Trying other mirror. > >>http://ftp-stud.fht-esslingen.de/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable > >>Trying other mirror. > >>http://wftp.tu- > >>chemnitz.de/pub/linux/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable > >>Trying other mirror. > >>http://archive.cs.uu.nl/mirror/dag.wieers/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable > >>Trying other mirror. > >>http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/RPMS/nm > >>ap-frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable Trying other mirror. > >>http://mirrors.ircam.fr/pub/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable > >>Trying other mirror. > >>http://apt.sw.be/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable > >>Trying other mirror. > >>http://rh- > >>mirror.linux.iastate.edu/pub/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable > >>Trying other mirror. > >>http://mirror.cpsc.ucalgary.ca/mirror/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable > >>Trying other mirror. > >>http://ftp2.lcpe.uni- > >>sofia.bg/freshrpms/pub/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not > >>Satisfiable > >>Trying other mirror. > >>(2/2): nmap-4.01-1.2.el4. 100% |=========================| 746 kB > >>00:01 > >>http://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2.el4. > >>rf.i386.rpm: [Errno -1] Package does not match checksum Trying other mirror. > >>http://ftp-stud.fht- > >>esslingen.de/dag/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2.el4.rf.i386.rpm: > >>[Errno 9] Requested Range Not Satisfiable Trying other mirror. > >>http://wftp.tu- > >>chemnitz.de/pub/linux/dag/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2.el4.rf. > >>i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying other mirror. > >>http://archive.cs.uu.nl/mirror/dag.wieers/redhat/el4/en/i386/dag/RPMS/nmap- > >>4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying > >>other mirror. > >>http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/RPMS/nm > >>ap-4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable > >>Trying other mirror. > >>http://mirrors.ircam.fr/pub/dag/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2.e > >>l4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying other > >>mirror. > >>http://apt.sw.be/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2.el4.rf.i386.rpm: > >>[Errno 9] Requested Range Not Satisfiable Trying other mirror. > >>http://rh- > >>mirror.linux.iastate.edu/pub/dag/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2. > >>el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying other > >>mirror. > >>http://mirror.cpsc.ucalgary.ca/mirror/dag/redhat/el4/en/i386/dag/RPMS/nmap- > >>4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying > >>other mirror. > >>http://ftp2.lcpe.uni- > >>sofia.bg/freshrpms/pub/dag/redhat/el4/en/i386/dag/RPMS/nmap-4.01-1.2.el4.rf > >>.i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying other mirror. > >> > >> > >>Error Downloading Packages: > >> nmap - 2:4.01-1.2.el4.rf.i386: failure: > >>RPMS/nmap-4.01-1.2.el4.rf.i386.rpm from rpmforge: [Errno 256] No more > >>mirrors to try. > >> nmap-frontend - 2:4.01-1.2.el4.rf.i386: failure: RPMS/nmap- > >>frontend-4.01-1.2.el4.rf.i386.rpm from rpmforge: [Errno 256] No more > >>mirrors to try. OK ... I think we may have 2 separate problems here. One problem is a mirror that shows zero length on a file in dag's repo which is critical to be able to do updates at all. To fix this problem, I don't use that mirror at all for dag repo files ... here is my dag repo entry: [dag] name=Dag-EL$releasever baseurl=http://dag.linux.iastate.edu/dag/redhat/el$releasever/en/$basearch/dag http://www.mirrorservice.org/sites/apt.sw.be/redhat/el$releasever/en/$basearch/dag/ http://mirrors.ircam.fr/pub/dag/redhat/el$releasever/en/$basearch/dag/ gpgcheck=1 enabled=1 This solves the error that the mirror http://apt.sw.be/ is routinely broken ... BUT there is also a problem specifically with nmap ... it is a broken package checksum in the yum metadata files. Last time Dag had this problem it was a bug with the way the createrepo -c function worked. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20060215/4ba8b903/attachment-0005.sig>