Bug 391959 - Patch 1c908e6 should be backported to 5.0.0
Summary: Patch 1c908e6 should be backported to 5.0.0
Status: RESOLVED NOT A BUG
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.0.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-17 11:00 UTC by Felix
Modified: 2018-03-17 14:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix 2018-03-17 11:00:17 UTC
Bug 390834 (related to the inability of accepting scheduled entries from the ledger) was fixed by patch 1c908e6, which will be released with 5.0.1 stable. This is a major usability issue, as not being able to work as with the previous versions forces the user to go back and forth between the ledger and the scheduled entries tab.

Can this patch be included in the 5.0.0 branch?
Comment 1 Thomas Baumgart 2018-03-17 12:57:17 UTC
To clarify a few things, there is no such thing as the 5.0.0 branch.

5.0.0 is a release and the number is fixed and will never change. Nevertheless, 5.0.0 marks the starting point of the 5.0 branch, which received a bunch of fixes (as the one you mention). The next maintenance release will be drawn from the tip of this branch, will be named 5.0.1 and, as you can figure out by now, will contain the fix without doubt. It's then up to the packagers to create updates for distro specific packages.
Comment 2 Felix 2018-03-17 13:10:54 UTC
(In reply to Thomas Baumgart from comment #1)
> To clarify a few things, there is no such thing as the 5.0.0 branch.
> 
> 5.0.0 is a release and the number is fixed and will never change.
> Nevertheless, 5.0.0 marks the starting point of the 5.0 branch, which
> received a bunch of fixes (as the one you mention). The next maintenance
> release will be drawn from the tip of this branch, will be named 5.0.1 and,
> as you can figure out by now, will contain the fix without doubt. It's then
> up to the packagers to create updates for distro specific packages.

Then, question: should I just locally apply the patch and recompile the package (in my case, for Arch linux), or would be seen as acceptable contacting the packager to include this specific commit?

Thank you for your time, by the way. I really appreciate your efforts and software.
Comment 3 Jack 2018-03-17 14:41:31 UTC
You could ask, but I doubt Arch or any other distro would respin a package just to add a patch for a non-critical (even though very annoying) bug, especially when a bug-fix version of the application will be released shortly.  

Wait until 5.0.1 is released, then check how soon Arch will package it - and my guess is that they will be rather quick about it.   

If you really want the fix now, then recompiling yourself is probably the best short term option.  As Thomas said, you don't need to apply any patch if you just compile from the head of the 5.0 branch.