Package dependencies broken

Bug #209181 reported by Bastian Doetsch
22
Affects Status Importance Assigned to Milestone
libaqbanking (Ubuntu)
Fix Released
Critical
Reinhard Tartler
libchipcard (Ubuntu)
Fix Released
Undecided
Unassigned
libktoblzcheck (Ubuntu)
Fix Released
Undecided
Unassigned
qbankmanager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

libaqbanking is currently uninstallable in hardy. It also fails to build from source because of an incompatible version of libgwenhyfar in the archive.

Updated packages for testing have been uploaded to the gnucash PPA. Please install them with the following instructions:

execute the following instructions in a shell:

cat <<EOT | sudo tee -a /etc/apt/sources.list
deb http://ppa.launchpad.net/gnucash/ubuntu hardy main
deb-src http://ppa.launchpad.net/gnucash/ubuntu hardy main
EOT

sudo apt-get update
sudo apt-get install qbankmanager gnucash libaqbanking-plugins-libgwenhywfar47 \
    libchipcard-libgwenhywfar47-plugins

Now please startup qbankmanager. If you have an online banking account, try to use it.

Revision history for this message
Reinhard Tartler (siretart) wrote :

this is pretty critical for the package. explanation follows:

Changed in libaqbanking:
assignee: nobody → siretart
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
Reinhard Tartler (siretart) wrote :

This is pretty severe. It seems that the copy of libgwenhywfar in the hardy archive is to new for the old copy of libaqbanking:

libgwenhywfar | 3.0.1-1 | http://archive.ubuntu.com hardy/universe Sources
libaqbanking | 2.3.3-2 | http://archive.ubuntu.com hardy/universe Sources

In debian, we have these versions:
libgwenhywfar | 3.2.0-1 | http://ftp.de.debian.org sid/main Sources
libaqbanking | 3.3.0+dfsg-1 | http://ftp.de.debian.org sid/main Sources

In anycase, libaqanking fails to build from source, because we don't have the libgwenhywfar38-dev in the archive; it has been renamed by the new libgwenhywfar to libgwenhywfar47-dev.

This makes it clear that the existing package in hardy hasn't seen any testing at all. I basically see now the following options:

a) update to the (new upstream) versions of libaqbanking and libgwenhyfar in unstable. This would be preferred by many users, since it introduces support for HBCI using gnutls (so private rebuilds for making gnucash online banking capable aren't necessary anymore).

b) revert to the versions we had in gutsy.

c) further investigations/research if we can just downgrade libgwenhywfar to a version that is known to build against the exact version of what we have right now in hardy.

The list is approximatly my preferred list of options.

Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... seems to have the following rdepends in regards to source packages:

libchipcard
qbankmanager

anything I missed (the number of binary packages from libaqbanking might have confused me)?

Revision history for this message
Reinhard Tartler (siretart) wrote :

Right.

I have now uploaded the following packages to the gnucash team PPA for hardy:

libktoblzcheck
libchipcard
libgwenhywfar
qbankmanager

all of them are unmodified sources from debian/unstable, so they could be just synced from debian.

Revision history for this message
Reinhard Tartler (siretart) wrote :

setting back to state NEW for motu-release consideration

Changed in libaqbanking:
status: Confirmed → New
Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... the only affected package, which is not a library package is qbankmanager, right?

I guess I'm ok with the upgrade of the libraries in general, but I'd like some testing of qbankmanager first, thanks!

Revision history for this message
Reinhard Tartler (siretart) wrote :

sure, no problem. I've just added bugtasks for the other missing packages.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Ack from me to go forward once testing is done.

Revision history for this message
Reinhard Tartler (siretart) wrote : Call for testing: qbankmanager/gnucash/hbci users

Rationale: cf. https://launchpad.net/bugs/209181

If you are runnung hardy and use qbankmanager, please give the packages
from http://launchpad.net/~gnucash/+archive a shot. They are unmodified
sources from debian/unstable, and I expect them to work in hardy just
fine.

How to test: execute the following instructions in a shell:

cat <<EOT | sudo tee -a /etc/apt/sources.list
deb http://ppa.launchpad.net/gnucash/ubuntu hardy main
deb-src http://ppa.launchpad.net/gnucash/ubuntu hardy main
EOT

sudo apt-get install qbankmanager gnucash

Now the latest versions of qbankmanager and gnucash should be available
for use on your system. Please test them and report your experiences
(both positive and negative) to https://launchpad.net/bugs/209181.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

I'm going to test it now. Feedback follows...

Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

Okay. Here's what I have so far:

a) Everything installs fine. No apt-errors anymore.

b)Gnucash lacks its symbol in the start menu.

c) Seems to be compiled without any online modules - do I have to do it myself or will it be enabled by your builds as gnutls is now supported by aqbanking?

Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

Just started QBankingManager. It seems to import all HBCI config and account data correctly and I couldn't spot a bug so far - but as I'm using Gnucash I'm no authority on this...

Revision history for this message
Reinhard Tartler (siretart) wrote :

Somehow the upload of libaqbanking to the PPA has gone missing. I've reuploaded it and updated the test instructions in the bug description.

description: updated
Revision history for this message
Reinhard Tartler (siretart) wrote :

okay, I've now tested the packages from the PPA myself in a virtualbox, and the packages seem to work just fine for me.

I'd therefore recommend syncing the mentioned packages from unstable into hardy.

Regarding my note about gnucash: I'm sorry for the misinformation, gnucash still needs to be ported to the new libaqbanking, which is not finished yet. See http://wiki.gnucash.org/wiki/AqBanking3_Porting for details. This means we have no regression, but still no working gnucash-hbci in ubuntu.

Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

So in my opinion there are the following options, as I don't think the porting will be done anytime soon:

1) Install Gutsy aqbanking packages (and lock them in apt) and compile gnucash 2.2.4 against it.

2) Introduce the gutsy packages with a different name and make gnucash depend on them

3) Introduce the new packages with a different name and keep the aqbanking packages from gutsy.

4) Keep the packages from Gutsy and upload the new packages in a later Ubuntu release when the porting is done.

Anymore options?

I'd like option 3) best, as this doesn't obsolete the documentation available for enabling HBCI support in gnucash. Moreover, people that want to use the new packages would have them available in the repository.

Revision history for this message
Reinhard Tartler (siretart) wrote : Re: [Bug 209181] Re: Package dependencies broken

options 2 & 3 are the maximum efford, and I don't think someone can come
up with such packages in a timely fashion. Furthermore, option 2 can be
implemented outside the archive, like in the gnucash PPA.

I don't quite understand the difference between 1 & 4, but both of them
require downgrading existing packages in hardy. I am proposing the
opposite: Update them to the version currently in unstable!

Regarding the possibilty of compiling gnucash-hbci:

 - Since debian has already updated, I expect howtos and documentation
   how to do that anyway will appear soon

 - you can still compile and install libaqbaking2 yourself in /usr/local
   or in your home

 - hardy will be a LTS. Backports of gnucash when ready will be possible
   as soon as the porting has been done.

Still waiting for input of motu-release.

Revision history for this message
StefanPotyra (sistpoty) wrote :

Bastian and Reinhard, thanks for your insights:

This late in the cycle, I believe we shouldn't introduce new source packages, so 2 & 3 don't seem good options to me.

Likewise, I'm not too much favouring a downgrade as well. Am I right, that once gnucash is ported to the new libaqbanking, it can support HBCI out of the box, or are there still problems preventing us from building such a package?

Revision history for this message
Reinhard Tartler (siretart) wrote :

Currently, gnucash is not linked against libaqbanking because of license
problems (gnucash being GPL must not link against libaqbanking because
it links against libssl. libaqbanking itself is GPL with ssl linking
exception that gnucash is missing).

