debian-installer-netboot-images_20170615+deb9u3_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Mar 2018 20:29:21 +0100
Source: debian-installer-netboot-images
Binary: debian-installer-9-netboot-amd64 debian-installer-9-netboot-arm64 
debian-installer-9-netboot-armel debian-installer-9-netboot-armhf 
debian-installer-9-netboot-i386 debian-installer-9-netboot-mips 
debian-installer-9-netboot-mips64el debian-installer-9-netboot-mipsel 
debian-installer-9-netboot-ppc64el
Architecture: source
Version: 20170615+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 debian-installer-9-netboot-amd64 - Debian-installer network boot images for 
amd64
 debian-installer-9-netboot-arm64 - Debian-installer network boot images for 
arm64
 debian-installer-9-netboot-armel - Debian-installer network boot images for 
armel
 debian-installer-9-netboot-armhf - Debian-installer network boot images for 
armhf
 debian-installer-9-netboot-i386 - Debian-installer network boot images for i386
 debian-installer-9-netboot-mips - Debian-installer network boot images for mips
 debian-installer-9-netboot-mips64el - Debian-installer network boot images for 
mips64el
 debian-installer-9-netboot-mipsel - Debian-installer network boot images for 
mipsel
 debian-installer-9-netboot-ppc64el - Debian-installer network boot images for 
ppc64el
Changes:
 debian-installer-netboot-images (20170615+deb9u3) stretch; urgency=medium
 .
   * Update to 20170615+deb9u3 images, from stretch-proposed-updates
   * Fix Vcs-Browser field.
Checksums-Sha1:
 4d5076d77020c6e35306db9d607bb6f8efdbd0ed 2617 
debian-installer-netboot-images_20170615+deb9u3.dsc
 2d23e40c3fdc5faced5c1fce79a3f0edaa319aeb 6940 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 23af98185c2bf45c155c117c4242c3993329350c 6236 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo
Checksums-Sha256:
 63cd401ba776c545c2c559b39d466d1d65a74bed1ca9af406ee83387af3e5736 2617 
debian-installer-netboot-images_20170615+deb9u3.dsc
 32646c62406fbed53507b6a1047cdb6a2968cec68af88b005f0fd4aa8cd15e69 6940 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 adae47ad09d01c3d93c766f12bd8dd0450f321b72b145eeadf94601561023f05 6236 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo
Files:
 0dfe53c5e4e4a04c136318017409086a 2617 misc optional 
debian-installer-netboot-images_20170615+deb9u3.dsc
 d1a8d6030e7dbfe9ba8d86f88b45ccdb 6940 misc optional 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 8086ef95b750b95df07b3f58fdbc8e4b 6236 misc optional 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlqdnpIACgkQ/5FK8MKz
VSCMQBAAgaXDcO6en3jeANKp7rYDyhFlkFfh4Alk4e8pmHxiYeAr+f988vC1w8/0
zhLoG3FxaQSKlq/w85JG93kG8uY7dr6h9jUNGg4Xxi1YDUTO/EOgRnA63ojhnzgS
nU5waUBp7SlKPWSGCKiyXFrixwkXFd5bS6/n0Bt5/qZoNDJVjXNAMpgXrpX0yBXC
PJmw1Gvk4z963LZTZY7hl5NUXPwcOMZ/VkZv2pI990/nLRsho6FmMbcepoTNmijk
3lDEAkLDCNu2Nmug7QaXcxAXOeyt2fC0DMOg2qWO1FJ5K5ffojyKQKl4LLss/zGB
QQWxnDZc72KcD9bOrYhR+A83ofT4wTMtld2you3UAKUV8qcEKW3taGqFLQbhSu5c
y/pTzAHxpXgzBwVk1JlP3/ik4OdDKKxuAmY/QmWdyw9TzzqD2JyCSN2gwklDdlGz
R4mTqcA4u1g/sVAm3q+8BmwIegU9rfkkpk21QLHJULtJhWEKQn1CtVtPDli4MDlH
OQVd7NO72oPg6D4mKasMXli+9FWFUI30C2pNhR9+9OIXNg0EoRO+0d4oljt31u4U
6cFMW7SZSUCHwOey2jHyoJ/I3lzk2OCmiJHQV7jrYU9bOww+JKlXRPDLTglZqNgw
MeH8JrQipx+s+9Tn7x2RYDZVg4/3DZSFc48e23aD5aLZcwykNpY=
=KG/H
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Accepted debian-installer-netboot-images 20170615+deb9u3 (source) into proposed-updates->stable-new, proposed-updates

[Cyril Brulebois]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Mar 2018 20:29:21 +0100
Source: debian-installer-netboot-images
Binary: debian-installer-9-netboot-amd64 debian-installer-9-netboot-arm64 
debian-installer-9-netboot-armel debian-installer-9-netboot-armhf 
debian-installer-9-netboot-i386 debian-installer-9-netboot-mips 
debian-installer-9-netboot-mips64el debian-installer-9-netboot-mipsel 
debian-installer-9-netboot-ppc64el
Architecture: source
Version: 20170615+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 debian-installer-9-netboot-amd64 - Debian-installer network boot images for 
amd64
 debian-installer-9-netboot-arm64 - Debian-installer network boot images for 
arm64
 debian-installer-9-netboot-armel - Debian-installer network boot images for 
armel
 debian-installer-9-netboot-armhf - Debian-installer network boot images for 
armhf
 debian-installer-9-netboot-i386 - Debian-installer network boot images for i386
 debian-installer-9-netboot-mips - Debian-installer network boot images for mips
 debian-installer-9-netboot-mips64el - Debian-installer network boot images for 
mips64el
 debian-installer-9-netboot-mipsel - Debian-installer network boot images for 
mipsel
 debian-installer-9-netboot-ppc64el - Debian-installer network boot images for 
ppc64el
Changes:
 debian-installer-netboot-images (20170615+deb9u3) stretch; urgency=medium
 .
   * Update to 20170615+deb9u3 images, from stretch-proposed-updates
   * Fix Vcs-Browser field.
Checksums-Sha1:
 4d5076d77020c6e35306db9d607bb6f8efdbd0ed 2617 
debian-installer-netboot-images_20170615+deb9u3.dsc
 2d23e40c3fdc5faced5c1fce79a3f0edaa319aeb 6940 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 23af98185c2bf45c155c117c4242c3993329350c 6236 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo
Checksums-Sha256:
 63cd401ba776c545c2c559b39d466d1d65a74bed1ca9af406ee83387af3e5736 2617 
debian-installer-netboot-images_20170615+deb9u3.dsc
 32646c62406fbed53507b6a1047cdb6a2968cec68af88b005f0fd4aa8cd15e69 6940 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 adae47ad09d01c3d93c766f12bd8dd0450f321b72b145eeadf94601561023f05 6236 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo
Files:
 0dfe53c5e4e4a04c136318017409086a 2617 misc optional 
debian-installer-netboot-images_20170615+deb9u3.dsc
 d1a8d6030e7dbfe9ba8d86f88b45ccdb 6940 misc optional 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 8086ef95b750b95df07b3f58fdbc8e4b 6236 misc optional 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlqdnpIACgkQ/5FK8MKz
VSCMQBAAgaXDcO6en3jeANKp7rYDyhFlkFfh4Alk4e8pmHxiYeAr+f988vC1w8/0
zhLoG3FxaQSKlq/w85JG93kG8uY7dr6h9jUNGg4Xxi1YDUTO/EOgRnA63ojhnzgS
nU5waUBp7SlKPWSGCKiyXFrixwkXFd5bS6/n0Bt5/qZoNDJVjXNAMpgXrpX0yBXC
PJmw1Gvk4z963LZTZY7hl5NUXPwcOMZ/VkZv2pI990/nLRsho6FmMbcepoTNmijk
3lDEAkLDCNu2Nmug7QaXcxAXOeyt2fC0DMOg2qWO1FJ5K5ffojyKQKl4LLss/zGB
QQWxnDZc72KcD9bOrYhR+A83ofT4wTMtld2you3UAKUV8qcEKW3taGqFLQbhSu5c
y/pTzAHxpXgzBwVk1JlP3/ik4OdDKKxuAmY/QmWdyw9TzzqD2JyCSN2gwklDdlGz
R4mTqcA4u1g/sVAm3q+8BmwIegU9rfkkpk21QLHJULtJhWEKQn1CtVtPDli4MDlH
OQVd7NO72oPg6D4mKasMXli+9FWFUI30C2pNhR9+9OIXNg0EoRO+0d4oljt31u4U
6cFMW7SZSUCHwOey2jHyoJ/I3lzk2OCmiJHQV7jrYU9bOww+JKlXRPDLTglZqNgw
MeH8JrQipx+s+9Tn7x2RYDZVg4/3DZSFc48e23aD5aLZcwykNpY=
=KG/H
-END PGP SIGNATURE-

Bug#694068: netcfg: Wireless connectivity present during an install but absent afterwards

[Trent W. Buck]

Brian Potkin wrote:
> The number of users affected by this issue over the years is not
> insignificant. Not a single one has written in support of the
> situation.

This issue has bitten me at least twice so far.

This issue's history seems to be bogged down on whether interfaces(5) can be 
mode 0600 (to hide the cleartext passphrase).
This is not necessary; the passphrase can go in a separate file.

Here is a minimal config, assuming WPA2 PSK (not Enterprise) and DHCP (not 
static) for all SSIDs:

cat >/etc/network/interfaces <"/etc/wpa_supplicant/wpa_supplicant-$iface.conf"
chmod 0600 "/etc/wpa_supplicant/wpa_supplicant-$iface.conf"

If you don't want to udebify wpa_passphrase, you can do it by hand:

cat >"/etc/wpa_supplicant/wpa_supplicant-$iface.conf" 

debian-installer-netboot-images_20170615+deb9u3_source.changes ACCEPTED into proposed-updates->stable-new

[Debian FTP Masters]

Mapping stretch to stable.
Mapping stable to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Mar 2018 20:29:21 +0100
Source: debian-installer-netboot-images
Binary: debian-installer-9-netboot-amd64 debian-installer-9-netboot-arm64 
debian-installer-9-netboot-armel debian-installer-9-netboot-armhf 
debian-installer-9-netboot-i386 debian-installer-9-netboot-mips 
debian-installer-9-netboot-mips64el debian-installer-9-netboot-mipsel 
debian-installer-9-netboot-ppc64el
Architecture: source
Version: 20170615+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 debian-installer-9-netboot-amd64 - Debian-installer network boot images for 
amd64
 debian-installer-9-netboot-arm64 - Debian-installer network boot images for 
arm64
 debian-installer-9-netboot-armel - Debian-installer network boot images for 
armel
 debian-installer-9-netboot-armhf - Debian-installer network boot images for 
armhf
 debian-installer-9-netboot-i386 - Debian-installer network boot images for i386
 debian-installer-9-netboot-mips - Debian-installer network boot images for mips
 debian-installer-9-netboot-mips64el - Debian-installer network boot images for 
mips64el
 debian-installer-9-netboot-mipsel - Debian-installer network boot images for 
mipsel
 debian-installer-9-netboot-ppc64el - Debian-installer network boot images for 
ppc64el
Changes:
 debian-installer-netboot-images (20170615+deb9u3) stretch; urgency=medium
 .
   * Update to 20170615+deb9u3 images, from stretch-proposed-updates
   * Fix Vcs-Browser field.
Checksums-Sha1:
 4d5076d77020c6e35306db9d607bb6f8efdbd0ed 2617 
debian-installer-netboot-images_20170615+deb9u3.dsc
 2d23e40c3fdc5faced5c1fce79a3f0edaa319aeb 6940 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 23af98185c2bf45c155c117c4242c3993329350c 6236 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo
