Dear Micha, I tried for myself yesterday. I built upstream tarball 5.8.1 using your libaqbanking_5.7.8-3.debian.tar.xz. I needed the following changes in exported symbols to successfully build a debian package:
cat diff_libaqbanking35.symbols 83,84d82 < AB_AccountType_fromChar@Base 5.8.1 < AB_AccountType_toChar@Base 5.8.1 485,488d482 < AB_Banking_RuntimeConfig_GetCharValue@Base 5.8.1 < AB_Banking_RuntimeConfig_GetIntValue@Base 5.8.1 < AB_Banking_RuntimeConfig_SetCharValue@Base 5.8.1 < AB_Banking_RuntimeConfig_SetIntValue@Base 5.8.1 1499a1494 > #MISSING: 5.5.1# AB_Transaction_GetCreditorIdentifier@Base 4.2.3+svn.r1797 1522a1518 > #MISSING: 5.5.1# AB_Transaction_GetMandateReference@Base 4.2.3+svn.r1797 1621a1618 > #MISSING: 5.5.1# AB_Transaction_SetCreditorIdentifier@Base 4.2.3+svn.r1797 1644a1642 > #MISSING: 5.5.1# AB_Transaction_SetMandateReference@Base 4.2.3+svn.r1797 But I can't tell whether this may pose problems with debian policy to remove symbols from a package? As far as I understand the gnucash git commit100ef2a01d, version 5.7.9 should also contain the necessary code to pass the registration information. - online browseable at https://github.com/Gnucash/gnucash/commit/100ef2a01decda3ed54cf7204ae38bfd8766521d Unfortunately, gnucash even in unstable (and any released version AFAIK) does not yet contain the necessary registration code. But I was able to get rid of the HBCI warnings when building a debian package from the git maint branch against libaqbanking 5.8.1. See gnucash bugreport #935503 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935503 Maybe his can help to create a stable-backport, o even stable-updates package? Yours Matthias Merz -- Ovfg QH arhtvrevt. :)
smime.p7s
Description: S/MIME cryptographic signature
