Your message dated Thu, 04 Sep 2025 10:04:46 +0000
with message-id <[email protected]>
and subject line Bug#1112265: fixed in asahi-scripts 20250713-1
has caused the Debian Bug report #1112265,
regarding asahi-scripts: update-m1n1 is not idempotent, breaking intended 
safeguards
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 [email protected]
immediately.)


-- 
1112265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112265
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: asahi-scripts
Version: 20250130-3
Severity: important
Tags: upstream fixed-upstream trixie forky sid
X-Debbugs-Cc: [email protected]

Dear Maintainer,

update-m1n1 is not idempotent: if executed twice, it will happily create a
new boot binary, replace the old boot binary (/boot/efi/m1n1/boot.bin.old) with
the current one (/boot/efi/m1n1/boot.bin) and then move the new boot binary to
the path of the current one (/boot/efi/m1n1/boot.bin) without checking if
the new binary is the same as the current one. This breaks the fundamental
safeguard of making sure the current boot binary is always different from the
old one.

A real-life scenario where this can cause breakage is after kernel updates.
Suppose one has kernel version A and B installed, A < B, and call A and B the
boot binaries that update-m1n1 generated starting from the respective DTBs,

A: /boot/efi/m1n1/boot.bin.old
B: /boot/efi/m1n1/boot.bin

When the user updates to kernel version C, a new boot binary is generated and
we are left with

B: /boot/efi/m1n1/boot.bin.old
C: /boot/efi/m1n1/boot.bin

If the user now removes kernel version A, update-m1n1 is called again and we
are left with

C: /boot/efi/m1n1/boot.bin.old
C: /boot/efi/m1n1/boot.bin

which are the same binary. If kernel version C is broken for some reason, and
1. the breakage also affects the DTBS, or 2. the DTBs in C and kernel B are
incompatible, then the user won't be able to revert to using kernel B and/or
boot binary B. If update-m1n1 were idempotent (i.e. if it checked that the new
boot binary is different from the current one before doing the replacements),
it would be impossible to end up in this situation.

Cheers!

--- End Message ---
--- Begin Message ---
Source: asahi-scripts
Source-Version: 20250713-1
Done: Tobias Heider <[email protected]>

We believe that the bug you reported is fixed in the latest version of
asahi-scripts, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Heider <[email protected]> (supplier of updated asahi-scripts 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 04 Sep 2025 11:33:53 +0200
Source: asahi-scripts
Architecture: source
Version: 20250713-1
Distribution: sid
Urgency: medium
Maintainer: Tobias Heider <[email protected]>
Changed-By: Tobias Heider <[email protected]>
Closes: 1112262 1112264 1112265
Changes:
 asahi-scripts (20250713-1) unstable; urgency=medium
 .
   [ NoisyCoil ]
   * New upstream release (Closes: #1112262, #1112265)
   * d/patches:
     - add 0000-Backport-asahi-diagnose-drop-tas2764.patch to drop the
       tas2764 quirk checks (Closes: #1112262)
     - add 0000-Backport-update-m1n1-Expand-DTBS.patch to limit the DTBs
       included in the boot binary
     - 0003-debian-Add-initramfs-tools-implementation-for-cpio-f.patch:
       add the apple_nvmem_spmi module to the initramfs explicitly and
       declare simple-mfd-spmi and nvmem_spmi_mfd obsolete, imported
       from corresponding dracut changes (Closes: #1112264)
     - 0004-debian-Support-asahi-diagnose.patch: output APT sources and
       preferences
     - drop 0005-asahi-diagnose-update-doc-link.patch, merged upstream
     - refresh
 .
   [ Tobias Heider ]
   * d/p/*-install-debian-target.patch: Install dracut configs
Checksums-Sha1:
 18f36aa0cd609d8b8556427c292cf7b0f87352cf 1977 asahi-scripts_20250713-1.dsc
 1370b8ec841b0972ac4b7bbd4eb2a1c1fee68582 12852 
asahi-scripts_20250713.orig.tar.gz
 ece3f8eb6a506e1c84f68313d6b00e3bcd9c1181 9152 
asahi-scripts_20250713-1.debian.tar.xz
 e149da507180a3fe9b475f23efbf87b0897625b3 5353 
asahi-scripts_20250713-1_source.buildinfo
Checksums-Sha256:
 dee6dd12455778c80497bd59c325cb9ed3cdf644be8ad6fa9954e1f4c963580f 1977 
asahi-scripts_20250713-1.dsc
 1de1f220ebbf3eaed7b7d75c402ec0dbf799c73dee9ab6635cf106bfa8b117ab 12852 
asahi-scripts_20250713.orig.tar.gz
 1973cbdd7b3f94e9157b128422088ee041f005f467d516e4cbe8cde2cebf62ae 9152 
asahi-scripts_20250713-1.debian.tar.xz
 72fd2b12a3cca06455c2c8557701dc61a62d804d6e1c18658bff032277a4aea3 5353 
asahi-scripts_20250713-1_source.buildinfo
Files:
 d902d79f52b7000f426d700f3e4f94bd 1977 admin optional 
asahi-scripts_20250713-1.dsc
 eaae1ccf6bc89a6f64ed8ee7743ef477 12852 admin optional 
asahi-scripts_20250713.orig.tar.gz
 203c751bf5bd7b50ddc3a70940ad535a 9152 admin optional 
asahi-scripts_20250713-1.debian.tar.xz
 4629b16489f24625bca401e0cbccaa2b 5353 admin optional 
asahi-scripts_20250713-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm2k9dECALopv+APeE0mPAyzP6doFAmi5XY0ACgkQE0mPAyzP
6dq1rxAAjjISwbeLiql12/1kuPGyeCAS6TkhsvvQw0MztIXktGn34idhzM3dNCRD
d10VWEQ4JyVEJ+V5qwJN7NHnGSRdCSQkB2r73ZQsN0iQsnit7GgZr0ECs1oq+iY7
vSkDhuPzvNLNC8BEOAp0z7Y+cuZeRcEaeohxvWlEE2NDN521EKofPNULbJneLttc
r4QbdmR9J5ugYE8jbf/2nAcsDr1FfZvq2vm7ZWCxYkIeSkwyrRA7w6pt0/7gfdzo
CD88eSTOF6X1m6W5KuK2dxcvgvrIlROSuCkJDdK1mB/1xCKsjLMtgbMXYyhAbE6t
ROkLj49XJlosg8z34EyQZAEUhI9ZpFyeQDtfdBjfUAxvwLswQTCs+jfdGJaC4vjS
FCaLire9qQGZxzKbjj1FR8K6RmGUxO8eflGvpiDoY/m1J/T+o1FOBuZMpz7+GBeV
AvxUavx6+KqH2Q2vxxTprdOGvJNcTKNqlaa1Sg7FOot/KGnmIag1hwT7ZoEpRO1H
ZR4Dusmaaj3Ed14ccOucovpqi6Ftl4Syy+uWCCeeWErd744gA5S3y7NjAWeF5FlM
lITFnAzVUbICxWLLjfsYXkAvYcUviVuxkxew7frp5fH/Mzm9+Btgb/NwlrB37y91
mhgKDZmiCyGbCb3KEH5Q6qsqQqpVfQWUMshqAC2U41uK/DUNCKw=
=IYWf
-----END PGP SIGNATURE-----

Attachment: pgpyoCRZU59OT.pgp
Description: PGP signature


--- End Message ---

Reply via email to