Bug 18815 - Bad autoreqs in kmymoney (plugins + devel libraries)
Summary: Bad autoreqs in kmymoney (plugins + devel libraries)
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
Depends on:
Reported: 2016-06-29 10:27 CEST by j pierre LAJOIE
Modified: 2016-06-30 17:26 CEST (History)
2 users (show)

See Also:
Source RPM: kmymoney-4.8.0-1.mga6
Status comment:


Description j pierre LAJOIE 2016-06-29 10:27:28 CEST
Description of problem:impossible to install new update 8.0

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

How reproducible:all times

Steps to Reproduce:
1.open ccm look for kmymoney 
2.load and install

Kmymoney is out pb since last uodate MGA6

Postby taboutanche » Jun 29th, '16, 05:44
Hello, in mageia6 64
Since the last update Mageia6 Monday june 27 a new version of Kmymoney (8. 0) was put online.
My previous kmymoney version 7.4 had been overwritten and the new version does not install.
Error : - in case of use of MCC :"Désolé le paquetage suivant ne peut pas être sélectionné
Lib64kmn_mymoney4-4.8.0-1.mga6.x86-64 "
-another message is :
Désolé, le paquetage suivant ne peut pas être sélectionné :
- lib64kmm_mymoney4-4.8.0-1.mga6.x86_64 (en raison de conflit avec kmymoney-devel-4.8.0-1.mga6.x86_64)

if i try to install it in konsole with urpmi i have this message :
"Certains paquages demandés ne peuvent être installés ; kmymoney-devel-4.8.0-1mga6.x86-64(car devel (libkmm_payeeidentifier(64bit) est non satisfait)"

It is impossible to recharge the old version ( from deposits ou URPMI --downgrade,...)

Re: Kmymoney is out pb since last uodate MGA6

Postby jkerr82508 » Jun 29th, '16, 09:55
This is caused by a packaging error. I believe that kmymoney should not require kmymoney-devel. It has been discussed (although I can't at the present locate a link). I expect it will be fixed soon. You may wish to open a bug report to make sure that it isn't forgotten about. https://bugs.mageia.org/
Rémi Verschelde 2016-06-29 10:33:23 CEST

Assignee: bugsquad => lists.jjorge
Source RPM: kmymoney v8.0 => kmymoney-4.8.0-1.mga6

Rémi Verschelde 2016-06-29 10:34:03 CEST

Summary: packaging problèm => Bad autoreqs in kmymoney (plugins + devel libraries)

Comment 1 José Jorge 2016-06-29 11:53:20 CEST
This is an upstream problem, as their install script does not build correctly this lib. I asked for help in an upstream bug report 


but got no answer for now.


Comment 2 David GEIGER 2016-06-29 12:02:41 CEST
So why you have updated this package if now it doesn't work at all and if there are upstream issue in this new release?

Please test locally next time before ask for a freeze push!! Thanks!!

CC: (none) => geiger.david68210

Comment 3 Rémi Verschelde 2016-06-29 12:29:52 CEST
I confirm that this is an upstream bug though it was not properly reported, as kmymoney 4.8.0 it does not build libpayeeidentifier.so (and you confused them with the lib64 suffix, so in this end it was badly triaged).

I think I've debugged it all here: https://bugs.kde.org/show_bug.cgi?id=364387#c10

This is easy to workaround on our side, you need to put the wrongly-named .so in its own library like the other ones, and exclude it in the devel package. But the better fix would of course be for upstream (or us, the patch should be trivial) to fix the CMake buildsystem.
Comment 4 David GEIGER 2016-06-29 15:42:24 CEST
So should be fixed now with kmymoney-4.8.0-2.mga6!
Comment 5 j pierre LAJOIE 2016-06-29 17:47:42 CEST
good job guys
kmymoney works again!
You are very reactive.
Personally I found some faults but quickly corrected.
I would also say that I am delighted by Mageia 6 and you did a great job!
good luck for the next.
you can close this bug.
Comment 6 James Kerr 2016-06-30 17:26:58 CEST
I can confirm that kmymoney-4.8.0-2.mga6 installs without errors.

Closing as fixed.

CC: (none) => jim
Resolution: (none) => FIXED

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