Bug#884618: transition: cryptsetup
Control: tags -1 - confirmed
On 18/12/17 19:32, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
>
> On 17/12/17 19:27, Jonas Meurer wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian.org@packages.debian.org
>> Usertags: transition
>>
>> Hey there,
>>
>> 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
>>
>> 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?
>
> Please upload it to unstable. I will schedule the binNMUs once cryptsetup is built.
Actually I just read the thread about the -udeb uninstallability. Let's wait
until that is fixed or until Cyril says it's alright to break that.
Cheers,
Emilio
Reply to: