https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #19 from Jack ---
The problem is that if it can't simply be cherry-picked, then it means a lot of
work to modify it so it can be applied to the 5.1 branch. This means commit to
that branch is not likely.
There has been no formal announcemen
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #18 from Antoine T ---
Hi, is-there chance we see a small patch in 5.1 branch? I know it is too big to
cherry-pick, but this is just about the part that is doing the setMemo.
BTW, will there be a new release from master branch in 2025, if t
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #17 from Thomas Baumgart ---
> Hmm if I am looking at the build related to my test:
> https://binary-factory.kde.org/view/AppImage/job/KMyMoney_Release_appimage-centos7/607/
> , it looks to me like the build is done against master branch, no
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #16 from Antoine T ---
(In reply to Jack from comment #15)
> I'm sorry if it wasn't clear enough, but this patch is not yet available in
> the 5.1 branch, so you will continue to see the problem in 5.1.3 and even
> the nightly build from the
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #15 from Jack ---
I'm sorry if it wasn't clear enough, but this patch is not yet available in the
5.1 branch, so you will continue to see the problem in 5.1.3 and even the
nightly build from the 5.1 branch. It is only available in master br
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #14 from Antoine T ---
Ok, I tested with
https://binary-factory.kde.org/view/AppImage/job/KMyMoney_Release_appimage-centos7/lastSuccessfulBuild/artifact/kmymoney-5.1-607-linux-gcc-x86_64.AppImage
. Version info shows: 5.1.3-2fecc3fb5
The is
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #13 from Jack ---
First, as Thomas said in his last comment, the patch needs to be backported
since it can't simply be cherry-picked. (I'm quite sure this has not been done
yet.) This is because the code involving the change has changed to
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #12 from Antoine T ---
(In reply to Jack from comment #10)
> Antoine, I'm a bit confused. Is the bug currently that when doing a QIF
> import with 5.1.2, if the Payee is changed based on matching rules, you lose
> the information in the ori
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #11 from Thomas Baumgart ---
To make it easier, here is the (corrected) description from bug 463854:
-8<
STEPS TO REPRODUCE
1. Create a QIF file containing
---
D12/12/2022
T-12.10
PCARTE 09/12/22 AGRCSTCB*4563
---
2. Cre
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #10 from Jack ---
Antoine, I'm a bit confused. Is the bug currently that when doing a QIF import
with 5.1.2, if the Payee is changed based on matching rules, you lose the
information in the original field? I know for sure this was fixed in
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #9 from Antoine T ---
*** Bug 463854 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=351535
Antoine T changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=351535
Jack changed:
What|Removed |Added
Status|CLOSED |RESOLVED
CC|ostroffjh@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #6 from Antoine T ---
Oups cannot set the status as FIXED. I closed it anyway.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=351535
Antoine T changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #5 from Antoine T ---
Hi, sorry
https://bugs.kde.org/show_bug.cgi?id=351535
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #3 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=351535
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=351535
--- Comment #1 from Justin Zobel ---
Thank you for the bug report.
As this report hasn't seen any changes in 5 years or more, we ask if you can
please confirm that the issue still persists.
If this bug is no longer persisting or relevant please change
19 matches
Mail list logo
