Your message dated Sun, 7 Jan 2024 13:42:19 +0100 with message-id <ZZqcK_PpWrawFsf2@eldamar.lan> and subject line Re: Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version has caused the Debian Bug report #1060150, regarding linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version 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 owner@bugs.debian.org immediately.) -- 1060150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060150 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---Package: linux-image-6.6.9-amd64
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version
- From: Carlos Suérez <bitseater@gmail.com>
- Date: Sat, 6 Jan 2024 14:00:58 +0100
- Message-id: <[🔎] e5f6e219-b473-4da8-91e8-7e800ccdf0c8@gmail.com>
Version: 6.6.9-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation? System update failure with manual 'apt
update' at terminal.
* What exactly did you do (or not do) that was effective (or
ineffective)? I have tried to install the package only
* What was the outcome of this action? I get the same error
* What outcome did you expect instead? Update done
-- 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.8-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 linux-image-6.6.9-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.142
ii kmod 31-1
ii linux-base 4.9
Versions of packages linux-image-6.6.9-amd64 recommends:
ii apparmor 3.0.12-1+b2
ii firmware-linux-free 20200122-3
Versions of packages linux-image-6.6.9-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.12~rc1-12
pn linux-doc-6.6 <none>
*** Output when i try to update/install the linux-image package from 6.6.8 to 6.6.9 ***
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure):
el subproceso instalado paquete linux-image-6.6.9-amd64 script post-installatio
n devolvió el código de salida de error 1
Se encontraron errores al procesar:
linux-image-6.6.9-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks for your attention and greetings.
Carlos Suárez (bitseater)
--- End Message ---
--- Begin Message ---
- To: Carlos Suérez <bitseater@gmail.com>, 1060150-done@bugs.debian.org
- Subject: Re: Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sun, 7 Jan 2024 13:42:19 +0100
- Message-id: <ZZqcK_PpWrawFsf2@eldamar.lan>
- In-reply-to: <[🔎] f117cebe-de6f-4b04-b05d-376f58f750e6@gmail.com>
- References: <[🔎] e5f6e219-b473-4da8-91e8-7e800ccdf0c8@gmail.com> <[🔎] ZZlmRgMN8wxunYZ2@eldamar.lan> <[🔎] 07fa0efe-e2a2-4f8f-93d7-60fb8ec15eee@gmail.com> <[🔎] e5f6e219-b473-4da8-91e8-7e800ccdf0c8@gmail.com> <[🔎] f117cebe-de6f-4b04-b05d-376f58f750e6@gmail.com>
Hi Carlos, On Sun, Jan 07, 2024 at 11:52:00AM +0100, Carlos Suérez wrote: > Hi Salvatore, > > I have found an error in '/etc/grub.d//proxifiedScripts/linux' caused by > grub-customizer. I have to uninstall grub-customizer, delete and purge all > content about it. Then i can install linux-image-6.6.9-amd64. I'm sorry for > the inconvenience. > > Can you close this issue? Thanks. Thanks for reporting back! Closing the issue then. Regards, Salvatore
--- End Message ---