[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#705840: marked as done (unblock: libaqbanking/5.0.24-4)



Your message dated Sun, 21 Apr 2013 13:15:46 +0200
with message-id <5173CA62.2040401@debian.org>
and subject line Re: Bug#705840: unblock: libaqbanking/5.0.24
has caused the Debian Bug report #705840,
regarding unblock: libaqbanking/5.0.24-4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
705840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705840
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package libaqbanking

A user reported to me in private that the AqBanking plugins to Gwenhywfar get
lost on upgrade from squeezy to wheezy. The reason is that the package
libaqbanking-plugins-libgwenhywfar47 got renamed to
libaqbanking-plugins-libgwenhywfar60, but (intentionally) no other package
depends or recommends the package libaqbanking-plugins-libgwenhywfar60.  The
impact is, that for all users that want to use it, AqBanking doesn't work
anymore.

I would like to add a transitional dummy package
libaqbanking-plugins-libgwenhywfar47 that depends on
libaqbanking-plugins-libgwenhywfar60, so that AqBanking continues to work on
upgrades from squeeze to wheezy. You can find the suggested changes attached to
this mail.

As the suggested change introduces a new binary package, is there any special
need to raise attention of the FTP masters before the upload?

unblock libaqbanking/5.0.24
diff -Nru libaqbanking-5.0.24/debian/changelog libaqbanking-5.0.24/debian/changelog
--- libaqbanking-5.0.24/debian/changelog	2012-12-09 13:43:14.000000000 +0100
+++ libaqbanking-5.0.24/debian/changelog	2013-04-20 20:42:36.000000000 +0200
@@ -1,3 +1,11 @@
+libaqbanking (5.0.24-4) unstable; urgency=low
+
+  * Add transitional dummy package libaqbanking-plugins-libgwenhywfar47
+    (closes: #705839), which existed in squeeze, but was renamed to
+    libaqbanking-plugins-libgwenhywfar60 in wheezy. It should help users
+    upgrading from squeeze to wheezy.
+
+ -- Micha Lenk <micha@debian.org>  Sat, 20 Apr 2013 20:38:44 +0200
+
 libaqbanking (5.0.24-3) unstable; urgency=low
 
   * Revert injection of build flags from dpkg-buildflags, as requested by the
diff -Nru libaqbanking-5.0.24/debian/control libaqbanking-5.0.24/debian/control
--- libaqbanking-5.0.24/debian/control	2012-06-03 19:28:50.000000000 +0200
+++ libaqbanking-5.0.24/debian/control	2013-04-20 20:38:00.000000000 +0200
@@ -86,6 +86,18 @@
  .
  This package contains plugins to libgwenhywfar.
 
+Package: libaqbanking-plugins-libgwenhywfar47
+Section: oldlibs
+Architecture: all
+Depends: libaqbanking-plugins-libgwenhywfar60
+Description: AqBanking plugins to libgwenhywfar - transitional dummy package
+ AqBanking provides a middle layer between the applications
+ and online banking libraries implementing various file formats and protocols.
+ Plugins supporting OFX, DTAUS, and HBCI are available.
+ .
+ Transitional package for renaming of libaqbanking-plugins-libgwenhywfar47 to
+ libaqbanking-plugins-libgwenhywfar60.
+
 Package: libaqbanking-data
 Section: libs
 Architecture: all

--- End Message ---
--- Begin Message ---
Hi Jonathan,

Am 21.04.2013 12:06, schrieb Jonathan Wiltshire:
> There seems to be some confusion:
> 
> Package: libaqbanking34 Recommends: libaqbanking34-plugins,
> libaqbanking-plugins-libgwenhywfar60

I agree, there is some confusion -- on my side.

I should have checked this on my own in advance, because the one who
reported the issue originally has indeed installation of recommended
packages disabled. So, sorry for the noise!

I am closing this bug now.

Regards,
Micha

--- End Message ---

Reply to: