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

Re: Problems with shim and shim-signed in unstable, and proposed solutions to unblock us

On Mon, Mar 04, 2019 at 04:30:46PM +0000, Steve McIntyre wrote:
>>    3. Upload new version of the shim-signed source package and a
>>       (lightly) bodged binary package
>>    3a. Use versions:
>>             - source: 1.28+nmu2
>>             - binary: 1.28+nmu2+0.9+1474479173.6c180c6-1
>>    3b. Needs as build-deps an old version of sbsigntool (0.6-3.2) and
>>        specifically version 0.9+1474479173.6c180c6-1 of shim in the
>>        build chroot
>>    3c. Then upload source+amd64
>>    3d. New shim-signed binary package changes in a few ways:
>>        * new version of the binary now include fbx64.efi.signed and
>>          mmx64.efi.signed (copied across from the shim binary package)
>>        * add Replaces: shim (= 0.9+1474479173.6c180c6-1) so we don't
>>          conflict on those binaries
>>        * remove Depends: shim (the whole point!)
>>        * change Build-Depends to list the specific versions used for
>>          shim and sbsigntool
>>    3e. Already tested and working. I built this (source and binary
>>        debdiffs attached) and tested OK on SB system
>>    3f. This package is instantly RC-buggy due to the unavailable
>>        build-deps. We know...

I've just uploaded #3 to unstable this evening.

Steve McIntyre, Cambridge, UK.                                steve@einval.com
"You can't barbecue lettuce!" -- Ellie Crane

Attachment: signature.asc
Description: PGP signature

Reply to: