Description of problem: Start with a clean up-to-date M5, x86_64, nvidia, KDE basic install. Additional apps include: nfs-utils openssh-server rsyslog proftp apache awstats gparted webmin M5 boots to working desktop. All updates installed. Using: Mageia-6-rc-x86_64-DVD.iso 03/23/17 Execute install/upgrade 1min left on install the following error is displayed: An error occured error 'script' failed for glib-6:2.22-21.mga6.x86_64 proceeding also displayed the following errors /etc/imapd.conf from install of lib64nfsidmap0-0.27-1.mga6.x86_64 conflicts with file from package nfsutils-1:1.3.0-6.mga5.x86_64 ktexteditor is needed by kwrite-2:16.12.3-1.mga6.x86_64
Install then terminated.
Please compress (with xz) /root/drakx/ddebug.log which has the time stamp of the upgrade, and attach it to this bug report.
CC: (none) => marja11See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=20111Keywords: (none) => 6RC, NEEDINFO
(In reply to Marja van Waes from comment #2) > Please compress (with xz) /root/drakx/ddebug.log which has the time stamp of > the upgrade, and attach it to this bug report. Sorry, nothing in it. A zero byte file.
A little more work on this install/upgrade. Even after the failed install the test system was able to boot to a working desktop. Most of the M6 worked. I then proceeded to change the repo to the m6 repo and execute a: urpmi --auto-update --auto Almost 500 package were upgraded. A reboot of the system stalled at the three question marks screen.
(In reply to William Kenney from comment #3) > (In reply to Marja van Waes from comment #2) > > > Please compress (with xz) /root/drakx/ddebug.log which has the time stamp of > > the upgrade, and attach it to this bug report. > > Sorry, nothing in it. A zero byte file. That's sad :-( Next time you hit any issues in stage2 (the traditional installer) that make it impossible to proceed, please * attach a USB key * switch to tty2 * type: bug (report.bug will be written to the USB key) * compress with xz and then attach report.bug.xz to your bug report. Thanks :-) Now assuming the error you saw wasn't > error 'script' failed for glib-6:2.22-21.mga6.x86_64 but error 'script' failed for glibc-6:2.22-21.mga6.x86_64 Because we don't have a glib package, but we do have glibc-6:2.22-21.mga6.x86_64 However, _not_ closing this report as duplicate of 20111, because of: (In reply to William Kenney from comment #0) > proceeding also displayed the following errors > > /etc/imapd.conf from install of lib64nfsidmap0-0.27-1.mga6.x86_64 conflicts > with file from package nfsutils-1:1.3.0-6.mga5.x86_64 ktexteditor is needed > by kwrite-2:16.12.3-1.mga6.x86_64 Assigning to KDE team for the latter, even if I don't know what they can do without the full logs. @ Akien WDYT abot the /etc/imapd.conf conflict? Should this bug report be cloned for that? nfs-utils was among the additionally installed apps in Mga5, see comment 0
Assignee: bugsquad => kdeSummary: Errors experianced during M5 -> M6 upgrade attempt => Errors experianced during M5 -> M6 upgrade attempt (ktexteditor is needed by kwrite-2:16.12.3-1.mga6.x86_64)Source RPM: (none) => kateKeywords: NEEDINFO => (none)CC: (none) => rverschelde
(In reply to Marja van Waes from comment #5) > > WDYT abot the /etc/imapd.conf conflict? Should this bug report be cloned for > that? nfs-utils was among the additionally installed apps in Mga5, see > comment 0 It should be in its own bug report yes.
(In reply to Rémi Verschelde from comment #6) > (In reply to Marja van Waes from comment #5) > > > > WDYT abot the /etc/imapd.conf conflict? Should this bug report be cloned for > > that? nfs-utils was among the additionally installed apps in Mga5, see > > comment 0 > > It should be in its own bug report yes. Thanks, it's bug 20586
Priority: Normal => release_blocker
Summary: Errors experianced during M5 -> M6 upgrade attempt (ktexteditor is needed by kwrite-2:16.12.3-1.mga6.x86_64) => Errors experienced during M5 -> M6 upgrade attempt (ktexteditor is needed by kwrite-2:16.12.3-1.mga6.x86_64)
I've had a look a the kate and ktexteditor spec files but I don't see anything wrong - I guess the message might just have appeared because the other issues mentioned in this report forced the upgrade to abort maybe while kwrite was in the transaction. Anyway, without more detailed logs we can't know. Closing as MOVED for now as the other issues mentioned here are tracked in other bug reports.
Status: NEW => RESOLVEDResolution: (none) => MOVED