Bug#738616: removing newer libasio-dev (v1.10) from unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 11/02/14 22:18, Markus Wanner wrote:
> Daniel,
>
> On 02/11/2014 09:46 PM, Daniel Pocock wrote:
>> Has anybody else tried something else to deal with this package
>> transition or reversion to 1.4.8? Or did I do something wrong
>> when adding the epoch?
>
> I think you did just fine, but PTS is lagging behind. See here:
> http://metadata.ftp-master.debian.org/changelogs/main/a/asio/asio_1.4.8-3_changelog
I
>
notice that everything seemed to fall into place shortly after
sending that email - my reSIProcate packages are building now
> Does this allow us to close this bug? And at least degrade #738613
> to non-serious? (Otherwise, your upload won't migrate to testing,
> either, I guess.)
>
We should mark 738613 fixed in the new version I think
> On 02/11/2014 01:40 PM, Julien Cristau wrote:
>> Please try to avoid versioned -dev packages. Unless you really
>> really have to keep both versions around for years.
>
> Rethinking that, I agree. For effectively two debian packages
> (abiword and resiprocate, disregarding ball) that rely on
> libasio-dev, it's hardly worth the effort of maintaining two
> separate versions.
>
> The other point being that (this variant of) asio being a
> headers-only library doesn't change the fact that any -dev package
> is only used during a build, but not when running any program
> (binary). In other words, just like any other -dev package, an
> upgrade of it won't ever break a compiled binary. At the worst, it
> leads to an FTBFS (as 1.10.1 does for both, BTW).
>
It is an awkward question - if the API change is mild and the new
version is better in every way then killing of the old version (with
enough time for a transition) is fair enough
If there are any question marks over stability of the new version or
if it is so much work that the packagers of resiprocate and abiword
can't easily fix it, then the pain of keeping an old version
libasio1.4-dev may be much less
As a reSIProcate upstream,
* We just released 1.9.0 with a dependency on asio 1.4.x
* I'm happy to look at asio version for our 1.10.x release cycle.
* only one part of reSIProcate uses asio, so I could also split the
package upstream, reduce the scope for future conflicts like this
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJS+pWGAAoJEOm1uwJp1aqDITYQALlGaQpOyNJw3Vz3JtXd+us/
JDUBV94PZqhZSC4KVZeNSMY6n1jQufHpvbkVapXJDO4GgiCp4yWU/NtEVjCP07sl
8+YjJcLep783kI2YVkjm1Fo+6JeVXdQfE827663/h58jEX1U9Lk7bEhdM26u7VdQ
n4JyY2GFS8BXO9sLAxopoo8xcT6RWW0GnZlvcjO0GuF1tXrLVII3BJBCCvxmSUkA
MWu7FL6fUFI/JgGejQbiOl60i7GtlzCHlwlp0o3uBSvU1s6rQMoR+0J0Dbw9c5Og
qi2mdF2N9dXeVA86EErWTvyobPcjI0Wg3uQSizIsLoK9uD79CKPqcA23bGfqie7x
5dv9ZOcY8Hpxm2S3V5UPmZvyKTNI4A6AbG1N+X2HnlUVK5++NkMsMb5QRW3y6oQ9
YD03EvFQfyAjIC8A1T4n0poTpxUM3rl9uyCqziZsEWOzbgjJaLOvwhsqAO7JHx3y
sRFpSWn1J24blji270PJx4w/b3ZBD0zbXj6lhZDCNW9R3uqoVvxKwB5LyPlQKvTe
bZ/z3/ZNByTlytlsN+ZVim9V3q/7tDsKqBL5QIqHcl1D+4ez5Nw9IPnE1iGtakBm
l4Wx4JkYxfRdSLEgtXVZCWsD6Pte2Ftsj8eGKm8EwkdXmWjp5hW7Xm9XDbXMgrTT
YKZ2l9NBfFqAdh6Ve8r+
=lMdP
-----END PGP SIGNATURE-----
Reply to: