Bug#951387: Please accept https://salsa.debian.org/installer-team/console-setup/merge_requests/3
Hi Adrian, John Paul Adrian Glaubitz writes: > On 3/9/20 10:33 PM, Nicholas D Steeves wrote: >>> Hi, why such simple patch isn't accepted - 3 weeks already passed... >>> >> >> Don't feel bad! Here's one I've been waiting three years for (tested >> with custom install media in a VM): >> >> >> https://salsa.debian.org/installer-team/partman-btrfs/-/merge_requests/1/commits > > I can have a look tomorrow. > Thank you! Best, Nicholas signature.asc Description: PGP signature
Bug#953588: debootstrap: fails for mirrors without translations
Control: block 953592 by -1 On Tue, 10 Mar 2020 23:04:03 +0100 Johannes 'josch' Schauer wrote: > recent debootstrap fails silently if the given mirror does not contain > translations. this breaks the autopkgtest of mmdebstrap, thus adding the blocking bug. It seems that even creating an APT_CONFIG with ' Acquire::Languages "none";' in it gets ignored. Maybe the environment is somehow cleaned before debootstrap calls apt-get? signature.asc Description: signature
Processed: Re: debootstrap: fails for mirrors without translations
Processing control commands: > block 953592 by -1 Bug #953592 [mmdebstrap] mmdebstrap: autopkgtest fails 953592 was not blocked by any bugs. 953592 was not blocking any bugs. Added blocking bug(s) of 953592: 953588 -- 953588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953588 953592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953594: debootstrap: not anymore possible to do stable debootstrap from snapshot.d.o
Package: debootstrap Version: 1.0.121 Severity: normal Hi, when I debootstrap a stable release from snapshot.d.o, the security mirror gets added to the sources.list and an upgrade is performed. There is no option to prevent this from happening. This means that I cannot anymore create a chroot of a specific stable snapshot with debootstrap because debootstrap will enforce an upgrade from the current security mirror. I think it should be possible to use debootstrap for this purpose. Thanks! cheers, josch -- System Information: Debian Release: bullseye/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.20.1-1.1 Versions of packages debootstrap recommends: ii arch-test 0.15-2 ii debian-archive-keyring 2019.1 ii gnupg 2.2.19-2 Versions of packages debootstrap suggests: pn squid-deb-proxy-client ii ubuntu-keyring [ubuntu-archive-keyring] 2018.09.18.1-5 -- no debconf information
Bug#953593: debootstrap: --no-check-gpg and --keyring options not working with Debian stable chroots
Package: debootstrap Version: 1.0.121 Severity: normal Hi, the --keyring and --no-check-gpg options do not seem to be passed on to "apt-get update". When I try to debootstrap with these options I get in my debootstrap.log: Ign:1 http://127.0.0.1:8000/debian stable InRelease Hit:2 http://127.0.0.1:8000/debian stable Release Ign:3 http://127.0.0.1:8000/debian stable Release.gpg Get:4 http://security.debian.org/debian-security stable/updates InRelease [65.4 kB] Get:5 http://security.debian.org/debian-security stable/updates/main amd64 Packages [182 kB] Get:6 http://security.debian.org/debian-security stable/updates/main Translation-en [96.0 kB] Reading package lists... E: The repository 'http://127.0.0.1:8000/debian stable Release' is not signed. The rest of debootstrap before worked fine because I used --no-check-gpg but it fails at this step. Same with the --keyring option. Thanks! cheers, josch -- System Information: Debian Release: bullseye/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.20.1-1.1 Versions of packages debootstrap recommends: ii arch-test 0.15-2 ii debian-archive-keyring 2019.1 ii gnupg 2.2.19-2 Versions of packages debootstrap suggests: pn squid-deb-proxy-client ii ubuntu-keyring [ubuntu-archive-keyring] 2018.09.18.1-5 -- no debconf information
Bug#951709: /boot should get a bigger share of disk in default installation
On Tue, Mar 10, 2020 at 09:50:07PM +0100, Holger Wansing wrote: > Hi, > > Ben Hutchings wrote: > > On Thu, 2020-02-20 at 18:50 +0530, Pirate Praveen wrote: > > > Package: debian-installer > > > Version: 20190702+deb10u3 > > > Severity: important > > > > > > With initrd around 60+ MBs, 236 MB /boot in a 300 GB hard disk can hold > > > only 2 versions of the kernels at the same time. When installing a 3rd > > > kernel /boot gets filled up. I think it should be able to store at > > > least 3 kernels and ideally 4 or even more. > > > > > > The paritions were created automatically with just /home in a separate > > > partition with lvm by debian buster installer. > > > > I agree; the default size of /boot is now too small. I think we should > > normally allocate at least 500 MB to it. > > This has just been addressed; see > https://salsa.debian.org/installer-team/partman-auto/-/commit/cf6b2d152b08b6c78da6a6f7ca26a99bdadfdfce > Not quite. If Ben says we need at least 500M, then we'll have to adjust further, as that commit uses 512M as a maximum. For comparison Ubuntu's partman-auto sets the min at 512M and max at 768M. Do people feel that's where we should go? Cheers, Julien
Bug#953588: debootstrap: fails for mirrors without translations
Package: debootstrap Version: 1.0.121 Severity: normal Hi, recent debootstrap fails silently if the given mirror does not contain translations. From debootstrap.log: Ign:1 http://127.0.0.1/debian stable InRelease Hit:2 http://127.0.0.1/debian stable Release Ign:4 http://127.0.0.1/debian stable/main Translation-en Ign:4 http://127.0.0.1/debian stable/main Translation-en Ign:4 http://127.0.0.1/debian stable/main Translation-en Err:4 http://127.0.0.1/debian stable/main Translation-en 404 File not found [IP: 127.0.0.1 80] Get:5 http://security-cdn.debian.org/debian-security stable/updates InRelease [65.4 kB] Get:6 http://security-cdn.debian.org/debian-security stable/updates/main amd64 Packages [182 kB] Get:7 http://security-cdn.debian.org/debian-security stable/updates/main Translation-en [96.0 kB] Fetched 343 kB in 1s (501 kB/s) Reading package lists... E: Failed to fetch http://127.0.0.1/debian/dists/stable/main/i18n/Translation-en 404 File not found [IP: 127.0.0.1 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Another problem is, that this happens silently after the message "I: Base system installed successfully." I noticed the problem because my shell is printing the exit status of the last command but other users might just think that debootstrap finished successfully. There should definitely be some kind of error message when apt fails. Best including either the reason or a pointer to debootstrap.log which is currently not documented in the man page. Thanks! cheers, josch -- System Information: Debian Release: bullseye/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.20.1-1.1 Versions of packages debootstrap recommends: ii arch-test 0.15-2 ii debian-archive-keyring 2019.1 ii gnupg 2.2.19-2 Versions of packages debootstrap suggests: pn squid-deb-proxy-client ii ubuntu-keyring [ubuntu-archive-keyring] 2018.09.18.1-5 -- debconf-show failed
Bug#951709: /boot should get a bigger share of disk in default installation
Hi, Ben Hutchings wrote: > On Thu, 2020-02-20 at 18:50 +0530, Pirate Praveen wrote: > > Package: debian-installer > > Version: 20190702+deb10u3 > > Severity: important > > > > With initrd around 60+ MBs, 236 MB /boot in a 300 GB hard disk can hold > > only 2 versions of the kernels at the same time. When installing a 3rd > > kernel /boot gets filled up. I think it should be able to store at > > least 3 kernels and ideally 4 or even more. > > > > The paritions were created automatically with just /home in a separate > > partition with lvm by debian buster installer. > > I agree; the default size of /boot is now too small. I think we should > normally allocate at least 500 MB to it. This has just been addressed; see https://salsa.debian.org/installer-team/partman-auto/-/commit/cf6b2d152b08b6c78da6a6f7ca26a99bdadfdfce I will adjust the changelog to close this bug as well. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: Bug#950344 marked as pending in partman-auto
Processing control commands: > tag -1 pending Bug #950344 [partman-auto] debian-installer: fails to install on small SSD if the system has lots of RAM Added tag(s) pending. -- 950344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#949651 marked as pending in partman-auto
Processing control commands: > tag -1 pending Bug #949651 [partman-auto] installation-reports: install on lenovo server fails guided partitioning Added tag(s) pending. -- 949651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
debootstrap_1.0.121_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Mar 2020 21:42:03 +0900 Source: debootstrap Architecture: source Version: 1.0.121 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Hideki Yamane Closes: 953404 Changes: debootstrap (1.0.121) unstable; urgency=medium . * Fix "debootstrapping testing and stable results in exit 100", use CODENAME for check properly (Closes: #953404) Checksums-Sha1: 3b182164a264d5bfac9424dc94a2f32aa88e1ad2 1919 debootstrap_1.0.121.dsc dccef8e1d297b93a73ef2710a3e2943e740c407d 77208 debootstrap_1.0.121.tar.gz 8aeaf6e109cd77fcb05bbec2d8e783cc948e4499 5913 debootstrap_1.0.121_amd64.buildinfo Checksums-Sha256: 9f40f8363f30849901fbf2a922c7353adae86a0550ba761c396f984054ca3ea3 1919 debootstrap_1.0.121.dsc c32e0f18c393c1f0ba8fa80768cb3e2669978aef71bd8e5c9aaf9902ba2e9e84 77208 debootstrap_1.0.121.tar.gz d6c6ad7897d19bdb7d3c972b04dd7e8579096a601f3f99bab2958d063644da50 5913 debootstrap_1.0.121_amd64.buildinfo Files: ff32a5ac2dbb96a2427c9bd5092494bc 1919 admin optional debootstrap_1.0.121.dsc 648d19be256effa29d8df027717b3df3 77208 admin optional debootstrap_1.0.121.tar.gz 0909976e95e4c44392e2c3e9282ee220 5913 admin optional debootstrap_1.0.121_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAl5nlxwACgkQXTKNCCqq sUDh9g/+ONayI/NZMKDT2oaA+Ck/rgN812PLpsP/8iFLRF1S6dJrj5+zB5Jcdedh /gft+ZvMSUgoWAAdccvPbWzPerHx/EXMqpYZNOKSbI/NyUv3YCQgkdSrnjfFTNw5 dpyO7nt3ufy6pcGlNBRJJCkIbxHuurgS06xEY+gXyyUV60sjcYwL3UJM3Lih93dY 8evHGhs98/1N9Kvyfnbkq9jx+JvR9QbEjMCMYcRPlQwMBmuXARe+R9j3NpmRxP8j YeleLKQQUosKIEiByf4umvaU3deIv66tiOqQRgFD185kgcoeQ7r5RxFbln3Byta6 ufWjfGQJTeEazmGCobBD2b0lSMfhxrdw6dGT8hm4yndX+6An3SDz44UZdS/9r4x4 7Q9jqwVkadRO19wk90K2RZLVg2xTynYfXr38E2jHbcVlha3WumoWIWYyb3vmpXUz CWlLqukpjvvV2ZS8qQ9nY4lSqL7Efbw1gTg7636mY6LOb/Lve6oQQi5S4PtfaC39 ORtD6uDv9IcYSNZRo43ZwitdvdmDnWNS7Kr6gNChVu6QU8wNEi5D17U6VYOjNlsX /hVbw/Yq5It+qUm6RiCcpjUm2EcWLW1OS6e+y8MDXZ/6wzuTjxKBEKLwWegqR8zG VVgYKFaAM7GqrIPSv6knQhArQbDoOQ29iTJew6NU3PjOH2FoXTw= =VW8P -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of debootstrap_1.0.121_source.changes
debootstrap_1.0.121_source.changes uploaded successfully to localhost along with the files: debootstrap_1.0.121.dsc debootstrap_1.0.121.tar.gz debootstrap_1.0.121_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#953404: marked as done (debootstrapping testing and stable results in exit 100)
Your message dated Tue, 10 Mar 2020 13:49:48 + with message-id and subject line Bug#953404: fixed in debootstrap 1.0.121 has caused the Debian Bug report #953404, regarding debootstrapping testing and stable results in exit 100 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.) -- 953404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debootstrap Version: 1.0.120 Severity: grave Justification: renders package unusable Hi, steps to reproduce: $ sudo debootstrap --variant=minbase stable debian-stable [...] $ echo $? 100 It works for unstable though. Thanks! cheers, josch -- System Information: Debian Release: bullseye/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.20.1-1.1 Versions of packages debootstrap recommends: ii arch-test 0.15-2 ii debian-archive-keyring 2019.1 ii gnupg 2.2.19-2 Versions of packages debootstrap suggests: pn squid-deb-proxy-client ii ubuntu-keyring [ubuntu-archive-keyring] 2018.09.18.1-5 -- no debconf information --- End Message --- --- Begin Message --- Source: debootstrap Source-Version: 1.0.121 Done: Hideki Yamane We believe that the bug you reported is fixed in the latest version of debootstrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane (supplier of updated debootstrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Mar 2020 21:42:03 +0900 Source: debootstrap Architecture: source Version: 1.0.121 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Hideki Yamane Closes: 953404 Changes: debootstrap (1.0.121) unstable; urgency=medium . * Fix "debootstrapping testing and stable results in exit 100", use CODENAME for check properly (Closes: #953404) Checksums-Sha1: 3b182164a264d5bfac9424dc94a2f32aa88e1ad2 1919 debootstrap_1.0.121.dsc dccef8e1d297b93a73ef2710a3e2943e740c407d 77208 debootstrap_1.0.121.tar.gz 8aeaf6e109cd77fcb05bbec2d8e783cc948e4499 5913 debootstrap_1.0.121_amd64.buildinfo Checksums-Sha256: 9f40f8363f30849901fbf2a922c7353adae86a0550ba761c396f984054ca3ea3 1919 debootstrap_1.0.121.dsc c32e0f18c393c1f0ba8fa80768cb3e2669978aef71bd8e5c9aaf9902ba2e9e84 77208 debootstrap_1.0.121.tar.gz d6c6ad7897d19bdb7d3c972b04dd7e8579096a601f3f99bab2958d063644da50 5913 debootstrap_1.0.121_amd64.buildinfo Files: ff32a5ac2dbb96a2427c9bd5092494bc 1919 admin optional debootstrap_1.0.121.dsc 648d19be256effa29d8df027717b3df3 77208 admin optional debootstrap_1.0.121.tar.gz 0909976e95e4c44392e2c3e9282ee220 5913 admin optional debootstrap_1.0.121_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAl5nlxwACgkQXTKNCCqq sUDh9g/+ONayI/NZMKDT2oaA+Ck/rgN812PLpsP/8iFLRF1S6dJrj5+zB5Jcdedh /gft+ZvMSUgoWAAdccvPbWzPerHx/EXMqpYZNOKSbI/NyUv3YCQgkdSrnjfFTNw5 dpyO7nt3ufy6pcGlNBRJJCkIbxHuurgS06xEY+gXyyUV60sjcYwL3UJM3Lih93dY 8evHGhs98/1N9Kvyfnbkq9jx+JvR9QbEjMCMYcRPlQwMBmuXARe+R9j3NpmRxP8j YeleLKQQUosKIEiByf4umvaU3deIv66tiOqQRgFD185kgcoeQ7r5RxFbln3Byta6 ufWjfGQJTeEazmGCobBD2b0lSMfhxrdw6dGT8hm4yndX+6An3SDz44UZdS/9r4x4 7Q9jqwVkadRO19wk90K2RZLVg2xTynYfXr38E2jHbcVlha3WumoWIWYyb3vmpXUz CWlLqukpjvvV2ZS8qQ9nY4lSqL7Efbw1gTg7636mY6LOb/Lve6oQQi5S4PtfaC39 ORtD6uDv9IcYSNZRo43ZwitdvdmDnWNS7Kr6gNChVu6QU8wNEi5D17U6VYOjNlsX /hVbw/Yq5It+qUm6RiCcpjUm2EcWLW1OS6e+y8MDXZ/6wzuTjxKBEKLwWegqR8zG VVgYKFaAM7GqrIPSv6knQhArQbDoOQ29iTJew6NU3PjOH2FoXTw= =VW8P -END PGP SIGNATURE End Message ---
Processed: Bug#953404 marked as pending in debootstrap
Processing control commands: > tag -1 pending Bug #953404 [debootstrap] debootstrapping testing and stable results in exit 100 Added tag(s) pending. -- 953404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953541: installation-reports: Successful install on Lafite Pro 14 (bullseye / non-free firmware)
Package: installation-reports Severity: normal Hi, -- Package-specific info: Boot method: USB stick Image version: bullseye-DI-alpha1 NETINST with firmware 20191130-23:04 Date: Machine: PCSpecialist Lafite Pro 14 (Clevo L141CU chassis) Partitions: Model: ATA ADATA SU800NS38 (scsi) Disk /dev/sda: 512GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSize File system Name Flags 1 1049kB 538MB 537MB fat32 boot, esp 2 538MB 794MB 256MB ext2 3 794MB 512GB 511GB Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/matkustaja--vg-home: 253GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start EndSize File system Flags 1 0.00B 253GB 253GB ext4 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/matkustaja--vg-swap_1: 16.9GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End SizeFile system Flags 1 0.00B 16.9GB 16.9GB linux-swap(v1) Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/matkustaja--vg-root: 30.0GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End SizeFile system Flags 1 0.00B 30.0GB 30.0GB ext4 Model: Linux device-mapper (crypt) (dm) Disk /dev/mapper/sda3_crypt: 511GB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect media: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Worked a treat, thank you :) There are reports of incompatibility with NVME devices with this BIOS and Linux - so I got a non-NVME SSD. Install worked just fine, though the graphical installer couldn't talk to the trackpad, so I used the text installer. Seems to be running a bit on the hot side, so there may be work to be done around power management. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20191129" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux matkustaja 5.3.0-2-amd64 #1 SMP Debian 5.3.9-3 (2019-11-19) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9b41] (rev 02) lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:02f9] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:02ed] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:14.2 RAM memory [0500]: Intel Corporation Device [8086:02ef] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:02e8] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:02ea] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Device [8086:02e0] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: 00:17.0 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] lspci -knn: Subsystem: CLEVO/KAPOK Computer Device [1558:1401] lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel modules: ahci lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:02bd]
Re: Bug#950553: Remove task-print-{server,service}
Le mardi, 10 mars 2020, 08.46:24 h CET Laurent Bigonville a écrit : > On Mon, 03 Feb 2020 14:48:35 +0100 Didier 'OdyX' Raboud > > wrote: > > Hello, > > > > > > If that'd help for transition measures, I'd be happy to add a Provides: > > task-print-service on cups. > > The changelog says that cups is "pulled by the concerned desktop > environments". > > AFAICS, only cinnamon is explicitly pulling cups/cups-daemon, other have > indirect (soft) dependencies against cups. Hmm. KDE pulls cups through a print-manager Recommends. Others have system-config-printer. I don't know what has GNOME. > Could you please open bugs for this for the different desktop? or make > the task-desktop depends on cups directly? My point, when removing the task-print-service tasksel package, was that it is pointing directly to CUPS only, and a confusing select in d-i. But you're right, removing it makes several packages with dangling relations, and I'll file bugs against these. As for the desktop environments, I don't really want to impose on them _new_ dependencies on CUPS; as pulling it or not is really a design/strategy choice. Regards, -- OdyX signature.asc Description: This is a digitally signed message part.
Bug#950553: Remove task-print-{server,service}
On Mon, 03 Feb 2020 14:48:35 +0100 Didier 'OdyX' Raboud wrote: > > Hello, > > If that'd help for transition measures, I'd be happy to add a Provides: > task-print-service on cups. The changelog says that cups is "pulled by the concerned desktop environments". AFAICS, only cinnamon is explicitly pulling cups/cups-daemon, other have indirect (soft) dependencies against cups. Could you please open bugs for this for the different desktop? or make the task-desktop depends on cups directly? Kind regards, Laurent Bigonville
