Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 130791 - up2date reports file conflicts that rpm doesn't
up2date reports file conflicts that rpm doesn't
Product: Fedora
Classification: Fedora
Component: up2date (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Bret McMillan
Fanny Augustin
Depends On:
  Show dependency treegraph
Reported: 2004-08-24 15:07 EDT by Alexandre Oliva
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-31 23:48:37 EDT
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 Alexandre Oliva 2004-08-24 15:07:02 EDT
Description of problem:
Starting from bind-9.2.4rc7-7 man-pages-1.66-2 installed on the
system, running up2date to a local (file://) yum repository containing
today's rawhide (headers generated locally with yum-arch), up2date
reports a file conflict for the resolver man page, but installing
man-pages-1.67-2 with rpm before or after running up2date -u
--exclude=man-pages, that updates to bind-9.2.4-EL4_1, neither up2date
nor rpm report any conflict whatsoever.

It appears that up2date is being overly conservative in its conflict

Version-Release number of selected component (if applicable):
Comment 1 Adrian Likins 2004-08-26 15:51:14 EDT
is this a multilib box?
Comment 2 Alexandre Oliva 2004-08-27 09:01:48 EDT
Nope, pure i386.
Comment 3 Barry K. Nathan 2004-10-25 05:44:19 EDT
It could also be that RPM is too liberal now (as opposed to up2date
being too conservative). See bug 131766 for more info on RPM's
behavior change.
Comment 4 Barry K. Nathan 2004-10-25 06:36:05 EDT
OBTW, yum 2.1.10's file conflict behavior seems to match up2date's (in
my experience anyway).
Comment 5 Matthew Miller 2006-07-10 18:34:30 EDT
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!
Comment 6 Alexandre Oliva 2006-07-31 23:48:37 EDT
up2date is no longer available in newer releases.

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