Hi Martin, Am Donnerstag, 31. Dezember 2009 schrieben Sie: > Hi, > > On Thursday 31 December 2009, Rainer Dorsch wrote: > [...] > > > I was surprised that aqbanking4 deleted/overwrote the aqbanking3 settings > > (if that turns out to be true). I would have expected a message if I > > really want to do that.... > > [...] > > aqbanking-cli never deletes your old data folder, it just imports it and > possibly creates new folders. > > What version of AqBanking were you using before exactly? > > ".banking/" -> AqBanking1, 2 > ".aqbanking" -> AqBanking3 > ".aqbanking/settings" -> AqBanking4 >
Now I understand what happened: I used before aqbanking-3.8.2 now I upgraded to aqbanking-4.2.1. I started gnucash with aqbanking-4.2.1. Now .aqbanking/settings was created. Then I run aqbanking-cli updateconf which found the AqBanking4 configuration. I removed now .aqbanking/settings and aqbanking-cli works as expected: r...@blackbox:~$ aqbanking-cli updateconf Config for AqBanking 4 not found, update needed (-55) Config for AqBanking 3 found, importing Your configuration seems to be ok. r...@blackbox:~$ and gnucash finds the aqbanking account information. If aqbanking-cli updateconf would have asked me if I want to overwrite my aqbanking4 config with the aqbanking3 config, it would have worked right away for me. The whole point of upgrading for me was to get rid of the annoying cert warnings https://bugzilla.gnome.org/show_bug.cgi?id=559670 Micha provided a patch for that. I think the main part of the patch is: Index: src/import-export/aqbanking/gnc-ab-utils.c =================================================================== --- src/import-export/aqbanking/gnc-ab-utils.c (Revision 18540) +++ src/import-export/aqbanking/gnc-ab-utils.c (Arbeitskopie) @@ -804,3 +804,24 @@ return gnc_gen_trans_list_run(ieci->generic_importer); } + +GWEN_DB_NODE * +gnc_ab_get_permanent_certs(void) +{ + int rv; + GWEN_DB_NODE *perm_certs = NULL; + AB_BANKING *banking = gnc_AB_BANKING_new(); + + g_return_val_if_fail(banking, NULL); +#ifdef AQBANKING_VERSION_4_PLUS + rv = AB_Banking_LoadSharedConfig(banking, "certs", &perm_certs, 0); +#else + /* FIXME: Add code for older AqBanking versions */ + /* See QBankmanager 0.9.50 in src/kbanking/libs/kbanking.cpp lines 323ff + for a proper example of how to do this */ + rv = 0; +#endif + gnc_AB_BANKING_fini(banking); + g_return_val_if_fail(rv >= 0, NULL); + return perm_certs; +} I conclude from the patch that the certstore is in aqbanking. I would like to find out first if my certs do not make it to aqbanking or if aqbanking does not do the correct comparison. Can I dump all currently available certs aqbanking is aware of? I hoped for aqbanking-cli, but did not see an appropriate option... Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Aqbanking-devel mailing list Aqbanking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aqbanking-devel
