Rajesh Singh already did the package. I will update after SuSE Linux 10.0 release.

All required packages were already created and updated. Update is available for 10.1 and 10.0 supplementary.

Hi - I'm one of the gnucash developers, namely the one who maintains the German online banking (HBCI) features. The problem with the newly introduced gnucash-1.8.12 is that the online banking library has changed, but you didn't include all necessary parts for those users who used to use the HBCI features and want to continue to do so. If someone wants to use HBCI in gnucash, he needs the online banking library "aqbanking-1.2.0" (which is included in 10.1beta3) but together with the additional library "aqhbci-1.2.0" https://sourceforge.net/projects/aqhbci and "aqhbci-qt-tools-1.0.7". Alternatively, the versions aqbanking >= 1.3.0 had a major packaging redesign and already included those other packages. 

In conclusion: The current gnucash-1.8.12 cannot provide the same online banking features that gnucash-1.8.9 did; it will abort any such attempts with an error message similar to "No backend provider found". To fix this,
- either add the packages aqhbci-1.2.0 and aqhbci-qt-tools-1.0.7, 
- or upgrade "aqbanking" to any version >= 1.3.0.

On the positive side, I'd like to point out that you can probably remove the library "openhbci" from your distribution altogether, as it was used only for gnucash <= 1.8.9 and is no longer necessary.

Jürgen, can you comment on what we can do?

Oh, actually, once I'm at this: Unfortunately your version of the auxiliary library "gwenhywfar-1.19.2" is too new for your chosen older version of "aqbanking-1.2.0", as noted on http://www.linuxwiki.de/AqBanking (see "Installationsanleitung bei früherer Version") and it will not work correctly. (Sorry for that.) For "aqbanking-1.2.0" you would need "gwenhywfar-1.14.0" at maximum. It will not work with newer gwenhywfar. 

To reiterate the two alternatives from above: To continue to provide HBCI homebanking with gnucash, you need to 
- either downgrade gwenhywfar to "gwenhywfar-1.14.0" and add the packages aqhbci-1.2.0 and aqhbci-qt-tools-1.0.7
- or upgrade aqbanking to any version >= 1.3.0. (In that case, according to http://www.linuxwiki.de/AqBanking it is suggested to create sub-packages for all additional requirements, i. e. one aqbanking-qt3 package, one aqbanking-ofx package etc. A sample spec file is included in the aqbanking package from 1.3.1 onwards.)

(Sorry for again adding more issues) One more thing: To achieve full feature parity with the gnucash-1.8.9 features, HBCI chipcards should probably be supported as well. 
* In the gnucash-1.8.9/openhbci-0.9.x days, this was achieved by an additional package "openhbci-plugin-ddvcard" which required libchipcard-0.9.0 (libchipcard-0.9.1 is included in your 10.1beta3). IIRC the additional package openhbci-plugin-ddvcard wasn't provided in the original SUSE distribution, but at least all its requirements were.
* With aqbanking-1.2.0, this will be achieved by an additional package "aqhbci-plugin-ddvcard" (1.0.1) which requires libchipcard2-1.9.9, the successor of libchipcard. If you stick to this aqbanking option, you might consider upgrading your libchipcard package so that the aqhbci-plugin-ddvcard package can at least be easily compiled.
* With aqbanking >= 1.3.0, this does not any longer require an additional package, but only the existence of the libchipcard2 >= 1.9.13. If you upgrade libchipcard to at least this number, the distribution will directly provide HBCI chipcard support and neither the users nor you have to take any additional action in case someone wants the HBCI chipcards.

I am afraid that it's too late for aqbanking, libchipcard update due to crypto regulations freeze (in December last year).

And as far as I understand, we cannot provide proper HBCI function for gnucash-1.8.12 with libchipcard-0.9.x. Isn't it?

I have discussed update to libchipcard2 in past with Stephan Binner. Stable release of libchipcard2 was planned to mid of January, which was too late for cryptographic package. So we have decided to postpone the upgrade (and consequent aqbanking update) for SuSE Linux 10.2 not knowing these consequences.

If aqhbci-qt-tools does not contain any cryptographic technology, it may be possible to add it as a new package, but it may be unsufficient.

(In reply to comment #8)
> And as far as I understand, we cannot provide proper HBCI function for
> gnucash-1.8.12 with libchipcard-0.9.x. Isn't it?

HBCI has different modes of operation, distinguished by the user authentification: 1. RSA-keyfile, 2. DES Chipcards, 3. PIN/TAN numbers. With gnucash-1.8.9, #1 was supported always (and didn't need libchipcard), #2 was supported when the additional package was installed, and #3 was not yet supported (but is new in gnucash-1.8.12 with aqbanking). If you say libchipcard cannot be updated, then yes, your gnucash-1.8.12 cannot support mode #2 at all, no matter what aqbanking this is.

As for the other modes: In your current combination the other modes will not work, too, because of two problems: 1. The incompatibility of newer gwenhywfar-1.19.2 with older aqbanking-1.2.0 which will abort at runtime, and 2. the missing "aqhbci-1.2.0" and "aqhbci-qt-tools-1.0.7". The incompatibility between gwenhywfar and aqbanking requires that either one is changed, either the older upgraded or the newer downgraded. However, gwenhywfar contains cryptographic code as well, so I'm not sure whether such a downgrade is allowed for you. If neither gwenhywfar nor aqbanking can be changed, then gnucash-1.8.12 will ship with broken HBCI functions which will seem to be available but will abort at runtime.

The package aqhbci-qt-tools does not contain any cryptographic technology, but it has the compile time requirement of the package aqhbci, which contains code related to cryptographic technology. You would need to add both, otherwise that wouldn't make any sense. And this still doesn't solve the gwenhywfar/aqbanking version problem.

Let's fix this properly for 10.2.  Sorry, this is too late now.

Maintainer, please do an update by the end of april for everything so that it can be tested together.

Christian, for my understanding: would a downgrade of GnuCash-1.8.11 for SUSE Linux 10.1 solve the hbci problem?

(In reply to comment #11)
> Christian, for my understanding: would a downgrade of GnuCash-1.8.11 for SUSE
> Linux 10.1 solve the hbci problem?

No. In terms of library requirements and usage, gnucash 1.8.10, 1.8.11, and 1.8.12 are exactly identical; the major change was from 1.8.9 to 1.8.10. 

Iff you want to keep providing the HBCI functions, then only a downgrade to gnucash-1.8.9 (sigh) would be an option, because 1.8.9's hbci library "openhbci" is still included.

(huh? /me wonders why bugzilla switched this to NEEDINFO... switching back to the original ASSIGNED status)

By the way, if you talk about "end of april", then you might be interested in the progress of gnucash towards a gtk2 release. Currently the first unstable 1.9.0 is out and this is of course still far from being stable, but by the "end of April" you might already be in a position to decide whether to include one of the gtk2-versions. Current release schedule http://wiki.gnucash.org/wiki/Release_Schedule 

In terms of HBCI library requirements the gnucash-1.9.x series is unchanged from gnucash-1.8.12, requiring aqbanking>=1.0.0, but the final gnucash-2.0.0 will probably require aqbanking-1.3.0.

So just now we have two options for 10.1:
- Keep things as is (i. e. broken).
- Degrade gnucash.

For 10.2, I would prefer upgrade to latest versions, including Gnucash2. It will allow us to drop major part of GNOME1.

I have just started packaging of Gnucash2 beta and related packages.

Please download it from ftp://ftp.suse.com/pub/people/sbrabec/gnucash2 and its mirrors and let me know, what is 

Packages should work with SuSE Linux 10.1.

Please test its function and completness. I cannot test some features at all (smart card support, banking interface). Some opensc stuff is still missing and will be added later.

I haven't tested the runtime functionality (no SuSE10.1 at hand), but from checking the packages' file lists all seems fine.

However, there is one last packaging issue with gnucash and the auxiliary library "qof": In gnucash-1.9.x up to 1.9.5, it was possible to select either to link gnucash against an external qof installation or to use gnucash's internal copy of qof sources, and you obviously chose the former approach. But unfortunately there have been some unresolved arguments between the qof maintainer and the rest of the gnucash developers in April'06. Subsequently some architectural changes were done in gnucash and gnucash's copy of qof, but not in the separate project qof. Because of that, gnucash-1.9.6 and later will *not* have the option to link against an external qof installation anymore, http://svn.gnucash.org/trac/changeset/13930. This will most probably not change until the 2.0.x stable releases (maybe in later series, though). Because of that, the gnucash developers recommend to include the compiled libqof of gnucash's qof copy into the gnucash package, as in gnucash-1.9.6 and later gnucash unfortunately does not accept an external qof package anymore. Sorry for that.

Thanks for the info. I have unresolved qof issue about building against libgda - SuSE Linux 10.1 has a newer version of libgda with a different .pc and soname than qof expects.

The packages can have some devel splitting problems - for standard packages, we package .so and .la files as part of -devel subpackage, not installed by default.

But some parts of gnucash need .so for loading and other parts use ltdl and .la. I have tried to catch all these issues, but maybe I failed.

That is why I propose not to install -devel package for testing. If the installation of -devel will fix any such problem, please let me know.

Packages are submitted for SuSE Linux 10.2.

*sigh* we (=gnucash upstream) would definitely have preferred to ship gnucash-1.9.6 (released 2006-05-14) instead of 1.9.5 because, as explained above, with your 1.9.5 package you are using an external "qof" package whereas with 1.9.6 and newer (including 2.0.0) gnucash will neither compile nor run with an external "qof" package but instead only with the internal copy. Whatever. 

yeah, next time make sure gnucash releases a working version in time :)

SuSE Linux 10.2 is far enough, so I hope we will include gnucash-2.0.x.

I packaged 1.9.5 because it was the latest version in time of packaging the whole package stack.