Processed (with 1 error): Re: gnome-core should recommend network-manager instead of network-manager-gnome

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1071383 {Done: Jeremy Bícha } [gnome-core] gnome-core 
should recommend network-manager instead of network-manager-gnome
Bug #1077739 {Done: Jeremy Bícha } [gnome-core] Remove 
network-manager-gnome from the recommended list
Bug #1077740 {Done: Jeremy Bícha } [gnome-core] Remove 
network-manager-gnome from the list of dependencies
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions meta-gnome3/1:47~beta+1.
No longer marked as fixed in versions meta-gnome3/1:47~beta+1.
No longer marked as fixed in versions meta-gnome3/1:47~beta+1.
> reassign -1 task-gnome-desktop
Bug #1071383 [gnome-core] gnome-core should recommend network-manager instead 
of network-manager-gnome
Bug #1077739 [gnome-core] Remove network-manager-gnome from the recommended list
Bug #1077740 [gnome-core] Remove network-manager-gnome from the list of 
dependencies
Bug reassigned from package 'gnome-core' to 'task-gnome-desktop'.
Bug reassigned from package 'gnome-core' to 'task-gnome-desktop'.
Bug reassigned from package 'gnome-core' to 'task-gnome-desktop'.
No longer marked as found in versions meta-gnome3/1:43+1.
No longer marked as found in versions meta-gnome3/1:43+1.
No longer marked as found in versions meta-gnome3/1:43+1.
Ignoring request to alter fixed versions of bug #1071383 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1077739 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1077740 to the same values 
previously set
> fixed gnome-core/1:47~beta+1
Unknown command or malformed arguments to command.

> forwarded -1 
> https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31
Bug #1071383 [task-gnome-desktop] gnome-core should recommend network-manager 
instead of network-manager-gnome
Bug #1077739 [task-gnome-desktop] Remove network-manager-gnome from the 
recommended list
Bug #1077740 [task-gnome-desktop] Remove network-manager-gnome from the list of 
dependencies
Set Bug forwarded-to-address to 
'https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31'.
Set Bug forwarded-to-address to 
'https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31'.
Set Bug forwarded-to-address to 
'https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31'.

-- 
1071383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071383
1077739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077739
1077740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: win32-loader: FTBFS: Error: Can't find IDC_LIST1 (1016) in the custom UI!

[Debian Bug Tracking System]

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

> reassign 1076933 binutils-mingw-w64-i686 2.42.50.20240625-1+11.6
Bug #1076933 [src:win32-loader] win32-loader: FTBFS: Error: Can't find 
IDC_LIST1 (1016) in the custom UI!
Bug reassigned from package 'src:win32-loader' to 'binutils-mingw-w64-i686'.
No longer marked as found in versions win32-loader/0.10.6.
Ignoring request to alter fixed versions of bug #1076933 to the same values 
previously set
Bug #1076933 [binutils-mingw-w64-i686] win32-loader: FTBFS: Error: Can't find 
IDC_LIST1 (1016) in the custom UI!
Marked as found in versions binutils-mingw-w64/11.6.
> affects 1076933 + win32-loader
Bug #1076933 [binutils-mingw-w64-i686] win32-loader: FTBFS: Error: Can't find 
IDC_LIST1 (1016) in the custom UI!
Added indication that 1076933 affects win32-loader
> notfound 1076933 2.42-4+11.5
Bug #1076933 [binutils-mingw-w64-i686] win32-loader: FTBFS: Error: Can't find 
IDC_LIST1 (1016) in the custom UI!
Ignoring request to alter found versions of bug #1076933 to the same values 
previously set
>
End of message, stopping processing here.

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

Processed: Re: Bug#1076889: installation-guide: FTBFS: Error: xelatex compilation failed

[Debian Bug Tracking System]

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

> reassign 1076889 texlive-lang-french
Bug #1076889 [src:installation-guide] installation-guide: FTBFS: Error: xelatex 
compilation failed
Bug reassigned from package 'src:installation-guide' to 'texlive-lang-french'.
No longer marked as found in versions installation-guide/20230623.
Ignoring request to alter fixed versions of bug #1076889 to the same values 
previously set
> retitle 1076889 LaTeX error in French document
Bug #1076889 [texlive-lang-french] installation-guide: FTBFS: Error: xelatex 
compilation failed
Changed Bug title to 'LaTeX error in French document' from 'installation-guide: 
FTBFS: Error: xelatex compilation failed'.
> affects 1076889 + src:installation-guide
Bug #1076889 [texlive-lang-french] LaTeX error in French document
Added indication that 1076889 affects src:installation-guide
> found 1076889 2024.20240706-1
Bug #1076889 [texlive-lang-french] LaTeX error in French document
Marked as found in versions texlive-lang/2024.20240706-1.
> close 1076889 2024.20240706-2
Bug #1076889 [texlive-lang-french] LaTeX error in French document
Marked as fixed in versions texlive-lang/2024.20240706-2.
Bug #1076889 [texlive-lang-french] LaTeX error in French document
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1076889: installation-guide: FTBFS: Error: xelatex compilation failed

[Santiago Vila]

reassign 1076889 texlive-lang-french
retitle 1076889 LaTeX error in French document
affects 1076889 + src:installation-guide
found 1076889 2024.20240706-1
close 1076889 2024.20240706-2
thanks

Hi. This is most probably the bug above, so it's already fixed.

Thanks.

Bug#1076933: win32-loader: FTBFS: Error: Can't find IDC_LIST1 (1016) in the custom UI!

[Santiago Vila]

s/fr.nsh /<>/build/l10n/templates/ga.nsh /<>/build/l10n/templates/gl.nsh /<>/build/l10n/templates/he.nsh /<>/build/l10n/templates/hr.nsh /<>/build/l10n/templates/hu.nsh /<>/build/l10n/templates/is.nsh 
/<>/build/l10n/templates/it.nsh /<>/build/l10n/templates/ja.nsh /<>/build/l10n/templates/ko.nsh /<>/build/l10n/templates/lt.nsh /<>/build/l10n/templates/nb.nsh /<>/build/l10n/templates/nl.nsh /<>/build/l10n/templates/pl.nsh /<>/build/l10n/templates/pt.nsh /<>/build/l10n/templates/pt_BR.nsh /<>/build/l10n/templates/ro.nsh /<>/build/l10n/templates/ru.nsh 
/<>/build/l10n/templates/sk.nsh /<>/build/l10n/templates/sl.nsh /<>/build/l10n/templates/sq.nsh /<>/build/l10n/templates/sr.nsh /<>/build/l10n/templates/s...@latin.nsh /<>/build/l10n/templates/sv.nsh /<>/build/l10n/templates/th.nsh /<>/build/l10n/templates/tr.nsh /<>/build/l10n/templates/uk.nsh /<>/build/l10n/templates/zh_CN.nsh /<>/build/l10n/templates/zh_TW.nsh ; 
do echo "; BEGIN $i" ; cat $i ; echo "; END $i" ; done > /<>/build/l10n/templates/all.nsh
for i in ar be bg bs ca cs da de el en eo es eu fa fi fr ga gl he hr hu is it 
ja ko lt nb nl pl pt pt_BR ro ru sk sl sq sr sr@latin sv th tr uk zh_CN zh_TW ; 
do \
echo "Push \${`LANGUAGE=$i /<>/l10n/win32-loader.sh 
LANG_ENGLISH`}" ; \
echo "Push \"`LANGUAGE=$i /<>/l10n/win32-loader.sh 
English`\"" ; \
done > /<>/build/l10n/templates/dialog.nsh
rm locale/eo/LC_MESSAGES/win32-loader.mo locale/es/LC_MESSAGES/win32-loader.mo 
locale/be/LC_MESSAGES/win32-loader.mo locale/ko/LC_MESSAGES/win32-loader.mo 
locale/sv/LC_MESSAGES/win32-loader.mo locale/nl/LC_MESSAGES/win32-loader.mo 
locale/is/LC_MESSAGES/win32-loader.mo locale/fa/LC_MESSAGES/win32-loader.mo 
locale/lt/LC_MESSAGES/win32-loader.mo locale/ja/LC_MESSAGES/win32-loader.mo 
locale/bg/LC_MESSAGES/win32-loader.mo locale/he/LC_MESSAGES/win32-loader.mo 
locale/de/LC_MESSAGES/win32-loader.mo locale/hr/LC_MESSAGES/win32-loader.mo 
locale/sq/LC_MESSAGES/win32-loader.mo locale/it/LC_MESSAGES/win32-loader.mo 
locale/sr/LC_MESSAGES/win32-loader.mo locale/ro/LC_MESSAGES/win32-loader.mo 
locale/sk/LC_MESSAGES/win32-loader.mo locale/uk/LC_MESSAGES/win32-loader.mo 
locale/pt_BR/LC_MESSAGES/win32-loader.mo locale/bs/LC_MESSAGES/win32-loader.mo 
locale/nb/LC_MESSAGES/win32-loader.mo locale/ar/LC_MESSAGES/win32-loader.mo 
locale/th/LC_MESSAGES/win32-loader.mo locale/eu/LC_MESSAGES/win32-loader.mo 
locale/ru/LC_MESSAGES/win32-loader.mo locale/zh_TW/LC_MESSAGES/win32-loader.mo 
locale/fr/LC_MESSAGES/win32-loader.mo locale/zh_CN/LC_MESSAGES/win32-loader.mo 
locale/sl/LC_MESSAGES/win32-loader.mo locale/ga/LC_MESSAGES/win32-loader.mo 
locale/gl/LC_MESSAGES/win32-loader.mo locale/hu/LC_MESSAGES/win32-loader.mo 
locale/pl/LC_MESSAGES/win32-loader.mo 
locale/sr@latin/LC_MESSAGES/win32-loader.mo 
locale/pt/LC_MESSAGES/win32-loader.mo locale/fi/LC_MESSAGES/win32-loader.mo 
locale/ca/LC_MESSAGES/win32-loader.mo locale/el/LC_MESSAGES/win32-loader.mo 
locale/tr/LC_MESSAGES/win32-loader.mo locale/da/LC_MESSAGES/win32-loader.mo 
locale/cs/LC_MESSAGES/win32-loader.mo
make[3]: Leaving directory '/<>/build/l10n'
makensis -V3 "-XUnicode True" -DVERSION=0.10.6 -D4DIGITS_DATE=2022.03.21.2258 
-D_OUTFILE_NAME=build/win32-loader_0.10.6_all.exe -DBUILD_DIR=build -DNOCD=yes -DPXE=yes -DNOCD=yes 
-DOPTIONS_TXT="+net +pxe" main.nsi
MakeNSIS v3.10-2 - Copyright 1999-2023 Contributors
See the file COPYING for license details.
Credits can be found in the Users Manual.

Command line defined: "VERSION=0.10.6"
Command line defined: "4DIGITS_DATE=2022.03.21.2258"
Command line defined: "_OUTFILE_NAME=build/win32-loader_0.10.6_all.exe"
Command line defined: "BUILD_DIR=build"
Command line defined: "NOCD=yes"
Command line defined: "PXE=yes"
Command line defined: "NOCD=yes"
Command line defined: "OPTIONS_TXT=+net +pxe"
Processing config: /etc/nsisconf.nsh
Processing script file: "main.nsi" (UTF8)
Error: Can't find IDC_LIST1 (1016) in the custom UI!
!include: error in script: "download.nsi" on line 42
Error in script "main.nsi" on line 127 -- aborting creation process
make[2]: *** [Makefile:175: build/win32-loader_0.10.6_all.exe] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: error: make -j2 "INSTALL=install --strip-program=true" 
STANDALONE=yes PXE=yes NOT_ALLKERNELS=yes OUTFILE_NAME=build/win32-loader_0.10.6_all.exe 
BUILD_DIR=build returned exit code 2
make[1]: *** [debian/rules:34: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:28: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202407/

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1076889: installation-guide: FTBFS: Error: xelatex compilation failed

[Santiago Vila]

allation-media)
Writing build.out.fr.i386/html/ch02s05.html for sect1(memory-disk-requirements)
Writing build.out.fr.i386/html/ch02.html for chapter(hardware-req)
Writing build.out.fr.i386/html/ch03s01.html for sect1(install-overview)
Writing build.out.fr.i386/html/ch03s02.html for sect1(backup)
Writing build.out.fr.i386/html/ch03s03.html for sect1(needed-info)
Writing build.out.fr.i386/html/ch03s04.html for sect1(minimum-hardware-reqts)
Writing build.out.fr.i386/html/ch03s05.html for sect1(non-debian-partitioning)
Writing build.out.fr.i386/html/ch03s06.html for sect1(pre-install-bios-setup)
Writing build.out.fr.i386/html/ch03.html for chapter(preparing)
Writing build.out.fr.i386/html/ch04s01.html for sect1(official-cdrom)
Writing build.out.fr.i386/html/ch04s02.html for sect1(downloading-files)
Writing build.out.fr.i386/html/ch04s03.html for sect1(boot-usb-files)
Writing build.out.fr.i386/html/ch04s04.html for sect1(boot-drive-files)
Writing build.out.fr.i386/html/ch04s05.html for sect1(install-tftp)
Writing build.out.fr.i386/html/ch04s06.html for sect1(automatic-install)
Writing build.out.fr.i386/html/ch04s07.html for sect1(verifying-files)
Writing build.out.fr.i386/html/ch04.html for chapter(install-methods)
Writing build.out.fr.i386/html/ch05s01.html for sect1
Writing build.out.fr.i386/html/ch05s02.html for 
sect1(boot-installer-accessibility)
Writing build.out.fr.i386/html/ch05s03.html for sect1(boot-parms)
Writing build.out.fr.i386/html/ch05s04.html for sect1(boot-troubleshooting)
Writing build.out.fr.i386/html/ch05.html for chapter(boot-installer)
Writing build.out.fr.i386/html/ch06s01.html for sect1
Writing build.out.fr.i386/html/ch06s02.html for sect1(modules-list)
Writing build.out.fr.i386/html/ch06s03.html for sect1(module-details)
Writing build.out.fr.i386/html/ch06s04.html for sect1(loading-firmware)
Writing build.out.fr.i386/html/ch06s05.html for sect1(customization)
Writing build.out.fr.i386/html/ch06.html for chapter(d-i-intro)
Writing build.out.fr.i386/html/ch07s01.html for sect1(base-boot)
Writing build.out.fr.i386/html/ch07s02.html for sect1(mount-encrypted-volumes)
Writing build.out.fr.i386/html/ch07s03.html for sect1(login)
Writing build.out.fr.i386/html/ch07.html for chapter(boot-new)
Writing build.out.fr.i386/html/ch08s01.html for sect1(shutdown)
Writing build.out.fr.i386/html/ch08s02.html for sect1(debian-orientation)
Writing build.out.fr.i386/html/ch08s03.html for sect1(further-reading)
Writing build.out.fr.i386/html/ch08s04.html for sect1(mail-setup)
Writing build.out.fr.i386/html/ch08s05.html for sect1(kernel-baking)
Writing build.out.fr.i386/html/ch08s06.html for sect1(rescue)
Writing build.out.fr.i386/html/ch08.html for chapter(post-install)
Writing build.out.fr.i386/html/apas01.html for sect1(howto-preliminaries)
Writing build.out.fr.i386/html/apas02.html for sect1(howto-getting-images)
Writing build.out.fr.i386/html/apas03.html for sect1(howto-installation)
Writing build.out.fr.i386/html/apas04.html for sect1(howto-installation-report)
Writing build.out.fr.i386/html/apas05.html for sect1(howto-installation-finally)
Writing build.out.fr.i386/html/apa.html for appendix(installation-howto)
Writing build.out.fr.i386/html/apbs01.html for sect1(preseed-intro)
Writing build.out.fr.i386/html/apbs02.html for sect1(preseed-using)
Writing build.out.fr.i386/html/apbs03.html for sect1(preseed-creating)
Writing build.out.fr.i386/html/apbs04.html for sect1(preseed-contents)
Writing build.out.fr.i386/html/apbs05.html for sect1(preseed-advanced)
Writing build.out.fr.i386/html/apb.html for appendix(appendix-preseed)
Writing build.out.fr.i386/html/apcs01.html for sect1(partition-sizing)
Writing build.out.fr.i386/html/apcs02.html for sect1(directory-tree)
Writing build.out.fr.i386/html/apcs03.html for sect1
Writing build.out.fr.i386/html/apcs04.html for sect1(device-names)
Writing build.out.fr.i386/html/apcs05.html for sect1(partition-programs)
Writing build.out.fr.i386/html/apc.html for appendix(partitioning)
Writing build.out.fr.i386/html/apds01.html for sect1(linuxdevices)
Writing build.out.fr.i386/html/apds02.html for sect1(tasksel-size-list)
Writing build.out.fr.i386/html/apds03.html for sect1(linux-upgrade)
Writing build.out.fr.i386/html/apds04.html for sect1(plip)
Writing build.out.fr.i386/html/apds05.html for sect1(pppoe)
Writing build.out.fr.i386/html/apd.html for appendix(random-bits)
Writing build.out.fr.i386/html/apes01.html for sect1(about)
Writing build.out.fr.i386/html/apes02.html for sect1(contributing)
Writing build.out.fr.i386/html/apes03.html for sect1(contributors)
Writing build.out.fr.i386/html/apes04.html for sect1(trademarks)
Writing build.out.fr.i386/html/ape.html for appendix(administrivia)
Writing build.out.fr.i386/html/apf.html for appendix(appendix-gpl)
Writing build.out.fr.i386/html/index.html for book
Info: creating .pdf file...
xelatex failed
install.fr.profiled.tex:42: Undefined control sequence \FBCompactItemize@setup.
install.fr.profiled.tex:42: l

Bug#1073785: marked as done (debootstrap-udeb: removal of trixie --> sid link causes fatal error in D-I)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 21:04:19 +
with message-id 
and subject line Bug#1073785: fixed in debootstrap 1.0.136
has caused the Debian Bug report #1073785,
regarding debootstrap-udeb: removal of trixie --> sid link causes fatal error 
in D-I
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.)


-- 
1073785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap-udeb
Version: 1.0.135
Severity: serious
User: debian...@lists.debian.org
Usertags: openqa

While testing daily netinst debian-installer images with openQA, we see that
debootstrap fails:

  https://openqa.debian.net/tests/272866#step/install_base/1

  "The debootstrap program exited with an error (return value 1)"

looking in the syslog, one finds:

  debootstrap: E: NOSCRIPT
  debootsrtap: EA: /usr/share/debootstrap/scripts/trixie
  debootstrap: EF: No such script: %s

If I reinstate the trixie --> sid symlink, the installation can then proceed.

I presume that when removing the "redundant" links in commit 2d3eae91, there was
an intent that the scripting should default to "sid" when the required script is
found to be missing, but this seems not to have been done correctly.

It looks to me as if 73e1b5f9 simply fails to deal with the case where
distro-info is unavailable (debian-installer does not include it).

Cheers, Phil.
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.136
Done: Luca Boccassi 

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 1073...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (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, 18 Jun 2024 21:36:25 +0100
Source: debootstrap
Architecture: source
Version: 1.0.136
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Luca Boccassi 
Closes: 1073785
Changes:
 debootstrap (1.0.136) unstable; urgency=medium
 .
   [ Philip Hands ]
   * reinstate Debian codename symlinks (closes: #1073785)
   * drop unneeded addition of "test extras"
   * switch to using branch2repo for salsa-ci
   * avoid setting DEF_MIRROR to https://https://...
Checksums-Sha1:
 f83f8d4d187b4bad3d1c457fd112a7f94b72f77b 2053 debootstrap_1.0.136.dsc
 06a12533a8065be94387fa4f9578c4be002869f4 93499 debootstrap_1.0.136.tar.gz
 03fa202d0888b7dc31925ce9029a87b6fe355339 6589 
debootstrap_1.0.136_source.buildinfo
Checksums-Sha256:
 9f561c4a3f6e891737da7dd7b19a48979298028b6d0cffd03a0dd5f346186549 2053 
debootstrap_1.0.136.dsc
 a5c2067e6480f74df5079016629d3fd35497a2c634c385eb1e1ddf718a9f7498 93499 
debootstrap_1.0.136.tar.gz
 964584ac07b864700049800b3037742a02fab4e8c8e0fb3ce9e9db27d84c2263 6589 
debootstrap_1.0.136_source.buildinfo
Files:
 6c052fb398a6dc7c6fd9b778dce406bd 2053 admin optional debootstrap_1.0.136.dsc
 566b5833560f4098894d622b98b6cdb3 93499 admin optional 
debootstrap_1.0.136.tar.gz
 9969ae1a227ed71d509fa0c4a09035e4 6589 admin optional 
debootstrap_1.0.136_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmZx8AIRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB7e1g//Uu0bt1ZRIwrFV93nhgsqTtjoeH12uWQp
CNxULE2k3eN+TmnuKga+4u4W2y1qG4a19y4E9OljErfGiSz6HogchWyCS8U0dlHW
pZBZ8GtTT5tbAijzavj+BKk+kj9du44eGz7M0YI/yqLeYNiXn6WTTCcQO9x3TrhP
6d/kvkiWEvxJlnnPCHlFIjlK/Waog6X07Lt8cZjjnyDJ8Srg40ACmgR99AUknPZq
vR+tw7vnzmDS1elHCTA5Bv9PhSgQ1xMw5FRsHgLPeR3AZmJDtRUP85nh2S07Bw4o
cb+VajPZe4Rr8seL399msIuF0JtdU7xGFgBDpW4g8UKRe4Jw6EPT48ZWC80vQBPq
eTYMb3tDhlGz3MnC9PJDnAbc3VVmeHJh3PBeXzaTDyQ/dLj8n+2YlM2FpS+pnE8d
G5NUuefHgBwl4/ITk2txhjSLI0/Cjt1cLx/HfJnAaToCJY4I61m7zxJVDPmgt5NH
hbqlXbZeS0AaveS30otRxZCtQcIWSXLN3LKcebD7VgYsVLixzJoMDtYV87FBYxe4
7L9N0BBZBxnA8MaLBejCCx/95Xe1CoEq2apXPsaMsUvc/nlJzJCvbXabgGezfm/C
lHYQvFhZ4vkSZZ9rrGxnAFjV5ShKQXRTSEZ9yujJWRvB6nCRgTI767PIJ/qdgl6y
RyYSQ/hE8Rw=
=QswL
-END PGP SIGNATURE-



pgp0Aa4zdcyqx.pgp
Description: PGP signature
--- End Message ---

Bug#1073785: debootstrap-udeb: removal of trixie --> sid link causes fatal error in D-I

[Philip Hands]

Package: debootstrap-udeb
Version: 1.0.135
Severity: serious
User: debian...@lists.debian.org
Usertags: openqa

While testing daily netinst debian-installer images with openQA, we see that
debootstrap fails:

  https://openqa.debian.net/tests/272866#step/install_base/1

  "The debootstrap program exited with an error (return value 1)"

looking in the syslog, one finds:

  debootstrap: E: NOSCRIPT
  debootsrtap: EA: /usr/share/debootstrap/scripts/trixie
  debootstrap: EF: No such script: %s

If I reinstate the trixie --> sid symlink, the installation can then proceed.

I presume that when removing the "redundant" links in commit 2d3eae91, there was
an intent that the scripting should default to "sid" when the required script is
found to be missing, but this seems not to have been done correctly.

It looks to me as if 73e1b5f9 simply fails to deal with the case where
distro-info is unavailable (debian-installer does not include it).

Cheers, Phil.

Processed (with 1 error): update dep17 bug metadata

[Debian Bug Tracking System]

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

> # assign from source to binary
> reassign 1051460 crowdsec-custom-bouncer
Bug #1051460 [src:crowdsec-custom-bouncer] crowdsec-custom-bouncer: move 
systemd units to /usr
Bug reassigned from package 'src:crowdsec-custom-bouncer' to 
'crowdsec-custom-bouncer'.
No longer marked as found in versions crowdsec-custom-bouncer/0.0.15-3.
Ignoring request to alter fixed versions of bug #1051460 to the same values 
previously set
> reassign 1054084 crowdsec
Bug #1054084 [src:crowdsec] let dh_installsystemd choose the location of 
systemd units
Bug reassigned from package 'src:crowdsec' to 'crowdsec'.
No longer marked as found in versions crowdsec/1.4.6-6.
Ignoring request to alter fixed versions of bug #1054084 to the same values 
previously set
> reassign 1054086 lsm
Bug #1054086 [src:lsm] lsm: let dh_installsystemd choose the location of units
Bug reassigned from package 'src:lsm' to 'lsm'.
No longer marked as found in versions lsm/1.0.4-2.
Ignoring request to alter fixed versions of bug #1054086 to the same values 
previously set
> reassign 1054480 pki-server
Bug #1054480 [src:dogtag-pki] dogtag-pki: installs a systemd unit twice once 
dh_installsystemd installs to /usr
Bug reassigned from package 'src:dogtag-pki' to 'pki-server'.
No longer marked as found in versions dogtag-pki/11.2.1-2.
Ignoring request to alter fixed versions of bug #1054480 to the same values 
previously set
> reassign 1057803 libfli2
Bug #1057803 [src:libfli] libfli: delegate placement of udev files to 
pkg-config data
Bug reassigned from package 'src:libfli' to 'libfli2'.
No longer marked as found in versions libfli/2.0+20221221182632-1.
Ignoring request to alter fixed versions of bug #1057803 to the same values 
previously set
> reassign 1057900 apcupsd
Bug #1057900 {Done: Thorsten Alteholz } [src:apcupsd] 
apcupsd: move files from / to /usr
Bug reassigned from package 'src:apcupsd' to 'apcupsd'.
No longer marked as found in versions apcupsd/3.14.14-3.1.
No longer marked as fixed in versions apcupsd/3.14.14-4.
> reassign 1058764 opendmarc
Bug #1058764 [src:opendmarc] opendmarc: installs deprecated 
/lib/opendmarc/opendmarc.service.generate
Bug reassigned from package 'src:opendmarc' to 'opendmarc'.
No longer marked as found in versions opendmarc/1.4.2-4.
Ignoring request to alter fixed versions of bug #1058764 to the same values 
previously set
> reassign 1058840 libplayeronecamera2
Bug #1058840 [src:libplayerone] libplayerone: use udev.pc to place udev rules
Bug reassigned from package 'src:libplayerone' to 'libplayeronecamera2'.
No longer marked as found in versions libplayerone/3.1.0+20221218103507-1.
Ignoring request to alter fixed versions of bug #1058840 to the same values 
previously set
> reassign 1058844 libinovasdk1
Bug #1058844 [src:libinovasdk] libinovasdk: use udev.pc to place udev rules
Bug reassigned from package 'src:libinovasdk' to 'libinovasdk1'.
No longer marked as found in versions libinovasdk/1.3.6-3.
Ignoring request to alter fixed versions of bug #1058844 to the same values 
previously set
> reassign 1059371 snoopy
Bug #1059371 [src:snoopy] snoopy: installs library into /lib
Bug reassigned from package 'src:snoopy' to 'snoopy'.
No longer marked as found in versions snoopy/2.5.1-1.
Ignoring request to alter fixed versions of bug #1059371 to the same values 
previously set
> reassign 1060195 hfsprogs
Bug #1060195 [src:hfsprogs] hfsprogs: install files into /usr (DEP17)
Bug reassigned from package 'src:hfsprogs' to 'hfsprogs'.
No longer marked as found in versions hfsprogs/540.1.linux3-5.
Ignoring request to alter fixed versions of bug #1060195 to the same values 
previously set
> reassign 1061245 cups-daemon
Bug #1061245 [src:cups] cups: install systemd units into /usr
Bug reassigned from package 'src:cups' to 'cups-daemon'.
No longer marked as found in versions cups/2.4.7-1.
Ignoring request to alter fixed versions of bug #1061245 to the same values 
previously set
> reassign 1061332 cifs-utils
Bug #1061332 [src:cifs-utils] cifs-utils: install files into /usr
Bug reassigned from package 'src:cifs-utils' to 'cifs-utils'.
No longer marked as found in versions cifs-utils/2:7.0-2.
Ignoring request to alter fixed versions of bug #1061332 to the same values 
previously set
> reassign 1061527 libelogind0
Bug #1061527 [src:elogind] elogind: install files into /usr
Bug reassigned from package 'src:elogind' to 'libelogind0'.
No longer marked as found in versions elogind/252.9-1debian3.
Ignoring request to alter fixed versions of bug #1061527 to the same values 
previously set
> reassign 1064126 libnss-libvirt,libvirt-daemon-system
Bug #1064126 [src:libvirt] libvirt: install NSS modules and systemd units into 
/usr
Bug reassigned from package 'src:libvirt' to 
'libnss-libvirt,libvirt-daemon-system'.
No longer marked as found in versions libvirt/10.0.0-2.
Ignoring request to alter fixed versions of bug #1064126 to the same values 
previously set
> # bump to important as announced

Re: Grub error on an installed system

[Pascal Hambourg]

On 06/06/2024 at 12:35, darkpenguin wrote:


Harmless messages are fine, but what could be taking about 4 seconds of
waiting at "Welcome to GRUB!" before the menu? Is there any way to find out?


You can try adding 'set debug=all' and 'echo ' commands in 
/boot/efi/EFI/debian/grub.cfg and /boot/grub/grub.cfg.

Re: Grub error on an installed system

[darkpenguin]

Thanks for the info! So it won't be in Bookworm then, but should be
there right after.

Harmless messages are fine, but what could be taking about 4 seconds of
waiting at "Welcome to GRUB!" before the menu? Is there any way to find out?


On 06/06/24 14:30, Pascal Hambourg wrote:
> On 06/06/2024 at 11:51, darkpenguin wrote:
>>
>> On a new Bookworm installation I see a new issue: before grub-efi shows
>> the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and
>> then flashes an error for a split second:
>>
>> error: no such device: /.disk/info
>> error: no such device: /.disk/mini-info
> 
> These (harmless) messages are caused by the early grub.cfg embedded in 
> the monolithic EFI GRUB image memdisk, which was originally designed for 
> installation media. It has been removed since version 2.06-14 when the 
> FAT memdisk image was replaced with a SquashFS one.
> 
> <https://salsa.debian.org/grub-team/grub/-/commit/5171e04d28138d244dbef846f79b3376602a84c1>
> 

Re: Grub error on an installed system

[Pascal Hambourg]

On 06/06/2024 at 11:51, darkpenguin wrote:


On a new Bookworm installation I see a new issue: before grub-efi shows
the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and
then flashes an error for a split second:

error: no such device: /.disk/info
error: no such device: /.disk/mini-info


These (harmless) messages are caused by the early grub.cfg embedded in 
the monolithic EFI GRUB image memdisk, which was originally designed for 
installation media. It has been removed since version 2.06-14 when the 
FAT memdisk image was replaced with a SquashFS one.


<https://salsa.debian.org/grub-team/grub/-/commit/5171e04d28138d244dbef846f79b3376602a84c1>

Grub error on an installed system

[darkpenguin]

Hello!

(I'm not sure where should I go with this, but seems like it's about
"Debian boot" and likely has something to do with the installer.)

On a new Bookworm installation I see a new issue: before grub-efi shows
the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and
then flashes an error for a split second:

error: no such device: /.disk/info
error: no such device: /.disk/mini-info

Trying to find any information about this, the only thing I've found is:

https://unix.stackexchange.com/questions/753732/what-does-grub-error-no-such-device-disk-info-mean-and-how-to-fix-it

So this is likely not for the upstream grub, but for the Debian
adaptation of grub.


I've tried to fix it for a while, and now I'm not sure if the error is
still there, because it flashes so quickly. But a significant
multiple-second delay on "Welcome to GRUB!" on a very modern PC is
definitely there. Is there a way to see the logs from this stage of grub
loading?


(Please CC me - I'm not on the list)

-- 
darkpenguin

Bug#1072188: Package error

[Peter Carter]

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: Dell 7020
Processor:Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Memory: 16G
Partitions:
filesystem Type 1K-blocks Used Available Use% Mounted on 
udev   devtmpfs   8108416    0   8108416   0% /dev tmpfs 
 tmpfs  1628976 1552   1627424   1% /run /dev/sda3 
 btrfs    468253696 32781716 430568940   8% / tmpfs  tmpfs 
 8144876    0   8144876   0% /dev/shm tmpfs  tmpfs 
5120   16  5104   1% /run/lock efivarfs   efivarfs 
  128   96    28  78% /sys/firmware/efi/efivars /dev/sdb1 
 btrfs    976761560 5920 974597824   1% /data /dev/sda1 
 vfat    497684 4480    493204   1% /boot/efi overlay 
   overlay  468253696 32781716 430568940   8% 
/var/lib/docker/overlay2/afa24d7e3210883370c5732 
914467d97f210df47b7a7635495e899928a72/merged tmpfs  tmpfs 
 1628972  232   1628740   1% /run/user/1000


Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor 
DRAM Controller [8086:0c00] (rev 06)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: hsw_uncore 00:02.0 VGA 
compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 
   DeviceName:  Onboard IGD    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i915    Kernel modules: 
i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor HD Audio Controller [808 6:0c0c] (rev 06) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
snd_hda_intel    Kernel modules: snd_hda_intel 00:14.0 USB 
controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI [8086:8c31] (rev 04)    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: xhci_hcd    Kernel modules: xhci_pci 
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
mei_me    Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: 
Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04) 
   DeviceName:  Onboard LAN    Subsystem: Dell Device 
[1028:05a4]    Kernel driver in use: e1000e    Kernel modules: 
e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 
Series Chipset Family USB EHCI #2 [8086:8c2d] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: 
Intel Corporation 8 Series/C220 Series Chipset High Definition Audio 
Controller [ 8086:8c20] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: snd_hda_intel    Kernel 
modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #1 [808 6:8c10] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #5 [808 6:8c18] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 8 
Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: 
Intel Corporation Q87 Express LPC Controller [8086:8c4e] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
lpc_ich    Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: 
Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA 
Controller 1 [AHCI mode] [8086:8c02] (rev 04)    DeviceName: 
 Onboard SATA controller #1    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: ahci    Kernel modules: ahci 00:1f.3 
SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family 
SMBus Controller [8086:8c22] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i801_smbus    Kernel 
modules: i2c_i801 02:00.0 Network controller [0280]: Intel Corporation 
Wireless 7265 [8086:095a] (rev 59)    Subsystem: Intel Corporation 
Dual Band Wireless-AC 7265 [Stone Peak 2 AC] [8086:5010]    Kernel 
driver in use: iwlwifi    Kernel modules: iwlwifi


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]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone 

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> tags 731859 -reproducible +pending
Unknown tag/s: reproducible.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

Bug #731859 [debootstrap] debootstrap: variant=fakechroot fails
Requested to remove no tags; doing nothing.
Bug #731859 [debootstrap] debootstrap: variant=fakechroot fails
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[Philip Hands]

Michael Tokarev  writes:

> 09.02.2024 16:58, ca...@allfreemail.net
>> Package: console-setup
>> Followup-For: Bug #1063518
>> 
>> Consider making all scripts provided by console-setup
>> shellcheck-clean, there are lots of tiny issues that can turn into
>> big issues under the right conditions.
>
> Please do not do this. Shellcheck is a huge problem and we had large amount
> of bugs due to people trying to apply its suggestions.  It's very difficult
> in many cases to spot why shellcheck is wrong (classic is the suggestion to
> put $var into double quotes "$var" which breaks badly if $var is supposed to
> contain zero or more separate words - this way, even boot scripts has become
> buggy leading to system becoming unbootable).
>
> Shellcheck is a very bad tool.

I think the reality is somewhere between these two positions.

Shellcheck is not particularly helpful for most of D-I because it
doesn't have a shell variant that perfectly matches our busybox sh
build.  That might have just improved, since I notice that a busybox sh
variant has just been merged upstream, so we'll see if that makes things
better.

On the other hand, if I'd been paying attention at the time, the fact
that this change dropped the number of shellcheck reports for setupcon
from 189 to 1 should have rung some alarm bells, but it seems that I've
learnt to ignore the little '!' in my emacs status bar -- I'll have to
keep an eye on that in future.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[Michael Tokarev]

09.02.2024 17:57, Thorsten Bonow :

dash << 'EOF'    [15:28:53]
if $( (true) 2>/dev/null); then
  echo "42"
fi
EOF
42

which only works in dash because of the added space between the command 
substitution $(...) and the subshell (...).

Does dash think it has to do arithmetic expansion "$((...))"?


Yes, arithmetic, and that's what bash does too.  dash does not understand
space between two closing parens though, ') )'.  And this is logical - if
the opening is "((", use the same matching "))" for closing.

$(( ... )) is arithmetic expression,
$( ( ... ) ) is a subshell.

Everything else is asking for trouble like this.


But what's POSIX take on this?  I couldn't find anything.  Is this a bug in 
dash or in setupcon?


It's a bug in setupcon.

/mjt

Bug#1063518: marked as done (console-setup: setupcon: 1386: Syntax error: Missing '))')

[Debian Bug Tracking System]

Your message dated Fri, 09 Feb 2024 15:34:15 +
with message-id 
and subject line Bug#1063518: fixed in console-setup 1.226
has caused the Debian Bug report #1063518,
regarding console-setup: setupcon: 1386: Syntax error: Missing '))'
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.)


-- 
1063518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup
Version: 1.225
Severity: grave

After the upgrade from 1.223, console-setup.service failed to start due
to a syntax error in the setupcon script:

,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`

It looks like dash does not like the construct in line 907 where there
is an opening '$((' but the closing parentheses are split.

,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.226
Done: Philip Hands 

We believe that the bug you reported is fixed in the latest version of
console-setup, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philip Hands  (supplier of updated console-setup 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: Fri, 09 Feb 2024 15:45:38 +0100
Source: console-setup
Architecture: source
Version: 1.226
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Philip Hands 
Closes: 1063518
Changes:
 console-setup (1.226) unstable; urgency=medium
 .
   * Team upload
 .
   * setupcon: fix mistaken $((  (closes: 1063518)
Checksums-Sha1:
 84294e5b75b00aad2cced6b0cfab0635682b6c3e 3340 console-setup_1.226.dsc
 ff1036c7201a486a791040148128711a5a746106 1685272 console-setup_1.226.tar.xz
Checksums-Sha256:
 25d949da1eb3e494bed1f3fc11074c5221ce54bd1463963b0b9417b9b89922f9 3340 
console-setup_1.226.dsc
 992be8dfcc5b99c42cb0f2914d987298e281e9232eb2492302d97dc3ff6412bd 1685272 
console-setup_1.226.tar.xz
Files:
 82130112e2f68bcbbe925f8d337b7acd 3340 utils optional console-setup_1.226.dsc
 81e55c7e628e52eeb52efa6cbaeeb03f 1685272 utils optional 
console-setup_1.226.tar.xz

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEE3/FBWs4yJ/zyBwfW0EujoAEl1cAFAmXGQE8PHHBoaWxAaGFu
ZHMuY29tAAoJENBLo6ABJdXAuuMP/i3ZoM4rKVGU3yZilBPOYOeLxvPdqHzqxGuZ
huCceNMgLX7CFN4Je1t2CoUwV5Xp8V9/+uR1ZZ624nvoH+iIsuSyK9N+uk/xFTw+
9fwNgY3Wf1bRI7H6jMF35ZK8pwo9I1aCzoflEI/dTemzTi5ewgaGKwSL+MEkuZwB
MBs1gpnEe8ERsTfE6DEb9/7V8eK2rLXq1RFXSu1M+wMGG8i0vmvV7KavUcs1obgL
kYH0YMRO6DnBfmzqb3mOnwF3LKBRoiyejh8tk7qREfd5UDSt5zCwd+3erarFIjaw
3j4aPV6b26vMzlEIr85HhodjU0dOSrM/UeuYIQPTH0pvKO9mo9RXJ4FoJ8RVgALG
5/kGZIJJNlBASKksLli/HWR2zonyExz9d6un9KwQg7825TT4q5uaH09ytmfYI4Dz
nJL4VeUybWo/EyqfplknUUi3yBmlCAaUx3uuS1hYO2/HFDYa2YZP6RA4jEV9sreJ
koGzSI0AowPSziGx6n3rOiSLUfpik8ZBCfy+alm4zB5XYtPW/60qmYIs67UKqdmd
hnnPDQAAwF4Vmhb1f8ZXRpOLyvIgnx+vWWdy1pQf9YZFHA/UmTIPSR0ZAPtupLdj
HFHdQLeE0I5ZjymHVyh1SyUUK4v5swXYasfvXBXhTADODgMo1BXmZ9hQz+Bi31GP
MYv0Hz4t
=YBWD
-END PGP SIGNATURE End Message ---

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[Thorsten Bonow]

Thorsten Bonow  writes:


[...]


But what's POSIX take on this?  I couldn't find anything.  Is this a
bug in dash or in setupcon?


I'm stupid[1].  It's a bug in setupcon, POSIX requires the space:

"The syntax of the shell command language has an ambiguity for
expansions beginning with "$((", which can introduce an arithmetic
expansion or a command substitution that starts with a subshell.
Arithmetic expansion has precedence; that is, the shell shall first
determine whether it can parse the expansion as an arithmetic
expansion and shall only parse the expansion as a command substitution
if it determines that it cannot parse the expansion as an arithmetic
expansion.  The shell need not evaluate nested expansions when
performing this determination.  If it encounters the end of input
without already having determined that it cannot parse the expansion
as an arithmetic expansion, the shell shall treat the expansion as an
incomplete arithmetic expansion and report a syntax error.  A
conforming application shall ensure that it separates the "$(" and '('
into two tokens (that is, separate them with white space) in a command
substitution that starts with a subshell.  For example, a command
substitution containing a single subshell could be written as:

$( (command) )"


Footnotes:
[1]  
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[Thorsten Bonow]

Package: console-setup
Version: 1.225
Severity: grave

After the upgrade from 1.223, console-setup.service failed to start 
due

to a syntax error in the setupcon script:

,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`

It looks like dash does not like the construct in line 907 where 
there

is an opening '$((' but the closing parentheses are split.

,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`


I tried

dash << 'EOF'[15:28:53]
if $( (true) 2>/dev/null); then
 echo "42"
fi
EOF
42

which only works in dash because of the added space between the 
command substitution $(...) and the subshell (...).


Does dash think it has to do arithmetic expansion "$((...))"?

bash and zsh in sh mode accept nesting a subshell within the command 
substitution without an extra space.  In the last version of the 
script, backticks were used, circumventing this issue.


But what's POSIX take on this?  I couldn't find anything.  Is this a 
bug in dash or in setupcon?


Toto

PS: To the proposal of a cleanup: 'checkbashisms' doesn't return any
errors, but IMHO, at least closing (double) quotes on
a line of their own should be fixed:

$ cat /bin/setupcon | grep -n "^\(\"\|'\)$"
[15:47:07]

87:'
145:"
148:"
190:"
193:"
208:"

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[Michael Tokarev]

09.02.2024 16:58, ca...@allfreemail.net

Package: console-setup
Followup-For: Bug #1063518

Consider making all scripts provided by console-setup shellcheck-clean, there 
are lots of tiny issues that can turn into big issues under the right 
conditions.


Please do not do this. Shellcheck is a huge problem and we had large amount
of bugs due to people trying to apply its suggestions.  It's very difficult
in many cases to spot why shellcheck is wrong (classic is the suggestion to
put $var into double quotes "$var" which breaks badly if $var is supposed to
contain zero or more separate words - this way, even boot scripts has become
buggy leading to system becoming unbootable).

Shellcheck is a very bad tool.

/mjt

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[cacin]

Package: console-setup
Followup-For: Bug #1063518

Consider making all scripts provided by console-setup shellcheck-clean, there 
are lots of tiny issues that can turn into big issues under the right 
conditions.

https://tracker.debian.org/pkg/shellcheck

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

[Sven Joachim]

Package: console-setup
Version: 1.225
Severity: grave

After the upgrade from 1.223, console-setup.service failed to start due
to a syntax error in the setupcon script:

,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`

It looks like dash does not like the construct in line 907 where there
is an opening '$((' but the closing parentheses are split.

,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`


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

Bug#1060383: marked as done (ERROR UPDATING)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jan 2024 16:34:24 +
with message-id <20240110163424.gb2838...@tack.einval.com>
and subject line Re: Bug#1060383: ERROR UPDATING
has caused the Debian Bug report #1060383,
regarding ERROR UPDATING
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.)


-- 
1060383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: Discover
Versione: 5.27.5


Hi to all,
I have been experiencing errors when updating the system for a few days now.
I attach an info.txt file of my system.

thank you
Roberto

Scaricamento del pacchetto non riuscito:E: 
http://mxrepo.com/mx/repo bookworm/main amd64 ddm-mx all 23.12.02 is not 
(yet) available (Impossibile connettersi a mxrepo.com:443 
(70.40.214.183). - connect (111: Connessione rifiutata))
E: http://mxrepo.com/mx/repo bookworm/main amd64 firefox amd64 
121.0.1~mozillabinaries-1mx23+1 is not (yet) available (Impossibile 
connettersi a mxrepo.com:https:)
E: http://mxrepo.com/mx/repo bookworm/main amd64 firefox-l10n-xpi-it 
amd64 121.0.1~mozillabinaries-1mx23+1 is not (yet) available 
(Impossibile connettersi a mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 formatusb amd64 
24.01.01 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: http://mxrepo.com/mx/repo bookworm/main amd64 lo-main-helper all 
24.01.3mx23 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: http://mxrepo.com/mx/repo bookworm/main amd64 
mx-packageinstaller-pkglist all 24.01.3mx23 is not (yet) available 
(Impossibile connettersi a mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 mx-packageinstaller 
amd64 24.1 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 mx-tweak amd64 
24.01.01mx23 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 system-keyboard-qt 
amd64 24.01.01mx23 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)


System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 
12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID= ro 
quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: 
MX-23.1_KDE_x64 Libretto
July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Vmware System: VMware product: VMware Virtual Platform v: N/A serial: 

Chassis: No Enclosure type: 1 serial: 
  Mobo: Intel model: 440BX Desktop Reference Platform serial:  BIOS: Phoenix
v: 6.00 date: 11/12/2020
CPU:
  Info: model: AMD Ryzen 5 7530U with Radeon Graphics bits: 64 type: MCP arch: 
Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 
(25) model-id: 0x50 (80)
stepping: 0 microcode: 0x
  Topology: cpus: 1x cores: 2 smt:  cache: L1: 128 KiB desc: 
d-2x32 KiB; i-2x32 KiB
L2: 1024 KiB desc: 2x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1996 min/max: N/A cores: 1: 1996 2: 1996 bogomips: 7984
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer 
sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, 
RSB filling,
PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: 
Virtual-1
empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, 
Virtual-8
bus-ID: 00:0f.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: 
kwin_x11 driver: X:
loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx 
display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") 
s-diag: 582mm (22.93")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1920x1080 hz: 60 size: N/A modes: 
max: 1920x1080
min: 640x480
  API: OpenGL v: 4.5 Mesa 23.1.2-1~mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 
bits)
direct-render: Yes
Audio:
  Device-1: Ensoniq ES1371/E

Bug#1060383: ERROR UPDATING

[Roberto Zapetti]

Package: Discover
Versione: 5.27.5


Hi to all,
I have been experiencing errors when updating the system for a few days now.
I attach an info.txt file of my system.

thank you
Roberto

Scaricamento del pacchetto non riuscito:E: 
http://mxrepo.com/mx/repo bookworm/main amd64 ddm-mx all 23.12.02 is not 
(yet) available (Impossibile connettersi a mxrepo.com:443 
(70.40.214.183). - connect (111: Connessione rifiutata))
E: http://mxrepo.com/mx/repo bookworm/main amd64 firefox amd64 
121.0.1~mozillabinaries-1mx23+1 is not (yet) available (Impossibile 
connettersi a mxrepo.com:https:)
E: http://mxrepo.com/mx/repo bookworm/main amd64 firefox-l10n-xpi-it 
amd64 121.0.1~mozillabinaries-1mx23+1 is not (yet) available 
(Impossibile connettersi a mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 formatusb amd64 
24.01.01 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: http://mxrepo.com/mx/repo bookworm/main amd64 lo-main-helper all 
24.01.3mx23 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: http://mxrepo.com/mx/repo bookworm/main amd64 
mx-packageinstaller-pkglist all 24.01.3mx23 is not (yet) available 
(Impossibile connettersi a mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 mx-packageinstaller 
amd64 24.1 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 mx-tweak amd64 
24.01.01mx23 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)
E: https://mxrepo.com/mx/repo bookworm/main amd64 system-keyboard-qt 
amd64 24.01.01mx23 is not (yet) available (Impossibile connettersi a 
mxrepo.com:https:)


System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 
12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID= ro 
quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: 
MX-23.1_KDE_x64 Libretto
July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Vmware System: VMware product: VMware Virtual Platform v: N/A serial: 

Chassis: No Enclosure type: 1 serial: 
  Mobo: Intel model: 440BX Desktop Reference Platform serial:  BIOS: Phoenix
v: 6.00 date: 11/12/2020
CPU:
  Info: model: AMD Ryzen 5 7530U with Radeon Graphics bits: 64 type: MCP arch: 
Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 
(25) model-id: 0x50 (80)
stepping: 0 microcode: 0x
  Topology: cpus: 1x cores: 2 smt:  cache: L1: 128 KiB desc: 
d-2x32 KiB; i-2x32 KiB
L2: 1024 KiB desc: 2x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1996 min/max: N/A cores: 1: 1996 2: 1996 bogomips: 7984
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer 
sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, 
RSB filling,
PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: 
Virtual-1
empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, 
Virtual-8
bus-ID: 00:0f.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: 
kwin_x11 driver: X:
loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx 
display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") 
s-diag: 582mm (22.93")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1920x1080 hz: 60 size: N/A modes: 
max: 1920x1080
min: 640x480
  API: OpenGL v: 4.5 Mesa 23.1.2-1~mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 
bits)
direct-render: Yes
Audio:
  Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371 v: 
kernel
bus-ID: 02:03.0 chip-ID: 1274:1371 class-ID: 0401
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: 
active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack 
type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82371AB/EB/MB PIIX4 ACPI vendor: VMware Virtual Machine type: 
network bridge
driver: N/A modules: i2c_piix4 port: N/A bus-ID: 00:07.3 chip-ID: 8086:7113 
class-ID: 0680
  Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single 
Port driver: e1000
v: kernel port: 2000 bus-ID: 02:01.0 chip-ID: 8086:100f class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 
Drives:
 

Wrong error message in debian-installer

[Antonio Greco]

Hello,

I made a stupid error while partitioning: I created a new partition
whose size was 50 MB (instead of 50 GB). I did dot notice the error
and went on with the installation process. Suddenly the installation
stopped claiming that

"package util-linux_2.38.1-5+b1_amd64.deb is corrupt".

The reason was simply that there was no space left on the device, and
there was no room enough to accommodate that package. The package was
not corrupt. I went crazy for one day, until I finally noticed my error.

I strongly recommend that when there is no space left on the device,
the debian-installer raise the usual error message

"No space left on device"

instead of "package xxx is corrupt". I hope this comment is useful.

Best regards

Antonio Greco



- Messaggio inoltrato da Antonio Greco  -
   Data: Wed, 20 Dec 2023 22:25:09 +0100
 Da: Antonio Greco 
Oggetto: iso image corrupted?
  A: ow...@bugs.debian.org

Hello,

it seems that package util-linux_2.38.1-5+b1_amd64.deb
included in

https://gemmei.ftp.acc.umu.se/debian-cd/current/amd64/iso-cd/debian-12.4.0-amd64-netinst.iso

is corrupted (see attachment). Can you please notify this
to the maintainer?

Best regards,

Antonio Greco

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Marc Haber]

On Fri, Sep 08, 2023 at 09:37:53PM +0200, Philip Hands wrote:
> If you'd like to test the result of building that merge request into a
> mini.iso, you can give it a go with this:
> 
> https://salsa.debian.org/philh/grub-installer/-/jobs/4675763/artifacts/file/debian/output/debian-202306XX+salsaci+20230908+294-amd64-gtkmini.iso

I can confirm that this .iso installs fine on both BIOS and EFI VMs in
libvirt and kvm on amd64.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Philip Hands]

Hi Edward,

Edward Little  writes:

> Please remove the following email address:  e.little...@gmail.com

I guess that you're subscribed to the debian-boot mailing list.

If so, you'll have seen copies of the mails seen here:

  https://lists.debian.org/debian-boot/2023/09/threads.html

in which case you can unsubscribe here:

  https://lists.debian.org/debian-boot/

Since I'm looking at that page, I've done that for you (you should
already have a confirmation mail)

BTW every email forwarded by the debian mailing list system includes a
footer with links to unsubscription instructions, just in case you're on
other lists you don't want to be on.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Edward Little]

Please remove the following email address:  e.little...@gmail.com

On Fri, Sep 8, 2023 at 3:45 PM Philip Hands  wrote:

> Marc Haber  writes:
>
> > On Fri, Sep 08, 2023 at 03:48:25PM +0200, Pascal Hambourg wrote:
> >> On 08/09/2023 at 13:56, Marc Haber wrote :
> >> > I tried installing sid from mini.iso into a libvirt/qemu/kvm VM with
> >> > BIOS "firmware", choosing mainly default values, and ended up with the
> >> > system logging "grub-installer: error: Error creating
> >> > /target/sys/firmware/efi/efivars" and an error message "Failed to
> mount
> >> > /target/proc, Mounting the proc file system on /target/proc failed".
> >>
> >> This issue has been discussed in #1031183 starting from
> >> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031183#17>
> >> (it is a different issue from the original bug report, so a separate bug
> >> should have been filed) and a merge request is in progress.
> >> <
> https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/19
> >
> >
> > Loooks like the same issue, happens also with a regular netinst install.
>
> If you'd like to test the result of building that merge request into a
> mini.iso, you can give it a go with this:
>
>
> https://salsa.debian.org/philh/grub-installer/-/jobs/4675763/artifacts/file/debian/output/debian-202306XX+salsaci+20230908+294-amd64-gtkmini.iso
>
> which was built in this pipeline:
>
> https://salsa.debian.org/philh/grub-installer/-/pipelines/577147
>
> where you will find links to the commit & branch that's from.
>
> Cheers, Phil.
> --
> Philip Hands -- https://hands.com/~phil
>

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Philip Hands]

Marc Haber  writes:

> On Fri, Sep 08, 2023 at 03:48:25PM +0200, Pascal Hambourg wrote:
>> On 08/09/2023 at 13:56, Marc Haber wrote :
>> > I tried installing sid from mini.iso into a libvirt/qemu/kvm VM with
>> > BIOS "firmware", choosing mainly default values, and ended up with the
>> > system logging "grub-installer: error: Error creating
>> > /target/sys/firmware/efi/efivars" and an error message "Failed to mount
>> > /target/proc, Mounting the proc file system on /target/proc failed".
>> 
>> This issue has been discussed in #1031183 starting from
>> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031183#17>
>> (it is a different issue from the original bug report, so a separate bug
>> should have been filed) and a merge request is in progress.
>> <https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/19>
>
> Loooks like the same issue, happens also with a regular netinst install.

If you'd like to test the result of building that merge request into a
mini.iso, you can give it a go with this:

https://salsa.debian.org/philh/grub-installer/-/jobs/4675763/artifacts/file/debian/output/debian-202306XX+salsaci+20230908+294-amd64-gtkmini.iso

which was built in this pipeline:

https://salsa.debian.org/philh/grub-installer/-/pipelines/577147

where you will find links to the commit & branch that's from.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Marc Haber]

On Fri, Sep 08, 2023 at 03:48:25PM +0200, Pascal Hambourg wrote:
> On 08/09/2023 at 13:56, Marc Haber wrote :
> > I tried installing sid from mini.iso into a libvirt/qemu/kvm VM with
> > BIOS "firmware", choosing mainly default values, and ended up with the
> > system logging "grub-installer: error: Error creating
> > /target/sys/firmware/efi/efivars" and an error message "Failed to mount
> > /target/proc, Mounting the proc file system on /target/proc failed".
> 
> This issue has been discussed in #1031183 starting from
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031183#17>
> (it is a different issue from the original bug report, so a separate bug
> should have been filed) and a merge request is in progress.
> <https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/19>

Loooks like the same issue, happens also with a regular netinst install.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Pascal Hambourg]

On 08/09/2023 at 13:56, Marc Haber wrote :


I tried installing sid from mini.iso into a libvirt/qemu/kvm VM with
BIOS "firmware", choosing mainly default values, and ended up with the
system logging "grub-installer: error: Error creating
/target/sys/firmware/efi/efivars" and an error message "Failed to mount
/target/proc, Mounting the proc file system on /target/proc failed".


This issue has been discussed in #1031183 starting from
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031183#17>
(it is a different issue from the original bug report, so a separate bug 
should have been filed) and a merge request is in progress.

<https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/19>

Bug#1051468: cannot install BIOS machine with mini.iso, error creating /target/sys/firmware/efi/efivars

[Marc Haber]

Source: debian-installer
Version: 20230607+deb12u1
Severity: minor

Hi,

I tried installing sid from mini.iso into a libvirt/qemu/kvm VM with
BIOS "firmware", choosing mainly default values, and ended up with the
system logging "grub-installer: error: Error creating
/target/sys/firmware/efi/efivars" and an error message "Failed to mount
/target/proc, Mounting the proc file system on /target/proc failed".

See attached screenshots.

Sadly, the system doesn't get far enough to pull the entire log.

Greetings
Marc


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-security'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.12-zgws1 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Roland Clobus]

Follow-up redirected to debian-live

Hello Sakkra Billa,

On 18/08/2023 15:27, Sakkra Billa wrote:
I followed the tutorial from: 
https://www.willhaley.com/blog/custom-debian-live-environment/ 


That tutorial is a summary/excerpt from 
https://live-team.pages.debian.net/live-manual/ to which it also points.


> ... Please guide me that where did i
> go wrong and how can i make my live iso installable.

I would recommend to use the live-build tool instead of doing each step 
manually. [1]


The official Debian 12 (Bookworm) live images are generated by 
live-build. If you want to extend your local version, I would recommend 
you to read [2] as well.


With kind regards,
Roland Clobus

