Bug 15297 - upgrading from KDE Mga4 to Mga5B3 has installer error: 'script' failed for kio4-imap-4.13.3-1.mga5.x86_64
Summary: upgrading from KDE Mga4 to Mga5B3 has installer error: 'script' failed for ki...
Status: RESOLVED DUPLICATE of bug 14971
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-15 09:58 CET by Ben McMonagle
Modified: 2015-02-16 05:58 CET (History)
0 users

See Also:
Source RPM: Mageia-5-beta3-x86_64-DVD
CVE:
Status comment:


Attachments

Description Ben McMonagle 2015-02-15 09:58:21 CET
Description of problem:
upgrading from KDE Mga4 to Mga5B3 has installer error: 'script' failed for kio4-imap-4.13.3-1.mga5.x86_64.
install will complete.


Version-Release number of selected component (if applicable):
Mageia-5-beta3-x86_64-DVD


How reproducible: 


Steps to Reproduce:
1.create new in KDE install of Mga4 and update to latest.
2.run upgrade from Mga5B3 dvd.
3.at end of install, popup advises "an error occurred ".error: 'script' failed for kio4-imap-4.13.3-1.mga5.x86_64.

install will complete



Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2015-02-15 17:59:22 CET
Thanks for the report.  This is mostly likely a duplicate of Bug 14971.  RPM is currently reporting the wrong package for the script error.  If you search for this error in the logs in /root/drakx, you should see adwaita-icon-theme involved in the transaction that produced this error.  If so, please mark as a duplicate of Bug 14971.
Comment 2 Ben McMonagle 2015-02-16 05:58:28 CET
created transaction for installing on /mnt (remove=0, install=0, upgrade=14)
adwaita-icon-theme-3.14.1-1.mga5.noarch

this means duplicate of Bug 14971?

Hopefully I have marked it correctly.

*** This bug has been marked as a duplicate of bug 14971 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.