[Debian-med-packaging] Bug#738616: removing newer libasio-dev (v1.10) from unstable

[Daniel Pocock]

On 11/02/14 11:49, Julien Cristau wrote:
> On Tue, Feb 11, 2014 at 10:44:30 +0100, Daniel Pocock wrote:
>
>> Package: release.debian.org
>>
>> We would like the version of libasio-dev in unstable to revert to the
>> version currently in testing (1.4.8-2)
>>
> You might want to explain why.

API changes make it incompatible

Fedora and EPEL still carry 1.4.8 which is widely used by dependencies
such as those mentioned below

>
>> Can you please remove the v1.10.1-1 libasio-dev from unstable or let me
>> know what action to take, e.g. should I upload a 1.4.8-3 package?
>>
> No, we can't do that.  And you shouldn't do that.  What you can do is
> use an epoch to make the version number go backwards.

Ok, I will do that and upload later today


>> Also, could you please comment on whether we should plan a transition
>> for asio 1.10 to enter jessie?  Markus is maintaining the package,
>> reSIProcate is the only build dependency we know of and if there are no
>> others then a formal transition probably isn't required.
>>
>> Is there an equivalent of "apt-cache rdepends" that can help us locate
>> any other packages with a build dependency on libasio-dev?  As it is a
>> header library, no packages declare a runtime dependency on it.
>>
> wget -qO- http://ftp.debian.org/debian/dists/sid/main/source/Sources.gz | zcat | grep-dctrl -FBuild-Depends -sPackage libasio-dev
>
> Adjusting for contrib and non-free left as an exercise for the reader.

Thanks for that feedback

Looks like the following three packages are impacted by this build
dependency:

src:abiword
src:ball
src:resiprocate

All those packages need patching to work with the new version of asio
due to API changes

Does the release team have any preference for making this a formal
transition or we should just work it out informally between the
maintainers of these packages?

Markus, please have a brief look at
https://wiki.debian.org/Teams/ReleaseTeam/Transitions