Bug#333104: kbanking

2005-10-20 Thread Thomas Viehmann
Hi Mark, Micha, Release gurus,

first, my apologies for not following up on the Mark's ITP which I
overlooked...

As you may or may not know, the kbanking library as introduced to
Debian/unstable in October is obsolete and is probably (on the way to
being) at least partially unusable since about August when upstream
integrated kbanking into AqBanking (packaged as libaqbanking).

Wishlist bug #333104 also asks for libkbanking to be provided by
libaqbanking, which is IMHO the way to go.

So I'd like to know:
- Mark, would you mind if libaqbanking provided libkbanking1?
- Release team: kmymoney2 has already been mentioned to be tying
  gnucash to kde. Is my impression that an update of libaqbanking
  introducing libkbanking1 (and a build-dependency on kdelibs4-dev)
  is disruptive to the testing migration?

If and when Mark and the release team give their OK, I'd upload
aqbanking with kbanking today.


Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#333104: kbanking

2005-10-20 Thread Thomas Bushnell BSG
Thomas Viehmann [EMAIL PROTECTED] writes:

 - Release team: kmymoney2 has already been mentioned to be tying
   gnucash to kde. Is my impression that an update of libaqbanking
   introducing libkbanking1 (and a build-dependency on kdelibs4-dev)
   is disruptive to the testing migration?

Thomas, I know you know this, but other readers might not, and it
might help the release managers decide the right answer to your
question:

The gnucash in testing and unstable currently is not linked against
libaqbanking.  I plan to link gnucash against aqbanking only *after*
the current unstable version migrates into testing.

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#333104: kbanking

2005-10-20 Thread Steve Langasek
On Thu, Oct 20, 2005 at 01:02:56AM -0700, Thomas Bushnell BSG wrote:
 Thomas Viehmann [EMAIL PROTECTED] writes:

  - Release team: kmymoney2 has already been mentioned to be tying
gnucash to kde. Is my impression that an update of libaqbanking
introducing libkbanking1 (and a build-dependency on kdelibs4-dev)
is disruptive to the testing migration?

 Thomas, I know you know this, but other readers might not, and it
 might help the release managers decide the right answer to your
 question:

 The gnucash in testing and unstable currently is not linked against
 libaqbanking.  I plan to link gnucash against aqbanking only *after*
 the current unstable version migrates into testing.

True, but libaqbanking is currently in testing and is tied to both the
libofx and qt-x11-free transitions, so it's part of this mess today.

Since nothing else in testing depends on libaqbanking, though, I've already
decided to pull libaqbanking from testing temporarily when the time comes in
order to avoid having to get gnucash and KDE into testing at the same time.
So in light of that, there's no reason to hold off on uploading
libaqbanking.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Bug#333104: kbanking

2005-10-20 Thread Mark Purcell
On Thursday 20 October 2005 08:50, Thomas Viehmann wrote:
 first, my apologies for not following up on the Mark's ITP which I
 overlooked...

I became aware after I had built kbanking, also I wasn't aware how soon the 
aqbanking direct support for kbanking was going to be, so I uploaded 
kbanking.

 As you may or may not know, the kbanking library as introduced to
 Debian/unstable in October is obsolete and is probably (on the way to
 being) at least partially unusable since about August when upstream
 integrated kbanking into AqBanking (packaged as libaqbanking).

It actually still works and I have had reports that kmymoney2 supports HBCI 
with kbanking and aqbanking as seperate packages, but I agree they should be 
provided from aqbanking now.

My one query is Does kmymoney2 build with kbanking from aqbanking? Do you have 
some test debs I can look into?

 Wishlist bug #333104 also asks for libkbanking to be provided by
 libaqbanking, which is IMHO the way to go.

Agreed.

 So I'd like to know:
 - Mark, would you mind if libaqbanking provided libkbanking1?

I am happy for libaqbanking to provide libkbanking1, provided kmymoney2 will 
build.

I'm unsure if you will need to use some special Replaces: Conflicts: headers 
because we are effectivly merging two upstream sources.

 - Release team: kmymoney2 has already been mentioned to be tying
   gnucash to kde. Is my impression that an update of libaqbanking
   introducing libkbanking1 (and a build-dependency on kdelibs4-dev)
   is disruptive to the testing migration?

I wasn't aware of this problem.  I see that kmymoney2 is being removed from 
testing today :-(


 If and when Mark and the release team give their OK, I'd upload
 aqbanking with kbanking today.

When you upload aqbanking with kbanking, I'll upload kmymoney2 with kbanking 
support!

Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#333104: kbanking

2005-10-20 Thread Steve Langasek
On Thu, Oct 20, 2005 at 06:12:32PM +0100, Mark Purcell wrote:
  - Release team: kmymoney2 has already been mentioned to be tying
gnucash to kde. Is my impression that an update of libaqbanking
introducing libkbanking1 (and a build-dependency on kdelibs4-dev)
is disruptive to the testing migration?

 I wasn't aware of this problem.  I see that kmymoney2 is being removed from 
 testing today :-(

Yes, it's a temporary removal for purely logistical reasons -- removing
kmymoney2 from testing while the transition completes is a better option
than either leaving an uninstallable kmymoney2 in testing, or allowing the
transition to continue to be delayed indefinitely (as is otherwise likely
without the use of some force to keep maintainers from uploading packages to
unstable...)  Barring any new uploads of kmymoney2 that would introduce new
dependencies, the package should get back into testing just fine when the
rest of KDE makes the transition.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Bug#333104: kbanking

2005-10-20 Thread Micha Lenk
Hello Mark and Thomas,

Mark Purcell schrieb:
 My one query is Does kmymoney2 build with kbanking from aqbanking? Do you 
 have 
 some test debs I can look into?

The packages I've build and checked in to svn.debian.org are available
under http://aqbanking.alioth.debian.org/unstable/

So I'd like to know:
- Mark, would you mind if libaqbanking provided libkbanking1?
 
 I am happy for libaqbanking to provide libkbanking1, provided kmymoney2 will 
 build.

I've tried to build kmymoney2 (release version 0.8) with the
libkbanking1-package I've build from AqBanking source. The build
succeded, but I've not been able to use kmymoney2 with my already
configured AqBanking accounts since the context menu entry for
connecting KMyMoney2 accounts to AqBanking accounts is disabled. I
haven't had enough time yet for figuring out whether this was my fault
or not...

Mark, I would appreciate it if you could test whether the packages are
ready for use with KMyMoney2...

 I'm unsure if you will need to use some special Replaces: Conflicts: headers 
 because we are effectivly merging two upstream sources.

Hmm, I don't know either, but since the packagename remains the same I
think it might suffice to ask ftp-master (?) to remove all libkbanking
packages from the Debian archives and upload the new AqBanking packages
providing the additional package libkbanking1.

If and when Mark and the release team give their OK, I'd upload
aqbanking with kbanking today.

Thomas, if you agree with the changes (have a look at the SVN
changelogs) I've made in the packages mentioned above, and if Mark has
no objections please upload them. :)

Yours
  Micha


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]