After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 538913 - Need a way to release fixes for (German) chart of accounts
Need a way to release fixes for (German) chart of accounts
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: General
git-master
Other All
: Normal normal
: ---
Assigned To: Andreas Köhler
Andreas Köhler
: 473348 (view as bug list)
Depends on:
Blocks: 433428 473506
 
 
Reported: 2008-06-18 09:21 UTC by Rolf Leggewie
Modified: 2018-06-29 22:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rolf Leggewie 2008-06-18 09:21:20 UTC
Please describe the problem:
For gnucash to be usable and supportable in a German business environment (bug 473506), in addition to bringing out yearly updates/additions (bug 473348 and bug 473350) we need a way to release fixes for mistakes we have already shipped in the SKR accounts and which the user has started to use.  Maybe at first this can only be done with gross hacks like sed-scripts, etc.  The SQL-stuff will probably be easier to manipulate.  

Let's think about this some more.  Please share your ideas.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Rolf Leggewie 2008-06-22 07:20:40 UTC
Maybe it is possible to overwrite old account definitions with new ones?  I'll need to test what happens if an account exists already but with a slightly different setup.  If we can overwrite information, we could export the affected accounts into an update package.
Comment 2 Rolf Leggewie 2008-07-07 00:06:47 UTC
*** Bug 473348 has been marked as a duplicate of this bug. ***
Comment 3 Rolf Leggewie 2008-07-07 14:34:56 UTC
http://www.parit.ca/projects/pythongnucash/ ?  Maybe that would be a way manipulate the data?  I am not sure the project is being actively developped.
Comment 4 Derek Atkins 2008-07-07 14:45:01 UTC
No clue.  It's not part of the gnucash project so we cannot depend on it inside gnucash.
Comment 5 Rolf Leggewie 2008-07-10 16:52:17 UTC
It is a part of gnucash now ;-)  And I would have used it anyway if it presented a solution.  Just like I would have used sed/awk if that presented a solution.

We will probably need to store some kind of information inside the gnucash file what version the SKR chart is at.  I am thinking about maybe abusing a dummy, hidden, placeholder account's comment.  Better solutions welcome.
Comment 6 Derek Atkins 2008-07-10 17:32:53 UTC
> It is a part of gnucash now ;-) 

Not for long.  I plan to back out that changeset as it's breaking reports.
Comment 7 Rolf Leggewie 2008-11-14 21:25:39 UTC
I am starting to strongly lean towards supporting SQL-based backends for German accounting only.  That would easily allow all kinds of checks and updates outside of gnucash's limitations.
Comment 8 Rolf Leggewie 2008-11-14 21:26:31 UTC
The SQL backend still has a few hickups to cure, though.  I am confident that can be achieved in a sane timeframe.
Comment 9 John Ralls 2018-06-29 22:05:43 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=538913. Please continue processing the bug there and please update any external references or bookmarks.