Red Hat Bugzilla – Bug 130791
up2date reports file conflicts that rpm doesn't
Last modified: 2007-11-30 17:10:47 EST
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):
is this a multilib box?
Nope, pure i386.
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
OBTW, yum 2.1.10's file conflict behavior seems to match up2date's (in
my experience anyway).
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.
up2date is no longer available in newer releases.