Description of problem:
FC1 was shipped with tcpdump-3.7.2-7.1, libpcap-0.7.2-7.1, and
arpwatch-2.1all-7.1. The recently announced updated are
tcpdump-3.7.2-7.fc1.1, libpcap-0.7.2-7.fc1.1 and arpwatch-2.1all-7.fc1.1
In each of these cases, rpm and up2date consider the older package to
be "newer" than the update. Therefore the updated packages are
ignored. Given the dependency that many have on up2date selecting the
packages to be updated, this is not a reasonable situation.
i found the thread i was looking for
"alpha vs numeric"
asymmetric triggering bug ??
3.7.2-7.fc1.1 < 3.7.2-7.1
f < 1
I have updated Fedora Update Advisory page for tcpdump at
FedoraNEWS.ORG with this issue.
A testing build containing the fix was uploaded to the testing
channel, with a newer version number than the one that was in the
testing channel before. This should fix it. It did for me :-)
Thanks, Harald (or whoever it was that built the package :-)