Checksums-Sha256:
 63cd401ba776c545c2c559b39d466d1d65a74bed1ca9af406ee83387af3e5736 2617 
debian-installer-netboot-images_20170615+deb9u3.dsc
 32646c62406fbed53507b6a1047cdb6a2968cec68af88b005f0fd4aa8cd15e69 6940 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 adae47ad09d01c3d93c766f12bd8dd0450f321b72b145eeadf94601561023f05 6236 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo
Files:
 0dfe53c5e4e4a04c136318017409086a 2617 misc optional 
debian-installer-netboot-images_20170615+deb9u3.dsc
 d1a8d6030e7dbfe9ba8d86f88b45ccdb 6940 misc optional 
debian-installer-netboot-images_20170615+deb9u3.tar.xz
 8086ef95b750b95df07b3f58fdbc8e4b 6236 misc optional 
debian-installer-netboot-images_20170615+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlqdnpIACgkQ/5FK8MKz
VSCMQBAAgaXDcO6en3jeANKp7rYDyhFlkFfh4Alk4e8pmHxiYeAr+f988vC1w8/0
zhLoG3FxaQSKlq/w85JG93kG8uY7dr6h9jUNGg4Xxi1YDUTO/EOgRnA63ojhnzgS
nU5waUBp7SlKPWSGCKiyXFrixwkXFd5bS6/n0Bt5/qZoNDJVjXNAMpgXrpX0yBXC
PJmw1Gvk4z963LZTZY7hl5NUXPwcOMZ/VkZv2pI990/nLRsho6FmMbcepoTNmijk
3lDEAkLDCNu2Nmug7QaXcxAXOeyt2fC0DMOg2qWO1FJ5K5ffojyKQKl4LLss/zGB
QQWxnDZc72KcD9bOrYhR+A83ofT4wTMtld2you3UAKUV8qcEKW3taGqFLQbhSu5c
y/pTzAHxpXgzBwVk1JlP3/ik4OdDKKxuAmY/QmWdyw9TzzqD2JyCSN2gwklDdlGz
R4mTqcA4u1g/sVAm3q+8BmwIegU9rfkkpk21QLHJULtJhWEKQn1CtVtPDli4MDlH
OQVd7NO72oPg6D4mKasMXli+9FWFUI30C2pNhR9+9OIXNg0EoRO+0d4oljt31u4U
6cFMW7SZSUCHwOey2jHyoJ/I3lzk2OCmiJHQV7jrYU9bOww+JKlXRPDLTglZqNgw
MeH8JrQipx+s+9Tn7x2RYDZVg4/3DZSFc48e23aD5aLZcwykNpY=
=KG/H
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Re: [Pkg-dns-devel] What to do with isc-dhcp-client-udeb?

[Cyril Brulebois]

Hi all,

Ondřej Surý  (2018-01-23):
> I would also love to get rid of the isc-dhcp-client-udeb, but so far
> the message from the busybox team was that the dhcp client there
> doesn't compile there and needs some upstream work to get it working.
> 
> (As a matter of fact, the busybox doesn't compile at all on kfreebsd-*
> and hurd-i386 right now.)
> 
> As for the BIND libraries and libatomic.
> 
> There has been some effort to replace the custom atomic code with a
> C-provided counterpart - it also fixes the mips deadlocks.
> 
> But generally, I would prefer to move all BIND libraries into "custom"
> namespace, so the libraries are not used by anything else, and either:
> 
> a) use the custom copy of the libraries inside isc-dhcp
> b) prepare separate package for the lib-udeb that would
>follow the BIND 9.11 development (BIND 9.11 is to be supported for
>next 4 years) and then remove those AND isc-dhcp from Debian.
> 
> The upcoming ISC-DHCP release 4.4.0 is ought to be the _last_ major
> upgrade, see: https://www.isc.org/blogs/isc-dhcp-the-last-branch/
> 
> And if porting udhcpc to kFreeBSD proves to be much work, then perhaps
> porting dhclient from OpenBSD might be an option?

Thanks for your feedback, Ondřej.

It'd be helpful to have some input from hurd and kfreebsd people, so
that we know what to do with isc-dhcp-client-udeb in the end…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processing of debian-installer-netboot-images_20170615+deb9u3_source.changes

[Debian FTP Masters]

debian-installer-netboot-images_20170615+deb9u3_source.changes uploaded 
successfully to localhost
along with the files:
  debian-installer-netboot-images_20170615+deb9u3.dsc
  debian-installer-netboot-images_20170615+deb9u3.tar.xz
  debian-installer-netboot-images_20170615+deb9u3_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Re: Installing 2 encrypted Debians alongside Windows

[Jonathan Carter (highvoltage)]

On 05/03/2018 17:44, coco...@t-online.de wrote:
> If I try to accomplish this with the 9.2.1 install DVD, will Debian
> Installer be aware of the existence of the pre-existing Debian install
> when generating/updating Grub?

Yep.

-Jonathan

Installing 2 encrypted Debians alongside Windows

[coco...@t-online.de]

Hi.

Debian 9.2.1 MATE.
LUKS-encrypted via Debian Installer from 9.2.1 DVD.
Current partition scheme: EFI; Windows 10; Debian /boot; LUKS-encrypted
Debian /root & /swap; Unallocated; Windows 10 Recovery.

I'd like to have a second, LUKS-encrypted install of Debian on the
unallocated partition, so that I'll ultimately be able to choose between
booting Windows, Encrypted Debian A and Encrypted Debian B from the
default Grub boot menu.

If I try to accomplish this with the 9.2.1 install DVD, will Debian
Installer be aware of the existence of the pre-existing Debian install
when generating/updating Grub?

Thanks.

Re: Clean up bug report for debootstrap

[Hideki Yamane]

On Sun, 25 Feb 2018 23:22:04 +0900
Hideki Yamane  wrote:
>  It seems that we can close below bug reports for debootstrap with
>  proposed patches (including mine).

 I've prepared NMU for fixes about old archived releases and will
 upload 10 delayed queue. I believe that it is no harm for buster/sid
 since it doesn't tough any part of it, see attached patch.

 And set temporary repo at https://salsa.debian.org/henrich/debootstrap
 so you can pull changes from it later.

diff --git a/debian/changelog b/debian/changelog
index b1ef82b..7421862 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+debootstrap (1.0.93+nmu1) unstable; urgency=medium
+
+  * Non-maintainer Upload.
+  * Use force_md5 for breezy, dapper and edgy (Closes: #659360, #676373)
+Now you can create Ubuntu breezy/dapper/edgy chroot.
+  * Add Suggests: ubuntu-archive-keyring for debootstraping Ubuntu on Debian.
+When you fetch Ubuntu packages ubuntu-archive-keyring is necessary.
+(Closes: #736995)
+  * Change repository URI for old Ubuntu releases (Closes: #676370, #839073)
+Archived Ubuntu releases are at old-releases.ubuntu.com/ubuntu
+  * Set correct keyring and default mirror for old debian releases.
+Now you can fetch popato/woody/sarge/etch/lenny/squeeze if you want.
+(Closes: #891404, #600647, #792729)
+
+ -- Hideki Yamane   Mon, 05 Mar 2018 22:28:22 +0900
+
 debootstrap (1.0.93) unstable; urgency=medium
 
   [ Mattia Rizzolo ]
diff --git a/debian/control b/debian/control
index e987ace..0d9d9a9 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Package: debootstrap
 Architecture: all
 Depends: ${misc:Depends}, wget
 Recommends: gnupg, ${keyring}
+Suggests: ubuntu-archive-keyring
 Description: Bootstrap a basic Debian system
  debootstrap is used to create a Debian base system from scratch,
  without requiring the availability of dpkg or apt. It does this by
diff --git a/scripts/breezy b/scripts/breezy
index 2148cec..f15967a 100644
--- a/scripts/breezy
+++ b/scripts/breezy
@@ -3,6 +3,7 @@ mirror_style release
 download_style apt
 finddebs_style from-indices
 variants - buildd
+force_md5
 
 case $ARCH in
   alpha|ia64) LIBC="libc6.1" ;;
diff --git a/scripts/dapper b/scripts/dapper
index af83c0c..b1e44d0 100644
--- a/scripts/dapper
+++ b/scripts/dapper
@@ -10,6 +10,7 @@ mirror_style release
 download_style apt
 finddebs_style from-indices
 variants - buildd
+force_md5
 
 case $ARCH in
   alpha|ia64) LIBC="libc6.1" ;;
diff --git a/scripts/edgy b/scripts/edgy
index 01d6568..719a258 100644
--- a/scripts/edgy
+++ b/scripts/edgy
@@ -1,6 +1,6 @@
 case $ARCH in
   amd64|i386|powerpc|sparc)
-default_mirror http://archive.ubuntu.com/ubuntu
+default_mirror http://old-releases.ubuntu.com/ubuntu
 ;;
   *)
 default_mirror http://ports.ubuntu.com/ubuntu-ports
