Bug#773255: Add TI OMAP5 uEVM board support db

> On Dec 19, 2014, at 16:15, Ian Campbell wrote: > > On Fri, 2014-12-19 at 13:38 +0800, Chen Baozi wrote: >> I’ve only booted the system by ‘bootz’ without initrd. If I load the raw >> initrd image (rather than ‘uInitrd”), when I use bootz, it would output: >> >> Wrong Ramdisk Image Format >> R

Bug#773555: unblock: partman-efi/59

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package partman-efi The changes since version 56 are tiny - see attached. They consist of: * a fix from Leif for #773311, a silly bug introduced in my own changes in #7

which HSM for secure boot keys

I remember some discussion about how to store the shim keys at debconf, and some hardware security module being passed around. I'm looking for a recommendation for a HSM for my own shim keys. Was there ever a conclusion on how to store the keys for debian, and does anyone remember what that littl

Bug#771485: installation-reports: Installation disk scan hangs at 81% with LVM inside crypt partition

Hi, I encountered the same issue when trying to setup LVM inside a crypt partition. The reason for the hanging partitioner is a crashing 'parted_server' process: kernel: [ 422.613251] parted_server[15630]: segfault at 8 ip 0040b4b1 sp 7fff35d63ee0 error 4 in parted_server[40+1200

Bug#773274: more d-i encryption testing

I had some time to try a couple more tests for #773274 and observed a few more things. * In my set of steps to repeat the bug I said to setup two partitions for encryption. I just tested and it doesn't seem to matter if one of them is going to be for swap (which d-i defaults to if you choose ra

partman-efi_59_i386.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 19 Dec 2014 07:12:17 +0100 Source: partman-efi Binary: partman-efi Architecture: source i386 Version: 59 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier

Bug#773311: marked as done (confusing dialogue on lack of EFI system partition on non-x86)

Your message dated Fri, 19 Dec 2014 09:20:37 + with message-id and subject line Bug#773311: fixed in partman-efi 59 has caused the Debian Bug report #773311, regarding confusing dialogue on lack of EFI system partition on non-x86 to be marked as done. This means that you claim that the proble

Processing of partman-efi_59_i386.changes

partman-efi_59_i386.changes uploaded successfully to localhost along with the files: partman-efi_59.dsc partman-efi_59.tar.xz partman-efi_59_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.deb

Processing of partman-efi_59_i386.changes

partman-efi_59_i386.changes uploaded successfully to ftp-master.debian.org along with the files: partman-efi_59.dsc partman-efi_59.tar.xz partman-efi_59_i386.udeb Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ.

Re: Providing (armhf) u-boot images together with d-i images?

On Thu, 2014-12-18 at 20:44 +0100, Karsten Merker wrote: > On Thu, Dec 18, 2014 at 10:48:07AM -0800, Vagrant Cascadian wrote: > > > I don't know how realistic it is to provide concatenateable images with > > the u-boot "bare" image as one file, and the kernel + initrd + dtb + > > boot.scr as a sec

Bug#773255: Add TI OMAP5 uEVM board support db

On Fri, 2014-12-19 at 13:38 +0800, Chen Baozi wrote: > I’ve only booted the system by ‘bootz’ without initrd. If I load the raw > initrd image (rather than ‘uInitrd”), when I use bootz, it would output: > > Wrong Ramdisk Image Format > Ramdisk image is corrupt or invalid > > This is the reason th