Hi, On Dienstag 19 Juli 2011, Marc-Jano Knopp wrote: [...] > > martin@gwenhywfar:/tmp$ aqbanking-cli chkacc --rbank=37020500 > > --raccount=5151 4:2011/07/19 21-51-20:aqbanking(25637):de.c: 116: Bank > > data for KtoBlzCheck not found (-51), falling back to default > > martin@gwenhywfar:/tmp$ echo $? > > 0 > > ------------------------------------------X8 > > Btw.: What does the above error message mean? [...]
It just means that there is no bankinfo file delivered by AqBanking (for prepacked binaries there is a bankinfo file for ktoblzcheck), so we let ktoblzcheck use its own file. [...] > But then again, I read somewhere that if aqbanking-cli cannot find > libktoblzcheck and/or ktoblzcheck, it will use its own database (which > might be out of date, but I checked a few more bank code / account > number combinations, and all of them failed). [...] That's true, in fact AqBanking always uses its own database. But checking of account numbers is done be the appropriate library (ktoblzcheck). So while AqBanking knows about the banks it can't check account numbers by itself. That's why AqBanking works well enough without ktoblzcheck as long as you don't need to check account numbers but just need to know the name of a bank identified by its bank code (BLZ). [...] > seems to build (version 5.0.14 as opposed to my currently installed > 5.0.10) plugins that are linked to libktoblzcheck: [...] Which makes me think that the packager decided to build the packages without ktoblzcheck support... Or there is no reference to ktoblzcheck-dev in the builddeps of AqBanking's package for Debian. [...] > > Only if "indifferent" is returned (e.g. meaning that the validity could > > not be verified, e.g. because the remote bank is not yet known to > > ktoblzcheck) the check still passes in addition to the case where the > > combination actually is positively valid. That's because "indifferent" > > doesn't necessarily mean that the combination in fact *is* invalid... > > Hm, I see. On the other side, this is a bit counter-intuitive. At least > I would expect some kind of interaction like "Could not verify bank > code / account number combination. Continue anyway? [Yn]". [...] That was changed by request. Some users often had transfer orders for banks which weren't known to ktoblzcheck. In that case ktoblzcheck can't say whether a combination is valid. Aborting in such a case wasn't an option to them, so I've been asked to change the behaviour to the way it currently is. Asking the user isn't an option either, because aqbanking-cli is supposed to be used non-interactively (e.g. in the background without the possibility of user intervention). Regards Martin -- "Things are only impossible until they're not" Martin Preuss - http://www2.aquamaniac.de/ AqBanking - http://www.aqbanking.de/ LibChipcard - http://www.libchipcard.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
