Bug#820168: debian-installer: The Grub installation step in Debian Testing Installer fails on Gigabyte MP30-AR0

[Ronald Maas]

Hi KiBi,

Good news. I was able to successfully install Stretch RC2 on the
Gigabyte MP30-AR0 motherboard. Also the installer was able to
recognize the network properly, so this bug and also bug 820022 can be
closed.

Attached the dmesg output for reference.

A minor issue remaining is that the AST2400 VGA adapter is not
recognized out of the box. Serial console did work and I was also able
to ssh into the machine after installation and reboot. Reason is
CONFIG_DRM_AST is not set in the kernel configuration. Hope Debian
kernel team could consider changing it to compile it as a module.

Thanks for all the hard work.

Kind regards,
Ronald Maas

On Fri, Feb 3, 2017 at 6:38 PM, Cyril Brulebois  wrote:
> Control: tag -1 - d-i
>
> Hi Ronald,
>
> Ronald Maas  (2016-04-05):
>> The Grub installation step in Debian Installer failed on TianoCore
>> UEFI firmware. The /target/boot/efi directory is empty and the
>> following error is displayed:
>>
>> GRUB installation failed
>> The 'grub-efi-arm64' package failed to install into /target/
>>
>> Version-Release number of selected component (if applicable):
>>
>> Debian Testing DVD ISO dated 28-03-2016
>>
>> How reproducible:
>>
>> Every time.
>>
>> Steps to Reproduce:
>>
>> 1. Download 
>> http://cdimage.debian.org/cdimage/weekly-builds/arm64/iso-dvd/debian-testing-arm64-DVD-1.iso
>> 2. Verify checksum
>> 3. Copy to USB drive using Windows Win32DiskImager
>> 4. Insert drive in X-Gene system
>> 5. Boot X-Gene system
>> 6. Navigate to UEFI Shell
>> 7. Enter the following command to start the Fedora installer:
>>FS1:\EFI\BOOT\BOOTAA64.EFI
>> 8. In the Grub boot menu select the first menu option and hit enter
>> 9. Proceed through the remaining steps of the setup procedure. Selecting
>>default options where applicable. Note on the MP30-AR0 the network is not
>>function (see bug report
>>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820022. So skip this 
>> step
>>to continue
>> 10. After the GRUB installation step fails, continue without bootloader and 
>> reboot
>> 11. System fails to boot Debian Testing and starts the UEFI Shell instead
>>
>> Actual results:
>>
>> No GRUB bootloader is installed. After restarting the system, no 'debian' 
>> menu
>> entry is visible in UEFI and the /boot/efi directory is empty
>>
>> Expected results:
>>
>> To be able to boot Debian Testing after selecting the 'debian' menu entry in
>> UEFI. Also /boot/efi should contain EFI/debian/grubaa64.efi
>>
>> Additional info:
>>
>> Hardware
>> Gigabyte MP30-AR0 motherboard with APM X-Gene 1 processor flashed with 
>> TianoCore UEFI
>> Kingston KVR16LE11S8/4HB 16 GB ECC DDR3 DRAM
>> HGST Deskstar NAS 6 TB hard drive
>> Logitech USB keyboard
>>
>> The standard U-Boot firmware has been replaced by TianoCore UEFI using the 
>> steps described in: 
>> https://rwmj.wordpress.com/2016/03/08/gigabyte-mp30-ar0-flashing-uefi/
>
> Any chance you could give Stretch RC 2 a try? Info/download at:
>   https://www.debian.org/devel/debian-installer/
>
>
> KiBi.
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.0-1-arm64 (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 
(2017-01-12)
[0.00] Boot CPU: AArch64 Processor [500f0001]
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: EFI v2.40 by American Megatrends
[0.00] efi:  ACPI 2.0=0x807ff43000  ESRT=0x807e161e18  SMBIOS 
3.0=0x807e161c18 
[0.00] esrt: Reserving ESRT space from 0x00807e161e18 to 
0x00807e161e50.
[0.00] On node 0 totalpages: 4194304
[0.00]   DMA zone: 8192 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 524288 pages, LIFO batch:31
[0.00]   Normal zone: 57344 pages used for memmap
[0.00]   Normal zone: 3670016 pages, LIFO batch:31
[0.00] percpu: Embedded 22 pages/cpu @807fffe93000 s50200 r8192 
d31720 u90112
[0.00] pcpu-alloc: s50200 r8192 d31720 u90112 alloc=22*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[0.00] Detected PIPT I-cache on CPU0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 4128768
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-arm64 
root=/dev/sda2 ro quiet
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 
bytes)
[0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 
bytes)
[0.00] software IO TLB [mem 0xfbfec000-0xfffec000] (64MB) mapped at 
[80007bfec000-80007ffebfff]
[0.00] Memory: 16363176K/16777216K available (6780K kernel code, 1020K 
rwdata, 2164K rodata, 3264K init, 634K bss, 414040K reserved, 0K cma-reserved)
[0.00] Virtual kernel memory layout:
[0.00] modules : 

Bug#854653: encourage users to generate strong passwords

[Christian PERRIER]

reassign 854653 user-setup
thanks

Quoting Antoine Beaupre (anar...@debian.org):
> Package: debian-installer
> Severity: wishlist
> 
> After reflecting for a few days about password generation and writing
> an [article][1] about it, I was told the debian-installer may be a good
> place to encourage people to set strong passwords. In the d-i, we set
> one or three critically important passwords: the main user account
> and, optionnally, the root account and crypto passphrase. The latter
> password seems especially important to be cryptographically secure.


This is more or less #364526

I don't merge the bugs as they're phrased differently but I think the
spirit is the same.but in 11 years, it seems that nobody stepped
up to implement something..:-)



signature.asc
Description: PGP signature

Processed: Re: Bug#854653: encourage users to generate strong passwords

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 854653 user-setup
Bug #854653 [debian-installer] encourage users to generate strong passwords
Bug reassigned from package 'debian-installer' to 'user-setup'.
Ignoring request to alter found versions of bug #854653 to the same values 
previously set
Ignoring request to alter fixed versions of bug #854653 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854653: encourage users to generate strong passwords

[Antoine Beaupre]

Package: debian-installer
Severity: wishlist

After reflecting for a few days about password generation and writing
an [article][1] about it, I was told the debian-installer may be a good
place to encourage people to set strong passwords. In the d-i, we set
one or three critically important passwords: the main user account
and, optionnally, the root account and crypto passphrase. The latter
password seems especially important to be cryptographically secure.

[1]: https://lwn.net/SubscriberLink/713806/f43f8fca9c10099a/

As things stand, the user is left on his own: there are little
instructions on how to choose a proper password, what to do with it,
how to not forget it...

I would recommend actually generating the password for the user, using
a random sample of words from a word list. This can be done with the
diceware or xkcdpass software, or it could be implemented from scratch
if we do not want the extra dependency.

If entropy is an issue, we can tell the user to enter the results from
actual dice rolls. But after reviewing a [CCC talk about entropy in
the kernel][2], I am actually quite confident that the kernel RNG, in
modern Linux installs, is sufficiently initialized for cryptographic
use.

[2]: https://media.ccc.de/v/32c3-7441-the_plain_simple_reality_of_entropy)

I understand this is a significant change, but I didn't want that idea
to get lost anywhere. I believe that randomly-generated yet memorable
passphrases could significantly improve the security of Debian
installs.

Thank you for your consideration.

A.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

debootstrap_1.0.88_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Feb 2017 23:53:10 +
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.88
Distribution: unstable
Urgency: high
Maintainer: Debian Install System Team 
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 836525
Changes:
 debootstrap (1.0.88) unstable; urgency=high
 .
   [ Sven Joachim ]
   * Strip the arch-qualifier (Closes: #836525)
Checksums-Sha1:
 b778435007242c30f6169f02559186e4cc97 1777 debootstrap_1.0.88.dsc
 d23bbc304b782bca7fa33f1fe05497cf18a1c596 65590 debootstrap_1.0.88.tar.gz
 c4fc027eeb4cdf92ef610da8303c9939e5b80be9 18928 debootstrap-udeb_1.0.88_all.udeb
 3d7cc69f52adc9cbd011d6112c299f3e0a87a143 66230 debootstrap_1.0.88_all.deb
 ae94c30baefc8f4ea97f8e5b1528998f80b80436 5606 
debootstrap_1.0.88_amd64.buildinfo
Checksums-Sha256:
 f406a1accdb266d97199fa58637a2fd51c8a8c26aa29add35db05832662c56b1 1777 
debootstrap_1.0.88.dsc
 a08332bb288223a7afca125b5d5946dcfa36720f36138fee3fea299aad80d2f8 65590 
debootstrap_1.0.88.tar.gz
 debe35cf7fc1477bffbab47b60b65ca2248ac8d571cf791f16635ecf152f4ab8 18928 
debootstrap-udeb_1.0.88_all.udeb
 4549c01f84a720bc01a31d89f7dd747ae3156de004fed3a6507af348458c1238 66230 
debootstrap_1.0.88_all.deb
 848d6542bf9f03aa45ac5b98682e3ffea090196c7d19edccc22484cea506ee7f 5606 
debootstrap_1.0.88_amd64.buildinfo
Files:
 f451934a9905f3128ceb0239d92df2ce 1777 admin extra debootstrap_1.0.88.dsc
 a822abc3703ac0745e5f130fe4da1b28 65590 admin extra debootstrap_1.0.88.tar.gz
 42558b8184ff76f2c274755a3bb345a2 18928 debian-installer extra 
debootstrap-udeb_1.0.88_all.udeb
 d332257fea1f892a6ba7e1843d426ee9 66230 admin extra debootstrap_1.0.88_all.deb
 91f88cfd858de00d30f08181f41eb725 5606 admin extra 
debootstrap_1.0.88_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYm7IkAAoJEFh5eVc0QmhOVE4QAJvz3hivKOGuTLbMZ4ETW6qd
Fm1KclFEjkPR+ADm8paX8cWonR34sunm/MVnZcYu3QBh9cH3rTrguSZj0hMZTrZ3
7/TmHUIwKItdr/Iyg2tFo9Fv9zdFOCBzcNqIACTT7sJqyzEBRBiMzZKGoT03jXFg
7tcI5yw0APEoAAkAqZh0G9URrcYTyIgjHW8FclAnq+lSrcLnRiCCjyf3t1Ot74u4
yJf+8/0zS9fb//xtZJwFyhyGmiSwWCCT3Ci6D63XZ7Lomkwj+c01/glKzGsVWLUp
dJyrNB6OQFgWxwGvVfbr9/o4aMBwqio2Zwd3nKTYQoIjsaC0EY0vTUmwHnVaTNx5
ZlJldc7adjsd9PV86AQC399MpZGuxDJ46xVM9QEIdNRA6Zoo0/RVma6PZD5J7KLp
J5rRj5jUmF/wsVQSFWcVIOrlkyLTWp3ym0/OUtClTASYtcHgsGsEJJ+ht+aRyHqb
gWZQadCxa8004tJt8cFoktJQtNsZfeDwpPXsLNW+qC/CTs3+IQGodA2ypKFSFpwn
aD9pOC0SxO1mpi8I2BApT/97BcRgStS5u39i8F8gMZQXqC3H4i441SsGglJ9V3eB
hofoCnDcDcJ1mhcQ2Xngqq4S0x0m8ZyYrU0EdMzoPDxry3NkNWAoiIM2ya6jAonr
GxgwGmzNoD9W12cnux79
=KVOE
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of debootstrap_1.0.88_amd64.changes

[Debian FTP Masters]

debootstrap_1.0.88_amd64.changes uploaded successfully to localhost
along with the files:
  debootstrap_1.0.88.dsc
  debootstrap_1.0.88.tar.gz
  debootstrap-udeb_1.0.88_all.udeb
  debootstrap_1.0.88_all.deb
  debootstrap_1.0.88_amd64.buildinfo

Greetings,

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

Bug#836525: marked as done (debootstrap: doesn't support arch-qualified dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 00:18:29 +
with message-id 
and subject line Bug#836525: fixed in debootstrap 1.0.88
has caused the Debian Bug report #836525,
regarding debootstrap: doesn't support arch-qualified dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
836525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.24-1
Severity: important

The fix for bug #834706 has the side effect that libc6-dev now depends
on linux-libc-dev:$arch :

,
| $ apt-cache show libc6-dev | grep ^Depends
| Depends: libc6 (= 2.24-1), libc-dev-bin (= 2.24-1), linux-libc-dev:i386 (>= 
4.6.4-1)
`

While dpkg and apt obviously don't have a problem with that, debootstrap
cannot cope with it, and "debootstrap --variant=buildd" fails to even
download linux-libc-dev.  See the attached log.

Please clone/reassign to debootstrap as you see fit, but in any case it
would be nice to remove the extraneous arch qualification in the
dependency.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 4.7.2-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libc6-dev depends on:
ii  libc-dev-bin 2.24-1
ii  libc62.24-1
pn  linux-libc-dev:i386  

libc6-dev recommends no packages.

Versions of packages libc6-dev suggests:
ii  glibc-doc 2.24-1
ii  manpages-dev  4.07-1

-- no debconf information

gpgv: Signature made Sat Sep  3 05:35:17 2016 CEST
gpgv:using RSA key 8B48AD6246925553
gpgv: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy) 
"
gpgv: Signature made Sat Sep  3 05:35:17 2016 CEST
gpgv:using RSA key 7638D0442B90D010
gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) 
"
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg':
 missing description
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg':
 missing architecture
Selecting previously unselected package base-passwd.
(Reading database ... 0 files and directories currently installed.)
Preparing to unpack .../base-passwd_3.5.40_i386.deb ...
Unpacking base-passwd (3.5.40) ...
dpkg: base-passwd: dependency problems, but configuring anyway as you requested:
 base-passwd depends on libc6 (>= 2.8); however:
  Package libc6 is not installed.
 base-passwd depends on libdebconfclient0 (>= 0.145); however:
  Package libdebconfclient0 is not installed.

Setting up base-passwd (3.5.40) ...
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 24 package 'dpkg':
 missing description
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 24 package 'dpkg':
 missing architecture
Selecting previously unselected package base-files.
dpkg: regarding .../base-files_9.6_i386.deb containing base-files, 
pre-dependency problem:
 base-files pre-depends on awk
  awk is not installed.

dpkg: warning: ignoring pre-dependency problem!
(Reading database ... 41 files and directories currently installed.)
Preparing to unpack .../base-files_9.6_i386.deb ...
Unpacking base-files (9.6) ...
dpkg: base-files: dependency problems, but configuring anyway as you requested:
 base-files depends on awk; however:
  Package awk is not installed.

Setting up base-files (9.6) ...
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 50 package 'dpkg':
 missing description
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 50 package 'dpkg':
 missing architecture
dpkg: regarding .../archives/dpkg_1.18.10_i386.deb containing dpkg, 
pre-dependency problem:
 dpkg pre-depends on libbz2-1.0
  libbz2-1.0 is not installed.

dpkg: warning: ignoring pre-dependency problem!
dpkg: regarding .../archives/dpkg_1.18.10_i386.deb containing dpkg, 
pre-dependency problem:
 dpkg pre-depends on libc6 (>= 2.11)
  libc6 is not installed.

dpkg: warning: ignoring pre-dependency problem!
dpkg: regarding .../archives/dpkg_1.18.10_i386.deb containing dpkg, 
pre-dependency problem:
 dpkg pre-depends on liblzma5 (>= 5.1.1alpha+20120614)
  liblzma5 is not installed.

dpkg: warning: ignoring pre-dependency problem!
dpkg: regarding .../archives/dpkg_1.18.10_i386.deb containing dpkg, 
pre-dependency problem:
 dpkg 

Bug#697488: marked as done (debootstrap: wrong default mirror)

[Debian Bug Tracking System]

Your message dated Wed, 8 Feb 2017 23:51:43 +
with message-id <20170208235143.ga...@einval.com>
and subject line Closing old bug
has caused the Debian Bug report #697488,
regarding debootstrap: wrong default mirror
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
697488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.44
Severity: normal

Hello,

I tried to bootstrap a chroot and in the chroot that sources.list is
pre-filled with the US mirror.

Since the recommended mirrror is http://http.debian.net the default
should perhaps reflect this.

Thanks

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 
'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 
'precise')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages debootstrap depends on:
ii  wget  1.13.4-3

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2012.4
ii  gnupg   1.4.12-6

debootstrap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: debootstrap
Version: 1.0.85

This has been fixed for a while already.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...--- End Message ---

Re: Bug#854524: unblock: linux/4.9.6-3

[Cyril Brulebois]

Jonathan Wiltshire  (2017-02-08):
> Control: tag -1 moreinfo
> 
> On Wed, Feb 08, 2017 at 01:46:50AM +, Ben Hutchings wrote:
> > Please unblock package linux
> > 
> > This includes many important bug fixes, including security fixes, and
> > new hardware support.  It also disables logfs, which is being removed
> > in Linux 4.10 and therefore would not be supportable in stretch.
> > 
> > The debdiff would be too large for you to review, unfortunately.
> > Instead, here are the changelog entries:
> 
> Likely to take on trust, but needs a d-i ack either way.

Fine with me, thanks.


KiBi.


signature.asc
Description: Digital signature

Re: console-setup upload?

[Anton Zinoviev]

On Wed, Feb 08, 2017 at 06:53:05AM +0100, Christian PERRIER wrote:
> 
> Ideally in this pre-release time, I shouldn't be uploading as is. May
> I suggest that the relevant commit is moved to a "post-release" branch
> or are there advices that this change should be in the released
> package.
> 
> Seeking for advice, then.

Personally, I would love to receive some advice about this too...

Postponing would be ok if only #817232 wasn't with grave severity...

> -if [ -x "/etc/init.d/keyboard-setup" ]; then
> -update-rc.d keyboard-setup remove >/dev/null
> -fi
> -if [ -x "/etc/init.d/console-setup" ]; then
> -update-rc.d console-setup remove >/dev/null
> -fi
> -dpkg-maintscript-helper rm_conffile /etc/init.d/keyboard-setup 1.138~ -- "$@"
> -dpkg-maintscript-helper rm_conffile /etc/init.d/console-setup 1.138~ -- "$@"
> +for file in keyboard-setup console-setup; do
> +dpkg-maintscript-helper rm_conffile /etc/init.d/$file 1.138~ -- "$@"
> +if [ -x /etc/init.d/$file ]; then
> +update-rc.d $file remove >/dev/null
> +fi
> +done

I took this code unchanged from a comment in BTS.  In order to make it 
easier to track the changes, I've just modified it (in an equivalent 
way).  The new diff is the following:

diff --git a/debian/keyboard-configuration.preinst 
b/debian/keyboard-configuration.preinst
index 9bf83a7..66571f4 100644
--- a/debian/keyboard-configuration.preinst
+++ b/debian/keyboard-configuration.preinst
@@ -2,13 +2,13 @@
 
 set -e
 
+dpkg-maintscript-helper rm_conffile /etc/init.d/keyboard-setup 1.138~ -- "$@"
+dpkg-maintscript-helper rm_conffile /etc/init.d/console-setup 1.138~ -- "$@"
 if [ -x "/etc/init.d/keyboard-setup" ]; then
 update-rc.d keyboard-setup remove >/dev/null
 fi
 if [ -x "/etc/init.d/console-setup" ]; then
 update-rc.d console-setup remove >/dev/null
 fi
-dpkg-maintscript-helper rm_conffile /etc/init.d/keyboard-setup 1.138~ -- "$@"
-dpkg-maintscript-helper rm_conffile /etc/init.d/console-setup 1.138~ -- "$@"
 
 #DEBHELPER#

In this way the change becomes obvious --- only the order of execution 
of the commands is changed. Rationale: according to update-rc.d(8) "The 
script must have been deleted already.  If the script is still present 
then update-rc.d aborts with an error message."  This, indeed, means 
that update-rc.d has to be run before dpkg-maintscript-helper rm_conffile.

Anton Zinoviev

Bug#834942: debian-installer: Can't boot via serial console in qemu

[Samuel Thibault]

Hello,

Simon Ruderich, on Mon 06 Feb 2017 14:12:16 +0100, wrote:
> Then please consider this a feature request. It would be awesome
> if the installer could be booted over serial without needing any
> graphical output.

Well, the problem is that d-i can't assume what is plugged on the
serial port, and what bad things could happen by emitting output
there.  It could even brick some piece of hardware which happens to be
plugged there.  This could for instance be very problematic for braille
devices...

Samuel

Bug#854588: debian-installer: recognize arrow keys as esc in serial console

[Samuel Thibault]

Hello,

YunQiang Su, on Wed 08 Feb 2017 21:51:45 +0800, wrote:
> On Wed, Feb 8, 2017 at 9:35 PM, Samuel Thibault  wrote:
> > YunQiang Su, on Wed 08 Feb 2017 21:20:44 +0800, wrote:
> >> When append an console option like:
> >>   console=ttyS0,115200n8
> >> and close vga by
> >>   vga=off
> >>
> >> We can redirect the installer output with serial cable.
> >> So we can see the installer interface with minicom or SecureCRT.
> >>
> >> For most keys, it seems works well, while when press
> >> arrow keys "up"/"down"/"left"/"right",
> >> they are recognized as 'ESC' key.
>
> The guide says that the default term of installer is vt102,
> and I also used vt102.
> So they are the same.

Ok.  I'm then surprised that you have any issue.  I have just tried
this:

€ kvm -cdrom debian-stretch-DI-rc2-amd64-netinst.iso -serial pty -m 1G   
char device redirected to /dev/pts/8 (label serial0)

and in another terminal

€ minicom -D /dev/pts/8

and things work just fine, arrows work as expected, minicom being
configured in VT102 mode.

Samuel

Re: Bug#852215: FTBFS on non-release architectures

[Steven Chamberlain]

Cyril Brulebois wrote:
> [...] kfreebsd-* (which currently FTBFS anyway…).

Regarding that, is it okay I commit to sid this specific change for
kfreebsd-amd64:

--- a/build/Makefile
+++ b/build/Makefile
@@ -149,7 +149,7 @@ ifeq ($(DEB_HOST_ARCH),kfreebsd-i386)
 MFSROOT_LIMIT := 42m
 else ifeq ($(DEB_HOST_ARCH),kfreebsd-amd64)
 # See Bug#783773 for derivation.
-MFSROOT_LIMIT := 74m
+MFSROOT_LIMIT := 78m
 endif
 
 define mkfs.ufs1

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Re: Bug#854524: unblock: linux/4.9.6-3

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Wed, Feb 08, 2017 at 01:46:50AM +, Ben Hutchings wrote:
> Please unblock package linux
> 
> This includes many important bug fixes, including security fixes, and
> new hardware support.  It also disables logfs, which is being removed
> in Linux 4.10 and therefore would not be supportable in stretch.
> 
> The debdiff would be too large for you to review, unfortunately.
> Instead, here are the changelog entries:

Likely to take on trust, but needs a d-i ack either way.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Re: Bug#853809: unblock: e2fsprogs/1.43.4-2

[Theodore Ts'o]

On Fri, Feb 03, 2017 at 10:34:09PM +0100, Emilio Pozuelo Monfort wrote:
> 
> This seems fine to me, unblocked. Cc'ing debian-boot@/Cyril for the udeb 
> unblock.
>

Hi, I've since found a regression that I would like to fix via a
cherry pick from upstream.  The e2fsprogs/1.43.4-2 package hasn't
transitioned into testing yet (it will in 3 more days).

Enclosed please find the source debdiff.  Would you prefer that I wait
for 1.43.4-2 to transition into testing, and then upload 1.43.4-3 and
then file a new unblock request?

Many thanks!!

- Ted

dpkg-source: warning: extracting unsigned source package 
(/build/debian/e2fsprogs_1.43.4-2.dsc)
dpkg-source: warning: extracting unsigned source package 
(/build/jessie/e2fsprogs_1.43.4-3.dsc)
diff -Nru e2fsprogs-1.43.4/debian/changelog e2fsprogs-1.43.4/debian/changelog
--- e2fsprogs-1.43.4/debian/changelog   2017-01-31 19:54:55.0 -0500
+++ e2fsprogs-1.43.4/debian/changelog   2017-02-05 20:46:55.0 -0500
@@ -1,3 +1,10 @@
+e2fsprogs (1.43.4-3) UNRELEASED; urgency=medium
+
+  * Fix tune2fs regression introduced in 1.43.4 --- enabling additional
+quota types has become a no-op.
+
+ -- Theodore Y. Ts'o   Sun, 05 Feb 2017 20:46:55 -0500
+
 e2fsprogs (1.43.4-2) unstable; urgency=medium
 
   * Re-enable metadata_csum for Debian (which was accidentally disabled
diff -Nru e2fsprogs-1.43.4/debian/patches/series 
e2fsprogs-1.43.4/debian/patches/series
--- e2fsprogs-1.43.4/debian/patches/series  2017-01-31 19:54:55.0 
-0500
+++ e2fsprogs-1.43.4/debian/patches/series  2017-02-05 20:46:55.0 
-0500
@@ -1,2 +1,3 @@
 e2fsprogs-1.43.4-release-fixup
 enable-metadata_csum-by-default
+tune2fs-fix-quota-enablement-regression
diff -Nru 
e2fsprogs-1.43.4/debian/patches/tune2fs-fix-quota-enablement-regression 
e2fsprogs-1.43.4/debian/patches/tune2fs-fix-quota-enablement-regression
--- e2fsprogs-1.43.4/debian/patches/tune2fs-fix-quota-enablement-regression 
1969-12-31 19:00:00.0 -0500
+++ e2fsprogs-1.43.4/debian/patches/tune2fs-fix-quota-enablement-regression 
2017-02-05 20:46:55.0 -0500
@@ -0,0 +1,71 @@
+From: Eric Whitney 
+Description: tune2fs: fix quota enablement regression
+ Commit 5c2a665afa (Avoid dereferencing beyond allocated memory in quota
+ handling) induced a quota enablement regression in tune2fs.  Attempts
+ to enable a particular quota type (tune2fs -O project , for
+ example) set the appropriate feature flag in the superblock but the
+ quota file for the type is not initialized.
+ . 
+ The regression prevents the current version of xfstests from running
+ generic/383, 384, 385, and 386 (all project quota tests) with e2fsprogs
+ 1.43.4.  These tests exit with the message "Installed kernel does not
+ support project quotas", but the actual problem is that the project
+ quota file is not present.
+Origin: upstream, commit: 5f82cc95b31f87c62f18848142597d094fe966ee
+---
+ misc/tune2fs.c | 20 ++--
+ 1 file changed, 10 insertions(+), 10 deletions(-)
+
+diff --git a/misc/tune2fs.c b/misc/tune2fs.c
+index 62395776..f1bad606 100644
+--- a/misc/tune2fs.c
 b/misc/tune2fs.c
+@@ -1483,7 +1483,7 @@ static void handle_quota_options(ext2_filsys fs)
+   quota_ctx_t qctx;
+   ext2_ino_t qf_ino;
+   enum quota_type qtype;
+-  int enable = 0;
++  unsigned int qtype_bits = 0;
+ 
+   for (qtype = 0 ; qtype < MAXQUOTAS; qtype++)
+   if (quota_enable[qtype] != 0)
+@@ -1492,19 +1492,19 @@ static void handle_quota_options(ext2_filsys fs)
+   /* Nothing to do. */
+   return;
+ 
+-  retval = quota_init_context(, fs, 0);
++  for (qtype = 0; qtype < MAXQUOTAS; qtype++) {
++  if (quota_enable[qtype] == QOPT_ENABLE)
++  qtype_bits |= 1 << qtype;
++  }
++
++  retval = quota_init_context(, fs, qtype_bits);
+   if (retval) {
+   com_err(program_name, retval,
+   _("while initializing quota context in support 
library"));
+   exit(1);
+   }
+-  for (qtype = 0 ; qtype < MAXQUOTAS; qtype++) {
+-  if (quota_enable[qtype] == QOPT_ENABLE) {
+-  enable = 1;
+-  break;
+-  }
+-  }
+-  if (enable)
++
++  if (qtype_bits)
+   quota_compute_usage(qctx);
+ 
+   for (qtype = 0 ; qtype < MAXQUOTAS; qtype++) {
+@@ -1540,7 +1540,7 @@ static void handle_quota_options(ext2_filsys fs)
+ 
+   quota_release_context();
+ 
+-  if (enable) {
++  if (qtype_bits) {
+   ext2fs_set_feature_quota(fs->super);
+   ext2fs_mark_super_dirty(fs);
+   } else {
+-- 
+2.11.0.rc0.7.gbe5a750
+

Re: Multibboot vanishes swap UUID

[Lennart Sorensen]

On Wed, Feb 08, 2017 at 04:18:32PM +0100, foo fighter wrote:
> 
> Hi,
> 
> 
> 
> I have an issue with Debian multiboot environments which 
> reuse SWAP-partitions. As a default option, each installation 
> formats the SWAP partition (if SWAP partitions are used) as far 
> as I understand. This changes the UUID of the SWAP partition(s). In 
> /etc/fstab, the UUID of the SWAP partitions is referenced as a constant. In 
> other existing installations, the old UUID of the SWAP partition (overwritten 
> by the new installation) is no valid or found during boot (systemd 
> timeout).
> 
> 
> 
> Shouldnt we preserve a UUID of an existing 
> SWAP-partition?
> 
> 
> Distro: Debian stretch
> 
> 
> Any ideas?

Don't format swap if you want to keep the UUID.

Of course reusing swap would be a very bad idea if you ever tried to
use suspend to disk.

Personally I don't understand wanting more than one system installed,
since that's the one I use.  What would I use another system for?
Experiments and testing I do in chroots or virtual machines.

-- 
Len Sorensen

Multibboot vanishes swap UUID

[foo fighter]

Hi,

 

I have an issue with Debian multiboot environments which reuse SWAP-partitions. As a default option, each installation "formats" the SWAP partition (if SWAP partitions are used) as far as I understand. This changes the UUID of the SWAP partition(s). In /etc/fstab, the UUID of the SWAP partitions is referenced as a constant. In other existing installations, the old UUID of the SWAP partition (overwritten by the new installation) is no valid or found during boot (systemd timeout).

 

Shouldn't we preserve a UUID of an existing SWAP-partition?


Distro: Debian stretch


Any ideas?

 

Yours lopiuh

Bug#854588: debian-installer: recognize arrow keys as esc in serial console

[YunQiang Su]

On Wed, Feb 8, 2017 at 9:35 PM, Samuel Thibault  wrote:
> Hello,
>
> YunQiang Su, on Wed 08 Feb 2017 21:20:44 +0800, wrote:
>> When append an console option like:
>>   console=ttyS0,115200n8
>> and close vga by
>>   vga=off
>>
>> We can redirect the installer output with serial cable.
>> So we can see the installer interface with minicom or SecureCRT.
>>
>> For most keys, it seems works well, while when press
>> arrow keys "up"/"down"/"left"/"right",
>> they are recognized as 'ESC' key.
>
> As described in the manual, you also need to make sure that you set the
> TERM variable too, otherwise there is little probability that it makes
> between the terminal you are using and what d-i uses.
>
> Please read the manual, really.

The guide says that the default term of installer is vt102,
and I also used vt102.
So they are the same.

>
> Samuel



-- 
YunQiang Su

Bug#854588: debian-installer: recognize arrow keys as esc in serial console

[Samuel Thibault]

Hello,

YunQiang Su, on Wed 08 Feb 2017 21:20:44 +0800, wrote:
> When append an console option like:
>   console=ttyS0,115200n8
> and close vga by
>   vga=off
> 
> We can redirect the installer output with serial cable.
> So we can see the installer interface with minicom or SecureCRT.
> 
> For most keys, it seems works well, while when press
> arrow keys "up"/"down"/"left"/"right",
> they are recognized as 'ESC' key.

As described in the manual, you also need to make sure that you set the
TERM variable too, otherwise there is little probability that it makes
between the terminal you are using and what d-i uses.

Please read the manual, really.

Samuel

Bug#854588: debian-installer: recognize arrow keys as esc in serial console

[YunQiang Su]

Package: src:debian-installer

When append an console option like:
  console=ttyS0,115200n8
and close vga by
  vga=off

We can redirect the installer output with serial cable.
So we can see the installer interface with minicom or SecureCRT.

For most keys, it seems works well, while when press
arrow keys "up"/"down"/"left"/"right",
they are recognized as 'ESC' key.

I also test it in PMON2000, it seems not having this problem.
aka arrow keys works well.


-- 
YunQiang Su

Bug#854565: disk-detect looks for obsolete name

[Allan Jacobsen]

Package: installation-reports

Boot method: PXE (network install)
Image version: Stretch RC2
Date: 20170208

Machine: Cisco UCSB-B200-M4
Processor: Intel Xeon E5-2660
Memory: 32Gbyte
Partitions: Not found, that is the problem.

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [E]

I am making a PXE install on multipath disks, and "multipath -ll"
detects the disk, but disk-detect looks for mpath0-9 name instead of
mpatha-z, so no disks is found.

The name change was in 2008, so it is time for an update.

Best regards

Allan Jacobsen

Bug#854553: debian-installer: please add fb-modules to loongson-3 installer

[YunQiang Su]

Package: src:debian-installer
Version: 20170127

Please add
 pkg-lists/netboot/mips{64,}el/loongson-3.cfg
to debian-installer.
The content of them should be:
 fb-modules-${kernel:Version}

As most of Loongson machines uses radeon video card,
without them, the installer cannot show anything on screen.

-- 
YunQiang Su