Created attachment 4896 [details] ddebug.log i installed a virtualbox vm of mga3 64 bit with kde, i used the downloaded Mageia-4-RC-x86_64-DVD.iso to do an upgrade selecting uk options, this failed some minutes into installing packages with a message regarding @170 packages couldn't be installed and a list of conflicting packages and needed files. sadly this text cannot be cut and pasted from vbox since the shared clipboard is not in operation at that time, i have attached the /root/drakx/ddebug.log obtained by mounting the vm disk image afterwards this is all done in an mga3 64 bit host updated running virtualbox 4.2.16 how reproducible: every time i tried the upgrade steps to reproduce: install mga3 in vm use Mageia-4-RC-x86_64-DVD.iso for upgrade in vm
Please attach the whole /root/drakx/report.bug.xz
CC: (none) => thierry.vignaud
Keywords: (none) => NEEDINFO
or install.log if not available
Attachment 4896 mime type: application/octet-stream => text/plain
(but please compress it before attaching)
Created attachment 4898 [details] report.bug.xz as requested,
Comment on attachment 4898 [details] report.bug.xz I see no errors in it. What's more, after checking, I see "DrakX v15.54" => this is a mga3 report.
Attachment 4898 is obsolete: 0 => 1
isn't the upgrade logs in update.log ?
(In reply to Thierry Vignaud from comment #5) > Comment on attachment 4898 [details] > report.bug.xz > > I see no errors in it. > What's more, after checking, I see "DrakX v15.54" => this is a mga3 report. my apologies, i find the virtualbox interface for snapshots v.confusing, since you can't mount a difference file i thought i had merged the current state but it seems i may have reverted instead aaaarg! i shall start from scratch with no snapshotting (is that a word?). again, mea culpa bascule
Created attachment 4900 [details] install.log.bz2 ok, i just looked at report.bug.xz and yes, i can see why you told me it was an mga3 install, and from there i assumed i had made a mistake with manipulating vbox disk images, now i am not so sure because the install.log has nothing but references to mga4 files and then seems to end in garbage, there is also present in /root/drakx a install.log.1 which seems to be the file from the install of the mga3 i used as a base for the upgrade. i shall do as a i said in my last post but i think that i actually had it right the first time bascule
Ok. That's a cascade of errors. A first transaction failed b/c of a file conflict between vim & asciidoc (bug #11122 which we fixed a couple days ago) B/c of that error, the other packages in the transaction were not installed/upgraded. Thus later transactions were packages depended on packages that were in the transaction that failed could not be installed thus making more transactions to fails, thus more missing dependancies for later transactions & so on. *** This bug has been marked as a duplicate of bug 11122 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE