| Summary: | conflicts in upgrading from mga5 to mga6 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Chris Denice <eatdirt> |
| Component: | RPM Packages | Assignee: | Barry Jackson <zen25000> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | release_blocker | CC: | jani.valimaa, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | eigen3-3.3.3-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Chris Denice
2017-03-11 11:18:32 CET
Priority:
Normal =>
release_blocker
Rémi Verschelde
2017-03-11 11:26:30 CET
CC:
sysadmin-bugs =>
(none)
Marja Van Waes
2017-03-11 13:15:44 CET
CC:
(none) =>
marja11 (In reply to Chris Denice from comment #0) > > The same happened with lib64jsoncpp-devel claiming a conflict on the file: > /usr/include/jsoncpp/json > CC'ing wally for that one, even if it should go into a separate report CC:
(none) =>
jani.valimaa Conflicts can happen if there's directory <-> symlink conversion. From https://fedoraproject.org/wiki/Packaging:Directory_Replacement "Due to a known limitation with RPM, it is not possible to replace a directory with any kind of file or symlink, nor is it possible to replace a symlink to a directory with a directory, without RPM producing file conflict errors while trying to install the package." (In reply to Jani Välimaa from comment #2) > Conflicts can happen if there's directory <-> symlink conversion. > And that's the case with eigen3 and jsoncpp. In both pkgs directory is changed to symlink. Fixed all mentioned pkgs: * eigen3: added %pretrans script to remove old directory * jsoncpp: added %pretrans script to remove old directory * guvcview: splitted out translations from lib pkg (as lib major was changed, two different pkgs provided translation files with the exact same name -> conflict). Thanks Wally, you rock!! Can this bug be closed? (In reply to Frédéric Buclin from comment #6) > Can this bug be closed? I think so, wally pushed: eigen3-3.3.3-2.mga6 jsoncpp-1.6.5-6.mga6 guvcview-2.0.5-3.mga6 Status:
NEW =>
RESOLVED |
Just did a mga5 upgrade to cauldron on the command line with urpmi. Everything went smooth, up to the usual issues with mirror out-of-sync. However a few conflicting files appeared, from reasons that I don't understand. For instance: installing libx11-common-1.6.5-1.mga6.x86_64.rpm lib64vcd0-0.7.24-11.mga6.x86_64.rpm eigen3-devel-3.3.3-1.mga6.noarch.rpm x11-data-xkbdata-2.20-1.mga6.noarch.rpm tor-0.2.9.10-1.mga6.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ############################################################ Installation failed: file /usr/include/eigen3/Eigen from install of eigen3-devel-3.3.3-1.mga6.noarch conflicts with file from package eigen3-devel-3.2.2-3.mga5.noarch How this is possible? eigen3-devel-3.3.3-1.mga6.noarch is clearly newer than eigen3-devel-3.2.2-3.mga5.noarch, no conflicts should occur !?!?! The same happened with lib64jsoncpp-devel claiming a conflict on the file: /usr/include/jsoncpp/json and also on one of my package, guvcview. A conflict appeared on a language file gview-v4l2core.mo appearing in there in the spec file: %files -n %{libgvv4l2name} -f gview_v4l2core.lang I set this bug as release blocker, just to attract attention in case something nasty is going on. Any idea how to fix this? At least for my package guvcview, I do not get it! Thanks! Cheers, Chris.