@@ -10,6 +10,7 @@ mirror_style release
 download_style apt
 finddebs_style from-indices
 variants - buildd fakechroot
+force_md5
 
 if doing_variant fakechroot; then
 test "$FAKECHROOT" = "true" || error 1 FAKECHROOTREQ "This variant requires fakechroot environment to be started"
diff --git a/scripts/etch b/scripts/etch
deleted file mode 12
index 9a63c96..000
--- a/scripts/etch
+++ /dev/null
@@ -1 +0,0 @@
-sid
\ No newline at end of file
diff --git a/scripts/etch b/scripts/etch
new file mode 100644
index 000..22c89a9
--- /dev/null
+++ b/scripts/etch
@@ -0,0 +1,216 @@
+mirror_style release
+download_style apt
+finddebs_style from-indices
+variants - buildd fakechroot minbase
+default_mirror http://archive.debian.org/debian
+keyring /usr/share/keyrings/debian-archive-removed-keys.gpg
+force_md5
+
+if doing_variant fakechroot; then
+	test "$FAKECHROOT" = "true" || error 1 FAKECHROOTREQ "This variant requires fakechroot environment to be started"
+fi
+
+case $ARCH in
+	alpha|ia64) LIBC="libc6.1" ;;
+	kfreebsd-*) LIBC="libc0.1" ;;
+	hurd-*) LIBC="libc0.3" ;;
+	*)  LIBC="libc6" ;;
+esac
+
+work_out_debs () {
+	required="$(get_debs Priority: required)"
+
+	if doing_variant - || doing_variant fakechroot; then
+		#required="$required $(get_debs Priority: important)"
+		#  ^^ should be getting debconf here somehow maybe
+		base="$(get_debs Priority: important)"
+	elif doing_variant buildd; then
+		base="apt build-essential"
+	elif doing_variant minbase; then
+		base="apt"
+	fi
+
+	if doing_variant fakechroot; then
+		# ldd.fake needs binutils
+		required="$required binutils"
+	fi
+
+	case $MIRRORS in
+	https://*)
+		base="$base apt-transport-https ca-certificates"
+		;;
+	esac
+}
+
+first_stage_install () {
+	case "$CODENAME" in
+		etch|etch-m68k|jessie|jessie-kfreebsd|lenny|squeeze|wheezy) ;;
+		*)
+			EXTRACT_DEB_TAR_OPTIONS="$EXTRACT_DEB_TAR_OPTIONS -k"
+			setup_merged_usr
+			;;
+	esac
+
+	extract $required
+
+	mkdir -p "$TARGET/var/lib/dpkg"
+	: >"$TARGET/var/lib/dpkg/status"
+	: >"$TARGET/var/lib/dpkg/available"
+
+	setup_etc
+	if [ ! -e 

Bug#694068: netcfg: Wireless connectivity present during an install but absent afterwards

[Brian Potkin]

On Fri 23 Nov 2012 at 14:31:20 +, Brian Potkin wrote:

> I installed in expert mode over a wireless link from
> 
> Debian GNU/Linux testing "Wheezy" - Official Snapshot i386 NETINST Binary-1 
> 20121122-21:21
> 
> This ISO has netcfg_1.102. Only "Standard system utilities" was selected
> as a task. Re-booted as instructed. No network! Checked the contents of
> /etc/network/interfaces. The only interface available is lo. I'm still
> in a state of shock. :)

