Bug#870869: Segfault during libc-l10n install on kirkwood (armel)

2017-08-05 Thread Peter Mogensen
Package: base-installer Version: 1.169 While trying to install stretch on a QNAP 419PII, the installation consistently fails with a segfault in dpkg when it tries to install locales and libc-l10n. I install using the method described here: http://www.cyrius.com/debian/kirkwood/qnap/ts-41x/ins

Re: RFC: Switching guided partitioning to LVM by default?

2017-08-05 Thread Holger Levsen
On Sat, Aug 05, 2017 at 04:06:49PM -0400, Cyril Brulebois wrote: > Current default is the first entry, and I think we should switch to > second one, with LVM. I agree & yay! -- cheers, Holger signature.asc Description: Digital signature

Re: RFC: Switching guided partitioning to LVM by default?

2017-08-05 Thread Didier 'OdyX' Raboud
Le samedi, 5 août 2017, 22.20:21 h EDT Geert Stappers a écrit : > When we take LVM as default (which is fine for me) > then we should have the courage to have free PE. > So not assign all diskspace. Yes. I just tried on a stretch mini.iso, if you pick "Guided - use a whole disk with LVM" , the de

Re: RFC: Switching guided partitioning to LVM by default?

2017-08-05 Thread Wouter Verhelst
On Sat, Aug 05, 2017 at 04:06:49PM -0400, Cyril Brulebois wrote: > Is anyone aware of any drawbacks of switching to LVM by default? - It makes sharing the disk with other operating systems harder: partman requires that the LVM PVs are committed to disk before you can play around with LVs, and

Re: RFC: Switching guided partitioning to LVM by default?

2017-08-05 Thread Ben Hildred
On Sat, Aug 5, 2017 at 2:06 PM, Cyril Brulebois wrote: > Hi, > > While preparing some slides for my “News from the Debian Installer” talk > at DebConf17, it occured to me that we might want to reconsider the > default here: > > Guided - use a whole disk > Guided - use a whole disk with LV

Re: RFC: Switching guided partitioning to LVM by default?

2017-08-05 Thread Geert Stappers
On Sat, Aug 05, 2017 at 04:06:49PM -0400, Cyril Brulebois wrote: > Hi, > > While preparing some slides for my ???News from the Debian Installer??? talk > at DebConf17, it occured to me that we might want to reconsider the > default here: > > Guided - use a whole disk > Guided - use a whol

RFC: Switching guided partitioning to LVM by default?

2017-08-05 Thread Cyril Brulebois
Hi, While preparing some slides for my “News from the Debian Installer” talk at DebConf17, it occured to me that we might want to reconsider the default here: Guided - use a whole disk Guided - use a whole disk with LVM Guided - use a whole disk with encrypted LVM Manual Current

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

2017-08-05 Thread Cyril Brulebois
Vagrant Cascadian (2017-08-05): > Looks like either no version, or an older version was installed: > > https://d-i.debian.org/daily-images/armhf/20170805-00:05/build_hd-media.log > dpkg-checkbuilddeps: error: Unmet build dependencies: u-boot-rockchip (>= > 2017.07+dfsg1-3)

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

2017-08-05 Thread Vagrant Cascadian
-- root/root427127 2017-08-04 15:56 > ./usr/lib/u-boot/firefly-rk3288/u-boot.rksd Looks like either no version, or an older version was installed: https://d-i.debian.org/daily-images/armhf/20170805-00:05/build_hd-media.log dpkg-checkbuilddeps: error: Unmet build dependencies: u-boot-rockchip (>= 2017.07+dfsg1-3) live well, vagrant signature.asc Description: PGP signature

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

2017-08-05 Thread Vagrant Cascadian
On 2017-08-05, Cyril Brulebois wrote: > Cyril Brulebois (2017-08-05): >> Vagrant Cascadian (2017-08-04): >> > And now fixed in u-boot 2017.07+dfsg1-3 (just uploaded), corresponding >> > fix in debian-installer pushed to git. >> >> OK, I've just triggered a new “daily” attempt since the first one

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

2017-08-05 Thread Cyril Brulebois
Cyril Brulebois (2017-08-05): > Vagrant Cascadian (2017-08-04): > > I went with the latter approach, so u-boot-rockchip includes a single > > binary that debian-installer can use. > > > > > > >> Might be best to temporarily disable the firefly-rk3288 in d-i until I > > >> figure out what's best

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

2017-08-05 Thread Cyril Brulebois
Vagrant Cascadian (2017-08-04): > I went with the latter approach, so u-boot-rockchip includes a single > binary that debian-installer can use. > > > >> Might be best to temporarily disable the firefly-rk3288 in d-i until I > >> figure out what's best to do... > > > > I've disabled it in git for

Re: Avoiding use of symlinks in d-i archive tar

2017-08-05 Thread Bastian Blank
On Sun, Jul 30, 2017 at 04:45:38PM +0200, Cyril Brulebois wrote: > Yeah. Feel free to propose patches for that then. Pushed as branch "waldi/dedup-links" to debian-installer.git. > > This symlink is handled by the archive anyway. > OK; I would have thought so but I've never looked at implementati

Bug#794410: installer works now with debian-live-9.0.1-amd64-

2017-08-05 Thread edwin de held
The problem with the installer freeze at 12% seems to be solved at the 9.0.1 iso. When i did a fresh install (without additional firmware) with the "debian-live-9.0.1-amd64-xfce.iso" on the Acer Aspire E11 (ES1-111-C5Q9) the process ended up with a fully working debian installation. I previously