Bug#872410: AHCI module not loaded when using preseed

2017-08-20 Thread Gilles MOREL 
Hello,

I don't know this message is for me, but I don't know what is a 'depmod' and I 
don't know how to add one in the installer, considering I use the netinstaller 
from debian-installer-9-netboot-amd64 package.
--
Gilles Émilien MOREL 
Pensez à l'environnement, imprimez ce message electronique et jetez le bien au 
tri sélectif.

- Message original 
Ben Hutchings 
à Cyril Brulebois , 872...@bugs.debian.org, Gilles MOREL 

le jeudi 17 août 2017 à 22:50:28 +0100
avec Evolution 3.22.6-1 

Re: Bug#872410: AHCI module not loaded when using preseed
---
On Thu, 2017-08-17 at 17:48 +0200, Cyril Brulebois wrote:
> Hi Gilles,
> 
> Gilles MOREL  (2017-08-17):
> > After some search, I noticed that the ahci kernel module was not
> > loaded when I use preseed.
> 
> This is strange, it seems the sata-modules udeb is fetched just fine,
> I'm not sure why ahci wouldn't be loaded.
> 
> linux.git has this as its configuration:
> 
> debian/installer/modules/sata-modules:drivers/ata/ahci* ?
> 
> so ahci* modules should end up in that udeb, and that's indeed the
> case for what I can see.
> 
> Are you using brand new hardware for which support might be missing?
> Is the non-preseed installation loading appropriate modules… on the
> same HW as the failing preseed installation?

Could this be due to a missing 'depmod' in the installer?

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.



signature.asc
Description: This is a digitally signed message part.

Bug#872577: debootstrap: Handle existing /dev

2017-08-20 Thread Ansgar Burchardt 
Dan Nicholson writes:
> On Fri, Aug 18, 2017 at 2:48 PM, Henrique de Moraes Holschuh
>  wrote:
>> Wouldn't it be more straigthforward to "test -e || mknod" ?
>
> I definitely considered that, but it seemed more noisy to the code to
> add a conditional for every call. But I'd be fine reworking to that
> approach if that's more acceptable, though.

You can always introduce a `mknod_if_not_exists` function or so.  Though
I'm not sure this is worth here (the name is so long the `test -e` is
almost shorter).

Ansgar

Re: Please unblock glibc/2.24-14

2017-08-20 Thread Aurelien Jarno 
On 2017-08-20 00:56, Cyril Brulebois wrote:
> Hello,
> 
> Aurelien Jarno  (2017-08-19):
> > glibc/2.24-14 has been blocked for long in unstable due to the linux
> > package not migrating. Unfortunately it failed to migrate at the same
> > time due to bug#871275, which has nothing to glibc besides the fact that
> > "libc-bin" appears in the log.
> > 
> > In short, after waiting for more than 2 weeks, it missed the freeze only
> > by a few hours. It would be nice to have it in testing asap, as the
> > current version in testing is not buildable with binutils 2.19 which is
> > now in testing. Besides that nothing to worry about for d-i.
> 
> glibc  | 2.24-14   | testing| source
> glibc  | 2.24-14   | unstable   | source
> 
> Happened during the 1000Z run.

Thanks!

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#872725: installation-reports: When installing with a encrypted swap, device was saved as /dev/sda2 in /etc/crypttab, but on first boot devices had been switched (sda became sdb, and vice versa).

2017-08-20 Thread Julien Lecomte 
Package: installation-reports
Severity: important

Dear Maintainer,

-- Package-specific info:

Boot method: CD on USB flashdrive
Image version: latest debian 9 available on site (as of 2017-08-19)
Date: 2017-08-20

Machine: built
Partitions: cf. below

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

When I installed Debian, I chose the following for my personalized partition:

/dev/sda
  /dev/sda1 => /boot, ext4
  /dev/sda2 => encrypted, swap
  /dev/sda3 => encrypted, /

I left my /dev/sdb as unused, it only has /dev/sdb1

The following got saved in crypttab:
sda2_crypt /dev/sda2 /dev/urandom cipher=aes-xts-plain64,size=256,swap
sda3_crypt UUID=34d65b53-5df5-48da-8ca6-884b38a9cd7d none luks

And the fstab was saved as :
UUID=f2050f17-78c5-431f-bfdc-80af4f2d0dc9 /boot ext4 discard,sync 0 2
/dev/mapper/sda3_crypt / ext4 discard,errors=remount-ro 0   1
/dev/mapper/sda2_crypt none swap sw 0 0


Nevertheless, on reboot, I noticed that swap was not mounted. The issue is that
on first reboot, /dev/sda and /dev/sdb got switched.

All the partitions referenced by UUID got mounted correctly.

I'm probably lucky that /dev/sda2 from install didn't point to anything anymore 
since it could have trashed a partition of mine.

Shouldn't /etc/crypttab be created by using the UUID or partid of the swap?


Thanks,
Julien



-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170615"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux pumilio 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core 
Processor DRAM Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset 
Family USB xHCI Controller [8086:8cb1]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 9 Series 
Chipset Family ME Interface #1 [8086:8cba]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection (2) I218-V [8086:15a1]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:85c4]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset 
Family USB EHCI Controller #2 [8086:8cad]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset 
Family HD Audio Controller [8086:8ca0]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8618]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset 
Family PCI Express Root Port 1 [8086:8c90] (rev d0)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 9 Series Chipset 
Family PCI Express Root Port 5 [8086:8c98] (rev d0)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset 
Family USB EHCI Controller #1 [8086:8ca6]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 9 Series Chipset 
Family Z97 LPC Controller [8086:8cc4]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset 
Family SATA Controller [AHCI Mode] [8086:8c82]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn:

Bug#872725: installation-reports: When installing with a encrypted swap, device was saved as /dev/sda2 in /etc/crypttab, but on first boot devices had been switched (sda became sdb, and vice versa).

2017-08-20 Thread Cyril Brulebois 
Hi Julien,

Julien Lecomte  (2017-08-20):
> Boot method: CD on USB flashdrive
> Image version: latest debian 9 available on site (as of 2017-08-19)
> Date: 2017-08-20
> 
> Machine: built
> Partitions: cf. below
> 
> Initial boot:   [O]
> Detect network card:[O]
> Configure network:  [O]
> Detect CD:  [O]
> Load installer modules: [O]
> Clock/timezone setup:   [O]
> User/password setup:[O]
> Detect hard drives: [O]
> Partition hard drives:  [O]
> Install base system:[O]
> Install tasks:  [O]
> Install boot loader:[O]
> Overall install:[O]
> 
> Comments/Problems:
> 
> When I installed Debian, I chose the following for my personalized partition:
> 
> /dev/sda
>   /dev/sda1 => /boot, ext4
>   /dev/sda2 => encrypted, swap
>   /dev/sda3 => encrypted, /
> 
> I left my /dev/sdb as unused, it only has /dev/sdb1
> 
> The following got saved in crypttab:
> sda2_crypt /dev/sda2 /dev/urandom cipher=aes-xts-plain64,size=256,swap
> sda3_crypt UUID=34d65b53-5df5-48da-8ca6-884b38a9cd7d none luks
> 
> And the fstab was saved as :
> UUID=f2050f17-78c5-431f-bfdc-80af4f2d0dc9 /boot ext4 discard,sync 0 2
> /dev/mapper/sda3_crypt / ext4 discard,errors=remount-ro 0   1
> /dev/mapper/sda2_crypt none swap sw 0 0
> 
> 
> Nevertheless, on reboot, I noticed that swap was not mounted. The issue is 
> that
> on first reboot, /dev/sda and /dev/sdb got switched.
> 
> All the partitions referenced by UUID got mounted correctly.
> 
> I'm probably lucky that /dev/sda2 from install didn't point to
> anything anymore since it could have trashed a partition of mine.
> 
> Shouldn't /etc/crypttab be created by using the UUID or partid of the
> swap?

I've only toyed with guided encrypted LVM setups, and there swap is on an
LV, so I haven't seen this yet.

Storing /dev/sda2 there looks buggy indeed, esp. since the root partition
is pointed to by UUID instead…

I'm not familiar with the relevant code yet though.


KiBi.


signature.asc
Description: Digital signature

Bug#872577: debootstrap: Handle existing /dev

2017-08-20 Thread Ben Hildred 
On Sun, Aug 20, 2017 at 3:25 AM, Ansgar Burchardt  wrote:

> Dan Nicholson writes:
> > On Fri, Aug 18, 2017 at 2:48 PM, Henrique de Moraes Holschuh
> >  wrote:
> >> Wouldn't it be more straigthforward to "test -e || mknod" ?
> >
> > I definitely considered that, but it seemed more noisy to the code to
> > add a conditional for every call. But I'd be fine reworking to that
> > approach if that's more acceptable, though.
>
> You can always introduce a `mknod_if_not_exists` function or so.  Though
> I'm not sure this is worth here (the name is so long the `test -e` is
> almost shorter).
>
> Ansgar
>
>
function mknod-e () {
[ -e "$1" ] || mknod "$@"
}



-- 
--
Ben Hildred
Automation Support Services

Re: l10n co-coordinator

2017-08-20 Thread Holger Wansing 
Hi Lior and list,

Cyril Brulebois  wrote:
> > For the installer itself, I would not start before the release of Stretch,
> > it's too late for that now.
> > My first target would be the installer for buster.
> 
> I'm adding Lior in copy of this small subthread since he just approached me
> during DebConf, as he would like to help with translation coordination. :)

So welcome in our new sub-team :-)

My idea for the installer was basically, to send a call for translation
updates to all languages, which are outdated, means searching for new
translators for those languages on the relevant l10n lists.

However, at debconf a new intend was called out to change the whole 
translation infrastructure for the installer (in the long term of course,
no quick actions to be expected IMO).

This is why I'm somewhat unsure how to proceed...
Should I try for recruiting new translators, even if the workflow changes
heavily some time later?
Recruiting new translators means explanation of workflow to some degree, what
would be to no avail, if infrastructure changes.


Thoughts?
Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#872577: debootstrap: Handle existing /dev

2017-08-20 Thread Philip Hands 
Ben Hildred <426...@gmail.com> writes:

> On Sun, Aug 20, 2017 at 3:25 AM, Ansgar Burchardt  wrote:
>
>> Dan Nicholson writes:
>> > On Fri, Aug 18, 2017 at 2:48 PM, Henrique de Moraes Holschuh
>> >  wrote:
>> >> Wouldn't it be more straigthforward to "test -e || mknod" ?
>> >
>> > I definitely considered that, but it seemed more noisy to the code to
>> > add a conditional for every call. But I'd be fine reworking to that
>> > approach if that's more acceptable, though.
>>
>> You can always introduce a `mknod_if_not_exists` function or so.  Though
>> I'm not sure this is worth here (the name is so long the `test -e` is
>> almost shorter).
>>
>> Ansgar
>>
>>
> function mknod-e () {
> [ -e "$1" ] || mknod "$@"
> }

$1 for mknod in this case is liable to be '-m'

The attached patch might satisfy the quest for neatness.

One could instead call the function something like
ensure-exists-in-target and leave the /dev/'s on all the filenames, if
that were considered clearer.

Cheers, Phil.


signature.asc
Description: PGP signature
>From 28f460d35d8925442ce5a63c45b51d04a0db37dd Mon Sep 17 00:00:00 2001
From: Philip Hands 
Date: Sun, 20 Aug 2017 23:48:34 +0200
Subject: [PATCH] in setup_devices_simple(), only create devices that do not
 yet exist

---
 functions | 19 ---
 1 file changed, 12 insertions(+), 7 deletions(-)

