Description of problem: attempting an upgrade of a new and up-to-date Mageia-6 (by editing existing on-line-media) fails with conflict with python-chardet-2.3.0-3.mga6.noarch. removing this package (and dependency deluge-1.3.15-1.mga6) allows the upgrade to proceed. if the upgrade is halted after the first approx 179 packages and deluge (and dependencies inc python-chardet) is now installed, the upgrade can be restarted without further incidents. Version-Release number of selected component (if applicable): How reproducible: 2 out of 2 times (i586 and x86_64) Steps to Reproduce: 1.create a new and up-to-date Mga6 2.replace on-line media with cauldron versions 3.attempt upgrade
Assigning to the registered maintainer.
CC: (none) => marja11Assignee: bugsquad => geiger.david68210
What are the real files who are conflicting during the upgrade?
urpmi --auto-update [list of packages] Proceed with the installation of the 177 packages? (Y/n) y Installation failed: file /usr/bin/chardetect from install of python3-chardet-3.0.4-3.mga7.noarch conflicts with file from package python-chardet-2.3.0-3.mga6.noarch urpme python-chardet-2.3.0-3.mga6 To satisfy dependencies, the following 2 packages will be removed (8MB): deluge-1.3.15-1.mga6.noarch (due to missing python-chardet) python-chardet-2.3.0-3.mga6.noarch Remove 2 packages? (y/N) y urpmi --auto-update [list of packages] Proceed with the installation of the 177 packages? (Y/n) y You should restart your computer for glibc restarting urpmi [decline more packages] urpmi deluge To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Release (distrib1)") deluge 1.3.15 1.mga6 noarch geoip 1.6.9 2.mga6 i586 (recommended) python2-chardet 3.0.4 3.mga7 noarch 8.7MB of additional disk space will be used. 2MB of packages will be retrieved. Proceed with the installation of the 3 packages? (Y/n) y urpmi --auto-update [continue with upgrade]
Should be fixed now with python-chardet-3.0.4-4.mga7 Please test it, thanks!
Thanks David, that works great. closing as resolved /fixed
Resolution: (none) => FIXEDStatus: NEW => RESOLVED