Bug#776021: unblock: cryptsetup/2:1.6.6-5
Control: tags -1 -moreinfo
Hi,
Am 01.02.2015 um 19:27 schrieb Jonas Meurer:
> Hi again,
>
> Am 29.01.2015 um 22:51 schrieb Jonas Meurer:
>> Hi,
>>
>> Am 29.01.2015 um 19:26 schrieb Cyril Brulebois:
>>> Niels Thykier <niels@thykier.net> (2015-01-29):
>>>> Ack from RT, adding KiBi to CC for a d-i ack.
>>>>
>>>
>>> Why isn't the BTS updated with the information contained in the unblock
>>> request? It'd be very helpful to avoid having incorrect or insufficient
>>> information in the BTS, if at all to avoid wasted efforts…
>>
>> I'm sorry for that. As I tried to explain in the unblock request,
>> bugreport #773456 was not exactly about the critical problem I
>> introduced with 2:1.6.6-4. But I should have opened an RC bug myself
>> before doing the upload to make this more clear to you. I apologize for
>> not doing that. Now it's clear to me that this would be the correct way
>> to go, especially in that phase of release freeze - and that I would
>> have saved some hassle on your side that way.
>>
>>> Since we have this:
>>> cryptsetup-udeb: /lib/cryptsetup/cryptdisks.functions
>>>
>>> I'm going to ask whether anyone has tested this new cryptsetup in a d-i
>>> context to make sure the fix isn't triggering more fun elsewhere…
>>>
>>> Failing at least basic testing, I'm not exactly excited with a quick
>>> migration to testing.
>>
>> It's a one-line fix for the init scripts. cryptdisks.functions is
>> sourced by the init scripts and by crypdisks_st{art,op}, it's not used
>> anywhere else. I cannot imagine any interference with debian-installer.
>> Actually the only relevant change is that the precheck for a
>> ubuntu-specific upstart initscript changed from
>>> invoke-rc.d --quiet cryptdisks-udev status && ...
>> to
>>> [ -x /sbin/status ] && ...
>>
>> The one-character change following in the grep regex is only relevant to
>> upstart-based ubuntu systems anyway.
>>
>> But if you want me to, I could do basic testing. I guess that testing
>> the daily-built images from sid would be the right thing in that case?
>
> I did some d-i testing today and for me everything worked as expected. I
> used the d-i images from
> http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/amd64/iso-cd/
> which uses cryptsetup 2:1.6.6-5 udebs.
any news on that? Is there anything I can do to help you making the
cryptsetup 2:1.6.6-5 transition to jessie happen?
Btw, thanks a lot for your great work on making the release happen!
Cheers,
jonas
Reply to: