Your message dated Sat, 29 Mar 2025 10:11:05 -0400
with message-id <[email protected]>
and subject line Re: Bug#1101556: apt-listchanges: displays some entries twice
has caused the Debian Bug report #1101556,
regarding apt-listchanges: displays some entries twice
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.)
--
1101556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101556
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-listchanges
Version: 4.8
Dear developer,
Today I received an e-mail showing twice the same NEWS entry :
-----%<-----
--- Nouveautés pour qemu-efi-aarch64 ---
edk2 (2025.02-5) unstable; urgency=medium
The EFI_MEMORY_ATTRIBUTE_PROTOCOL is now enabled by default in the
AAVMF_CODE.secboot.fd image. This is a security feature that will
cause crashes for operating systems with bootloaders that do not
observe proper memory access semantics. Users that experience issues
with such bootloaders have the options to either append the following
to the qemu-system-aarch64 command line:
-fw_cfg name=opt/org.tianocore/UninstallMemAttrProtocol,string=y
or switch to the no-secboot image, which uninstalls this protocol by
default.
-- dann frazier <[email protected]> Fri, 28 Mar 2025 08:23:47 -0600
--- Nouveautés pour ovmf ---
edk2 (2025.02-5) unstable; urgency=medium
The EFI_MEMORY_ATTRIBUTE_PROTOCOL is now enabled by default in the
OVMF_CODE_4M.secboot.fd image. This is a security feature that will
cause crashes for operating systems with bootloaders that do not
observe proper memory access semantics. Users that experience issues
with such bootloaders have the options to either append the following
to the qemu-system-x86_64 command line:
-fw_cfg name=opt/org.tianocore/UninstallMemAttrProtocol,string=y
or switch to the OVMF_CODE_4M.fd (non-secboot) image, which uninstalls
this protocol by default.
-- dann frazier <[email protected]> Fri, 28 Mar 2025 08:23:47 -0600
----->%-----
Again, the problem seems to stem from the fact that apt-listchanges
parses changelogs for each binary package, whereas it should do so for
source packages.
Regards,
--
Raphaël Halimi
--- End Message ---
--- Begin Message ---
Please look more carefully. Those two changelog entries are different.
On 3/29/25 6:06 AM, Raphaël Halimi wrote:
Package: apt-listchanges
Version: 4.8
Dear developer,
Today I received an e-mail showing twice the same NEWS entry :
-----%<-----
--- Nouveautés pour qemu-efi-aarch64 ---
edk2 (2025.02-5) unstable; urgency=medium
The EFI_MEMORY_ATTRIBUTE_PROTOCOL is now enabled by default in the
AAVMF_CODE.secboot.fd image. This is a security feature that will
cause crashes for operating systems with bootloaders that do not
observe proper memory access semantics. Users that experience issues
with such bootloaders have the options to either append the following
to the qemu-system-aarch64 command line:
-fw_cfg name=opt/org.tianocore/UninstallMemAttrProtocol,string=y
or switch to the no-secboot image, which uninstalls this protocol by
default.
-- dann frazier <[email protected]> Fri, 28 Mar 2025 08:23:47 -0600
--- Nouveautés pour ovmf ---
edk2 (2025.02-5) unstable; urgency=medium
The EFI_MEMORY_ATTRIBUTE_PROTOCOL is now enabled by default in the
OVMF_CODE_4M.secboot.fd image. This is a security feature that will
cause crashes for operating systems with bootloaders that do not
observe proper memory access semantics. Users that experience issues
with such bootloaders have the options to either append the following
to the qemu-system-x86_64 command line:
-fw_cfg name=opt/org.tianocore/UninstallMemAttrProtocol,string=y
or switch to the OVMF_CODE_4M.fd (non-secboot) image, which uninstalls
this protocol by default.
-- dann frazier <[email protected]> Fri, 28 Mar 2025 08:23:47 -0600
----->%-----
Again, the problem seems to stem from the fact that apt-listchanges
parses changelogs for each binary package, whereas it should do so for
source packages.
Regards,
--- End Message ---