[1] Disclaimer: I'm one of the maintainers of live-build, so I'm biased
[2] https://wiki.debian.org/ReproducibleInstalls/LiveImages


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Thomas Schmitt]

Hi,

Sakkra Billa wrote:
> In order to
> install it on my VM I installed calamares, calamares-settings-debian and
> rsync

My advise from debian-user to ask at debian-boot was rather a reply to
your other statement:

Sakkra Billa wrote:
> > I tried debian di too but wasn't successful in that
> > either it said that the kernel version for live and installer
> > were not the same.


Have a nice day :)

Thomas

Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Sakkra Billa]

I followed the tutorial from:
https://www.willhaley.com/blog/custom-debian-live-environment/ to make a
live custom debian 12 image. In order to install it on my VM I installed
calamares, calamares-settings-debian and rsync . The live image works
perfectly and the installation also finishes without errors but when i
reboot my VM into the installed environment, it boots into grub minimal
bash line editing mode. On typing boot it says "load the kernel first".* I
did not change any of the calamares settings everything is default*. I
guess that i am missing some important files or applications required for
installation. Please guide me that where did i go wrong and how can i make
my live iso installable.
Thanks in advance,

Bug#1040727: The Installation system doesn't check available free disk space, either provides an uninformative error message or completes installation "successfully" with a resulting non-working syste

[Super Veridical]

Package: installation-reports

Boot method: "-cdrom" key in qemu with OVMF firmware
Image version: 
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.0.0-amd64-kde.iso
Date: Jul 8 2023

Machine: ASUS ROG STRIX B650E-F GAMING WIFI
Processor: AMD Ryzen 9 7950X, "-cpu host -smp 6" flags in qemu
Memory: "-m 6000" flag in qemu
Partitions: "Guided partition" method during the installation with a
single root partition.

The entire qemu command:
qemu-system-x86_64 -nic user,model=virtio-net-pci -cpu host -smp 6 -m
6000 -enable-kvm -device virtio-vga-gl -display gtk,gl=on -drive
file=/usr/share/edk2-ovmf/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on
-drive if=pflash,format=raw,file=OVMF_VARS.fd -drive
format=raw,file=sda.img,if=virtio -drive
format=raw,file=sdb.img,if=virtio -cdrom
~/debian-live-12.0.0-amd64-kde.iso

qemu --version output: "QEMU emulator version 7.2.3"
Host OS: Gentoo Linux

With "qemu-img create -f raw -o size=6G sda.img" i.e. 6GB virtual hdd:

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[E]

proceeds to the system installation step despite not having enough
space in the root partition, fails with an uninformative error message
"the step that failed : install the system", in all three installation
modes (livecd, graphical, text)

with "qemu-img create -f raw -o size=12G sda.img" (should work
according to this documentation entry
https://www.debian.org/releases/stable/amd64/ch03s04.en.html):

Overall install:[E]

Installs seemingly successfully, but shows black screen after login
due to completely exhausted disk space on the root partition. "Avail
0" in df output. I.e. installation process exhausted disk space but
completed installation without an apparent error.

with "qemu-img create -f raw -o size=22G sda.img" works perfectly fine.

Bug#815187: Bug debian-Installer (bookworm): Installation grub fails without error message

[Pascal Hambourg]

On 27/06/2023 at 17:55, CJ Kucera wrote:


Just popping in to say that I've run into this exact problem on Debian
12 (Bookworm) as well.  I'm installing onto a system with two drives in
a raid1 config, so the installer presents a dialog with these choices
for installing GRUB:

 - Enter device manually
 - /dev/sda  (ata-VBOX_HARDDISK_VBcb2c038a-37db3d41)
 - /dev/sdb  (ata-VBOX_HARDDISK_VB9084690a-b32386db)

If choose "Enter device manually", and type in "/dev/sda", I get two
statuses shown on the next progress bar:

 1. running "grub-install /dev/sda"
 2. running "update-grub"

If I instead pick the dropdown entry for "/dev/sda", the installer skips
the "grub-install" step and goes right to "update-grub," which leaves the
freshly-installed OS in an unbootable state.

Interestingly, if I *manually* type in /dev/sda (which installs GRUB
properly) and then go back and re-install GRUB using the dropdown entry,
from that point forward the dropdown selection works and I get the
"grub-install" step properly.


This looks like bug #1035096 (patch available but came too late for 
bookworm release).

Bug#815187: Bug debian-Installer (bookworm): Installation grub fails without error message

[CJ Kucera]

 280278   TLB shootdowns
/proc/interrupts: TRM:  0  0   Thermal event interrupts
/proc/interrupts: THR:  0  0   Threshold APIC interrupts
/proc/interrupts: DFR:  0      0   Deferred Error APIC interrupts
/proc/interrupts: MCE:  0  0   Machine check exceptions
/proc/interrupts: MCP:  2  2   Machine check polls
/proc/interrupts: ERR:  0
/proc/interrupts: MIS:  0
/proc/interrupts: PIN:  0  0   Posted-interrupt notification 
event
/proc/interrupts: NPI:  0  0   Nested posted-interrupt event
/proc/interrupts: PIW:  0  0   Posted-interrupt wakeup event
/proc/meminfo: MemTotal:4009564 kB
/proc/meminfo: MemFree: 2139072 kB
/proc/meminfo: MemAvailable:3265508 kB
/proc/meminfo: Buffers:   75016 kB
/proc/meminfo: Cached:  1530828 kB
/proc/meminfo: SwapCached:0 kB
/proc/meminfo: Active:   478956 kB
/proc/meminfo: Inactive:1170364 kB
/proc/meminfo: Active(anon): 215672 kB
/proc/meminfo: Inactive(anon):   159508 kB
/proc/meminfo: Active(file): 263284 kB
/proc/meminfo: Inactive(file):  1010856 kB
/proc/meminfo: Unevictable:   0 kB
/proc/meminfo: Mlocked:   0 kB
/proc/meminfo: SwapTotal:   1048568 kB
/proc/meminfo: SwapFree:1048568 kB
/proc/meminfo: Zswap: 0 kB
/proc/meminfo: Zswapped:  0 kB
/proc/meminfo: Dirty: 77684 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 43524 kB
/proc/meminfo: Mapped:24720 kB
/proc/meminfo: Shmem:331704 kB
/proc/meminfo: KReclaimable: 117904 kB
/proc/meminfo: Slab: 146204 kB
/proc/meminfo: SReclaimable: 117904 kB
/proc/meminfo: SUnreclaim:28300 kB
/proc/meminfo: KernelStack:1652 kB
/proc/meminfo: PageTables:  928 kB
/proc/meminfo: SecPageTables: 0 kB
/proc/meminfo: NFS_Unstable:  0 kB
/proc/meminfo: Bounce:0 kB
/proc/meminfo: WritebackTmp:  0 kB
/proc/meminfo: CommitLimit: 3053348 kB
/proc/meminfo: Committed_AS: 413172 kB
/proc/meminfo: VmallocTotal:   34359738367 kB
/proc/meminfo: VmallocUsed:   22036 kB
/proc/meminfo: VmallocChunk:  0 kB
/proc/meminfo: Percpu:  536 kB
/proc/meminfo: HardwareCorrupted: 0 kB
/proc/meminfo: AnonHugePages: 32768 kB
/proc/meminfo: ShmemHugePages:0 kB
/proc/meminfo: ShmemPmdMapped:0 kB
/proc/meminfo: FileHugePages: 0 kB
/proc/meminfo: FilePmdMapped: 0 kB
/proc/meminfo: HugePages_Total:   0
/proc/meminfo: HugePages_Free:0
/proc/meminfo: HugePages_Rsvd:0
/proc/meminfo: HugePages_Surp:0
/proc/meminfo: Hugepagesize:   2048 kB
/proc/meminfo: Hugetlb:   0 kB
/proc/meminfo: DirectMap4k:   73664 kB
/proc/meminfo: DirectMap2M: 4120576 kB
/proc/bus/input/devices: I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
/proc/bus/input/devices: N: Name="AT Translated Set 2 keyboard"
/proc/bus/input/devices: P: Phys=isa0060/serio0/input0
/proc/bus/input/devices: S: Sysfs=/devices/platform/i8042/serio0/input/input0
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=sysrq kbd leds event0 
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=120013
/proc/bus/input/devices: B: KEY=40200 3803078f800d001 fedfffef 
fffe
/proc/bus/input/devices: B: MSC=10
/proc/bus/input/devices: B: LED=7
/proc/bus/input/devices: 
/proc/bus/input/devices: I: Bus=0019 Vendor= Product=0006 Version=
/proc/bus/input/devices: N: Name="Video Bus"
/proc/bus/input/devices: P: Phys=LNXVIDEO/video/input0
/proc/bus/input/devices: S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input2
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=kbd event1 
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=3
/proc/bus/input/devices: B: KEY=3e000b 0 0 0
/proc/bus/input/devices: 
/proc/bus/input/devices: I: Bus=0011 Vendor=0002 Product=0006 Version=
/proc/bus/input/devices: N: Name="ImExPS/2 Generic Explorer Mouse"
/proc/bus/input/devices: P: Phys=isa0060/serio1/input0
/proc/bus/input/devices: S: Sysfs=/devices/platform/i8042/serio1/input/input3
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=mouse0 event2 
/proc/bus/input/devices: B: PROP=1
/proc/bus/input/devices: B: EV=7
/proc/bus/input/devices: B: KEY=1f 0 0 0 0
/proc/bus/input/devices: B: REL=143
/proc/bus/input/devices: 
/proc/asound/cards:  0 [I82801AAICH]: ICH - Intel 82801AA-ICH
/proc/asound/cards:   Intel 82801AA-ICH with AD1980 at irq 
21
dmidecode: # dmidecode 3.4
dmidecode: Getting SMBIOS data from sysfs.
dmidecode: SMBIOS 2.5 present.
dmidecode: 10 structures occupying 455 bytes.
dmidecode: Table at 0x000

Bug#815187: Bug debian-Installer (bookworm): Installation grub fails without error message

[CJ Kucera]

François POLASTRON wrote:
> I found a big bug in debian-Installer on a "BIOS Legacy" computer
> When trying to force grub installation in other device than primary disk, in 
> graphical mode the menu lets the user choose the device:
> /dev/sda
> /dev/sdb
> ...
> But when we choose one of a device debian-Installer don't install GRUB 
> WITHOUT 
> ERROR MESSAGE. 
> 
> In fact we must enter the device with the keyboard taping "/dev/sda"... to 
> contourn the bug. 

Good morning!

Just popping in to say that I've run into this exact problem on Debian
12 (Bookworm) as well.  I'm installing onto a system with two drives in
a raid1 config, so the installer presents a dialog with these choices
for installing GRUB:

- Enter device manually
- /dev/sda  (ata-VBOX_HARDDISK_VBcb2c038a-37db3d41)
- /dev/sdb  (ata-VBOX_HARDDISK_VB9084690a-b32386db)

If choose "Enter device manually", and type in "/dev/sda", I get two
statuses shown on the next progress bar:

1. running "grub-install /dev/sda"
2. running "update-grub"

If I instead pick the dropdown entry for "/dev/sda", the installer skips
the "grub-install" step and goes right to "update-grub," which leaves the
freshly-installed OS in an unbootable state.

Interestingly, if I *manually* type in /dev/sda (which installs GRUB
properly) and then go back and re-install GRUB using the dropdown entry,
from that point forward the dropdown selection works and I get the
"grub-install" step properly.

On a system which didn't get the grub-install step (so is unbootable), I
can at least boot into recovery mode and reinstall GRUB from there,
which requires just typing in /dev/sda and fixes things up.

I'm attaching the contents of /var/log from the installer after choosing
the menu item version (which skips grub-install), though I don't see
anything too obviously useful in there myself.

Let me know if I can provide any more info.

Cheers,
CJ


syslog.gz
Description: application/gzip


partman.gz
Description: application/gzip


firmware-summary.gz
Description: application/gzip

Bug#1032852: Error message clue:

[Charles Curley]

On Wed, 29 Mar 2023 08:41:43 +0200 Pascal Hambourg
 wrote:
> Hello,
> 

> 
> Already fixed in hw-detect 1.155:
> * Fix files removal for non-accepted firmware packages (See:
> #1032377).
> 
> 

I can confirm that, when running with no preseed, I now see the license
agreement and can accept it. My preseed file has the following:


# 
https://preseed.debian.net/debian-preseed/bookworm/amd64-non-free-firmware-full.txt
d-i firmware-ipw2x00/license/accepted boolean true

so I would not expect to see the license agreement. If I read the
syslog correctly, the preseeded license agreement accepted was handled
correctly:

May 22 18:16:52 debconf: --> SET firmware-ipw2x00/license/accepted true
May 22 18:16:52 debconf: <-- 10 firmware-ipw2x00/license/accepted doesn't exist
May 22 18:16:52 debconf: --> REGISTER debian-installer/dummy 
firmware-ipw2x00/license/accepted
May 22 18:16:52 debconf: <-- 0
May 22 18:16:52 debconf: --> SET firmware-ipw2x00/license/accepted true
May 22 18:16:52 debconf: <-- 0 value set
May 22 18:16:52 debconf: --> SUBST firmware-ipw2x00/license/accepted ID 
firmware-ipw2x00/license/accepted
May 22 18:16:52 debconf: Adding [ID] -> [firmware-ipw2x00/license/accepted]
May 22 18:16:52 debconf: <-- 0
May 22 18:16:52 debconf: --> FSET firmware-ipw2x00/license/accepted seen true


I did three installations at least as far as the WiFi business and have
the logs from them should anyone wish to see them.

Alas, there are other problems, but this seems to be fixed.

Thank you.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Processed (with 1 error): brcmfmac: requested firmware filename inconsistent with linux-firmware.git on non-devicetree systems

[Debian Bug Tracking System]

Processing control commands:

> unmerge 1029843 1030519
Unknown command or malformed arguments to command.

> reassign 1029843 src:linux
Bug #1029843 [hw-detect] hw-detect: firmware file path handling is fragile
Bug #1030519 [hw-detect] hw-detect: firmware file path handling is fragile
Bug reassigned from package 'hw-detect' to 'src:linux'.
Bug reassigned from package 'hw-detect' to 'src:linux'.
No longer marked as found in versions hw-detect/1.154.
No longer marked as found in versions hw-detect/1.154.
Ignoring request to alter fixed versions of bug #1029843 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1030519 to the same values 
previously set
> retitle 1029843 brcmfmac: requested firmware filename
Bug #1029843 [src:linux] hw-detect: firmware file path handling is fragile
Bug #1030519 [src:linux] hw-detect: firmware file path handling is fragile
Changed Bug title to 'brcmfmac: requested firmware filename' from 'hw-detect: 
firmware file path handling is fragile'.
Changed Bug title to 'brcmfmac: requested firmware filename' from 'hw-detect: 
firmware file path handling is fragile'.

-- 
1029843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029843
1030519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Cyril Brulebois]

Hi Timo!

Timo Aaltonen  (2023-05-02):
> Hi, fine by me!

Thanks, uploaded.

I'll keep an eye on it, and request an unblock (letting debian-x@ know via
X-Debbugs-Cc) once I've checked britney doesn't report any red flags.

It's going to be on two different radars of mine anyway:
 - https://d-i.debian.org/testing-summary.html#udebs
 - https://salsa.debian.org/installer-team/debian-installer/-/issues/1

So I shouldn't forget about it…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xserver-xorg-core-udeb 2:21.1.1-1
Bug #1035014 [installation-reports] installation-reports: Graphical installer 
has Xorg "no screens found" error
Bug reassigned from package 'installation-reports' to 'xserver-xorg-core-udeb'.
Ignoring request to alter found versions of bug #1035014 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1035014 to the same values 
previously set
Bug #1035014 [xserver-xorg-core-udeb] installation-reports: Graphical installer 
has Xorg "no screens found" error
Marked as found in versions xorg-server/2:21.1.1-1.
> affects -1 debian-installer
Bug #1035014 [xserver-xorg-core-udeb] installation-reports: Graphical installer 
has Xorg "no screens found" error
Added indication that 1035014 affects debian-installer

-- 
1035014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Cyril Brulebois]

Control: reassign -1 xserver-xorg-core-udeb 2:21.1.1-1
Control: affects -1 debian-installer

Hello debian-x,

Cyril Brulebois  (2023-04-27):
> Tracked down to 9c81b8f5b5 upstream:
>   https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5
> 
> Flipping the switch and wrapping it up in a netboot mini.iso
> debian-installer build led to a successful test (with amd64) by Keith.
> We'll try and confirm the same happens with arm64.
> 
> If you're happy with that approach, feel free to reassign to the udeb,
> and check the udeb-modesetting branch in xorg-server:
>   
> https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting

Any objections to my merging/uploading this?


> I don't have access to VirtualBox right now, but we've had reports of
> failures there as well, maybe that's the same kind of things.

For completeness:

A friend of mine tested all 3 available options (VBoxVGA, VMSVGA, and
VBoxSVGA) in VirtualBox, on both Windows and Apple hosts, and the
graphical installer worked fine for him in all cases, so it looks like
the VirtualBox reports we've received are about a different issue (and
we're lacking feedback at the moment).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed (with 1 error): Re: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 hw-detect
Bug #1029843 [live-boot] live-boot: Devices Requiring Firmware: multiple 
requested files in single line overlapping / special characters
Bug reassigned from package 'live-boot' to 'hw-detect'.
Ignoring request to alter found versions of bug #1029843 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1029843 to the same values 
previously set
> merge -1 1030519
Bug #1029843 [hw-detect] live-boot: Devices Requiring Firmware: multiple 
requested files in single line overlapping / special characters
Bug #1029843 [hw-detect] live-boot: Devices Requiring Firmware: multiple 
requested files in single line overlapping / special characters
Marked as found in versions hw-detect/1.154.
Bug #1030519 [hw-detect] check-missing-firmware: patch for files with space 
characters, mediamount and more (with code)
Merged 1029843 1030519
> affects -1 raspi-firmware
Bug #1029843 [hw-detect] live-boot: Devices Requiring Firmware: multiple 
requested files in single line overlapping / special characters
Bug #1030519 [hw-detect] check-missing-firmware: patch for files with space 
characters, mediamount and more (with code)
Added indication that 1029843 affects raspi-firmware
Added indication that 1030519 affects raspi-firmware
> title -1  check-missing-firmware: patch for files with space characters, 
> mediamount and more (with code)
Unknown command or malformed arguments to command.


-- 
1029843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029843
1030519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[kt programs]

On Thu Apr 27, 2023 at 10:39 PM +08, Cyril Brulebois wrote:
> Control: tag -1 patch
>
> Hi Keith and X team,
>
> and thanks for your report.
>
> Keith Toh  (2023-04-27):
> > Image version: 
> > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
> >  (2023-04-24 23:09)
>
> For the avoidance of doubt: same story with amd64.
>
> > Machine: UTM QEMU VM
> > 
> > When booting the installer in Graphical install mode, Xorg repeatedly
> > errors saying "no screens found". Based on the Xorg log, it is failing
> > to load the modesetting driver, as the file
> > /usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
> > dropped from xerver-xorg-core-udeb between bullseye and bookworm.
> > 
> > >From kibi on #debian-boot (https://paste.debian.net/1278647/):
> > xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
> > xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO
>
> Tracked down to 9c81b8f5b5 upstream:
>   https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5
>
> Flipping the switch and wrapping it up in a netboot mini.iso
> debian-installer build led to a successful test (with amd64) by Keith.
> We'll try and confirm the same happens with arm64.

