Bug 9518 - Installation error on upgrade to 3beta4 (kipi-plugins conflicts with kipi-plugins-htmlexport)
Summary: Installation error on upgrade to 3beta4 (kipi-plugins conflicts with kipi-plu...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Angelo Naselli
QA Contact:
URL:
Whiteboard: 3beta4
Keywords:
: 9525 (view as bug list)
Depends on:
Blocks: 8016
  Show dependency tree / graph
 
Reported: 2013-03-23 20:07 CET by Carolyn Rowse
Modified: 2013-03-26 21:59 CET (History)
4 users (show)

See Also:
Source RPM: digikam
CVE:
Status comment:

Attachments
Error message on upgrade failure (45.20 KB, image/png)
2013-03-23 20:08 CET, Carolyn Rowse 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Carolyn Rowse 2013-03-23 20:07:25 CET 
Description of problem:

I attempted an upgrade in VirtualBox from Mga2 to 3beta4 using the i586 classical installer DVD ISO.  The md5sum is fine.  Size of VM about 14 GB.

The attachment shows the error message which came up right at the end.  This was followed by a screen saying "An error occurred.  Installation failed."



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Carolyn Rowse 2013-03-23 20:08:16 CET 
Created attachment 3647 [details]
Error message on upgrade failure
Carolyn Rowse 2013-03-23 20:16:52 CET

CC: (none) => ennael1, isolde
Whiteboard: (none) => 3beta4

Comment 2 Manuel Hiebel 2013-03-23 22:52:30 CET 
has the install continue ?
if yes can you attach your /root/drakx/report.bug or ddebug.log or upgrade.log (don't remember which one it is for upgrade)
if not, attach an usb key and type bug in the tty3.

Component: RPM Packages => Installer
Blocks: (none) => 8016

Comment 3 Manuel Hiebel 2013-03-23 22:58:09 CET 
from the dev ml, 
"there was a file conflict between kipi-plugins and
kipi-plugins-htmlexport, I urpmed the latter."

so maybe you don't need that, anaselli, as you want

Component: Installer => RPM Packages
Assignee: bugsquad => anaselli
Summary: Installation error on upgrade to 3beta4 => Installation error on upgrade to 3beta4 (kipi-plugins conflicts with kipi-plugins-htmlexport)
Source RPM: (none) => digikam

Comment 4 Carolyn Rowse 2013-03-24 08:59:40 CET 
I couldn't boot the VM again after that, I got an error message in the first few seconds, something to do with Plymouth, and couldn't go any further.
Comment 5 Manuel Hiebel 2013-03-24 12:28:23 CET 
*** Bug 9525 has been marked as a duplicate of this bug. ***

CC: (none) => lupinehorror

Comment 6 Luc Menut 2013-03-24 14:09:25 CET 
The file conflicts between kipi-plugins and kipi-plugins-htmlexport should be fixed with digikam-3.1.0-2.mga3.

CC: (none) => lmenut

Comment 7 Angelo Naselli 2013-03-24 19:04:50 CET 
@Luc are you going to manage the kipi-plugins update problem?
If so thank you very much :)
Comment 8 Luc Menut 2013-03-24 21:35:53 CET 
(In reply to Angelo Naselli from comment #7)
> @Luc are you going to manage the kipi-plugins update problem?

which one?
is there another problem?
Comment 9 Angelo Naselli 2013-03-24 22:57:38 CET 
the one described in comment #3...
Comment 10 Luc Menut 2013-03-25 00:15:35 CET 
(In reply to Angelo Naselli from comment #9)
> the one described in comment #3...

It's the same problem.
I added to kipi-plugins:
Obsoletes:  kipi-plugins-htmlexport < 1:3.1.0
Conflicts:  kipi-plugins-htmlexport < 1:3.1.0

obsoletes to automatically remove kipi-plugins-htmlexport (removed in svn rev. 402557), and conflicts to ensure a proper ordering (remove kipi-plugins-htmlexport before updating to kipi-plugins to 3.1.0) because there are file conflicts.

http://svnweb.mageia.org/packages?view=revision&revision=404810

Hardware: i586 => All

Comment 11 Manuel Hiebel 2013-03-26 21:59:15 CET 
ok closing thanks

Status: NEW => REOPENED

Comment 12 Manuel Hiebel 2013-03-26 21:59:52 CET 
really..

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.