Bug#907642: Suggested solution

[Viktor VM Mihajlovski]

The attached patch would change s390 installation behavior to be in line
with other architectures w.r.t IP configuration.

As a side effect it would remove the requirement to build a
netcfg-static binary in d-i/netcfg.

-- 
Regards,
  Viktor Mihajlovski
diff --git a/build/pkg-lists/generic/s390.cfg b/build/pkg-lists/generic/s390.cfg
index 38caf90..9277834 100644
--- a/build/pkg-lists/generic/s390.cfg
+++ b/build/pkg-lists/generic/s390.cfg
@@ -1,6 +1,6 @@
 cdebconf-text-udeb
 
-netcfg-static
+netcfg
 nic-modules-${kernel:Version}
 s390-netdevice
 virtio-modules-${kernel:Version}
diff --git a/build/pkg-lists/generic/s390x.cfg b/build/pkg-lists/generic/s390x.cfg
index 38caf90..9277834 100644
--- a/build/pkg-lists/generic/s390x.cfg
+++ b/build/pkg-lists/generic/s390x.cfg
@@ -1,6 +1,6 @@
 cdebconf-text-udeb
 
-netcfg-static
+netcfg
 nic-modules-${kernel:Version}
 s390-netdevice
 virtio-modules-${kernel:Version}
diff --git a/build/pkg-lists/netboot/s390.cfg b/build/pkg-lists/netboot/s390.cfg
index 1aa1065..0fa732e 100644
--- a/build/pkg-lists/netboot/s390.cfg
+++ b/build/pkg-lists/netboot/s390.cfg
@@ -1,4 +1,4 @@
-netcfg-static
+netcfg
 nic-modules-${kernel:Version}
 s390-netdevice
 virtio-modules-${kernel:Version}
diff --git a/build/pkg-lists/netboot/s390x.cfg b/build/pkg-lists/netboot/s390x.cfg
index 1aa1065..0fa732e 100644
--- a/build/pkg-lists/netboot/s390x.cfg
+++ b/build/pkg-lists/netboot/s390x.cfg
@@ -1,4 +1,4 @@
-netcfg-static
+netcfg
 nic-modules-${kernel:Version}
 s390-netdevice
 virtio-modules-${kernel:Version}

Bug#907642: s390[x]: Installer forces static IP configuration

[Viktor VM Mihajlovski]

Package: debian-installer
Version: stable
Tags: d-i
User: debian-b...@lists.debian.org
Usertags: s390 s390x
X-Debbugs-CC: debian-s...@lists.debian.org

Installation on s390 or s390x always requires a static IP configuration.
This was a reasonable thing to do in the past, when only LPAR and z/VM
installations were common.
Installing in KVM however often requires the use of autoconfiguration
via DHCP which is not possible today.

-- 
Regards,
  Viktor Mihajlovski