how to update using new *.fc1.* rpms?

[jpkole]

I'm a newb @ this... please be patient.

I have a fedora core 1 installation with
with all products installed... including:
tcpdump-3.7.2-7.1

I pulled the new updated version:
tcpdump-3.7.2-7.fc1.1.i386.rpm

When I try to install it, I see:
# rpm -Uvh tcpdump-3.7.2-7.fc1.1.i386.rpm
Preparing... ############### [100%]
package tcpdump-3.7.2-7.1 (which is newer than tcpdump-3.7.2-7.fc1.1) is already installed


I must not understand how this is
suppose to work... although the
other 174 updates went in fine.

Any help would be appreciated.

Regards,
jpkole

[Jman]

It seems you already have tcpdump installed, as rpm is complaining you already have a newer version. Do you need the newer version?

If you don't like manually downloading rpms you could use the yum software updater , which downloads and installs rpms for you.

[jpkole]

Well, I did have tcpdump... but I got an
email notification from the mail alias of
fedora-announce-list@redhat.com and
it said:

Fedora Update Notification
FEDORA-2004-090
2004-03-02
---------------------------------
Name : tcpdump
Version : 3.7.2
Release : 7.fc1.1
----------------------------------
Update Information:

Updated tcpdump, libpcap, and
arpwatch packages fix vulnerabilities
in ISAKMP and RADIUS parsing.
....<snip>....

So, naturally, I thought I should update
to the more secure version. And now
I'm puzzled as to why it doesn't work
since this notifcation came today.

I tried the yum command:
yum upgrade tcpdump

And it reported:
No Upgrades available for tcpdump.

But why would it say that if this is a
brand new update/alert?

Thanks and regards,
jpkole

[tchung]

Hello,

You're right. There seems to be an issue with the latest tcpdump update package. I believe it has either older release number or older epoch number in the rpm spec.

I will contact the Red Hat developer to resolve this issue.

Thomas

[jpkole]

Please note there are actually 3 packages that did not install for the same reason:

arpwatch-2.1a11-7.fc1.1
libpcap-0.7.2-7.fc1.1
tcpdump-3.7.2-7.fc1.1

I believe that all came as a result of the tcpdump update.

Thanks and regards,
jpkole

[mhelios]

I also see this problem with the latest gnome-panel update. I currently have version 2.4.1-0.fc1 while up2date is offering 2.4.2-3 as an update. The "fc1" tag in the name seems to be tripping things up...

I've reported the issue, I'll update with the latest to the problem when possible.