Bug 2694 - Two KDE handbooks try to uninstall their applications
Summary: Two KDE handbooks try to uninstall their applications
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: John Balcaen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-10 15:20 CEST by Marek Laane
Modified: 2011-09-19 13:36 CEST (History)
1 user (show)

See Also:
Source RPM: kdewebdev4-4.7.1-1.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Marek Laane 2011-09-10 15:20:04 CEST 
Description of problem:
After recent decoupling of KDE applications' handbooks, handbooks of Kfilereplace and Kimagemapeditor can not be installed - rpmdrake shows warning saying that they are in conflict of Kfilereplace and Kimagemapeditor, respectively.


Error message (sorry, in Estonian, but probably easily understandable anyway):

Teiste uuendamiseks tuleb eemaldada järgmine pakett:
kfilereplace-4.7.1-1.mga2.i586
 (konflikti tõttu kfilereplace-handbook-4.7.1-1.mga2.i586-ga)


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Manuel Hiebel 2011-09-10 22:23:09 CEST

CC: (none) => balcaen.john

Comment 1 John Balcaen 2011-09-11 10:13:15 CEST 
It should be fixed with the next release.
I made a stupid typo using a wrong epoch in the conflicts.
Thanks for reporting the bug.

Status: NEW => RESOLVED
Hardware: i586 => All
Resolution: (none) => FIXED
Assignee: bugsquad => balcaen.john
Source RPM: (none) => kdewebdev4-4.7.1-1.mga2.src.rpm

Comment 2 John Balcaen 2011-09-11 10:28:16 CEST 
Well BS is currently broken so i can't push the package and there's also the libpng migration so i'll reopen for now.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 3 John Balcaen 2011-09-19 13:36:56 CEST 
ok package is now available.

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