Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 29 Sep 2019 10:56:48 +0900
Source: debootstrap
Architecture: source
Version: 1.0.116
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Hideki Yamane
Changes:
debootstrap
debootstrap_1.0.116_source.changes uploaded successfully to localhost
along with the files:
debootstrap_1.0.116.dsc
debootstrap_1.0.116.tar.gz
debootstrap_1.0.116_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Hi Nicholas,
thanks for your reply, I really appreciated your constructive approach.
I use Debian since 2007 and I did a lot of installation, I personally
use a FrankenDebian (testing with pinning toward SID and Experimental)
however when I install Debian on other machines I install
Holger Wansing wrote:
> _Description: Failed to copy file from installation media. Retry?
> There was a problem reading data. Please make sure you have inserted the
> installation media correctly. If retrying does not work, you should check
> - the integrity of your installation media.
> +
The root of the problem is that the Debian installer does not install
package cryptsetup-initramfs.
I retried with the guided partioning. Same result.
The generated initramfs does not contain dm-crypt.ko.
Package: debian-installer
Version: 2019-09-23
Severity: important
Dear Maintainer,
I installed from debian-testing-amd64-netinst.iso (bullseye) dated
2019-09-23 on my NVME drive
partition 1: efi
partition 2: boot
partition 3: encrypted volume
On encrypted volume: logical volume group LVM1
Hi,
a longer time ago I intended to make a template change for cdrom-retriever.
There was a user report claiming "The installer tells me to check the integrity
of the installation media. How can I do that?"
because the user was not aware of the corresponding main menu point.
So, now is the time
On Sat, 2019-09-28 at 17:20 +0800, Paul Wise wrote:
> Package: finish-install
> Version: 2.56
> Severity: important
> Tags: security
> Control: found -1 2.81
> Control: found -1 2.100
> Control: found -1 2.101
>
> finish-install creates a random seed in the location used by the
> urandom init
Hi, I am sending this to you guys in a sort of last resort desperation.
As it only relates to Debian as that is my current build environment.
Help Please.
My problem how to build a bootable iso image file (not of Debian)
I have an iso file [for an early version of UNIX (x86_32 code)]. I have
Processing commands for cont...@bugs.debian.org:
> retitle 941300 finish-install: write additional random seed to location for
> systemd systemd-random-seed.service
Bug #941300 [finish-install] finish-install: write random seed to correct
location for chosen init system
Changed Bug title to
Processing control commands:
> found -1 2.81
Bug #941300 [finish-install] finish-install: write random seed to correct
location for chosen init system
Marked as found in versions finish-install/2.81.
> found -1 2.100
Bug #941300 [finish-install] finish-install: write random seed to correct
Package: finish-install
Version: 2.56
Severity: important
Tags: security
Control: found -1 2.81
Control: found -1 2.100
Control: found -1 2.101
finish-install creates a random seed in the location used by the
urandom init script from the initscripts package. On systemd based
systems,
Package: installation-reports
Version: 2.71
Severity: important
Hello,
-- Package-specific info:
Boot method: network
Image version:
Date: 2019-09-28
Machine: QEmu VM
Partitions: N/A
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
14 matches
Mail list logo
