what constitutes an install "conflict"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  (a more detailed followup to an earlier post to fedora-list, but that
seems to be more appropriate here now that i've looked at it more
closely.)

  when i went to install the dpkg RPM i got from www.rpmfind.net, i was
told that there was a file conflict with the file
/usr/sbin/update-alternatives from the chkconfig package.  sure enough,
the current file by that name on my FC1 system is a symlink to the file
alternatives in the same directory, while the dpkg RPM wants to overwrite
that with an actual executable.

  i know i can cram the RPM on with "--force", but i'm always reluctant
to do that.  although, since it's just a symlink, i know i can always
restore it later.  i'm just curious why dpkg thinks it needs an 
update-alternatives program in the first place.

  more to the point, i was interested in whether there was a way to 
query an RPM file to see if there were looming conflicts.  when i tried

$ rpm -qp --conflicts <dpkg file>

i was told there were no conflicts.  ok, so i guess that means no 
conflicts at the package or capability level, but certainly, there's a 
conflict at the file level.  should i not expect to be told about that
as well?  just curious.

  and what's the recommended way to install this rpm, besides just
"--force"?  or is that the way to go in this case?

rday


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux