Bug 407056

Summary: KDE Neon Testiing Edition 2019-04-29 seems to have removed KMyMoney
Product: [Applications] kmymoney Reporter: Frank Osborne <wdd5988>
Component: buildsystemAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DOWNSTREAM    
Severity: major    
Priority: NOR    
Version: 5.0.4   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:

Description Frank Osborne 2019-04-29 16:56:46 UTC 
SUMMARY
KDE Neo Edition update on 29 April 2019 removed KMyMoney and did NOT replace it and when I tried to ReInstall it using Discover I got an error 'Dependency Resolution Failed' and I'm unable to reinstall.

STEPS TO REPRODUCE
1. Perform updates to KDE Neon testing edition on 29 April
2. Trying to run KMyMoney using krunner. Program not found.
3. Try to install KMyMoney using Discover
4. Receive error 'Dependency Resolution Failed'. unable to install

OBSERVED RESULT
No KMyMoney

EXPECTED RESULT

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.0
Kernel Version: 4.15.0-48-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz
Memory: 7.7 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 Jack 2019-04-29 20:23:43 UTC 
First, do you mean "Neo" or "Neon" edition?  (I'm not familiar with "Neo" although I admit I don't know much about "Neon" either.)

In either case, however, this is most likely a downstream packaging issue - you should report this to the neon team.  In fact, their website says about the testing edition "Featuring pre-release KDE software built the same day from bugfix branches. Good for testing. There is no QA. Will contain bugs."   This needs to be reported to them, as it may well be a simple oversight or typo in one of their configuration settings.
Comment 2 Frank Osborne 2019-04-30 14:40:58 UTC 
This occurred in KDE Neon Testing edition. I will close this ticket and resubmit to the Neon team.
Comment 3 Jack 2019-04-30 14:45:43 UTC 
If you do report to them, you can reference that bug here, in case anyone else searches here for the same problem.