debian-installer-utils (1.131) [PTS] [DDPO]

NEW: VCS has unreleased changes: 1.132 > 1.131

Git: https://salsa.debian.org/installer-team/debian-installer-utils.git
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: master
Path: debian/changelog
Browser: https://salsa.debian.org/installer-team/debian-installer-utils
Last scan: 2019-06-26 11:03:13+00
Next scan: 2019-06-27 11:20:00+00

Debian changelog in Git:

debian-installer-utils (1.132) UNRELEASED; urgency=medium

  * Remove Christian Perrier from Uploaders, with many thanks for all
    his contributions over the years! (Closes: #927528)

 -- Cyril Brulebois <kibi@debian.org>  Sat, 20 Apr 2019 22:33:43 +0200

This branch is 4 commits ahead of tag 1.131

Git log:

commit 3b4235a52000e490fe9beebab120122098e516d1
Author: Raphaël Hertzog <raphael@offensive-security.com>
Date:   Mon Jun 24 17:47:48 2019 +0200

    Revert "Disable modprobe for commands run via 'in-target'"
    
    This reverts commit 26f9c5f033ceedfd8d6099cdf2d49c1b6776e0e4.
    
    While this change looked like a good idea, as we really don't
    want to have modules randomly loaded from the /target, I haven't
    been able to find a good way to achieve this.
    
    diverting /sbin/modprobe generated broken initrd because the initrd
    are obviously generated from /target. Then I tried to create a
    modprobe configuration file to blacklist all modules but it suffers
    from the same problem... /etc/modprobe.d and /lib/modules.d are
    embedded in the initrd.
    
    Then I thought than /run/modprobe.d would be the perfect solution,
    except that /run is bind-mounted between /run and /target/run and
    doing the change in /target/run would thus also impact
    debian-installer's root environment and I didn't want to risk that.
    
    Setting up a different tmpfs in /target/run and /run would break other
    things because there are packages that rely on /run/udev being
    present.
    
    Thus I'm reverting this change and will apply a work-around only in
    hw-detect instead of offering that "protection" as a standard feature.

commit 26f9c5f033ceedfd8d6099cdf2d49c1b6776e0e4
Author: Raphaël Hertzog <raphael@offensive-security.com>
Date:   Sun Jun 23 15:26:22 2019 +0200

    Disable modprobe for commands run via "in-target"
    
    So that installation of *-dkms packages doesn't load modules in the
    installer kernel. Without this precaution, installing
    virtualbox-guest-dkms crashes the X server currently used by the graphical
    installer.

commit 6d4802763cc8cfce276813278381616927ba8905
Author: Holger Wansing <hwansing@mailbox.org>
Date:   Sun Apr 21 10:25:13 2019 +0200

    Add reference to bugreport

commit e322ee4ddc53b9daa2ef1329744bc273d6f4f11f
Author: Cyril Brulebois <kibi@debian.org>
Date:   Sat Apr 20 22:33:43 2019 +0200

    Remove Christian Perrier from Uploaders.
    
    With many thanks for all his contributions over the years!