[pkg-cryptsetup-devel] Upcoming transition: libcryptsetup4 -> libcryptsetup12

[Cyril Brulebois]

Hi Jonas,

Jonas Meurer <jonas at freesources.org> (2017-12-17):
> the upcoming upload of cryptsetup 2.0.0-1 will bump the libcryptsetup
> soname from 4 to 12. According to (the very thoughtful) upstream, the
> API (old functions) is backwards-compatible, so simple rebuilds of the
> reverse depenencies should be enough.
> 
> Here's a list of reverse depends:
> 
> bruteforce-luks
> cryptmount
> libpam-mount
> luksmeta
> systemd
> volume-key
> libblockdev
> zulucrypt
> 
> Debian-boot is Cc'ed as cryptsetup provides udebs, so debian-installer
> is affected as well.

Thanks for letting us (debian-boot@) know. AFAICT, on the udeb side we
only have crypsetup-udeb that depends on its library udeb, and no other
udebs are in the loop. Since a version with the bumped soname is
available in experimental, someone from the d-i team could build d-i
against it and see if cryptsetup still works as expected. And even if
that doesn't happen, we have no immediate plans for a release yet, so
there's no disruption risk: feel free to proceed whenever you see fit
(but see below).

> How shall we proceed? The package is ready to be uploaded. Shall we go
> ahead? Will you (the Release Managers) trigger the binary rebuilds
> afterwards? Or can/shall we do this ourselves?

You would usually request a transition slot through a bug report against
release.debian.org (pick 'transition'), and coordinate uploads & binNMUs
with the release team.


Cheers,
-- 
Cyril Brulebois (kibi at debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20171217/e33040d1/attachment.sig>