Summary: | app-office/gnucash-1.8.10 works on amd64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ryan Kelly <ryan-gentoo> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | CC: | sirmorcant |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ryan Kelly
2005-01-15 00:29:24 UTC
The problem is, as pointed out in bug 73702, aqhbci and aqhbci-ddvcard and aqhbci-wizard-kde need arch testing in order for gnucash to be marked as working on amd64. I now have access to a test account to use aqhbci and will be trying it out, but it will need someone with a german bank account to test this in order for the aqhbci-ddvcard to be known to work. Of course I can also compile this and _say_ it works meaning that it compiles and can access the test server, but this doesn't help a future german user who's chipcard doesn't function. Anyway I'll report my results when I'm done. Additionally your use flag's don't have ofx, which is another optional gnucash package that would need testing. I have tested this and can verify that libofx does work on amd64. Still OT, but in order to round up comment #8: Message on gnucash-user by Derek Atkins, one of the gnucash devs: === snip === BUG: 1.8.10: Invoices posted with "accumulate splits" create imbalanced transactions Derek Atkins warlord at MIT.EDU Sun Jan 23 23:45:56 EST 2005 I just discovered (and fixed) a bug in 1.8.10 that causes Invoices posted with "accumulate splits" to create imbalanced transactions. This same bug was also creating a memory leak every time you posted a transaction. The bug has been fixed in CVS, but 1.8.10 has the errant patch. You can workaround the problem in 1.8.10 by always posting invoices with the "accumulate splits" option turned off. If you've posted any invoices with 1.8.10 you should check your A/R and A/P accounts and see if the register reports an imbalanced transaction (you'll see a little 'x' box in corner by the transaction value). You will need to unpost and re-post any errant invoices to fix the data entry error(s). I'm hoping I can convince the release engineer to push out a 1.8.11. === snap === oops, sorry, wrong bug (blush) *** Bug 81327 has been marked as a duplicate of this bug. *** i marked it ~amd64 a while ago |