diff --git a/functions b/functions
index 3cfa0d4..6c40ec7 100644
--- a/functions
+++ b/functions
@@ -1162,18 +1162,23 @@ setup_dynamic_devices () {
 }
 
 setup_devices_simple () {
+	function ensure-exists-dev() {
+		local path="$TARGET/dev/$1" ; shift
+		[ -e "$path" ] || mknod -m 666 $path "$@"
+	}
+
 	# The list of devices that can be created in a container comes from
 	# src/core/cgroup.c in the systemd source tree.
-	mknod -m 666 $TARGET/dev/null	c 1 3
-	mknod -m 666 $TARGET/dev/zero	c 1 5
-	mknod -m 666 $TARGET/dev/full	c 1 7
-	mknod -m 666 $TARGET/dev/random	c 1 8
-	mknod -m 666 $TARGET/dev/urandom	c 1 9
-	mknod -m 666 $TARGET/dev/tty	c 5 0
+	ensure-exists-dev null		c 1 3
+	ensure-exists-dev zero		c 1 5
+	ensure-exists-dev full		c 1 7
+	ensure-exists-dev random	c 1 8
+	ensure-exists-dev urandom	c 1 9
+	ensure-exists-dev tty		c 5 0
 	mkdir $TARGET/dev/pts/ $TARGET/dev/shm/
 	# Inside a container, we might not be allowed to create /dev/ptmx.
 	# If not, do the next best thing.
-	if ! mknod -m 666 $TARGET/dev/ptmx c 5 2; then
+	if ! ensure-exists-dev ptmx c 5 2; then
 		warning MKNOD "Could not create /dev/ptmx, falling back to symlink. This chroot will require /dev/pts mounted with ptmxmode=666"
 		ln -s pts/ptmx $TARGET/dev/ptmx
 	fi
-- 
2.11.0

-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY

Bug#872764: Package: installation-reports

2017-08-20 Thread Frank Colcord 
Package: installation-reports

Boot method:
I downloaded iso by torrent to my Lenovo x200 running Ubuntu.
put ISO onto USB start up
put USB into my Lenovo x250
it booted fine.

Image version:

   1.

   https://cdimage.debian.org/cdimage/unofficial/non-free/
   cd-including-firmware/9.1.0+nonfree/amd64/bt-dvd/
   



Date: Started Sunday 20th August about 3pm GMT

Machine: Lenovo x250
Processor: not sure right now
Memory: 8 GB
Partitions: I said use the entire USB disk (128GB) and LVM encrypted.

Output of lspci -knn (or lspci -nn): sorry, can't since haven't aborted
installation yet.

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ 0]
Detect network card:[ 0]
Configure network:  [ 0]
Detect CD:  [  ] I don't have a CD
Load installer modules: [ 0] I think so.
Detect hard drives: [ 0] Detected all HD correctly
Partition hard drives:  [ 0] full disk encrypted LVM
Install base system:[ 0]
Clock/timezone setup:   [ 0]
User/password setup:[ 0]
Install tasks:  [ E]
it seems stuck in the middle of installing software. see above.

Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Hi, I've left the installation hanging. Still on the screen of my laptop.
I'd rather not start all over again.
I looked on IRC, but everyone asleep.
Will try to get on tomorrow evening.

kind regards, Frank



   1.


   X200 Download torrent of Debian 9 DVD 1 with non free software.
   1.

  https://cdimage.debian.org/cdimage/unofficial/non-free/
  cd-including-firmware/9.1.0+nonfree/amd64/bt-dvd/
  

  2.
  2.

   X200 install dvd to 16 GB USB drive
   3.

   X250 install usb to usb
   1.

  Bug: Doesn’t recognize mouse in the beginning, but does later, by the
  time I choose domain name.
  2.

  Bug: Installation procedure doesn’t have buttons on each screen to
  cancel cleanly.
  1.

 I really wanted those during netinstall
 3.

  Bug: Non free install still asked for wifi files, but they were there
  already, shouldn’t it detect before asking for them?


   1.

   Partition disks: guided: use entire disk and set up encrypted LVM
   2.

   Was able to point to other usb drive 128 gb
   3.

   Long time to erase disk
   4.

   Defaults selected ongoingly
   5.

   No extra desktops, just debian, not gnome.
   1.

  Something failed, got back to desktop choices, chose gnome
  6.

   Select and install software: /media/cdrom/:Please insert the disc
   labeled: ‘Debian GNU/Linux 9.1.0_Stretch_-Official amd64 DVD Binary-1
   20170722-11:29’ in the drive ‘media/cdrom/’ and press [Enter]
   1.

  Can’t exit, skip, give other media, etc., can’t escape, continue just
  stays there
  2.

  On file 1223 of 1479 blinks on the screen when I type escape
  3.