Can confirm that an arm64 mini.iso with the same fixes works.

> If you're happy with that approach, feel free to reassign to the udeb,
> and check the udeb-modesetting branch in xorg-server:
>   
> https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting
>
> I don't have access to VirtualBox right now, but we've had reports of
> failures there as well, maybe that's the same kind of things.
>
>
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Cyril Brulebois]

Control: tag -1 patch

Hi Keith and X team,

and thanks for your report.

Keith Toh  (2023-04-27):
> Image version: 
> http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
>  (2023-04-24 23:09)

For the avoidance of doubt: same story with amd64.

> Machine: UTM QEMU VM
> 
> When booting the installer in Graphical install mode, Xorg repeatedly
> errors saying "no screens found". Based on the Xorg log, it is failing
> to load the modesetting driver, as the file
> /usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
> dropped from xerver-xorg-core-udeb between bullseye and bookworm.
> 
> >From kibi on #debian-boot (https://paste.debian.net/1278647/):
> xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
> xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO

Tracked down to 9c81b8f5b5 upstream:
  https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5

Flipping the switch and wrapping it up in a netboot mini.iso
debian-installer build led to a successful test (with amd64) by Keith.
We'll try and confirm the same happens with arm64.

If you're happy with that approach, feel free to reassign to the udeb,
and check the udeb-modesetting branch in xorg-server:
  
https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting

I don't have access to VirtualBox right now, but we've had reports of
failures there as well, maybe that's the same kind of things.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #1035014 [installation-reports] installation-reports: Graphical installer 
has Xorg "no screens found" error
Added tag(s) patch.

-- 
1035014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Keith Toh]

Package: installation-reports
Severity: important

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
 (2023-04-24 23:09)

Machine: UTM QEMU VM


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
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 booting the installer in Graphical install mode, Xorg repeatedly
errors saying "no screens found". Based on the Xorg log, it is failing
to load the modesetting driver, as the file
/usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
dropped from xerver-xorg-core-udeb between bullseye and bookworm.

>From kibi on #debian-boot (https://paste.debian.net/1278647/):
xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230423-02:07:34"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08) 
aarch64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge 
[1b36:0008]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: 00:01.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:02.0 Display controller [0380]: Red Hat, Inc. Virtio GPU 
[1af4:1050] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: 00:04.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 
Host Controller [1033:0194] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:05.0 USB controller [0c03]: Red Hat, Inc. QEMU XHCI Host 
Controller [1b36:000d] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:06.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:07.0 Communication controller [0780]: Red Hat, Inc. Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:08.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG 
[1af4:1005]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0004]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
usb-list: 
usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 6.1.0-7-arm64 xhci-hcd
u

Re: d-i bug: spurious checksum error?

[Charles Curley]

On Wed, 19 Apr 2023 12:20:56 +0200
Philip Hands  wrote:

> According to the log, you actually invoked it with file=preseed.cfg:
> 
>   Kernel command line: BOOT_IMAGE=/install.386/vmlinuz priority=low
> vga=788 initrd=/install.386/gtk/initrd.gz ---  auto file=preseed.cfg
> DEBCONF_DEBUG=developer


Aha! Thank you for that catch. I re-ran the installation, double
checking my command line, and did not get that error.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


pgpuqOBX6eGC_.pgp
Description: OpenPGP digital signature

Re: d-i bug: spurious checksum error?

[Philip Hands]

Charles Curley  writes:

> I started a test installation with a preseed file. I launched d-i with
> the following command line:
>
> expertgui auto file=/media/preseed.cfg DEBCONF_DEBUG=developer

According to the log, you actually invoked it with file=preseed.cfg:

  Kernel command line: BOOT_IMAGE=/install.386/vmlinuz priority=low vga=788 
initrd=/install.386/gtk/initrd.gz ---  auto file=preseed.cfg 
DEBCONF_DEBUG=developer

which appears to have confused the installer into looking for it in
'/usr/lib/fetch-url//preseed.cfg':

  /bin/fetch-url: .: line 35: can't open '/usr/lib/fetch-url//preseed.cfg': No 
such file or directory

which isn't exactly helpful, and it certainly could have done better
when telling you what was wrong, but it's not at all clear that it was
going to be able to guess that you meant '/media/preseed.cfg' when you
said 'preseed.cfg'.

So, I'd say there's perhaps a bug in what it should guess the user meant
when specifying a relative path as a value for preseed/file, but
probably more likely it should just reject a relative path at that point
with an error about it needing a path that is somehow anchored.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Re: d-i bug: spurious checksum error?

[john doe]

On 4/18/23 23:52, Charles Curley wrote:

I started a test installation with a preseed file. I launched d-i with
the following command line:

expertgui auto file=/media/preseed.cfg DEBCONF_DEBUG=developer

When I told d-i to get the preseed file, it replied with a screen about
an incorrect checksum for the preseed file. The screen showed a
checksum string of "". (I took a screen shot of the error message, then
failed to preserve it. Sorry.)

I had recently added several items to my preseed file, one of which was:


# The installer can optionally verify checksums of preconfiguration files
# before using them. Currently only md5sums are supported, list the md5sums
# in the same order as the list of files to include.
#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d

I deleted those lines entirely, and re-ran the installation. I did not
get the checksum error on the second try, and the preseed file was
properly located and run.

Did I hit a bug? I doubt it is the way the last line is commented out,
because there are plenty of other lines that are similarly commented
out (no space between the # and the d).

syslog and preseed.cfg files are attached.





Unless I'm missing something, the file is to be checksummed before the
content is available to d-i, the lines would simply be  there to
document what the installer can do.

I would assume that it would work as kernel boot parameter.

--
John Doe

Re: Bug#1034072: Wireless interfaces trigger error messages about invalid WPA passphrases gets stuck during install

[Reto Schneider]

On 08.04.23 01:15, Cyril Brulebois wrote:

Adjusting title since I suppose you spotted #1031643 and forgot to
change the title when filing this bug about something else.


Should have been "interface=auto", not "hostname=auto" in the subject. 
Thanks for improving it.



Possible workarounds:
  - Remove Wi-Fi cards from machine during installation
  - Specify interface to be used (e.g. interface=enp2s0)


Disable firmware support:
  - https://www.debian.org/releases/bookworm/amd64/ch02s02.en.html


Can confirm, passing firmware=never works too.

Kind regards,
Reto

Processed: Re: Bug#1034072: Wireless interfaces trigger error messages about invalid WPA passphrases gets stuck during install

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Wireless interfaces trigger error messages about invalid WPA 
> passphrases
Bug #1034072 [installation-reports] installation-reports: Preseed with 
hostname=auto gets stuck during install
Changed Bug title to 'Wireless interfaces trigger error messages about invalid 
WPA passphrases' from 'installation-reports: Preseed with hostname=auto gets 
stuck during install'.

-- 
1034072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034072: Wireless interfaces trigger error messages about invalid WPA passphrases gets stuck during install

[Cyril Brulebois]

Control: retitle -1 Wireless interfaces trigger error messages about invalid 
WPA passphrases

Adjusting title since I suppose you spotted #1031643 and forgot to
change the title when filing this bug about something else.

Reto Schneider  (2023-04-08):
> Until in Bullseye and Bookworm Alpha 1, passing the arguments ...
> 
> /install.amd/vmlinuz auto=true priority=critical vga=off interface=auto
> initrd=/install.amd/initrd.gz --- console=ttyS0,115200n8
> 
> ... boots the installer and progresses on its own up to the point where it
> needs to ask about the location of the preseed file ("Download debconf
> preconfiguration file").
> 
> For Bookworm Alpha 2 and RC1 however, the installer, during the detection of
> network link on each interface, once testing the Wi-Fi ones, complains about
> the WPA passphrase being invalid:
> 
> [!]! Configure the network
> Invalid passphrase
> The WPA/WPA2 PSK passphrase was either too long (more than 64 characters) or
> too short (less than 8 characters).
> 
> I can either chose "Continue" (presents the same error message again) or back
> (which allows me to store the logs), but there seems to be no way of
> progressing with the installation.

Alpha 2 is the first release with official support for firmware packages,
which is likely the triggering bit here: they show up and are usable now.

I'm not familiar with the netcfg code enough to suggest anything at the
moment (e.g. something that would notice no passphrases have been
specified, meaning one should skip the interface or prompt for a
passphrase?), but I'll add another workaround in passing:

> Possible workarounds:
>  - Remove Wi-Fi cards from machine during installation
>  - Specify interface to be used (e.g. interface=enp2s0)

Disable firmware support:
 - https://www.debian.org/releases/bookworm/amd64/ch02s02.en.html


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1032852: Error message clue:

[Pascal Hambourg]

Hello,

On 29/03/2023 at 00:23, Charles Curley wrote:

I tried installing with the most recent weekly build. I noticed the
following line toward the end of syslog:

Mar 28 21:35:59 main-menu[425]: (process:4506): cut: 
/var/lib/dpkg/info/firmware-ipw2x00.md5sum: No such file or directory

This might be because the file name wanted is:

/var/lib/dpkg/info/firmware-ipw2x00.md5sums

Note the s on the end.


Already fixed in hw-detect 1.155:
* Fix files removal for non-accepted firmware packages (See: #1032377).

Re: Error debian Acer nitro 5

[Steve McIntyre]

Hi Diego,

On Mon, Mar 06, 2023 at 07:33:50PM -0300, Diego Santos wrote:
>package: installation reports Boot method: DVD? usb pen? Network?> Image version: got> Data:  Machine: an515-52-7974 Processor: i7 Intel acer nitro 5 an515-52-7974 | i7-8750h Memory:
>16 Partitions:  External use
>hdc 1 2 with dual boot windows I tested it without it as main Output from lspci
>-knn (or lspci -nn): Basic system installation checklist: [O] = OK, [E] = Error
>(describe below), [ ] = did not try Initial boot: [ ]ok Detect network card: [
>]ok Configure network: [ ],,ok free kernel mode Detect installation medium: [ ]
>gave installation error Load installer modules: [ ] loads davfail Detect hard
>drives: [ ] ok Partition hard drives: [ ] ok Install base system: [ ] ok Clock/
>time zone setting: [ ]ok Set username/password: [ ]ok Installation tasks: [ ]
>ok Install the bootloader: [ ] ok Installation total: [ ] not installed Accepts
>Ubuntu 19.04 kernel firmware well

I'm struggling to understand wha you're trying to tell us here. Could
you give us a little more information please? What error did you get,
exactly? Which Debian installer image were you trying to use?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.

Error debian Acer nitro 5

[Diego Santos]

package: installation reports Boot method:  Image version:  Data:  Machine:  External use hdc 1 2 with dual boot windows
I tested it without it as main Output from lspci -knn (or lspci -nn): Basic
system installation checklist: [O] = OK, [E] = Error (describe below), [ ]
= did not try Initial boot: [ ]ok Detect network card: [ ]ok Configure
network: [ ],,ok free kernel mode Detect installation medium: [ ] gave
installation error Load installer modules: [ ] loads davfail Detect hard
drives: [ ] ok Partition hard drives: [ ] ok Install base system: [ ] ok
Clock/time zone setting: [ ]ok Set username/password: [ ]ok Installation
tasks: [ ] ok Install the bootloader: [ ] ok Installation total: [ ] not
installed Accepts Ubuntu 19.04 kernel firmware well

Processed (with 1 error): Re: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1031622 -1
Bug #1031622 [src:e2fsprogs] mke2fs: should not enable orphan_file by default 
until trixie
Unable to merge bugs because:
package of #1031923 is 'd-i.debian.org' not 'src:e2fsprogs'
Failed to forcibly merge 1031622: Did not alter merged bugs.


-- 
1031622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
1031923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013203: os-prober: Dual boot Windows 10 grub-probe error unknown filesystem

[waltermd]

Package: os-prober
Version: 1.79
Severity: normal
X-Debbugs-Cc: zalek.ste...@gmail.com

Dear Maintainer, Mr. Zalek,
I would report the same issue on my laptop

Manufacturer: Dell Inc.
model:   Inspiron 14 5410 2-in-1
BIOS vers.: 2.9.0

Linux nomehost 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 
GNU/Linux

/etc/debian_version 11.6

The issue happened after an update to latest Debian release.
the dual boot is with Windows 11

here the output of the comand update-grub

utente@PC:~$ sudo update-grub
[sudo] password di utente: 
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-5.10.0-20-amd64
Found initrd image: /boot/initrd.img-5.10.0-20-amd64
Found linux image: /boot/vmlinuz-5.10.0-10-amd64
Found initrd image: /boot/initrd.img-5.10.0-10-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot 
entries.
/usr/sbin/grub-probe: errore: file system sconosciuto.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
/usr/sbin/grub-probe: errore: file system sconosciuto.
Adding boot menu entry for UEFI Firmware Settings ...
done

I solved the problem in the same way as Mr. Zalek modifying manually the file 
/boot/grub/grub.cfg

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/nvme0n1p1)' --class windows --class os 
$menuentry_id_option 'osprober-efi-/dev/nvme0n1p1' {
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 
--hint-efi=nvme0n1,gpt1 --hint-baremetal=ahci0,gpt1  C4E0-C8D8
else
  search --no-floppy --fs-uuid --set=root C4E0-C8D8
fi  
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###

here the outpu of the comand os-prober

@xxx:~$ sudo os-prober
/dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi

and the related section from messages log

Dec 30 17:53:42 PC os-prober: debug: running /usr/lib/os-probes/mounted/05efi 
on mounted /dev/nvme0n1p1
Dec 30 17:53:42 PC 05efi: debug: /dev/nvme0n1p1 is a FAT32 partition
Dec 30 17:53:42 PC 05efi: debug: /dev/nvme0n1p1 partition scheme is gpt
Dec 30 17:53:42 PC 05efi: debug: /dev/nvme0n1p1 partition type is 
c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Dec 30 17:53:42 PC 05efi: debug: running subtest 
/usr/lib/os-probes/mounted/efi/10elilo
Dec 30 17:53:42 PC 05efi: debug: running subtest 
/usr/lib/os-probes/mounted/efi/20microsoft
Dec 30 17:53:42 PC 20microsoft: result: Microsoft/Boot/bootmgfw.efi:Windows 
Boot Manager:Windows
Dec 30 17:53:42 PC 05efi: debug: bootloader Microsoft/Boot/bootmgfw.efi:Windows 
Boot Manager:Windows found by subtest /usr/lib/os-probes/mounted/efi/20microsoft
Dec 30 17:53:42 PC 05efi: result: 
/dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
Dec 30 17:53:42 PC os-prober: debug: os detected by 
/usr/lib/os-probes/mounted/05efi
Dec 30 17:53:42 PC os-prober: debug: running /usr/lib/os-probes/50mounted-tests 
on /dev/nvme0n1p2
Dec 30 17:53:42 PC 50mounted-tests: debug: /dev/nvme0n1p2 type not recognised; 
skipping
Dec 30 17:53:42 PC os-prober: debug: os detected by 
/usr/lib/os-probes/50mounted-tests
Dec 30 17:53:42 PC os-prober: debug: running /usr/lib/os-probes/50mounted-tests 
on /dev/nvme0n1p3
Dec 30 17:53:42 PC os-prober: debug: running /usr/lib/os-probes/50mounted-tests 
on /dev/nvme0n1p4
Dec 30 17:53:42 PC kernel: [  403.532431] device-mapper: uevent: version 1.0.3
Dec 30 17:53:42 PC kernel: [  403.532516] device-mapper: ioctl: 4.43.0-ioctl 
(2020-10-01) initialised: dm-de...@redhat.com
Dec 30 17:53:42 PC 50mounted-tests: debug: mounted using GRUB ntfs filesystem 
driver
Dec 30 17:53:42 PC 50mounted-tests: debug: running subtest 
/usr/lib/os-probes/mounted/05efi
Dec 30 17:53:42 PC 05efi: debug: /dev/nvme0n1p4 is ntfs partition: exiting
Dec 30 17:53:42 PC 50mounted-tests: debug: running subtest 
/usr/lib/os-probes/mounted/10freedos
Dec 30 17:53:42 PC 10freedos: debug: /dev/nvme0n1p4 is not a FAT partition: 
exiting
Dec 30 17:53:42 PC 50mounted-tests: debug: running subtest 
/usr/lib/os-probes/mounted/10qnx
Dec 30 17:53:42 PC 10qnx: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting
Dec 30 17:53:42 PC 50mounted-tests: debug: running subtest 
/usr/lib/os-probes/mounted/20macosx
Dec 30 17:53:42 PC macosx-prober: debug: /dev/nvme0n1p4 is not an HFS+ 
partition: exiting
Dec 30 17:53:42 PC 50mounted-tests: debug: running subtest 
/usr/lib/os-probes/mounted/20microsoft
Dec 30 17:53:42 PC 20microsoft: debug: Skipping legacy bootloaders on UEFI 
system
Dec 30 17:53:42 PC 50mounted-tests: debug: running subtest 
/usr/lib/os-probes/mounted/30utility
Dec 30 17:53:42 PC 30utility: debug: /dev/nvme0n1p4 is not a FAT 

Re: failed to insert STA entry for the AP (error -2)

[Kalle Valo]

Christoph Hellwig  writes:

> adding the debian-kernel list due to issues with using debian-installer
> daily snapshot to install on my brand new laptop with an ath11k_pci
> supported wifi chip.
>
> It turns out that while d-i comes with the ath11k and ath11k_pci
> drivers, but misses the qrtr, qrtr-mki and michael_mic modules that
> are needed for the driver to actually work and not just load.

s/qrtr-mki/qrtr-mhi/

And also CRYPTO_MICHAEL_MIC is needed. This the copy from Kconfig file
which should be an accurate list of dependencies:

config ATH11K
tristate "Qualcomm Technologies 802.11ax chipset support"
depends on MAC80211 && HAS_DMA
depends on CRYPTO_MICHAEL_MIC
select ATH_COMMON
select QCOM_QMI_HELPERS
...
config ATH11K_PCI
tristate "Atheros ath11k PCI support"
depends on ATH11K && PCI
select MHI_BUS
select QRTR
select QRTR_MHI

> On Wed, Dec 07, 2022 at 02:49:37PM +0200, Kalle Valo wrote:
>> Thanks. But this makes me wonder is it sensible to randomly install a
>> set of .ko files and drop the rest, like Debian's installer apparently
>> does? The dependency for drivers is pretty well documented in Kconfig
>> files, thanks to build testers testing with random configurations, but
>> if the installer omits all that there will be problems just like you are
>> experiencing. So for me MODULE_SOFTDEP() feels just like a band aid and
>> not a robust solution.
>
> I think a driver that a driver that has a runtime depedency on a
> certain module, but doesn't import symbols is always going to be
> somewhat problematic.  But I also agree that the arbitrary splitting
> of kernel modules into separate packages for the installer, or
> in fact not packaging them at all for the installer is rather
> problematic.  I'm not sure what the rationale is behind that, but
> I've added the debian-kernel and debian-boot lists.
>
>> Though I am happy to take your MODULE_SOFTDEP() patch, just wondering if
>> there is a better way to solve this. For example net/mac80211 (the
>> 802.11 stack) has a lot of crypto dependencies:
>> 
>>  select CRYPTO
>>  select CRYPTO_LIB_ARC4
>>  select CRYPTO_AES
>>  select CRYPTO_CCM
>>  select CRYPTO_GCM
>>  select CRYPTO_CMAC
>>  select CRC32
>> 
>> And it's not using MODULE_SOFTDEP() at all.
>
> Yes.  I'm not quite sure how the packages for d-i select which
> modules to include where, but given that other wifi hardware
> seems to work in the installer they must have figured this out
> somehow.

For older ath driver (ath6kl, ath9k, ath10k) the dependencies were quite
simple. ath11k was the first driver requiring MHI and QRTR for PCI
devices, so in that regard it's not surprising that this problem comes
up only now.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: failed to insert STA entry for the AP (error -2)

[Cyril Brulebois]

Hallo Christoph,

Christoph Hellwig  (2022-12-07):
> It turns out that while d-i comes with the ath11k and ath11k_pci
> drivers, but misses the qrtr, qrtr-mki and michael_mic modules that
> are needed for the driver to actually work and not just load.

Reminds me of: https://bugs.debian.org/761902 which meant my wireless
adapter was happy with WEP but not WPA.

> Yes.  I'm not quite sure how the packages for d-i select which modules
> to include where, but given that other wifi hardware seems to work in
> the installer they must have figured this out somehow.

What modules end up in what udebs is decided in src:linux, under
debian/installer/modules.

Commit fixing the bug mentioned above:
  
https://salsa.debian.org/kernel-team/linux/-/commit/782d644da7ab74e04bfebd30b66c264654028da3


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: failed to insert STA entry for the AP (error -2)

[Christoph Hellwig]

Hi all,

adding the debian-kernel list due to issues with using debian-installer
daily snapshot to install on my brand new laptop with an ath11k_pci
supported wifi chip.

It turns out that while d-i comes with the ath11k and ath11k_pci
drivers, but misses the qrtr, qrtr-mki and michael_mic modules that
are needed for the driver to actually work and not just load.

On Wed, Dec 07, 2022 at 02:49:37PM +0200, Kalle Valo wrote:
> Thanks. But this makes me wonder is it sensible to randomly install a
> set of .ko files and drop the rest, like Debian's installer apparently
> does? The dependency for drivers is pretty well documented in Kconfig
> files, thanks to build testers testing with random configurations, but
> if the installer omits all that there will be problems just like you are
> experiencing. So for me MODULE_SOFTDEP() feels just like a band aid and
> not a robust solution.

I think a driver that a driver that has a runtime depedency on a
certain module, but doesn't import symbols is always going to be
somewhat problematic.  But I also agree that the arbitrary splitting
of kernel modules into separate packages for the installer, or
in fact not packaging them at all for the installer is rather
problematic.  I'm not sure what the rationale is behind that, but
I've added the debian-kernel and debian-boot lists.


> Though I am happy to take your MODULE_SOFTDEP() patch, just wondering if
> there is a better way to solve this. For example net/mac80211 (the
> 802.11 stack) has a lot of crypto dependencies:
> 
>   select CRYPTO
>   select CRYPTO_LIB_ARC4
>   select CRYPTO_AES
>   select CRYPTO_CCM
>   select CRYPTO_GCM
>   select CRYPTO_CMAC
>   select CRC32
> 
> And it's not using MODULE_SOFTDEP() at all.

Yes.  I'm not quite sure how the packages for d-i select which
modules to include where, but given that other wifi hardware
seems to work in the installer they must have figured this out
somehow.

Bug#1021922: console-setup: FTBFS make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2

[Michael Biebl]

Am 18.10.22 um 17:23 schrieb Samuel Thibault:

Control: severity -1 important

Hello,

Michael Biebl, le lun. 17 oct. 2022 13:53:44 +0200, a ecrit:

Source: console-setup
Version: 1.210
Tags: ftbfs


1.210 does actually build, it's +binnmu1 that doesn't, because + in the
build path gets confused with file assembly on the command line:


umask 022; /<>/Fonts/bdf2psf --log /<>/Fonts/Arabic-Fixed15.log  
/<>/Fonts/bdf/9x15-IL2.bdf+/<>/Fonts/bdf/9x15.bdf+/<>/Fonts/bdf/9x15c.bdf  
/<>/Fonts/standard.equivalents \


Ah, interesting.


I have now uploaded 1.211, which will thus fulfill your NMU need, and be
able to propagate. Leaving this bug as important open since +something
uploads are an important thing to support.


nod

Thanks for the upload, Samuel!


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1021922: console-setup: FTBFS make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1021922 [src:console-setup] console-setup: FTBFS make: *** 
[Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2
Severity set to 'important' from 'serious'

-- 
1021922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021922: console-setup: FTBFS make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2

[Samuel Thibault]

Control: severity -1 important

Hello,

Michael Biebl, le lun. 17 oct. 2022 13:53:44 +0200, a ecrit:
> Source: console-setup
> Version: 1.210
> Tags: ftbfs

1.210 does actually build, it's +binnmu1 that doesn't, because + in the
build path gets confused with file assembly on the command line:

> umask 022; /<>/Fonts/bdf2psf --log 
> /<>/Fonts/Arabic-Fixed15.log  
> /<>/Fonts/bdf/9x15-IL2.bdf+/<>/Fonts/bdf/9x15.bdf+/<>/Fonts/bdf/9x15c.bdf
>   /<>/Fonts/standard.equivalents \

I have now uploaded 1.211, which will thus fulfill your NMU need, and be
able to propagate. Leaving this bug as important open since +something
uploads are an important thing to support.

Samuel

Bug#1021922: console-setup: FTBFS make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2

[Michael Biebl]

Source: console-setup
Version: 1.210
Severity: serious
Tags: ftbfs

console-setup FTBFS in unstable

gzip -9n >/acm/VISCII.acm >/<>/acm/VISCII.acm.gz
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-Fixed15.log  
/<>/Fonts/bdf/9x15-IL2.bdf+/<>/Fonts/bdf/9x15.bdf+/<>/Fonts/bdf/9x15c.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-Fixed15.psf 
/<>/Fonts/Arabic-Fixed15.sfm
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-Fixed16.log  
/<>/Fonts/bdf/georgian16.bdf+/<>/Fonts/bdf/unifont.bdf+/<>/Fonts/bdf/h16.bdf+/<>/Fonts/bdf/etl16-unicode.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-Fixed16.psf 
/<>/Fonts/Arabic-Fixed16.sfm
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-VGA14.log  
/<>/Fonts/bdf/legacy14i.bdf+/<>/Fonts/bdf/legacy14f.bdf+/<>/Fonts/bdf/legacy14l.bdf+/<>/Fonts/bdf/legacy14b.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-VGA14.psf 
/<>/Fonts/Arabic-VGA14.sfm
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-VGA16.log  
/<>/Fonts/bdf/u_vga16_fix.bdf+/<>/Fonts/bdf/u_vga16.bdf+/<>/Fonts/bdf/legacy16c.bdf+/<>/Fonts/bdf/legacy16f.bdf+/<>/Fonts/bdf/legacy16k.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-VGA16.psf 
/<>/Fonts/Arabic-VGA16.sfm
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-Fixed15.psf] Error 
2
make: *** Waiting for unfinished jobs
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-Fixed16.psf] Error 
2
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA14.psf] Error 2
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2



Full build log available at
https://buildd.debian.org/status/fetch.php?pkg=console-setup&arch=all&ver=1.210%2Bnmu1&stamp=1665832544&raw=0

Processed (with 1 error): dpms=false still not working

[Debian Bug Tracking System]

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

> unarchive 787279
Bug #787279 {Done: Holger Wansing } 
[installation-reports] Cannot disable screen blanking with Jessie preseed 
installation
Unarchived Bug 787279
> reopen 787279
Bug #787279 {Done: Holger Wansing } 
[installation-reports] Cannot disable screen blanking with Jessie preseed 
installation
Bug reopened
Ignoring request to alter fixed versions of bug #787279 to the same values 
previously set
> found 11.0.2
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#1013203: os-prober: Dual boot Windows 10 grub-probe error unknown filesystem

[Steven Zalek]

Package: os-prober
Version: 1.80
Severity: normal
X-Debbugs-Cc: zalek.ste...@gmail.com

Dear Maintainer,

What led to the situation:
Debian Testing new linux kernel 5.18.0-1 and updated grub 2.06-3 installed via
apt package manager; the new linux kernel installation prompted the update-grub
function to run.

By default this new version of grub does not run the the os-prober package,
hence, the Windows 10 partition was not detected and was eliminated from the
grub.cfg list of bootable partitions.

What I did that was effective/ineffective (part 1):
- Added 'GRUB_DISABLE_OS_PROBER=false' to /etc/default/grub and ran 'sudo
update-grub', forcing os-prober/grub to search for Windows partition
- this resulted in the Windows 10 partition on this computer (box0) to be
recognized, but with errors >>
  [incidentally, this exact procedure worked perfectly on my dual-boot Debian
Testing/Windows 10 laptop - no errors]

terminal output >>
---
zaleksf@box0:~$ sudo update-grub
[sudo] password for zaleksf:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-5.18.0-1-amd64
Found initrd image: /boot/initrd.img-5.18.0-1-amd64
Found linux image: /boot/vmlinuz-5.17.0-1-amd64
Found initrd image: /boot/initrd.img-5.17.0-1-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot
entries.
/usr/sbin/grub-probe: error: unknown filesystem.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
---

Outcome:
Upon rebooting and seeing the main grub list screen, there were the usual
entries for booting to Debian, Windows, etc. However, upon selecting the
Windows boot entry, I received an error indicating
'/EFI/Microsoft/Boot/bootmgfw.efi does not exist'

This was false, as I could find this file from both the Debian OS and Windows
OS file manager, and I could boot directly into Windows 10 from the BIOS using
the 'Enter/F12' key combination to bring up a list of boot partition choices
(which did show both Debian and Windows as options).

I investigated grub.cfg file and found that the 30_os-prober section for
Windows to be significantly truncated from its usual entry (and other Linux
kernel entries) >>

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda1)' --class windows --class os
$menuentry_id_option 'osprober-efi-/dev/sda1' {
insmod part_gpt
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###

What I did that was effective/ineffective (part 2):
Since my laptop (box1) also is dual-boot Debian Testing/Windows 10 with a
virtually identical set-up, I tried an experiment of copying its complete (and
functioning) 30_os-prober section to grub.cfg on this misbehaving desktop
system (box0). I tweaked this section (using logic) to point to the proper
Windows partition, etc. (since I really have no experience with grub at all).
Manually changed section 30_os-prober to this >>

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda1)' --class windows --class os
$menuentry_id_option 'osprober-efi-/dev/sda1' {
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-
efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  82CB-1126
else
  search --no-floppy --fs-uuid --set=root 54C7-5867
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###

Saved grub.cfg, rebooted machine and selected Windows entry from grub.

Outcome:

Can boot into the Windows 10 partition perfectly, just as before. All grub list
entries work correctly.

If I run 'update-grub' again, the grub-probe error is indicated in the
terminal, and the truncated/broken section 30_os-prober returns to
/boot/grub/grub.cfg

My machine (and Windows and Debian) works just fine. This machine has been
dual-boot Debian Testing/Windows 10 for the last 5 years and has never
experienced this issue before this version of grub/os-prober was introduced.

My recommendation is to look into why the os-prober successfully recognizes a
dual-boot Windows partition for some machines and not others. Please let me
know if I can send additional files to support troubleshooting and/or
development.

Best regards, SZ


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (80

Processed (with 1 error): reassing to correct package (try 2)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debootstrap
Bug #1008489 [deboostrap] dpkg: postinst should not warn about Debian's default 
filesystem layout
Warning: Unknown package 'deboostrap'
Bug reassigned from package 'deboostrap' to 'debootstrap'.
No longer marked as found in versions 1.0.102.
Ignoring request to alter fixed versions of bug #1008489 to the same values 
previously set
> found -1 1.0.102
Bug #1008489 [debootstrap] dpkg: postinst should not warn about Debian's 
default filesystem layout
Marked as found in versions debootstrap/1.0.102.
> creates unsupported filesystem layout
Unknown command or malformed arguments to command.


-- 
1008489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#621118: partman-auto-lvm: "error creating group" using a preseed recipe with 2 PV on the same disk

[Buck Huppmann]

Package: partman-auto-lvm
Version: 59ubuntu3
Followup-For: Bug #621118

I've had this problem as well (with the installer for ubuntu bionic).

The problem in my case, where I was trying to create a VG for each PV
/dev/sda3 and /dev/sda4, was most easily fixed by modifying partman-auto-lvm's
lib/auto-lvm.sh per the attached.

First thing to note is that your preseed file *has* to specify that one
of the VG's that you configure up with `vg_name` is set to be the one
that partman-auto-lvm will use as "@DEFAULT@" (`defvgname`, in the
script), like so:

d-i partman-auto-lvm/new_vg_name string ${one of the vg_names}

; otherwise, partman-auto-lvm will default to creating a new VG with a
name either taken from the hostname or "debian" (or "ubuntu", in my
case) and, when your recipe leaves no free PVs, it will croak, which is
what the original poster encountered. But, even accounting for that,
partman-auto-lvm will make duplicate PV assignments.

But, assuming you then have a recipe containing

... method{ lvm } vg_name { one of the vg_names }

... method{ lvm } vg_name{ another of the vg_names }

then the attached patch will keep from making duplicate assignments
on the same disk.

(To explain briefly, instead of just grabbing any PV and then ending
up with duplicate assignments, it checks the contents of
/var/lib/partman/auto_lvm_map/* and makes sure it's not choosing a PV
that's already been assigned. It's not foolproof, by any means, but it
worked for me, at least, and was easier to finagle into my boot process
[using a `partman/early_command` which overwrote /lib/partman/lib/auto-lvm.sh
in the installer image with my variant by echo-ing each line individually,
a la `{ echo 'line 1'; echo 'line 2'; ...; } > /lib/partman/lib/auto-lvm.sh`,
with `'\''` in place of every embedded single quote. Ugh. Not recommended
for regular use, but terraform handled the details])
--- b/lib/auto-lvm.sh   2017-01-26 16:31:57.0 -0500
+++ a/lib/auto-lvm.sh   2022-02-14 17:35:24.331012601 -0500
@@ -45,6 +45,7 @@
 # temporary name is stored into $DEFAULT_VG.
 auto_lvm_create_vg_map() {
local pv_device line recipe_device vg_name vg_file pv_device pv_found
+   local pv_found_in_other_map
 
rm -rf $VG_MAP_DIR
mkdir -p $VG_MAP_DIR
@@ -71,14 +72,23 @@
 
# Find the device for this PV from the list of known PVs
pv_found=
+   pv_found_in_other_map=
for pv_device in $pv_devices; do
if echo $pv_device | grep -q 
"$recipe_device[[:digit:]]*"; then
+   if grep -q "^$pv_device$" $VG_MAP_DIR/*; then
+   pv_found_in_other_map=$pv_device
+   else
+   pv_found=1
+   break
+   fi
-   pv_found=1
-   break
fi
done
if [ "$pv_found" ]; then
echo $pv_device >> $VG_MAP_DIR/$vg_name
+   elif [ "$pv_found_in_other_map" ]; then
+   # XXX no error message for this so just die
+   # without providing a clue
+   bail_out no_such_pv
else
bail_out no_such_pv
fi

Bug#1005729: Automatic partitioning fails on arm64 d-i with error message partman: mkfs.vfat: Not enough or too many clusters for filesystem

[Thomas Glanzmann]

Source: partman-efi
X-Debbugs-Cc: tho...@glanzmann.de
Version: 94
Severity: normal
Tags: d-i patch

Hello,
when installing Debian on an arm64 m1 machine, I get the following error during
auto partitioning or when creating a EFI System Partition with more than 256 MB:

partman: mkfs.vfat: Not enough or too many clusters for filesystem - try less 
or more sectors per cluster

When I try to manually create mkfs.vfat on the same system it works:

(air) [~] lsblk
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:00 465.9G  0 disk
├─nvme0n1p1 259:10   500M  0 part
├─nvme0n1p2 259:20 371.6G  0 part
├─nvme0n1p3 259:30   2.3G  0 part
├─nvme0n1p4 259:40 1G  0 part /boot/efi
├─nvme0n1p5 259:50  85.5G  0 part /
└─nvme0n1p6 259:60 5G  0 part
nvme0n2 259:70 3M  0 disk
nvme0n3 259:80   128M  0 disk
(air) [~] umount /boot/efi
(air) [~] mkfs.vfat /dev/nvme0n1p4
mkfs.fat 4.2 (2021-01-31)
(air) [~] mkfs.vfat -F 16 /dev/nvme0n1p4
mkfs.fat 4.2 (2021-01-31)

The sector size is report as 4096:

(air) [~] blockdev --getss /dev/nvme0n1
4096

The issue seems to be related to:

https://sources.debian.org/src/partman-efi/94/commit.d/format_efi/?hl=15#L66

Since mkfs.vfat don't have issue with creating file systems on block devices
with a sector size other than 4096, it is probably best to remove the whole code
block that sets the sectors per cluster and sector size. Find attached a patch.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.16.0-asahi-next-20220118-g5fa3c85b5f14 (SMP w/8 CPU threads; 
PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Report will be sent to Debian Bug Tracking System 

--- ./wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml.orig  2022-02-13 
09:33:30.099608502 +0100
+++ ./wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml   2022-02-13 
09:33:51.187037059 +0100
@@ -45,8 +45,8 @@
   EAP-TLS as work network.
 
 
-# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+# allow frontend (e.g., wpa_cli) to be used by all users in 'root' group
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 #
 # home network; allow all valid ciphers
 network={
@@ -79,7 +79,7 @@
 Aegis, Interlink RAD-Series)
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="example"
scan_ssid=1
@@ -101,7 +101,7 @@
 
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="example"
scan_ssid=1
@@ -123,7 +123,7 @@
 authentication
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="1x-test"
scan_ssid=1
@@ -148,7 +148,7 @@
 use.
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 network={
ssid="example"
scan_ssid=1
@@ -178,7 +178,7 @@
 (-Dwired or -Droboswitch on command line).
 
 
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
 ap_scan=0
 network={
key_mgmt=IEEE8021X
--- format_efi.orig 2022-02-14 04:42:29.023205868 +0100
+++ format_efi  2022-02-14 04:46:31.407838463 +0100
@@ -62,22 +62,8 @@
db_progress START 0 3 partman/text/formatting
db_progress INFO $template
db_progress SET 1
-   log_sector_size="$(blockdev --getss "$(cat device)")"
-   if [ "$log_sector_size" = 512 ]; then
-   mkdosfs_opts=
-   else
-   # mkdosfs has trouble handling cluster
-   # calculations for non-512-byte logical
-   # sectors.  Forcing one sector per cluster
-   # avoids this as long as the filesystem
-   # isn't too large, but that shouldn't be a
-   # problem for EFI System Partitions.
-   mkdosfs_opts='-s 1'
-   fi
if log-output -t partman --pass-stdout \
   $MKFS_FAT -F "${new_efi_fs#fat}" \
--S "$log_sector_size" \
-$mkdosfs_opts \
 "$device" >/dev/null; then
sync
status=OK

Processed (with 1 error): Re: Bug#1000239: Rescue system won't find root partition, but insists on /usr

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1000239 [debian-installer] Rescue system won't find root partition, but 
insists on /usr
Severity set to 'serious' from 'normal'
> tags = confirmed
Unknown command or malformed arguments to command.


-- 
1000239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#666559: marked as done (installation with btrfs fails due to grub-installer error)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #666559,
regarding installation with btrfs fails due to grub-installer error
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.)


-- 
666559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: grub-installer
Version: 1.70
Tags: d-i

Installation fails while using BTRFS during grub-installer step.
Log attached.

Mar 31 18:07:45 grub-installer: info: Installing grub on '/dev/sda'
Mar 31 18:07:45 grub-installer: info: grub-install supports --no-floppy
Mar 31 18:07:45 grub-installer: info: Running chroot /target 
grub-install  --no-floppy --force "/dev/sda"

Mar 31 18:07:45 grub-installer: /usr/sbin/grub-probe: error:
Mar 31 18:07:45 grub-installer:
Mar 31 18:07:45 grub-installer: cannot find a device for /boot/grub (is 
/dev mounted?)

Mar 31 18:07:45 grub-installer: .
Mar 31 18:07:45 grub-installer: error: Running 'grub-install 
--no-floppy --force "/dev/sda"' failed.


--
Melhores cumprimentos/Best regards,

Miguel Figueiredo


syslog.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Hi,

similar to the installation-reports bugs, I'm closing the grub-installer 
reports 
below.

These are reports for Debian 4 / 6 / 7 / 9 where grub-installer fails (for 
various reasons).


There have been numerous changes/improvements on this topics in the past, and 
also because of the age of the reports we should consider these problems as 
being fixed (or it is even reported in the bugs that they are fixed).
They are most likely of no use anymore for recent releases.

If you know, that the issue you reported (and gets closed here) is still 
existing in recent installation images, please file a new report for that with 
up-to-date details!

Thank you for filing these bug reports, they have been very useful at the time 
they were filed!


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489005
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610116
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611713
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612420
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621923
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647267
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659116
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665856
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666552
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668923
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686955
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690515
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690592
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702731
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729411
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771467
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780115
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806164
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806849
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416986
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252009
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292513
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310798
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489006
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578338
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582367
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=229128
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463842
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497168
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500079
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516392
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520361
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544949
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549703
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557242
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580461
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587699
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588670
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596877
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612025
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618498
https://bug

Bug#612420: marked as done (installation-reports: Grub install error when installing from USB (Debian Squeeze))

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #612420,
regarding installation-reports: Grub install error when installing from USB 
(Debian Squeeze)
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.)


-- 
612420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: important

I used "unetbootin" for installing Debian from USB.

In the final step of the installation, Grub wants to use the USB I'm using to
install Debian. It doesn't let me to choose the hard disk until I remove the
usb from the laptop, then I can install Grub properly in the hard disk.



-- Package-specific info:

Boot method: usb
Image version: debian 6 Stable (32 bits) netinstall
Date: 

Machine: Toshiba NB200
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

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="6.0 (squeeze) - installer build 20091104-00:01"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux MPB 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 4 [8086:2845] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 6 [8086:2849] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1

Bug#588670: marked as done (installation-reports: generated grub.cfg has off-by-one error in --fs-uuid index in the search command)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #588670,
regarding installation-reports: generated grub.cfg has off-by-one error in 
--fs-uuid index in the search command
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.)


-- 
588670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
Tags: d-i



-- Package-specific info:

Boot method: CD
Image version: debian-testing-amd64-netinst.iso downloaded on 2010-07-05 with 
size of 177694720
Date: 
Just after I downloaded, probably late 2010-07-05 or early 2010-07-06


Machine: Intel core duo desktop (amd64)
Partitions: 
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/mapper/raven-squeeze_root
  ext345413424   7428228  35678332  18% /
tmpfstmpfs 1025720 0   1025720   0% /lib/init/rw
udev tmpfs 1020608   208   1020400   1% /dev
tmpfstmpfs 1025720 0   1025720   0% /dev/shm
/dev/mapper/raven-backup
  ext3   111469344  50681712  55125324  48% /backup
/dev/mapper/raven-home
  ext3   309637120 194335144 102719064  66% /home
/dev/sda1 ext3  241116106107122561  47% /lenny_boot
/dev/mapper/raven-root
  ext3 6890048   6349176190872  98% /lenny_root

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 CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Perhaps I should have put an asterisk for the bootloader above to draw
your attention to a problem for it even though that install and
subsequent boot went fine.  The issue was the actual grub.cfg was
misconfigured for detection of the other OS on my disk (Debian Lenny)
so I could not dual-boot to Debian Lenny until I worked around that
misconfiguration issue.

Here are the details of one relevant stanza of /boot/grub/grub.cfg with
the misconfiguration:

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/mapper/raven-root.
menuentry "Debian GNU/Linux, kernel 2.6.26-2-amd64 (on /dev/mapper/raven-root)" 
{
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8d562f48-1631-4f09-b17d-07a31de23576
linux /vmlinuz-2.6.26-2-amd64 root=/dev/mapper/raven-root ro quiet 
initrd /initrd.img-2.6.26-2-amd64
}

That 8d562f48-1631-4f09-b17d-07a31de23576 is for the wrong disk!  It
should have referred to /lenny_boot above which is located at /dev/sda1.

Instead, we have the following results:

irwin@raven> ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jul  7 10:55 01e04e6e-4c6e-4106-81a6-4d9ed72ab74a -> 
../../dm-0
lrwxrwxrwx 1 root root 10 Jul  7 10:55 75107d16-1966-46d7-9cba-054336a129f9 -> 
../../dm-3
lrwxrwxrwx 1 root root 10 Jul  7 10:55 8d562f48-1631-4f09-b17d-07a31de23576 -> 
../../dm-1
lrwxrwxrwx 1 root root 10 Jul  7 10:55 d5668fa2-cce0-4466-a24e-871572af4d6d -> 
../../sda1
lrwxrwxrwx 1 root root 10 Jul  7 10:55 e0151002-5ae3-4095-b9e4-9400233ebbf7 -> 
../../dm-2
lrwxrwxrwx 1 root root 10 Jul  7 10:55 fec85ff4-5e79-43d3-a523-7c12b6608e9b -> 
../../dm-4

So the index was off by one (as I said on the subject line) and the
disk should have been referred to as
d5668fa2-cce0-4466-a24e-871572af4d6d (which refers to /dev/sda1) instead of
8d562f48-1631-4f09-b17d-07a31de23576 (which refers to /dev/dm-1).

Instead of bothering with changing the value assigned with the --set
option, I didn't have cut and paste at the time so I simply commented
out the entire search line, and as I hoped (I don't understand grub2
syntax that well) from then on I could dual boot to either the old
Debian Lenny or the new Debian Squeeze without issues.


  
This was a very minimal install of Debian squeeze because I don't like
the mix of packages that are installed as a result of running tasksel.
Instead, I skip the task part altogether, and after the resultingminimal system
boots, I do the rest of the install wi

Bug#580461: marked as done (squeeze Alpha1 + GRUB1: Error 23. Error while parsing number)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #580461,
regarding squeeze Alpha1 + GRUB1: Error 23. Error while parsing number
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.)


-- 
580461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method:
Downloaded netinst iso, burned on CD, booted from it, expert install.

Image version:
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso

Date: 2010-05-04 22:30 CET

Machine: Custom
Processor: Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz
Memory: MemTotal: 8163284 kB
Partitions:
$ df -Tl
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/md0  ext319228180637108  17614328   4% /
tmpfstmpfs 4081640 0   4081640   0% /lib/init/rw
udev tmpfs   10240   224 10016   3% /dev
tmpfstmpfs 4081640 0   4081640   0% /dev/shm
/dev/md1  ext3   878796568205024 834646148   1% /srv

$ sudo fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009c8eb

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1243219535008+  fd  Linux raid autodetect
/dev/sda22433  114283   898443157+   5  Extended
/dev/sda52433  111851   878908086   fd  Linux raid autodetect
/dev/sda6  111852  11428319535008+  fd  Linux raid autodetect

$ sudo fdisk -l /dev/sdb

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000a7bee

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1   1243219535008+  fd  Linux raid autodetect
/dev/sdb22433  114283   898443157+   5  Extended
/dev/sdb52433  111851   878908086   fd  Linux raid autodetect
/dev/sdb6  111852  11428319535008+  fd  Linux raid autodetect


Output of lspci -knn (or lspci -nn):
$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller 
[8086:2e20] (rev 03)
Subsystem: ASUSTeK Computer Inc. Device [1043:8336]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller [8086:2e22] (rev 03)
Subsystem: ASUSTeK Computer Inc. Device [1043:8336]
00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller [8086:2e23] (rev 03)
Subsystem: ASUSTeK Computer Inc. Device [1043:8336]
00:1a.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB 
UHCI Controller #4 [8086:3a37]
Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
Kernel driver in use: uhci_hcd
00:1a.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB 
UHCI Controller #5 [8086:3a38]
Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
Kernel driver in use: uhci_hcd
00:1a.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB 
UHCI Controller #6 [8086:3a39]
Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
Kernel driver in use: uhci_hcd
00:1a.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 
EHCI Controller #2 [8086:3a3c]
Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio 
Controller [8086:3a3e]
Subsystem: ASUSTeK Computer Inc. Device [1043:837b]
Kernel driver in use: HDA Intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express 
Root Port 1 [8086:3a40]
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express 
Root Port 5 [8086:3a48]
Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express 
Root Port 6 [8086:3a4a]
Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB 
UHCI Controller #1 [8086:3a34]
Subsystem: ASUSTeK Co

Bug#998087: arm64+virtio: "No device for installation media was detected" error

[Jean-Marc Ranger]

Package: debian-installer
Severity: normal
Tags: d-i
X-Debbugs-Cc: jmran...@hotmail.com

Dear Maintainer,

Environment:
- physical hardware is a Mac with an M1 processor, running MacOS
- VM provided by QEMU-6.1.0 + patches for that processor, hidden in the hombrew 
installer for QEMU
- using qemu-system-aarch64 - so arm64 VM on an arm64 physical CPU
- reproduced with both debian-11.1.0-arm64-netinst.iso and today's 
debian-testing-arm64-netinst.iso
- the ISO is made visible inside QEMU via its "-cdrom" command-line argument, 
which makes it visible under /dev/vda in Debian's installer
- for simplification, no other virtual hard disk exist
- Debian's normal "non-graphical, non-expert" install mode is used

Error:
- At installation step 4 (Detect and mount installation media), the installer 
fails to detect the ISO, and states "No device for installation media was 
detected".

Solution:
- to "Load drivers from removable media?", answer no
- to "Manually select a module and device for installation media, answer yes
- to "Module needed for accessing the installation media", select "none"
- enter "/dev/vda" (or "/dev/vda1") as the device file to use
- installation media is now detected, and installation continues.

Would it make sense to add the various /dev/vd? to the list of locations 
already automatically probed?

Thanks.

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> reopen 776917
Failed to reopen 776917: Not altering archived bugs; see unarchive.

> unarchive 776917
Bug #776917 {Done: Cyril Brulebois } [debootstrap] fails to 
debootstrap without systemd
Unarchived Bug 776917
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#757882: pkgsel: [text frontend] No feedback right after selecting the software tasks

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cdebconf
Bug #757882 [pkgsel] pkgsel: [text frontend] No feedback right after selecting 
the software tasks
Bug reassigned from package 'pkgsel' to 'cdebconf'.
No longer marked as found in versions pkgsel/0.42.
Ignoring request to alter fixed versions of bug #757882 to the same values 
previously set
> done -1 0.255
Unknown command or malformed arguments to command.


-- 
757882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: Bug#968195: keyboard-configuration: cannot set specific layout Français (Bépo, ergonomique, façon Dvorak, AFNOR) for tty console

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #968195 [keyboard-configuration] keyboard-configuration: cannot set 
specific layout Français (Bépo, ergonomique, façon Dvorak, AFNOR) for tty 
console
Added tag(s) patch.
> forcemerge -1 984427
Bug #968195 [keyboard-configuration] keyboard-configuration: cannot set 
specific layout Français (Bépo, ergonomique, façon Dvorak, AFNOR) for tty 
console
Unable to merge bugs because:
package of #984427 is 'console-setup' not 'keyboard-configuration'
Failed to forcibly merge 968195: Did not alter merged bugs.


-- 
968195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968195
984427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#990268: busybox: incorrect handling of output error for various BusyBox commands

[Vincent Lefevre]

Package: busybox
Version: 1:1.30.1-6+b2
Severity: normal

BusyBox does not always handle output error correctly, e.g. with
closed stdout. For instance:

$ busybox sh -c 'exec >&-; for i in echo env pwd; do echo "[$i]" >&2; $i; echo 
$? >&2; busybox $i; echo $? >&2; done'
[echo]
sh: write error: Bad file descriptor
1
echo: write error: Bad file descriptor
1
[env]
env: write error: Bad file descriptor
125
env: standard output: Bad file descriptor
0
[pwd]
1
255

There are 3 issues here:

1. For echo, in the error message, "sh" is written instead of "echo".
   But the message is OK for "busybox echo".

2. For "busybox env", the exit status is 0 instead of non-zero.
   But the exit status is correct for just "env".

3. For pwd and "busybox pwd", the error message is missing, though it
   is required by POSIX:
 https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pwd.html

Other BusyBox commands might be affected too. To be checked...

-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages busybox depends on:
ii  libc6  2.31-12

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed (with 1 error): Re: Bug#820838: os-prober: 40grub2 does not handle multiple initrd paths

[Debian Bug Tracking System]

Processing control commands:

> unmerge 820838 838177
Unknown command or malformed arguments to command.

> forwarded 820838 
> https://salsa.debian.org/installer-team/os-prober/-/merge_requests/8
Bug #820838 [os-prober] os-prober: 40grub2 does not handle multiple initrd paths
Bug #838177 [os-prober] os-prober: Fails to generate correct initrd line for 
Arch Linux if microcodes are installed
Set Bug forwarded-to-address to 
'https://salsa.debian.org/installer-team/os-prober/-/merge_requests/8'.
Set Bug forwarded-to-address to 
'https://salsa.debian.org/installer-team/os-prober/-/merge_requests/8'.
> retitle 838177 grub-common: grub.d/30_os-prober does not handle multiple 
> initrd paths
Bug #838177 [os-prober] os-prober: Fails to generate correct initrd line for 
Arch Linux if microcodes are installed
Bug #820838 [os-prober] os-prober: 40grub2 does not handle multiple initrd paths
Changed Bug title to 'grub-common: grub.d/30_os-prober does not handle multiple 
initrd paths' from 'os-prober: Fails to generate correct initrd line for Arch 
Linux if microcodes are installed'.
Changed Bug title to 'grub-common: grub.d/30_os-prober does not handle multiple 
initrd paths' from 'os-prober: 40grub2 does not handle multiple initrd paths'.
> reassign 838177 grub-common 2.02+dfsg1-20
Bug #838177 [os-prober] grub-common: grub.d/30_os-prober does not handle 
multiple initrd paths
Bug #820838 [os-prober] grub-common: grub.d/30_os-prober does not handle 
multiple initrd paths
Bug reassigned from package 'os-prober' to 'grub-common'.
Bug reassigned from package 'os-prober' to 'grub-common'.
No longer marked as found in versions os-prober/1.71, os-prober/1.63, and 
os-prober/1.75.
No longer marked as found in versions os-prober/1.71, os-prober/1.63, and 
os-prober/1.74.
Ignoring request to alter fixed versions of bug #838177 to the same values 
previously set
Ignoring request to alter fixed versions of bug #820838 to the same values 
previously set
Bug #838177 [grub-common] grub-common: grub.d/30_os-prober does not handle 
multiple initrd paths
Bug #820838 [grub-common] grub-common: grub.d/30_os-prober does not handle 
multiple initrd paths
Marked as found in versions grub2/2.02+dfsg1-20.
Marked as found in versions grub2/2.02+dfsg1-20.
> forwarded 838177 https://savannah.gnu.org/bugs/index.php?47681
Bug #838177 [grub-common] grub-common: grub.d/30_os-prober does not handle 
multiple initrd paths
Bug #820838 [grub-common] grub-common: grub.d/30_os-prober does not handle 
multiple initrd paths
Changed Bug forwarded-to-address to 
'https://savannah.gnu.org/bugs/index.php?47681' from 
'https://salsa.debian.org/installer-team/os-prober/-/merge_requests/8'.
Changed Bug forwarded-to-address to 
'https://savannah.gnu.org/bugs/index.php?47681' from 
'https://salsa.debian.org/installer-team/os-prober/-/merge_requests/8'.

-- 
820838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820838
838177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#988826: marked as done (grub-installer: reinstalling GRUB on a BIOS setup yields an error in rescue mode despite being successful)

[Debian Bug Tracking System]

Your message dated Tue, 25 May 2021 01:03:26 +
with message-id 
and subject line Bug#988826: fixed in grub-installer 1.178
has caused the Debian Bug report #988826,
regarding grub-installer: reinstalling GRUB on a BIOS setup yields an error in 
rescue mode despite being successful
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.)


-- 
988826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-installer
Version: 1.175
Severity: important
X-Debbugs-Cc: Steve McIntyre <93...@debian.org>

Hi,

Calling this important since it gives a wrong indication to users trying
to rescue their systems. During smoke testing for #987377, once the hang
is fixed, I've toyed with other options like reinstalling the bootloader.

I was surprised to find out that the rescue mode interface reports there
was an error while grepping -i for GRUB in /var/log/syslog only returned
the usual success messages from grub-install, yet we get an error code
set to 1…


A wild guess (unconfirmed at this stage, it's a little late in the day)
is a regression coming from this commit:
  
https://salsa.debian.org/installer-team/grub-installer/-/commit/5eada0008eede06c97d55adca1a9eb1eb9447aee

Namely, rescue.d/80grub-reinstall gets this new code (excerpt):

chroot /target mount /boot/efi || true
EXTRA_PATHS="$EXTRA_PATHS /target/boot/efi"
trap "umount $EXTRA_PATHS" HUP INT QUIT KILL PIPE TERM EXIT

The first line does generate an error/warning message that's harmless
(seen in /var/log/syslog, not in the interface) for BIOS systems.

But the suspected culprit is the unconditional addition of
/target/boot/efi (that's unlikely to exist on such systems) to
EXTRA_PATHS, coupled with the trap call. Since the umount there isn't
guarded with a “|| true”, and since the trap is deployed for EXIT as
well, it might be that we're trying to exit successfully, but end up
triggering an error due to the ENOENT when unmounting.

If that's confirmed, it might be better to guard this differently, e.g.
via:

if [ -e /target/boot/efi ]; then
chroot /target mount /boot/efi || true
EXTRA_PATHS="$EXTRA_PATHS /target/boot/efi"
fi

so that we can still throw errors when unmounting other items of the
EXTRA_PATHS list, without purposefully generating an error that we would
ignored via “|| true”, also ignoring possible other errors in the
process…

That's just a vague gut feeling, feel free to adjust in the best way
you can imagine. :)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: grub-installer
Source-Version: 1.178
Done: Steve McIntyre <93...@debian.org>

We believe that the bug you reported is fixed in the latest version of
grub-installer, 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 988...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated grub-installer 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: SHA256

Format: 1.8
Date: Tue, 15 May 2021 01:20:31 +0100
Source: grub-installer
Architecture: source
Version: 1.178
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 988826
Changes:
 grub-installer (1.178) unstable; urgency=medium
 .
   [ John Paul Adrian Glaubitz ]
   * Add support for Apple PowerMacintosh (New World)
 .
   [ James Addison ]
   * Add conditional tests around mount cleanup logic. Closes: #988826
Checksums-Sha1:
 16ffaa223bf3a3840eb995b89674085a13323ce3 2050 grub-installer_1.178.dsc
 1fd2eee6820e469783093c1b09af3d0673bef25d 229084 grub-installer_1.178.tar.xz
 23f7620d0ee62e7e007559e14be0407c06a9bd7f 6098 
grub-installer_1.178_source.buildinfo
Checksums-Sha256:
 6a9292eb56a5e3b297638f672dcd58f81cdb581037c6a018404655266691a0a9 2050 
grub-installer_1.178.dsc
 

Bug#988826: grub-installer: reinstalling GRUB on a BIOS setup yields an error in rescue mode despite being successful

[Cyril Brulebois]

Cyril Brulebois  (2021-05-20):
> Namely, rescue.d/80grub-reinstall gets this new code (excerpt):
> 
> chroot /target mount /boot/efi || true
> EXTRA_PATHS="$EXTRA_PATHS /target/boot/efi"
> trap "umount $EXTRA_PATHS" HUP INT QUIT KILL PIPE TERM EXIT
> 
> The first line does generate an error/warning message that's harmless
> (seen in /var/log/syslog, not in the interface) for BIOS systems.
> 
> But the suspected culprit is the unconditional addition of
> /target/boot/efi (that's unlikely to exist on such systems) to
> EXTRA_PATHS, coupled with the trap call. Since the umount there isn't
> guarded with a “|| true”, and since the trap is deployed for EXIT as
> well, it might be that we're trying to exit successfully, but end up
> triggering an error due to the ENOENT when unmounting.
> 
> If that's confirmed, it might be better to guard this differently, e.g.
> via:
> 
> if [ -e /target/boot/efi ]; then
> chroot /target mount /boot/efi || true
> EXTRA_PATHS="$EXTRA_PATHS /target/boot/efi"
> fi

That wouldn't be sufficient: umount would just get called with
$EXTRA_PATHS as a parameter. In my purposefully-broken test setup, I do
have a separate /boot partition on /dev/sda1 (encrypted LVM, without
cryptodisk), but it seems /boot doesn't get handled via EXTRA_PATHS.

With the if condition proposed above, we would just call “umount”
without any parameters, and we would get an error message from busybox,
telling us it expects at least one parameter…

Anyway, hopefully the problem is obvious enough for anyone to propose
and test proper solutions. :-)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#988826: grub-installer: reinstalling GRUB on a BIOS setup yields an error in rescue mode despite being successful

[Cyril Brulebois]

Package: grub-installer
Version: 1.175
Severity: important
X-Debbugs-Cc: Steve McIntyre <93...@debian.org>

Hi,

Calling this important since it gives a wrong indication to users trying
to rescue their systems. During smoke testing for #987377, once the hang
is fixed, I've toyed with other options like reinstalling the bootloader.

I was surprised to find out that the rescue mode interface reports there
was an error while grepping -i for GRUB in /var/log/syslog only returned
the usual success messages from grub-install, yet we get an error code
set to 1…


A wild guess (unconfirmed at this stage, it's a little late in the day)
is a regression coming from this commit:
  
https://salsa.debian.org/installer-team/grub-installer/-/commit/5eada0008eede06c97d55adca1a9eb1eb9447aee

Namely, rescue.d/80grub-reinstall gets this new code (excerpt):

chroot /target mount /boot/efi || true
EXTRA_PATHS="$EXTRA_PATHS /target/boot/efi"
trap "umount $EXTRA_PATHS" HUP INT QUIT KILL PIPE TERM EXIT

The first line does generate an error/warning message that's harmless
(seen in /var/log/syslog, not in the interface) for BIOS systems.

But the suspected culprit is the unconditional addition of
/target/boot/efi (that's unlikely to exist on such systems) to
EXTRA_PATHS, coupled with the trap call. Since the umount there isn't
guarded with a “|| true”, and since the trap is deployed for EXIT as
well, it might be that we're trying to exit successfully, but end up
triggering an error due to the ENOENT when unmounting.

If that's confirmed, it might be better to guard this differently, e.g.
via:

if [ -e /target/boot/efi ]; then
chroot /target mount /boot/efi || true
EXTRA_PATHS="$EXTRA_PATHS /target/boot/efi"
fi

so that we can still throw errors when unmounting other items of the
EXTRA_PATHS list, without purposefully generating an error that we would
ignored via “|| true”, also ignoring possible other errors in the
process…

That's just a vague gut feeling, feel free to adjust in the best way
you can imagine. :)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Processed (with 1 error): #983357: Netinst crashes xen domU when loading kernel

[Debian Bug Tracking System]

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

> reassign 983357 linux
Bug #983357 [debian-installer] Netinst crashes xen domU when loading kernel
Bug reassigned from package 'debian-installer' to 'linux'.
No longer marked as found in versions debian-installer/20201202.
Ignoring request to alter fixed versions of bug #983357 to the same values 
previously set
> severity grave
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#967896: Intel firmware loading error

[Ryan Lashkevich]

Similar Bug/Error is reproduced on MSI Modern 15 A10M with Intel WiFi-AC
9560.
All details are at unix.stackexchange
<https://unix.stackexchange.com/questions/644944/intel-firmware-installing-on-debian-buster-10-8-problems>
Thanks in advance for your bugfix.

Bug#954134: marked as done ([d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with error code 134)

[Debian Bug Tracking System]

Your message dated Sun, 28 Mar 2021 14:43:14 +0200
with message-id <20210328144314.8b91254a7d0d5b35dfe91...@mailbox.org>
and subject line Re: Bug#954134: [d-i bullseye alpha2] installing grub fails
has caused the Debian Bug report #954134,
regarding [d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with 
error code 134
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.)


-- 
954134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: grave


While testing the alpha2 netinst image on a spare Thinkpad, I found that grub
cannot be installed successfully (and rebooting into the new installation
fails as well). This was ok in alpha1.

This might look like an grub-installer issue, however there were only trivial
installation update releases since alpha1, so I suspect it's not in issue
in grub-installer. Therefore I file this against debian-installer.

I will sent installation logs shortly.


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
--- End Message ---
--- Begin Message ---
Hi,

Holger Wansing  wrote (Sun, 28 Mar 2021 14:39:41 +0200):
> Hi,
> 
> Steve McIntyre  wrote (Sat, 21 Mar 2020 17:00:59 +):
> >Hmm, this is getting annoying:
> >while doing several test installs, I thought I had a path how to reproduce
> >the issue, but then suddenly it looked completely different than before.
> >So, that's something between "some portion of coincidence involved" and
> >"wow, not it looks like a hardware failure".
> >
> >And since I was never able to reproduce the issue on amd64, it seems at
> >least to be a i386-only issue, and thus could be considered as a corner 
> >case...

Since I cannot reproduce this for a long time now, I'm closing this report.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#980607: marked as done (netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args])

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2021 17:18:58 +
with message-id 
and subject line Bug#980607: fixed in netcfg 1.171
has caused the Debian Bug report #980607,
regarding netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments 
for format [-Werror=format-extra-args]
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.)


-- 
980607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netcfg
Version: 1.169
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> cc -c -W -Wall -Werror -DNDEBUG -DNETCFG_VERSION="\"1.169\"" -I. -DWIRELESS 
> -DNM -Os -fomit-frame-pointer   -o test/test_inet_mton.o test/test_inet_mton.c
> In file included from test/srunner.h:1,
>  from test/test_inet_mton.c:1:
> test/test_inet_mton.c: In function ‘test_inet_mton_v4_24_fn’:
> test/test_inet_mton.c:12:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>12 |   "Mask address wasn't 24 bits");
>   |   ^
> test/test_inet_mton.c: In function ‘test_inet_mton_v4_22_fn’:
> test/test_inet_mton.c:24:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>24 |   "Mask address wasn't 22 bits");
>   |   ^
> test/test_inet_mton.c: In function ‘test_inet_mton_v6_64_fn’:
> test/test_inet_mton.c:38:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>38 |   "Mask address wasn't 64 bits");
>   |   ^~~~~
> test/test_inet_mton.c: In function ‘test_inet_mton_v6_60_fn’:
> test/test_inet_mton.c:52:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>52 |   "Mask address wasn't 60 bits");
>   |   ^
> cc1: all warnings being treated as errors
> make[1]: *** [Makefile:60: test/test_inet_mton.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/netcfg_1.169_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: netcfg
Source-Version: 1.171
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
netcfg, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated netcfg 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: Mon, 22 Feb 2021 17:58:31 +0100
Source: netcfg
Architecture: source
Version: 1.171
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 980607
Changes:
 netcfg (1.171) unstable; urgency=medium
 .
   * Team upload
 .
   [ Francisco Vilmar Cardoso Ruviaro ]
   * Update testcases to work with current Check API,
 patch from Dennis Filder . (Closes: #980607)
   * Satisfy GCC pedantery for strncpy() calls,
 patch from Dennis Filder .
 .
   [ Updated translations ]
   * Catalan (ca.po) by d
   * Danish (da.po) by Michael Millet
   * Galic

Bug#980607: [PATCH] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[John Paul Adrian Glaubitz]

> On Feb 22, 2021, at 12:24 AM, Francisco Vilmar Cardoso Ruviaro 
>  wrote:
> 
> Hello everyone,
> 
> I would like to help with this,
> I reviewed the patches (thanks Dennis) and created an MR at
> https://salsa.debian.org/installer-team/netcfg/-/merge_requests/5.
> 
> As Bart said, the patches solve the FTBFS.
> 
> I intend to make a delayed NMU in 7 days.

That shouldn’t be necessary as Holger is usually very quick working on d-i 
issues.

If Holger isn’t available, I can merge the patch and upload the updated package.

Adrian

Bug#980607: [PATCH] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[Francisco Vilmar Cardoso Ruviaro]

Hello everyone,

I would like to help with this,
I reviewed the patches (thanks Dennis) and created an MR at
https://salsa.debian.org/installer-team/netcfg/-/merge_requests/5.

As Bart said, the patches solve the FTBFS.

I intend to make a delayed NMU in 7 days.

Regards,
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00



OpenPGP_signature
Description: OpenPGP digital signature

Bug#980607: [PATCH] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[Dennis Filder]

On Wed, Feb 10, 2021 at 05:41:29PM +0100, Cyril Brulebois wrote:

> Patches fail to apply locally, and I'd rather avoid having to fix
> them up (possibly breaking things in the process).

Strange: When I download the patches from BTS somehow they have
mangled whitespace whereas my local patches don't.  No idea what
happened here.  Is that a known issue?  Regardless I attached the
patches anew compressed plus an md5sums file and verified that they
apply fine against current master HEAD
b897697d6f1d816b3420dac277bcd58da336da7e and preserve the whitespace
style of each changed line.

Regards,
Dennis.


netcfg_1.169-fix-CheckAPI.patch.gz
Description: application/gzip


netcfg_1.169-fix-strncpy.patch.gz
Description: application/gzip
5143239a2f25142ee06b02d4c70db735  netcfg_1.169-fix-CheckAPI.patch.gz
092ebedd836b8640f05d04ca9638e911  netcfg_1.169-fix-strncpy.patch.gz

Bug#980607: [PATCH] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[Cyril Brulebois]

Hallo Dennis,

Dennis Filder  (2021-02-10):
> Control: tag -1 + patch upstream
> 
> The attached patches allowed me to build netcfg 1.169 again, at least
> on amd64.

Thanks for your patches. Any chance I could trick you into pushing a
branch somewhere? Patches fail to apply locally, and I'd rather avoid
having to fix them up (possibly breaking things in the process).

The git repository is located here:
  https://salsa.debian.org/installer-team/netcfg

Thanks in advance!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#980607: [PATCH] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[Dennis Filder]

Control: tag -1 + patch upstream

The attached patches allowed me to build netcfg 1.169 again, at least
on amd64.
Description: Update testcases to work with current Check API
 Some calls of the Check API (fail_unless(), fail_if(), ...) were
 deprecated long ago and no longer compile correctly (#980607).  This
 patch works in the new calls and adds some polish where needed.
 .
 test/srunner.c: The Check API was apparently changed at some point to
 derive testcase names from function names plus a "_fn" suffix which
 breaks an old testcase.  Test for that and use the old name for now.
Author: Dennis Filder 
Bug-Debian: https://bugs.debian.org/980607
Last-Update: 2021-02-09
---
diff --git netcfg-1.169/test/test_nc_v6_interface_configured.c netcfg-1.169/test/test_nc_v6_interface_configured.c
index 92fa9c4..41afc7b 100644
--- netcfg-1.169/test/test_nc_v6_interface_configured.c
+++ netcfg-1.169/test/test_nc_v6_interface_configured.c
@@ -15,7 +15,7 @@ START_TEST(test_nc_v6_interface_configured_simple)

 	rv = nc_v6_interface_configured(&iface, 0);

-	fail_unless(rv == 1, "Didn't find SLAAC");
+	ck_assert_msg(rv == 1, "Didn't find SLAAC");

 	srunner_reset_path();
 }
diff --git netcfg-1.169/test/test_netcfg_gateway_reachable.c netcfg-1.169/test/test_netcfg_gateway_reachable.c
index 840d145..75f5414 100644
--- netcfg-1.169/test/test_netcfg_gateway_reachable.c
+++ netcfg-1.169/test/test_netcfg_gateway_reachable.c
@@ -11,12 +11,12 @@ START_TEST(test_netcfg_gateway_reachable_v4_24)
 	iface.masklen = 24;
 	iface.address_family = AF_INET;

-	fail_unless (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously unreachable");

 	strcpy(iface.gateway, "192.168.2.254");

-	fail_if (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (!netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously reachable");
 }
 END_TEST
@@ -31,12 +31,12 @@ START_TEST(test_netcfg_gateway_reachable_v4_22)
 	iface.masklen = 22;
 	iface.address_family = AF_INET;

-	fail_unless (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously unreachable");

 	strcpy(iface.gateway, "192.168.4.254");

-	fail_if (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (!netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously reachable");
 }
 END_TEST
@@ -51,12 +51,12 @@ START_TEST(test_netcfg_gateway_reachable_v6_64)
 	iface.masklen = 64;
 	iface.address_family = AF_INET6;

-	fail_unless (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously unreachable");

 	strcpy(iface.gateway, "2001:3:5::1");

-	fail_if (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (!netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously reachable");
 }
 END_TEST
@@ -71,12 +71,12 @@ START_TEST(test_netcfg_gateway_reachable_v6_48)
 	iface.masklen = 48;
 	iface.address_family = AF_INET6;

-	fail_unless (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously unreachable");

 	strcpy(iface.gateway, "2001:3:6::1");

-	fail_if (netcfg_gateway_reachable(&iface),
+	ck_assert_msg (!netcfg_gateway_reachable(&iface),
 	 "Gateway erroneously reachable");
 }
 END_TEST
diff --git netcfg-1.169/test/test_inet_ptom.c netcfg-1.169/test/test_inet_ptom.c
index 8d67119..6a45deb 100644
--- netcfg-1.169/test/test_inet_ptom.c
+++ netcfg-1.169/test/test_inet_ptom.c
@@ -7,7 +7,7 @@ START_TEST(test_inet_ptom_v4_24)

 	inet_ptom(AF_INET, "255.255.255.0", &masklen);

-	fail_unless (24 == masklen, "Expected masklen == 24, masklen was %i", masklen);
+	ck_assert_msg (24 == masklen, "Expected masklen == 24, masklen was %i", masklen);
 }
 END_TEST

@@ -17,7 +17,7 @@ START_TEST(test_inet_ptom_v4_22)

 	inet_ptom(AF_INET, "255.255.252.0", &masklen);

-	fail_unless (22 == masklen, "Expected masklen == 22, masklen was %i", masklen);
+	ck_assert_msg (22 == masklen, "Expected masklen == 22, masklen was %i", masklen);
 }
 END_TEST

@@ -27,7 +27,7 @@ START_TEST(test_inet_ptom_v6_64)

 	inet_ptom(AF_INET6, ":::::", &masklen);

-	fail_unless (64 == masklen, "Expected masklen == 64, masklen was %i", masklen);
+	ck_assert_msg (64 == masklen, "Expected masklen == 64, masklen was %i", masklen);
 }
 END_TEST

@@ -37,7 +37,7 @@ START_TEST(test_inet_ptom_v6_60)

 	inet_ptom(AF_INET6, ":::fff0::", &masklen);

-	fail_unless (60 == masklen, "Expected masklen == 60, masklen was %i", masklen);
+	ck_assert_msg (60 == masklen, "Expected masklen == 60, masklen was %i", masklen);
 }
 END_TEST

@@ -51,7 +51,7 @@ START_TEST(test_inet_ptom_v6_60_with_scraps)
 	 */
 	inet_ptom(AF_INET6, ":::fff0:::", &masklen);

-	fail_unless (60 == masklen, "Expected masklen == 60, masklen was %i", masklen);
+	ck_assert_msg (60 == masklen, "Expected masklen == 60, masklen was %i", masklen);
 }
 END_TEST

diff --git netcfg-1.169/test/

Processed: [PATCH] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch upstream
Bug #980607 [src:netcfg] netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too 
many arguments for format [-Werror=format-extra-args]
Added tag(s) upstream and patch.

-- 
980607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#980607: netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]

[Lucas Nussbaum]

Source: netcfg
Version: 1.169
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> cc -c -W -Wall -Werror -DNDEBUG -DNETCFG_VERSION="\"1.169\"" -I. -DWIRELESS 
> -DNM -Os -fomit-frame-pointer   -o test/test_inet_mton.o test/test_inet_mton.c
> In file included from test/srunner.h:1,
>  from test/test_inet_mton.c:1:
> test/test_inet_mton.c: In function ‘test_inet_mton_v4_24_fn’:
> test/test_inet_mton.c:12:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>12 |   "Mask address wasn't 24 bits");
>   |   ^
> test/test_inet_mton.c: In function ‘test_inet_mton_v4_22_fn’:
> test/test_inet_mton.c:24:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>24 |   "Mask address wasn't 22 bits");
>   |   ^
> test/test_inet_mton.c: In function ‘test_inet_mton_v6_64_fn’:
> test/test_inet_mton.c:38:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>38 |   "Mask address wasn't 64 bits");
>   |   ^~~~~
> test/test_inet_mton.c: In function ‘test_inet_mton_v6_60_fn’:
> test/test_inet_mton.c:52:15: error: too many arguments for format 
> [-Werror=format-extra-args]
>52 |   "Mask address wasn't 60 bits");
>   |   ^
> cc1: all warnings being treated as errors
> make[1]: *** [Makefile:60: test/test_inet_mton.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/netcfg_1.169_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Processed (with 1 error): please improve proxy support

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +patch *
Unknown tag/s: *.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore.

Bug #640992 [debootstrap] Please keep proxy setting in chroot
Added tag(s) patch.

-- 
640992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: Bug#977466: rootskel: bterm cannot start when requesting graphical console and serial console at the same time

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #977466 [rootskel] rootskel: bterm cannot start when requesting graphical 
console and serial console at the same time
Bug 977466 cloned as bug 977490
> reassign -2 lowmem
Bug #977490 [rootskel] rootskel: bterm cannot start when requesting graphical 
console and serial console at the same time
Bug reassigned from package 'rootskel' to 'lowmem'.
No longer marked as found in versions rootskel/1.131+10u1.
Ignoring request to alter fixed versions of bug #977490 to the same values 
previously set
> retitle -2 lowmem: delete graphical terminal related files in lawmen state
Bug #977490 [lowmem] rootskel: bterm cannot start when requesting graphical 
console and serial console at the same time
Changed Bug title to 'lowmem: delete graphical terminal related files in lawmen 
state' from 'rootskel: bterm cannot start when requesting graphical console and 
serial console at the same time'.
> merge -1 -2
Bug #977466 [rootskel] rootskel: bterm cannot start when requesting graphical 
console and serial console at the same time
Unable to merge bugs because:
package of #977490 is 'lowmem' not 'rootskel'
Failed to merge 977466: Did not alter merged bugs.


-- 
977466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977466
977490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems