On Wed, 2012-06-06 at 23:10 +0200, Micha Lenk wrote: > there was a new upstream release that introduced a soname bump in > libaqbanking.
That makes this a(n uncoordinated) transition, not a binNMU request. Thankfully one that doesn't appear to clash with any other ongoing transitions that I can see. > For this reason all packages with build-deps on libaqbanking33-dev needs a > source-full upload in order to switch to libaqbanking34-dev and to pick up the > dependency on the new package libaqbanking34. Why do the -dev package names contain (and therefore change with) the SONAME? Given that they all Provide "libaqbanking-dev", could the -dev package not simply be a concrete package named libaqbanking-dev? That also makes transitions much easier and avoids the need for source uploads on each change (unless there are API changes which require the source changes). > The package kmymoney has a build-dep on 'libaqbanking33-dev | > libaqbanking-dev'. For this reason I hope that a binNMU is enough as a short > term solution to the problem. It's not even a short term solution, I'm afraid. The buildds will only consider the first branch of an alternative build-dependency, which means libaqbanking33-dev will always be installed. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
