Re: Is RPM now stricter about checking for file conflicts?

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

 



On Sun, Oct 28, 2012 at 00:45:33 +0700,
  Michel Alexandre Salim <salimma@xxxxxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ever since I started tracking Fedora 18, Google Music Manager is no
longer installable, and now Oracle's Virtual Box cannot be installed
either (both from upstream Yum repositories).

 https://bugzilla.redhat.com/show_bug.cgi?id=870655

In both cases, RPM and yum aborts with file conflicts -- /lib/modules
for VirtualBox and /usr/bin for google-musicmanager.

It is stricter for F18 or F19, but I am only aware of checks for meta data (timestamps I think) being stricter. I don't know if that is what you are seeing though. I saw some packages that had conflicts on one fedora release not have them on another, even though it was the same version (there hadn't been a build for the newer release). I don't remember if the difference was between F17 and F18 or F18 and F19 though.
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux