Processed: reassign 1060924 to klibc-utils, forcibly merging 1055694 1060924
Processing commands for cont...@bugs.debian.org: > reassign 1060924 klibc-utils Bug #1060924 [initramfs-tools] update-initramfs: cp: warning: behavior of -n is non-portable and may change in future Bug reassigned from package 'initramfs-tools' to 'klibc-utils'. No longer marked as found in versions initramfs-tools/0.142. Ignoring request to alter fixed versions of bug #1060924 to the same values previously set > forcemerge 1055694 1060924 Bug #1055694 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug #1056912 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug #1059936 [klibc-utils] initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future" Bug #1060336 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug #1060924 [klibc-utils] update-initramfs: cp: warning: behavior of -n is non-portable and may change in future 1060924 was not blocked by any bugs. 1060924 was not blocking any bugs. Added blocking bug(s) of 1060924: 1058752 Added indication that 1060924 affects initramfs-tools Marked as found in versions klibc/2.0.13-2. Bug #1056912 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug #1059936 [klibc-utils] initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future" Bug #1060336 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Merged 1055694 1056912 1059936 1060336 1060924 > thanks Stopping processing here. Please contact me if you need assistance. -- 1055694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055694 1056912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056912 1059936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059936 1060336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060336 1060924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 1055694 1060924
Processing commands for cont...@bugs.debian.org: > forcemerge 1055694 1060924 Bug #1055694 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug #1056912 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug #1059936 [klibc-utils] initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future" Bug #1060336 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Unable to merge bugs because: package of #1060924 is 'initramfs-tools' not 'klibc-utils' Failed to forcibly merge 1055694: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055694 1056912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056912 1059936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059936 1060336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060336 1060924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060942: marked as done (linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), linux-image-
Your message dated Tue, 16 Jan 2024 20:54:41 +0100 with message-id <20240116195441.l5oywod3hcuzi...@shell.thinkmo.de> and subject line Re: Bug#1060942: linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) has caused the Debian Bug report #1060942, regarding linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) 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.) -- 1060942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux-signed-amd64 Version: 6.6.9+1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), dh-exec, python3:any, > sbsigntool, build-essential, fakeroot, linux-image-6.6.9-amd64-unsigned (= > 6.6.9-1), kernel-wedge (>= 2.105~), kmod, rsync, > linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), > linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) > Filtered Build-Depends: debhelper-compat (= 12), dh-exec, python3:any, > sbsigntool, build-essential, fakeroot, linux-image-6.6.9-amd64-unsigned (= > 6.6.9-1), kernel-wedge (>= 2.105~), kmod, rsync, > linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), > linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [612 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1089 B] > Get:5 copy:/<>/apt_archive ./ Packages [869 B] > Fetched 2570 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: linux-image-6.6.9-amd64-unsigned > (= 6.6.9-1) but it is not going to be installed >Depends: > linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1) but it is not going to be > installed >Depends: > linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) but it is not going to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/01/15/linux-signed-amd64_6.6.9+1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results 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 mark 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 mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- > During a rebuild of all packages in sid, your package failed to build > on amd64. Please blacklist the signed packages, this behaviour is a requirement of the secure boot signing. Nothing to see here. Bastian -- Most legends
Bug#1060942: linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-rt-amd64-u
Source: linux-signed-amd64 Version: 6.6.9+1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), dh-exec, python3:any, > sbsigntool, build-essential, fakeroot, linux-image-6.6.9-amd64-unsigned (= > 6.6.9-1), kernel-wedge (>= 2.105~), kmod, rsync, > linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), > linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) > Filtered Build-Depends: debhelper-compat (= 12), dh-exec, python3:any, > sbsigntool, build-essential, fakeroot, linux-image-6.6.9-amd64-unsigned (= > 6.6.9-1), kernel-wedge (>= 2.105~), kmod, rsync, > linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), > linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [612 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1089 B] > Get:5 copy:/<>/apt_archive ./ Packages [869 B] > Fetched 2570 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: linux-image-6.6.9-amd64-unsigned > (= 6.6.9-1) but it is not going to be installed >Depends: > linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1) but it is not going to be > installed >Depends: > linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) but it is not going to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/01/15/linux-signed-amd64_6.6.9+1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results 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 mark 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 mine so that we can identify if something relevant changed in the meantime.
Bug#1060924: update-initramfs: cp: warning: behavior of -n is non-portable and may change in future
Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: gag...@debian.org Dear Maintainer, When updating initramfs with `update-initramfs -u`, the following output appears on the console: update-initramfs: Generating /boot/initrd.img-6.6.11-amd64 W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915 W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915 cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead My guess is that update-initramfs is using cp with the -n option, and that the --update=none option should be used instead, according to the warning above. Thanks in advance. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.142 ii linux-base4.9 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: ii bash-completion 1:2.11-8 -- no debconf information
Bug#1059676: kernel FTBFS on hppa
This kernel bug is now fixed, since binutils will now support hppa64 binaries as well. See bz #1059674
