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

Bug#787024: transition: libaqbanking



On 27/05/15 23:11, Micha Lenk wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> 
> Hi release team,
> 
> The AqBanking library (source package libaqbanking) got its SONAME bumped. For
> this reason some package names need to be changed. I just uploaded the
> following binary package name changes as libaqbanking/5.6.0beta-1 to
> experimental:
> 
> libaqbanking34-dev -> libaqbanking35-dev
> libaqbanking34-plugins -> libaqbanking35-plugins
> libaqbanking34 -> libaqbanking35
> libaqbanking34-dbg -> libaqbanking35-dbg
> 
> On the Transitions wiki page you mention that changing the name of -dev
> packages should be avoided. As AqBanking's API seems to have stabilized
> recently, do you recommend to transition the -dev package to the new name
> libaqbanking-dev instead? If so, is there anything to keep in mind if the old
> package libaqbanking34-dev already has a Provides: libaqbanking-dev (it has it
> actually long since)? The reverse dependencies currently all build-depend on
> libaqbanking34-dev.

Please rename it to libaqbanking-dev. Unfortunately a

Provides: libaqbanking34-dev

is not going to help us, because all the build-dependencies on
libaqbanking34-dev are versioned. So the rdeps are going to need sourceful
uploads to update the b-d. But they were going to need that anyway had you
changed it to libaqbanking35-dev, so no big deal.

The fact that libaqbanking34-dev provides libaqbanking-dev is not a problem at all.

> The following reverse dependencies will be impacted by this transition:
> 
> abtransfers
> gnucash
> kmymoney

BTW do the rdeps build against the new version? Or do they need code changes?

> 
> Ben file:
> 
> title = "libaqbanking";
> is_affected = .depends ~ /libaqbanking34/ | .depends ~ /libaqbanking35/;
> is_good = .depends ~ /libaqbanking35/;
> is_bad = .depends ~ /libaqbanking34/;

A tracker will be automatically created once the package clears NEW.

Let us know once the package has been accepted in experimental.

Regards,
Emilio


Reply to: