Bug#904316: transition: boost-defaults
On Mon, 23 Jul 2018 10:26:34 +0100 Dimitri John Ledkov <xnox@ubuntu.com> wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
>
This transition was ready to be started for just over three months now.
May I upload boost-defaults to start the transition to boost1.67?
I believe I have answered all requests so far. There is no explicit
need or requirement to move all packages to boost1.67, if any packages
are not fixed to work with boost-default pointing at boost1.67 they
can revert to boost1.62, as both boost1.62 and boost1.67 are
co-installable. Multiple releases in the past shipped multiple boost
at the same time, thus this is not an unsual situation. Or can anyone
from the release team explain what is the hold up here? Most packages
are NMUable for this transition, some need patches uploading which do
exist for the vast majority of affected packages, and there are no
obviously broken sets of packages which would be caused by this
transition (i.e. simultaneously trying to link or dlopen two
incompatible boosts for example).
If there is still anything unresolved, please let me know.
Boost team is concerned about shipping boost-defaults pointing at 1.62
in the upcoming release. We are comfortable with shipping boost 1.67
as default, and only some minority of packages using boost1.62.
Regards,
Dimitri, on behalf of the Boost packaging team.
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> This is a transition request to upgrade boost defaults from 1.62 to
> 1.67. Whilst 1.65.1 never made it into Debian, it has in Ubuntu and
> the transition from 1.62->1.65.1 has been completed there. The
> transition from 1.65.1 -> 1.67 is ongoing, with almost all core
> packages transitioned already.
>
> The most common issues are general fixes due to rebuilding with newer
> gcc toolchain, removal of std::tr1::* provided namespace (e.g. instead
> of std::tr1::regex use either boost::regex or std::regex), and change
> in naming convention of boost_python sonames (which is now
> multi-python aware upstream, and debian now matching it).
>
> Majority of fixes are already present in upstream releases, Ubuntu
> uploads, or are trivial in nature.
>
> I would like to upload boost-defaults, to kick of transition and work
> towards removing boost1.62 from testing before relese.
>
> Ben file:
>
> title = "boost-defaults";
> is_affected = .depends ~ /libboost[a-z-.]*1\.6[0123457]/;
> is_good = .depends ~ /libboost[a-z-.]*1\.67/;
> is_bad = .depends ~ /libboost[a-z-.]*1\.6[012345]/;
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iQFEBAEBCgAuFiEEdzyZ69ChEXIhenw/ysLYuc0spfkFAltVn0oQHHhub3hAdWJ1
> bnR1LmNvbQAKCRDKwti5zSyl+Re8B/sEaeSBKBwkWJAxU5keO6ePeQ8+cYFSpIlU
> kfCjSjhMPwH0QjUFsRKuibq0aoP4kVHJjFrk4hWEDqgELR6/uwEdj77tF9hE9PK5
> HyzRHOFwQ/6B97LrjpFZJwqVlAaiJfpfoFMR702hx0kcSAVznzHFYVB39li4Y6jN
> dEH+tre6LUlaGb9ITUcvYsUw01OWQko0xG7QdBTeislhwo/rkI2rNaMX5Yf5bXff
> YR9+wDo6cktjW3qwDtpfDs3wDLBOyxIm1DM/1TXZQhy5XMQJduGFPe4u1oIWlxVG
> kXggcg4sKxSRU+uZgjFa9h5Lgvv5QWidDD8nR71R0CIv723tUlsb
> =34BB
> -----END PGP SIGNATURE-----
>
>
Reply to: