Description of problem: md5 error while upgrade to Cauldron from Mageia 6 Version-Release number of selected component (if applicable):Cauldron How reproducible: Following these steps:urpmi.removemedia -a to remove all your current urpmi repositories. After that, you need to add the cauldron repositories. If you have a 32-bit machine urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.i586.list' If you have an x86-64 machine: urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.x86_64.list' And then: urpmi --auto-update --auto Steps to Reproduce: 1. 2. 3.
Do you have the logs ?
Assignee: sysadmin-bugs => bugsquadProduct: Infrastructure => MageiaComponent: Others => RPM PackagesVersion: unspecified => 6
Yes, please attach log.txt that is the result of running, as root: journalctl -a --since="YYYY-MM-DD hh:mm" --until="YYYY-MM-DD hh:mm" and adjust the --since time to right before you started to upgrade and the --until time to where you got the error. If you can't login to the system, then use a Live DVD in live mode, or another install on the same computer, to mount the root partition of the install that fails to boot. There's a directory with a very long hexadecimal name in /that/partition's/var/log/journal/ Now run, as root, journalctl -D /path/into/that/hexadecimal/directory/ > log.txt please try to add --since="YYYY-MM-DD hh:mm" --until="YYYY-MM-DD hh:mm" before the path, but I'm not 100% sure those switches can be used with the -D option. and then attach log.txt to this bug report. (compress it with xz if it's too large to attach)
CC: (none) => marja11Keywords: (none) => NEEDINFOSummary: MD5 error upgrading Maheia 6 to cauldron with URPMI => MD5 error upgrading Mageia 6 to cauldron with URPMI
After use xz, log file still too big do attach.
(In reply to Gilberto F da Silva from comment #3) > After use xz, log file still too big do attach. So adding --since and --until date× didn't work? instead of xz log.txt, please try with xz -9 --text log.txt that should give better compression
Without logs, there is, unfortunately, nothing we can do :-( Anyway, cauldron now is very different from cauldron in January, whatever caused this error did most likely already get fixed. Closing.
Status: NEW => RESOLVEDResolution: (none) => OLD