debootstrap_1.0.116_source.changes ACCEPTED into unstable
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 (1.0.116) unstable; urgency=medium . [ Hideki Yamane ] * use salsa-pipeline for CI, instead of custom rule * disalbe unnecessary blhc and test-build-any CI test . [ Philip Hands ] * disable the failing autopkgtest job * provide support for Devuan release names Checksums-Sha1: 374b26de463c0b836f7aade976f45aa4cc586a16 1912 debootstrap_1.0.116.dsc 23893a5c614365ee8bad1d775c8cde8e8300679f 75723 debootstrap_1.0.116.tar.gz e0430a09bbefbdf2436009b79f7a030e50e6dbb9 5869 debootstrap_1.0.116_amd64.buildinfo Checksums-Sha256: baaa13752fde07696a5428b8b00c008d0086cbb9e1072ad551ad7b99b2bc28b1 1912 debootstrap_1.0.116.dsc cb33272d8f21b5cb8b26e9cc29be9d4627786ee53c5b7ec478973aa4273cf019 75723 debootstrap_1.0.116.tar.gz 9b04619ab1581177029b55693ad29d8b8835e9c90fb0c800e8e5096077f60b22 5869 debootstrap_1.0.116_amd64.buildinfo Files: c64d9c1d37ac6ddb56720803bd270214 1912 admin optional debootstrap_1.0.116.dsc 313267c7f40c7b52b2b9b856213cd178 75723 admin optional debootstrap_1.0.116.tar.gz ec33a7f6f66541751f55babe0b54b7df 5869 admin optional debootstrap_1.0.116_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAl2QI7sACgkQXTKNCCqq sUDKpBAAqtNQpBfs6xsP8TnSScpQ4LokEPML4RxACZPYW7cOzNg/rcWeHJc5c7Y3 WcFLWhCz7/VifC1jxU/Toxg8iqeS+aJ7rMmv/9RbM/wGeGTrU9oCiZYmYwjP8gIM uiV8VnKF6Y6kz7OLH+bGPhEuoE/n4juyTU+7yGuOSo5lYsU+Eha75xDEXIvtjCL9 zs2kPIF747xLUCko3VYaaYS6ggJECUkvl8ynD0/m41Mw/ok4T5W43zY9tRAXf5S6 nYhYXOGR7bS/8KoWQjeNFMDJa+QtjjNHC2uIk6b/q27Bq4Zg6TmtzVtq5JS8lDhZ 4npWtD16DXohqR3UnqhgwbAX751bhaLAqxaaLdbWrDxjJnYuOeExFPhofS+nFrKF 5NO5GYxGm2WgzqE1rWsfGTeZqJ+almArsTsfqHwMzzWtTa6zFXXiFj9VkW9GffRy feSAvQkZJnP1bTsUOPOvfvTMFzyVPOkKAHVAnaW4wS9YJoFDEOuqKfrNIJ5Xh2a1 2FOXjzXen3kRTCDNMoW0KxB5GaHY2phcKQmZsCPGpUPYuS22sE2h2Nk3JP+bXpNo I16Q3X05qE9h3m5ZWAYkaliiNg4wzwPRsGCyjbKq4eiM6u3hOBTRiSgggO+MsOhG kHgiMCHqFODR8OsNgR+4xjrQq/U22wd8ybqAliFVaKyNLioGRBo= =9EaW -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of debootstrap_1.0.116_source.changes
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)
Bug#935931: Re: Bug#935931: debian-installer: Reinstalling Debian on a current Debian installation without erasing or fomatting the home folder
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 definitely the current stable available. I have been performing exclusively desktop installations and while I consider the best option separating /home recently I found myself not able to get the right balance between "/", "/home" and "swap". The default "/" assigned is often too small while sometimes I wasted gigabyte never used. The "swap" with the amount of ram available today is always more accessory and with the SSD disk the trend is to reduce its use the most. Eventually I stopped to create a "swap" partition in favor of a "swap-file" (like Raspian e.g.); hence I also stopped to create "/" and "/home" but just "/" and still as LVM; at this point you don't have anymore issue with the space and if you need you can add all the disks you want because it is still a LVM partition. Now the case I am figuring out is the one you didn't separe "/" and "/home" (however the installer is still creating "swap") but you need to reinstall Debian because you screwed it up for some reason. Now a smart installer before to start everything takes its time to check the disk and discovers that you have, along a crypted disk and a LVM group, also a previous version of Debian hence check the users and it asks you if you want keep all the users, just one, etc... and then it reinstalls the system and recovers the setting from the user(s) you selected, without creating a FrankenDebian but just a fresh and **smart** installation. This leads in my opinion in creating a further voice for the Debian install: **the desktop installation**; Standard and Advanced are eventually too generic and do not target properly the desktop cases. If the D-I was properly able to read LUKS and LVM during the installation time, and if was also able to perform a smart installation as described in the paragraph above, a Desktop installation should be: 1. Create an encrypted partition by default (LUKS + LVM); 2. install everything in / ; 3. not create a "swap partition" but a swap-file. I also add that: 4. should deactivate root user by default, which is now considering a best practice; 5. should deactivate the source repos and asking to activate the "contrib" and "non-free" repos (like in Advanced Mode). I don't see any complicated tasks to achieve, others Linux distro already started to move in this direction while other *nix operative systems already do that since a long time. The only issues I see here are the resistance to the changes and the fact that actually the D-I has some issue to recognize the encrypted partitions and if you want reinstall Debian you can't preserve any of the partitions you want because it will consider the encrypted disks as blanks. Best regards, Daniel On 9/28/19 12:01 AM, Nicholas D Steeves wrote: Geert Stappers writes: On Fri, Sep 27, 2019 at 05:19:06PM -0400, Daniel wrote: Holger Wansing wrote: The debian-installer supports similar use case via the "separate partition for /home" approach. to reinstall Debian on top of itself without overwriting the home partition. Yes, that is what Holger is telling. I think Daniel is requesting an option that does something like this: find /install-target -maxdepth 1 | grep -v 'home\|lost+found' | xargs rm -rf Maybe this way isn't robust enough, but active mounts shouldn't have their mount points removed, because rm: cannot remove '/install-target/foo': Device or resource busy BTW, Daniel, you can decruft your system with "apt purge --autoremove foo", which also deletes config in /etc and will notify you if any files remain in /var. One of the greatest strengths of Debian is that unlike other operating systems, smooth upgrades between stable versions are taken seriously...gravely seriously...so one never needs to reinstall. The only things that I've seen that have ever required action are packages that needed manual configuration updates in /etc (equally solvable by apt purge), and obsolete/broken configuration in /home/user (not solved if this feature request is implemented). What problem is this feature request intended to solve? FrankenDebian? https://wiki.debian.org/DontBreakDebian Cheers, Nicholas P.S. apt install installation-birthday :-)
Re: Change template: add hint about the integrity check item in main menu
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 integrity of your installation media (there is an associated entry in > + the main menu for that). Looks okay to me! -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#941319: debian-installer: Volume group 'LVM1' not found
The root of the problem is that the Debian installer does not install package cryptsetup-initramfs.
Bug#941319: debian-installer: Volume group 'LVM1' not found
I retried with the guided partioning. Same result. The generated initramfs does not contain dm-crypt.ko.
Bug#941319: debian-installer: Volume group 'LVM1' not found
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 volume 1: root volume 2: swap volume 3: home Upon booting: Volume group "LVM1" not found Cannot process volume group LVM1 So I am left with an unusable system. Best regards Heinrich
Change template: add hint about the integrity check item in main menu
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 to add such hint to the installer :-) Adding debian-l10n-english to the loop for a template review. Patch is attached. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 diff --git a/debian/cdrom-retriever.templates b/debian/cdrom-retriever.templates index f80bf25..ac64639 100644 --- a/debian/cdrom-retriever.templates +++ b/debian/cdrom-retriever.templates @@ -1,8 +1,9 @@ Template: retriever/cdrom/error Type: boolean Default: true # :sl2: _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 integrity of your installation media (there is an associated entry in + the main menu for that). diff --git a/debian/changelog b/debian/changelog index 049e515..98d16a7 100644 --- a/debian/changelog +++ b/debian/changelog @@ -4,16 +4,18 @@ cdrom-retriever (1.46) UNRELEASED; urgency=medium * Remove Christian Perrier from Uploaders, with many thanks for all his contributions over the years! (Closes: #927542) [ Holger Wansing ] * Rephrase templates, to rename "CD"/"CD-ROM" into "installation media" (and add missing sublevel definition). * Add comment for translators, to keep main menu entry below a 55 columns limit. This updates all po|pot files. + * Change template, to add a hint about the existence of the 'Check the +integrity of installation media' entry in the main menu. -- Holger Wansing Mon, 16 Sep 2019 19:28:21 +0200 cdrom-retriever (1.45) unstable; urgency=medium * Remove duplicated Priority field from load-cdrom package description, to fix lintian tag. * Remove trailing whitespaces from changelog file, to fix lintian tag.
Bug#941300: finish-install: write random seed to correct location for chosen init system
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 script from the initscripts package. On systemd based > systems, systemd-random-seed.service overrides the urandom init script > but uses a different location for its random seed file. Consequently on > first boot of systemd based systems there is no random seed file so the > amount of entropy available is lower. [...] This should improve the randomness of /dev/urandom. However, the last time I checked, the systemd service does not change the kernel's entropy accounting. (And there was a small risk of using the seed twice, which would need to be fixed before changing that.) So this does not help with the problem of slow boots due to the kernel not accounting enough entropy. Ben. -- Ben Hutchings Sturgeon's Law: Ninety percent of everything is crap. signature.asc Description: This is a digitally signed message part
Question about building a full bootable image using (Debian 7)
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 stripped the files into a directory, then copied them (via tar) into my iso build directory, made my modifications I am OK up to that point. My Question is: How do I create a new bootable iso image file from my build directory ready for burning onto a DVD. I tried just burning the build directory tree but did not boot (I suspected as much but did it anyway). I am obviously missing as step maybe tools. target is a 486 bare machine and a P6 machine in both cases without an O/S, what on the DVD will eventually end up on the HD, once the DVD "works". Any help appreciated, and I know this sort of an oddball question. [please CC me directly with your solution, thank you. regards, Dave :-) (Ps not a newbie).
Processed: retitle 941300 to finish-install: write additional random seed to location for systemd systemd-random-seed.service
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 'finish-install: write additional random seed to location for systemd systemd-random-seed.service' from 'finish-install: write random seed to correct location for chosen init system'. > thanks Stopping processing here. Please contact me if you need assistance. -- 941300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: finish-install: write random seed to correct location for chosen init system
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 location for chosen init system Marked as found in versions finish-install/2.100. > found -1 2.101 Bug #941300 [finish-install] finish-install: write random seed to correct location for chosen init system Marked as found in versions finish-install/2.101. -- 941300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#941300: finish-install: write random seed to correct location for chosen init system
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, systemd-random-seed.service overrides the urandom init script but uses a different location for its random seed file. Consequently on first boot of systemd based systems there is no random seed file so the amount of entropy available is lower. /var/lib/urandom/random-seed /var/lib/systemd/random-seed I think finish-install needs to fix this with one of these options: 1. Write the random seed to both locations. This means that when switching init systems you get the old random seed. 2. Write two different random seeds to the two locations. This means that when switching init systems you get the a new random seed that has never been used before, but which was generated during the install. 3. Detect the chosen init system and write the random seed to the location preferred by that init system. This means that when switching init systems the first boot of the new init systems has no random seed. I think probably the second scenario is the best since then there is always a random seed available even when switching init systems and that random seed is never reused. I think this issue should get fixed in stable/oldstable too. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#941299: Unable to boot the Buster installer in qemu/libvirt when using the Virtio graphic card
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 Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: When trying to install debian Buster in qemu using a virtio graphic card, the installer fails to boot. gnome-boxes is setting up the VM with virtio GC by default without a way of changing that means that it's just not working for people using it. -- libvirt config generated by gnome-boxes: debian10-uni 653ca77b-846f-485d-b7ee-cf39bca606cc Debian 10 https://wiki.gnome.org/Apps/Boxes;> installation http://debian.org/debian/10 http://debian.org/debian/10:1 /home/bigon/Tlchargements/debian-10.0.0-amd64-netinst.iso 1048576 1048576 8 hvm /home/bigon/.cache/gnome-boxes/debian10-uni-kernel /home/bigon/.cache/gnome-boxes/debian10-uni-initrd keyboard-configuration/xkb-keymap=be debconf/priority=critical Broadwell-noTSX-IBRS destroy destroy destroy /usr/bin/qemu-system-x86_64
