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

Bug#738616: removing newer libasio-dev (v1.10) from unstable



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

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.)

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).

Granted, I should still have started a proper transition, rather than
uploading (an API-incompatible) 1.10.1 without notice. Please accept my
apologies, I should have known better.

Regards

Markus Wanner


Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: