Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Steve McIntyre
On Fri, Mar 17, 2017 at 05:37:07PM +0100, Miguel Hermanns wrote: >No other OS installed and I did not get that message. > >I'm using an NVMe Samsung 960 EVO drive for / and swap, and a traditional >WD Red for /home. I don't know if that may have an influence. OK, this is weird. :-/ I don't

Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
I don't have them, sorry :-( Sadly, I cannot reproduce the error for you, since the computer is already in use now. On Fri, Mar 17, 2017 at 5:54 PM, Steve McIntyre wrote: > On Fri, Mar 17, 2017 at 05:37:07PM +0100, Miguel Hermanns wrote: > >No other OS installed and I did not

Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
Dear Steve, It was the first time I installed something in EFI mode, as in the past I always switched back to legacy mode. So I'm quite sure I booted in EFI mode. After the installation and seeing that the computer was not booting, I started to research in the internet and found the Debian

Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
No other OS installed and I did not get that message. I'm using an NVMe Samsung 960 EVO drive for / and swap, and a traditional WD Red for /home. I don't know if that may have an influence. Best regards, Miguel On Fri, Mar 17, 2017 at 5:20 PM, Steve McIntyre wrote: > On

Re: 8.8 planning

2017-03-17 Thread Laura Arjona Reina
Hi El 14/03/17 a las 12:00, Julien Cristau escribió: > It's time to start thinking about our next stable point release. Here > are some dates, please let us know which ones would work. > > * April 8-9 > * April 15-16 Not sure, but could be > * April 22-23 > * April 29-30 > * May 6-7 Those,

Re: 8.8 planning

2017-03-17 Thread Adam D. Barratt
On Tue, 2017-03-14 at 12:00 +0100, Julien Cristau wrote: > It's time to start thinking about our next stable point release. Here > are some dates, please let us know which ones would work. > > * April 8-9 > * April 15-16 > * April 22-23 > * April 29-30 > * May 6-7 > > I know at least Adam can't

Bug#855960: flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2

2017-03-17 Thread Scott Barker
I know the db entry for the NETGEAR ReadyNAS Duo v2 is missing from this installer image, which is the one I've been using: http://ftp.debian.org/debian/dists/jessie/main/installer-armel/20150422+deb8u4+b2/images/kirkwood/netboot/marvell/openrd/uInitrd On Fri, Mar 17, 2017 at 04:28:46PM

Bug#855965: libdebian-installer: Please add support for NETGEAR ReadyNAS Duo v2

2017-03-17 Thread Martin Michlmayr
* Scott Barker [1969-12-31 18:48]: > Please add support for NETGEAR ReadyNAS Duo v2, which uses a "kirkwood" > processor: Thanks, I added this patch. -- Martin Michlmayr http://www.cyrius.com/

Bug#855960: flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2

2017-03-17 Thread Martin Michlmayr
* Scott Barker [1969-12-31 17:52]: > Please add suuport for NETGEAR ReadyNAS Duo v2. The db entry that works for > me is: Thanks, I added this in git. Do we also have to create any installation images in debian-installer? -- Martin Michlmayr http://www.cyrius.com/

Bug#839595: flash-kernel: Please add support for SolidRun Clearfog

2017-03-17 Thread Martin Michlmayr
* Christoph Egger [2016-12-27 17:55]: > Christoph Egger writes: > > I haven't updated u-boot yet, though it's still on my todo > > Seems to have worked. I have now u-boot 2016-11 SPL and "normal" > u-boot and everything works so far \o/ Karsten, I

Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

2017-03-17 Thread Martin Michlmayr
* Heinrich Schuchardt [2016-11-26 22:57]: > As mainline u-boot support is still under construction boot.scr > is build such that the stock u-boot can execute it. As you know, I added your prerequisite patch but I never added this patch and didn't explain why (apart from

Bug#855960: flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2

2017-03-17 Thread Martin Michlmayr
* Scott Barker [2017-03-17 17:47]: > I know the db entry for the NETGEAR ReadyNAS Duo v2 is missing from this > installer image, which is the one I've been using: Yeah, I just added the db entry to git. It's not even in the archive yet. -- Martin Michlmayr

Bug#845818: Re: Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

2017-03-17 Thread Martin Michlmayr
Hi Heinrich, * Heinrich Schuchardt [2017-03-18 02:39]: > U-Boot 2017-3 does not contain MMC support for the Odroid C2. > I have seen a recent patch series for MMC support. But I did not yet > build with it. If they are accepted for 2017.05, maybe Vagrant could add them to

Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Steve McIntyre
On Fri, Mar 17, 2017 at 03:20:33PM +0100, Miguel Hermanns wrote: >Package: partman-efi >Version: 75 >Severity: important > >Dear Maintainer, > >When installing debian stretch RC2, manual partitioning was done without >specifying an EFI boot partition. This did not trigger an error message >by

Bug#785149: patch working (and missing) on jessie

2017-03-17 Thread geoffroy desvernay
Hi all, Found this bug after trying to install "as usual" (network preseed) new machines here. Just to report that patching /usr/bin/grub-installer manually in d-i works (and resulting debian works flawlessly with standard kernel) Do you think backporting this to jessie will take time ? It

Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Steve McIntyre
On Fri, Mar 17, 2017 at 05:03:17PM +0100, Miguel Hermanns wrote: >Dear Steve, > >It was the first time I installed something in EFI mode, as in the past I >always switched back to legacy mode. So I'm quite sure I booted in EFI >mode. > >After the installation and seeing that the computer was not

Bug#818065: live-config / console-setup issue

2017-03-17 Thread Jörn Heissler
On Thu, Mar 16, 2017 at 07:03:04PM +0200, Anton Zinoviev wrote: > ls --full-time /etc/console-setup/cached* /etc/default/console-setup > /etc/default/keyboard This is from a configuration where I hard coded the two files in /etc/default/ and did not set the keyboard parameters elsewhere. Files

Bug#818065: live-config / console-setup issue

2017-03-17 Thread Anton Zinoviev
On Fri, Mar 17, 2017 at 08:17:42AM +0100, Jörn Heissler wrote: > > It appears to me that "Set console font and keymap" is done before > live-config regenerates the files. I think this explains the bug. Anton Zinoviev

Bug#858009: Debian "Full Disk Encryption" is a misnomer, /boot not encrypted, Evil Maid attacks, enable grub cryptodisk, improve guided encrypted partitioning

2017-03-17 Thread of....@protonmail.com
Package: debian-installer Version: stretch-rc2 The Debian Stretch RC2 installer and previous versions do not allow Full Disk Encryption since /boot is more vulnerable to Evil Maid attacks due to it being unencrypted. Securing /boot makes Evil Maid attacks slightly more difficult, raising the

Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
Package: partman-efi Version: 75 Severity: important Dear Maintainer, When installing debian stretch RC2, manual partitioning was done without specifying an EFI boot partition. This did not trigger an error message by partman, although according to section 6.3.3.3 of the installation guide it