In order to have gnucash with HBCI support, users have to recompile the
packages with the configure option --enable-hbci. This however FTBFS
with aqbanking 3.

I agree that ideally we would ship both. Maybe we can stick to
aqbanking2 in hardy, and provide aqbanking3 in a gnucash PPA or
hardy-backports. The question is whether we find a solution that fixes
libaqbanking in hardy without updating to libaqbanking3.

Patches welcome.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Revision history for this message
StefanPotyra (sistpoty) wrote :

Do you know, if gnucash might adopt the ssl-exception in the future? If so, I guess the best thing would be to upgrade now, and backport gnucash from intrepid, once this has happened.

Revision history for this message
Reinhard Tartler (siretart) wrote :

AFAIUI, it is not possible to reach all former gnucash developers so that a license change is unlikely.

However this bug is NOT about gnucash (which would be bug #5973), but about getting libaqanking and qbankmanager in a releasable state.

Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

I think Reinhard is right - the ssl-exception issue in gnucash is years old, so I doubt a license change will take place. Although the bug is about aqbanking it popped up due to me not being able to make my private gnucash build with hbci enabled.

So obviously I'd greatly appreciate if the aqbanking2 packages could find their way into hardy, even though I can't supply patches or insights which version of libgwenhyfar had to be included to enable aqbanking2 to build. I'll try to e-mail Martin Preuss, perhaps he'll supply a solution.

Thanks to all of you for your help so far!

Revision history for this message
StefanPotyra (sistpoty) wrote :

well, I'm asking because I have the impression, that gnucash is way more popular than qbankmanager, right?

So not having libaqbanking in a state so that gnucash can be built against it would be suboptimal imho, but even this would need a downgrade of packages. OTOH, if I understand Debian #303234 correctly, Gwenhywfar would eventually solve the no hbci issue.

(Why do these source packages have names that are so awkward to type btw. *g*).

Anyway, release-wise, I assume that the best option is to go for the upgrade. ACK #2, confirming.

Changed in libaqbanking:
status: New → Confirmed
Changed in libchipcard:
status: New → Confirmed
Changed in libktoblzcheck:
status: New → Confirmed
Changed in qbankmanager:
status: New → Confirmed
Revision history for this message
Reinhard Tartler (siretart) wrote :

Subscribing ubuntu-archive, as this is now a sync request:

Please sync the following packages from debian unstable (rationale: see above)

libaqbanking | 3.3.0+dfsg-1 | unstable
libktoblzcheck | 1.17-3 | unstable
libchipcard | 4.0.0-5 | unstable
qbankmanager | 0.9.49beta-2 | unstable

Revision history for this message
Martin Pitt (pitti) wrote :

[Updating] libaqbanking (2.3.3-2 [Ubuntu] < 3.3.0+dfsg-1 [Debian])
 * Trying to add libaqbanking...
  - <libaqbanking_3.3.0+dfsg.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
  - <libaqbanking_3.3.0+dfsg-1.dsc: downloading from http://ftp.debian.org/debian/>
  - <libaqbanking_3.3.0+dfsg-1.diff.gz: downloading from http://ftp.debian.org/debian/>
I: libaqbanking [universe] -> libaqbanking-doc_2.3.3-2 [universe].
I: libaqbanking [universe] -> aqbanking-tool_2.3.3-2 [universe].
I: libaqbanking [universe] -> libaqbanking-data_2.3.3-2 [universe].
[Updating] libchipcard (4.0.0-3 [Ubuntu] < 4.0.0-5 [Debian])
 * Trying to add libchipcard...
  - <libchipcard_4.0.0-5.diff.gz: downloading from http://ftp.debian.org/debian/>
  - <libchipcard_4.0.0.orig.tar.gz: already in distro - downloading from librarian>
  - <libchipcard_4.0.0-5.dsc: downloading from http://ftp.debian.org/debian/>
I: libchipcard [universe] -> libchipcard-dev_4.0.0-3 [universe].
I: libchipcard [universe] -> libchipcardc2_4.0.0-3 [universe].
I: libchipcard [universe] -> libchipcardd0_4.0.0-3 [universe].
I: libchipcard [universe] -> libchipcard-ctapi0_4.0.0-3 [universe].
I: libchipcard [universe] -> libchipcard-data_4.0.0-3 [universe].
I: libchipcard [universe] -> libchipcard-tools_4.0.0-3 [universe].
I: libchipcard [universe] -> libchipcard-libgwenhywfar47-plugins_4.0.0-3 [universe].
[Updating] libktoblzcheck (1.16-1 [Ubuntu] < 1.17-3 [Debian])
 * Trying to add libktoblzcheck...
  - <libktoblzcheck_1.17-3.dsc: downloading from http://ftp.debian.org/debian/>
  - <libktoblzcheck_1.17-3.diff.gz: downloading from http://ftp.debian.org/debian/>
  - <libktoblzcheck_1.17.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
I: libktoblzcheck [universe] -> libktoblzcheck1c2a_1.16-1 [universe].
I: libktoblzcheck [universe] -> libktoblzcheck1-dev_1.16-1 [universe].
I: libktoblzcheck [universe] -> ktoblzcheck_1.16-1 [universe].
I: libktoblzcheck [universe] -> python-ktoblzcheck_1.16-1 [universe].
[Updating] qbankmanager (0.9.39-2 [Ubuntu] < 0.9.49beta-2 [Debian])
 * Trying to add qbankmanager...
  - <qbankmanager_0.9.49beta-2.dsc: downloading from http://ftp.debian.org/debian/>
  - <qbankmanager_0.9.49beta.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
  - <qbankmanager_0.9.49beta-2.diff.gz: downloading from http://ftp.debian.org/debian/>
I: qbankmanager [universe] -> qbankmanager_0.9.39-2 [universe].

Changed in libaqbanking:
status: Confirmed → Fix Released
Changed in libchipcard:
status: Confirmed → Fix Released
Changed in libktoblzcheck:
status: Confirmed → Fix Released
Changed in qbankmanager:
status: Confirmed → Fix Released
Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

Hi all,

so I suppose there won't be a solution to build a HBCI-enabled GnuCash in Hardy without building and installing aqbanking2 locally in /usr/local. Does anyone of you know, whether the gutsy packages would work if I installed them (before I ruin my system...)?

Thanks for the swift bug fixing anyhow!

Revision history for this message
Reinhard Tartler (siretart) wrote :

Bastian Doetsch <email address hidden> writes:

> so I suppose there won't be a solution to build a HBCI-enabled GnuCash
> in Hardy without building and installing aqbanking2 locally in
> /usr/local. Does anyone of you know, whether the gutsy packages would
> work if I installed them (before I ruin my system...)?

I'd assume that they would work just fine in hardy. Just make sure that
you keep all related package (at least libaqbanking, libchipcard,
gnucash, etc...) at the version of gutsy.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Revision history for this message
Bastian Doetsch (bastian-doetsch) wrote :

To whom it may concern: the gutsy-backports gnucash packages from geole work. I successfully completed HBCI jobs on three different accounts from within gnucash.

What I did to make it work (so far I didn't experience any side-effects):

- deactivated all hardy repositories in synaptic
- activated official gutsy repo in synaptic as third-party repo (deb http://archive.ubuntu.com/ubuntu/ gutsy main universe restricted multiverse)
- added geole gutsy-backports repo (deb http://ubuntu.geole.info/ gutsy-backports universe multiverse)
- refreshed package lists
- installed aqbanking 2.3x and gnucash 2.2.4 packages
- deactivated gutsy repo
- re-activated hardy repositories.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.