[...]

The number of users affected by this issue over the years is not
insignificant. Not a single one has written in support of the
situation.

https://lists.debian.org/debian-user/2018/03/msg00066.html

has the latest experiences of three users.

Regards,

Brian.

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

[Kari Tanninen]

I think GuruPlug doesn't have SPI-flash -> BootRom is executed before 
U-boot -> virtual memory is set-up for MMU for U-boot.


88F6281 SoC is probably using Kirkwood series 12KB BootRom ver. 1.21 or 
later, but I cannot find prom source code (propietary/NDA stuff?).


88F6281 prom MMU memory setup is documented and there is some 
limitations for virtual memory address space (for physical/PCI memory 
address space mapping tables) after MMU setup and image needs special 
header -> special uImage format needed (?).


In my case, I guess when loading fdt separatelly U-boots can set memory 
paging correctly for  uInitrd. Loading to wrong place (=too high?) it 
overlaps virtul memory swithing tables. It depends ARM based SoC 
manufacturers BootRom MMU setups, if separete fdt loading is usable for 
general linux kernel/bootloder API.


What will be d-i debian-armel policy?

KTA




Kari Tanninen kirjoitti 4.3.2018 20:08:

To be exact, I have Guruplug Server plus -version, and this device SoC
is 88F6281.

KariT

Kari Tanninen kirjoitti 4.3.2018 15:11:

Ben wrote:

"This behaviour is configurable.  For armel and armhf we enable
CONFIG_ARM_ATAG_DTB_COMPAT and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER so that ATAG
variables override the DTB"

That is obvious cause of these uInitrd relocation problems.

I don't exactly know how U-boot passes ATAG-values to kernel but in
multiprocessing environment it is very difficult task anyway
(and there is even BareBox forked from U-boot for non-flexible
attitude of U-boot for these kernel/bootloader API issues).

ARM MMU/multiprocessing environment is straightforward, but very
complex. I found GuruPlug PXA168 SoC specifications, but there is
thousands of
pages of information and it is very difficult to guess how
kernel/U-boot uses it. Linux kernel is expecting very complete setup
on boot,
and most difficult part (MMU init) must be done on bootloader.

I think that BareBox approach is not very healthy either, there is
some odd features to use FDT, too. Keeping up two versions of FDT, for
example.

Best way to do it with Linux -kernel is to use one FDT-blob generated
by kconfig at kernel compile and load it by bootloader. At Kernel API
point of view
that should be same situation as PC and command line parameters and
other boot-time variables is supplied by bootloader by modifying
FDT-blob
(for example "choosen") nodes.

KariT

Ben Hutchings kirjoitti 3.3.2018 16:13:

On Fri, 2018-03-02 at 14:48 +0200, Kari Tanninen wrote:

"In Debian installer, for the various plug devices, we append to
the DTB at the end of the kernel rather than loading it separately."


Is that possible/reasonable?

U-boot have to link all files on boot and it is impossibe to append
command line parametres to fdt-blob
without resize fdt-blob at U-boot. U-boot is using physical 
addressing

only(?) and I think kernel cannot
resize itself before boot without relocation problems -> bootm_size
variable issue.

If fdt is used, kernel should discard ATAG-variables by default, I
think.

[...]

This behaviour is configurable.  For armel and armhf we enable
CONFIG_ARM_ATAG_DTB_COMPAT and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER so that ATAG
variables override the DTB.

Ben.