On 31.12.07 17:59:23, Micha Lenk wrote:
> Andreas Pakulat schrieb:
> > On 31.12.07 15:32:39, Micha Lenk wrote:
> >> Hi Andreas,
> >> 
> >> thank you for your valuable feedback.
> >> 
> >> Andreas Pakulat wrote:
> >> > currently it "seems" like aqbanking 2.3 and aqbanking 3.0 are
> >> > co-installable, but that is not the case as both use aqbanking-data and
> >> > at least hbci.xml for the older aqhbci plugin is missing from the 3.0
> >> > version of this package.
> >> 
> >> I tried to make the libaqbanking-data package usable for AqBanking 2.x
> >> and AqBanking 3.x. For the case mentioned above, you should notice that
> >> hbci.xml is still present in AqBanking 3.x's libaqbanking-data: It moved
> >> to /usr/share/aqbanking/backends/aqhbci/hbci.xml and should be reachable
> >> at the location AqBanking 2.x expects it by the symlink
> >> /usr/share/aqhbci/xml pointing to "../aqbanking/backends/aqhbci". This
> >> should resolve to /usr/share/aqbanking/backends/aqhbci and should make
> >> AqBanking 3.x's hbci.xml available at /usr/share/aqhbci/xml/hbci.xml,
> >> the path AqBanking 2.x expects it to be.
> >>
> >> Could you please check that this symlink is correct at your system?
> > 
> > There's no such symlink, but still a real xml directory in
> > /usr/share/aqhbci/. And aqhbci itself is also a real directory.
> 
> Could you please remove that directory and replace it by a symlink as it
> supposed to be on new installations? Please run these two commands as root:
> 
> rmdir /usr/share/aqhbci/xml
> ln -s ../aqbanking/backends/aqhbci /usr/share/aqhbci/xml
> 
> Does your AqBanking 2.x work now again?

yes.

> If yes I'll try to do these steps on libaqbanking-data's postinst script
> on installation.

I would think that dpkg first removes the files and dirs associated with
the old package and then unpacks the new package in which case there
shouldn't have been a problem. Maybe this is a bug in dpkg?

Andreas

-- 
Among the lucky, you are the chosen one.

Attachment: signature.asc
Description: Digital signature

Reply via email to