Mel <mel@xxxxxxxxxxx> writes: > James Wilkinson wrote: > >>> me go hmmmm. Whats up with this? Trojan or just a signing slip up? >> >> I suspect it's a signing slip-up. I'm seeing the same thing (on x86_64). > > > Me too. But I noticed that the non x86_64 version was ok. > > yum clean all and reload did not fix it. Looks like a new, signed rpm file has been propagated around. Unfortunately they didn't bother to bump the RPM version number so yum kept on getting some internal error with "range not satisfied" (from memory). Rummaging around /var/cache/yum and removing the old tcpdump* files fixed things, but then users shouldn't have to rummage around cache directories to get a distribution screw-up back on track. This is the sort of thing that makes new users say "linux is too complicated." -wolfgang -- Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/
