Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 117321 - version/release makes old package appear newer
version/release makes old package appear newer
Product: Fedora
Classification: Fedora
Component: tcpdump (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2004-03-02 15:28 EST by Gene Czarcinski
Modified: 2007-11-30 17:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-03 15:10:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2004-03-02 15:28:10 EST
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.
Comment 1 shrek-m 2004-03-02 18:49:27 EST
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
Comment 3 Thomas Chung 2004-03-03 13:01:25 EST

I have updated Fedora Update Advisory page for tcpdump at
FedoraNEWS.ORG with this issue.


Thomas Chung
FedoraNEWS.ORG (http://fedoranews.org)
Comment 4 Alexandre Oliva 2004-03-03 15:10:08 EST
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 :-)

Note You need to log in before you can comment on or make changes to this bug.