Exhausted mirrors and had the following errors.
(2/10): nmap-frontend-4.0 100% |=========================| 29 kB 00:00 http://apt.sw.be/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. (3/10): libpng-devel-1.2. 100% |=========================| 169 kB 00:00 (4/10): nmap-4.01-1.2.el4 100% |=========================| 746 kB 00:01 http://apt.sw.be/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.
Do I need to add some mirrors to these defaults? Or just be patient?
TIA Bill
(2/10): nmap-frontend-4.0 100% |=========================| 29 kB 00:00 http://apt.sw.be/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. (3/10): libpng-devel-1.2. 100% |=========================| 169 kB 00:00 (4/10): nmap-4.01-1.2.el4 100% |=========================| 746 kB 00:01 http://apt.sw.be/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.
Do I need to add some mirrors to these defaults? Or just be patient?
The packages that are failing are from a 3rd party repository. You should probably be using rpmforge instead of dag directly. Consider installing the rpmforge-release package from dag.wieers.com, and check out rpmforge.net. Using rpmforge will give you more mirrors to use, and may provide better results. It's also possible that you were trying to update as the mirrors were sync'ing and got a corrupt package.
-- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety'' Benjamin Franklin 1775
On Tue, 2006-02-14 at 08:18 -0500, Jim Perrin wrote:
(2/10): nmap-frontend-4.0 100% |=========================| 29 kB 00:00 http://apt.sw.be/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.
<snip a few similar lines>
Do I need to add some mirrors to these defaults? Or just be patient?
The packages that are failing are from a 3rd party repository. You should probably be using rpmforge instead of dag directly. Consider installing the rpmforge-release package from dag.wieers.com, and check out rpmforge.net. Using rpmforge will give you more mirrors to use, and may provide better results. It's also possible that you were trying to update as the mirrors were sync'ing and got a corrupt package.
Rpmforge already installed, just need to switch over to using it instead, I guess. I'll also try again in case I was a little early. Uh, if I start using rpmforge, will I need to wait longer for updates or just take a shot as soon as I see the announcements like I do now?
Thanks, Bill
-- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety'' Benjamin Franklin 1775 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, 2006-02-14 at 09:31 -0500, William L. Maltby wrote:
On Tue, 2006-02-14 at 08:18 -0500, Jim Perrin wrote:
(2/10): nmap-frontend-4.0 100% |=========================| 29 kB 00:00 http://apt.sw.be/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.
<snip a few similar lines>
Do I need to add some mirrors to these defaults? Or just be patient?
The packages that are failing are from a 3rd party repository. You should probably be using rpmforge instead of dag directly. Consider installing <snip>
Rpmforge already installed, just need to switch over to using it instead, I guess. I'll also try again in case I was a little early. Uh, if I start using rpmforge, will I need to wait longer for updates or just take a shot as soon as I see the announcements like I do now?
Hmmm... moved dag's repo out of the way so that rpmforge took over. Results now in a slew of messages:
...4.01-1.2.el4.rf.i386.rpm: [Errno -1] Package does not match checksum Trying other mirror.
for the two packages and
...4.01-1.2.el4.rf.i386.rpm: [Errno 9] Requested Range Not Satisfiable Trying other mirror.
for the two packages. Since this is quite sometime after the announcement(?), is it reasonable to suspect another problem? Or, again, am I just being too quick on the draw?
Feel free to ignore this if so. I'll retry getting that security update another time later in the week.
Thanks, Bill
for the two packages. Since this is quite sometime after the announcement(?), is it reasonable to suspect another problem? Or, again, am I just being too quick on the draw?
Feel free to ignore this if so. I'll retry getting that security update another time later in the week.
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".
-- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety'' Benjamin Franklin 1775
On Tue, 2006-02-14 at 10:55 -0500, Jim Perrin wrote:
for the two packages. Since this is quite sometime after the announcement(?), is it reasonable to suspect another problem? Or, again, am I just being too quick on the draw?
Feel free to ignore this if so. I'll retry getting that security update another time later in the week.
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.
Thanks anyway. Bill
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*.
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-f...: [Errno 9] Requested Range Not Satisfiable Trying other mirror. http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/RPMS/nma...: [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-f...: [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.r...: [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...: [Errno 9] Requested Range Not Satisfiable Trying other mirror. http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/RPMS/nma...: [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.el...: [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...: [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. [root@wlmlfs08 ~]#
Thanks anyway. Bill _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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. [root@wlmlfs08 ~]#
Thanks anyway. Bill
On Wed, 2006-02-15 at 09:44 +0100, 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.
Peter, thanks for taking the time. I see several other posts report the problem now, so apparently the "WorksForMe" poster has a better setup. Anyway, Johnny Hughes replied (in thread Re: [CentOS] DAG Repository) that there is a known and on-going problem of this type with that mirror that is so persistent that Dag made a form for dealing with it. It is here
http://dag.wieers.com/home-made/apt/FAQ.php#C1
You can allways update and, for the time, ignore nmap like this: yum --exclude=nmap update
Yes, I did that. In resolution of another problem a couple weeks back, I re-read completely the oft cited YUM documents. Combined with suggestions like yours above that I had seen on the lists before, that one stuck in my mind and allowed me to proceed regardless of the one bad file.
/Peter
<snip diag listing I sent>
What I'm thinking now is that there is probably some way to override the checksum/gpg checking from the command line. If so, and if I can find out what the real check sum is supposed to be, I could check the file and install it by turning off the checking (at the command line hopefully, instead of temp modification of the config file). So a little reading again of the YUM docs (I hope I don't have to do it so often that I no longer need to read it! =:-O ) and effort to get the right "numbers" and I shiould be able to get it done withb waiting for the habitually broken mirror folks to habitually fix it habitually temporarily again.
Again, thanks for the reply.
Bill
On Wednesday 15 February 2006 11:08, William L. Maltby wrote:
On Wed, 2006-02-15 at 09:44 +0100, 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.
Peter, thanks for taking the time. I see several other posts report the problem now, so apparently the "WorksForMe" poster has a better setup. Anyway, Johnny Hughes replied (in thread Re: [CentOS] DAG Repository) that there is a known and on-going problem of this type with that mirror that is so persistent that Dag made a form for dealing with it. It is here
http://dag.wieers.com/home-made/apt/FAQ.php#C1You can allways update and, for the time, ignore nmap like this: yum --exclude=nmap update
Yes, I did that. In resolution of another problem a couple weeks back, I re-read completely the oft cited YUM documents. Combined with suggestions like yours above that I had seen on the lists before, that one stuck in my mind and allowed me to proceed regardless of the one bad file.
/Peter
<snip diag listing I sent>
What I'm thinking now is that there is probably some way to override the checksum/gpg checking from the command line. If so, and if I can find out what the real check sum is supposed to be, I could check the file and install it by turning off the checking (at the command line hopefully, instead of temp modification of the config file).
The bigger ones yum config, the more servers you depend upon for sanity in order to get 100% success rate on yum update type commands :-/
I feel sorry for the rpmforge guys because they've had a lot of problems with their mirrors (and as such with users running yum). They do a great job and fantasic packages. The rpmforge-release package is a very good idea, it takes care of adding the relevant parts to your yum conf and as such reduces risks associated with the human factor.
As I wrote in the other sub thread, if yum and/or rpm barfs on the file it's probably not a good candidate for installing. Don't fall down to fedora levels of package checking ;-). If a package fails it's rpm sums, then it's broken and the user should wait for a fixed one.
/Peter
So a little reading again of the YUM docs (I hope I don't have to do it so often that I no longer need to read it! =:-O ) and effort to get the right "numbers" and I shiould be able to get it done withb waiting for the habitually broken mirror folks to habitually fix it habitually temporarily again.
Again, thanks for the reply.
Bill
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. [root@wlmlfs08 ~]#
Thanks anyway. Bill
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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>
<snip>
Adriano,
Thanks for taking the time. As you saw Peter suggested this too and I had done that part already. See my reply to him for the long-winded version.
Thanks, Bill
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/$basear... 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.
On Wed, 2006-02-15 at 04:36 -0600, Johnny Hughes wrote:
On Wed, 2006-02-15 at 08:02 -0300, Adriano Frare wrote:
<snip bunch of diag log
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/$basear... 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 ...
A couple of weeks ago, I was advised to install (and presumably use) rpmforge. Recently I moved dag's repo def out of the way and let the rpmforge stuff take over. Can I safely update the rpmforge.repo to not reference the remote mirror list (removing this reference is fraught with risk if changes occur?) and use the local file version (mirrors- rpmforge) updated to look similar to yours and still use rpmforge?
Anyway, I'll do that *unless* you say "STOP!".
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.
Do [I|we|you] need to do anything re notification to Dag? Do you feel the file is essentially OK and should I try to install by override the checking? Is that possible?
Thanks for making time, Bill
On Wednesday 15 February 2006 12:49, William L. Maltby wrote:
On Wed, 2006-02-15 at 04:36 -0600, Johnny Hughes wrote:
On Wed, 2006-02-15 at 08:02 -0300, Adriano Frare wrote:
<snip bunch of diag log
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/$basearc h/dag http://www.mirrorservice.org/sites/apt.sw.be/redhat/el$releasever/en/$bas earch/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 ...
A couple of weeks ago, I was advised to install (and presumably use) rpmforge. Recently I moved dag's repo def out of the way and let the rpmforge stuff take over. Can I safely update the rpmforge.repo to not reference the remote mirror list (removing this reference is fraught with risk if changes occur?) and use the local file version (mirrors- rpmforge) updated to look similar to yours and still use rpmforge?
Anyway, I'll do that *unless* you say "STOP!".
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.
Do [I|we|you] need to do anything re notification to Dag? Do you feel the file is essentially OK and should I try to install by override the checking? Is that possible?
that perticular file is most probably not good. don't try to force it in.
/Peter
Thanks for making time, Bill
On Wed, 2006-02-15 at 13:08 +0100, Peter Kjellström wrote:
On Wednesday 15 February 2006 12:49, William L. Maltby wrote:
On Wed, 2006-02-15 at 04:36 -0600, Johnny Hughes wrote:
On Wed, 2006-02-15 at 08:02 -0300, Adriano Frare wrote:
<snip bunch of diag log
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.
<snip>
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.
Do [I|we|you] need to do anything re notification to Dag? Do you feel the file is essentially OK and should I try to install by override the checking? Is that possible?
that perticular file is most probably not good. don't try to force it in.
/Peter
OK. I'll follow that approach and wait.
Thanks again, Bill
On Wed, 15 Feb 2006, Johnny Hughes wrote:
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/$basear... 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.
I am no longer using the createrepo -c functionality after the incident last time.
However it seems in the case of nmap, the checksum in the metadata is wrong. Not sure where this comes from (or how I can get rid of it) since I have created the repodata many times since this issue was first reported.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
On Thu, 2006-02-16 at 00:04 +0100, Dag Wieers wrote:
On Wed, 15 Feb 2006, Johnny Hughes wrote:
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
<snip>
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.
I am no longer using the createrepo -c functionality after the incident last time.
However it seems in the case of nmap, the checksum in the metadata is wrong. Not sure where this comes from (or how I can get rid of it) since I have created the repodata many times since this issue was first reported.
Just wanted to check, since it is a security update, is there anything we (I/you/CentOS...) need to do or is it a wait for the upstream folks to fix something?
TIA Bill
On Tue, 2006-02-14 at 10:55 -0500, Jim Perrin wrote:
for the two packages. Since this is quite sometime after the announcement(?), is it reasonable to suspect another problem? Or, again, am I just being too quick on the draw?
Feel free to ignore this if so. I'll retry getting that security update another time later in the week.
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".
Forgot to say did all that and results are the same. Thanks
-
Adriano Frare -
Dag Wieers -
Jim Perrin -
Johnny Hughes -
Peter Kjellström -
William L. Maltby