Bug#738616: removing newer libasio-dev (v1.10) from unstable
On Tuesday, 11. February 2014 11:49:22 Julien Cristau wrote:
> 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.
Or if you want to avoid using epochs, reupload 1.4.8 using as
1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release to
experimental. Once you upload upstream 1.11 you are back to normal version
numbers without having used an epoch inbetween.
On Tuesday, 11. February 2014 12:09:46 Daniel Pocock wrote:
> 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?
You should probably prepare these API adjustments in experimental and request
a regular transition once the packages are all fixed.
Andreas
Reply to: