Bug#568176: marked as done (memtest86+: multiboot image is broken)
Your message dated Tue, 11 Jan 2022 01:18:31 +
with message-id
and subject line Bug#568176: fixed in memtest86+ 5.31b+dfsg-1
has caused the Debian Bug report #568176,
regarding memtest86+: multiboot image is broken
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.)
--
568176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: memtest86+
Version: 4.00-2.2
Hello,
when I'm booting /boot/memtest86+_multiboot.bin on a Lenovo IdeaPad S12
VIA Nano w/ 3G RAM using grub2, it reports a wrong memory information
and lots of memory errors.
To compare this against the traditional /boot/memtest86+.bin image, I
added a grub2 menu entry via /etc/grub.d/40_custom:
menuentry "Memory test (memtest86+), traditional boot" {
linux16 /boot/memtest86+.bin
}
When I'm booting this entry (which btw. works fine), everything works as
expected: memory information is displayed correctly, no errors are
shown.
Thus, I assume this issue is somehow related to the multiboot patch.
Here is what the traditional memtest86+.bin image reports as system
information:
Memtest86+ v4.00
VIA Isaiah (CN) 1596 MHz
L1 Cache: 64k 19704 MB/s
L2 Cache: 1024k 5284 MB/s
L3 Cache: None
Memory: 2814M 1471 MB/s
Here is what memtest86+_multiboot.bin reports instead (note the Memory:
line):
Memtest86+ v4.00
VIA Isaiah (CN) 1596 MHz
L1 Cache: 64k 19704 MB/s
L2 Cache: 1024k 5198 MB/s
L3 Cache: None
Memory:640k 6514 MB/s
Thanks for your work & regards
Mario
--
The Encyclopedia Galactica, in its chapter on Love states that it is far
too complicated to define.
The Hitchhiker's Guide to the Galaxy has this to say on the subject of
love: Avoid, if at all possible.
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: memtest86+
Source-Version: 5.31b+dfsg-1
Done: Fabio Fantoni
We believe that the bug you reported is fixed in the latest version of
memtest86+, 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 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabio Fantoni (supplier of updated memtest86+ 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: Sun, 09 Jan 2022 21:41:58 +0100
Source: memtest86+
Architecture: source
Version: 5.31b+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Fabio Fantoni
Closes: 568176 612371 695246 783515 898636 977217 989030
Changes:
memtest86+ (5.31b+dfsg-1) experimental; urgency=medium
.
[ Fabio Fantoni ]
* QA upload.
* New upstream version 5.31b (Closes: #989030, #977217)
* Merge from ubuntu:
- Use elf version by default that should works on major of system.
- Drop the multiboot image from the GRUB menu for now, since it's
experimental and has known problems detecting all memory on some
systems at the moment.
- Support localization of GRUB menu entries.
- Don't present in GRUB menu on EFI systems, since it won't work.
(Closes: #695246)
- Close FD 3 when invoking update-grub.
* Warn that don't support EFI instead of exit silently (LP: 1863940)
* Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present
in /etc/default/grub (LP: #420967)
* Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL,
enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add
custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS
(Closes: #898636, #612371)
* Specify on grub2 menu entries when elf and bin are used
* d/control: Remove hwtools and kernel-patch-badram from suggests.
* d/copyright: add Upstream-Name, Upstream-Contact and Source fields
* Bumped Standards-Version to 4.6.0
* d/patches:
- update multiboot patch from coreboot patch based on the one of
Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176)
- refresh memtest86+-5.01-O0.patch
- disable memtest86+-5.01-array-size.patch an
Bug#570499: marked as done (memtest86+: only recognizes 640K of RAM)
Your message dated Tue, 11 Jan 2022 01:18:31 + with message-id and subject line Bug#568176: fixed in memtest86+ 5.31b+dfsg-1 has caused the Debian Bug report #568176, regarding memtest86+: only recognizes 640K of RAM 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.) -- 568176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: memtest86+ Version: 4.00-2.2 Severity: important memtest86+ only sees 640Kb of RAM. This behavior is observed both on an Dell latitude D410 and on an Acer AO751h. Here follows BIOS and ACPI maps for the D410 (w 2Gb RAM): [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 0010 - 7f7d1800 (usable) [0.00] BIOS-e820: 7f7d1800 - 8000 (reserved) [0.00] BIOS-e820: e000 - f0007000 (reserved) [0.00] BIOS-e820: f0008000 - f000c000 (reserved) [0.00] BIOS-e820: fec0 - fec1 (reserved) [0.00] BIOS-e820: fed2 - fee1 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] ACPI: RSDP 000fc9b0 00014 (v00 DELL ) [0.00] ACPI: RSDT 7f7d1f90 00040 (v01 DELLCPi R 27D5091C ASL 0061) [0.00] ACPI: FACP 7f7d2c00 00074 (v01 DELLCPi R 27D5091C ASL 0061) [0.00] ACPI: DSDT 7f7d3800 0390B (v01 INT430 SYSFexxx 1001 MSFT 010E) [0.00] ACPI: FACS 7f7e2000 00040 [0.00] ACPI: APIC 7f7d3400 00068 (v01 DELLCPi R 27D5091C ASL 0047) [0.00] ACPI: ASF! 7f7d3000 0005B (v16 DELLCPi R 27D5091C ASL 0061) [0.00] ACPI: MCFG 7f7d33c0 0003E (v16 DELLCPi R 27D5091C ASL 0061) [0.00] ACPI: SSDT 7f7d23e6 0023E (v01 PmRef Cpu0Ist 3000 INTL 20030522) [0.00] ACPI: SSDT 7f7d220e 001D8 (v01 PmRef Cpu0Cst 3001 INTL 20030522) [0.00] ACPI: SSDT 7f7d2013 001FB (v01 PmRefCpuPm 3000 INTL 20030522) [0.00] ACPI: Local APIC address 0xfee0 [0.00] 1155MB HIGHMEM available. [0.00] 883MB LOWMEM available. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (80, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages memtest86+ depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy memtest86+ recommends no packages. Versions of packages memtest86+ suggests: pn grub2 | grub (no description available) pn hwtools(no description available) pn kernel-patch-badram(no description available) pn memtest86 (no description available) pn memtester (no description available) ii mtools4.0.10-1 Tools for manipulating MSDOS files -- debconf information: shared/memtest86-run-lilo: false --- End Message --- --- Begin Message --- Source: memtest86+ Source-Version: 5.31b+dfsg-1 Done: Fabio Fantoni We believe that the bug you reported is fixed in the latest version of memtest86+, 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 568...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Fantoni (supplier of updated memtest86+ 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: Sun, 09 Jan 2022 21:41:58 +0100 Source: memtest86+ Architecture: source Version: 5.31b+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Fabio Fantoni Closes: 568176 612371 695246 783515 898636 977217 989030 Changes: memtest86+ (5.31b+dfsg-1) experimental; urgency=medium . [ Fabio Fantoni ] * QA upload. * New upst
Bug#612371: marked as done (memtest86+: configures grub with hardcoded serial port parameters)
Your message dated Tue, 11 Jan 2022 01:18:31 + with message-id and subject line Bug#612371: fixed in memtest86+ 5.31b+dfsg-1 has caused the Debian Bug report #612371, regarding memtest86+: configures grub with hardcoded serial port parameters 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.) -- 612371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: memtest86+ Version: 4.10-1.1 Severity: wishlist Hi, Please consider modifying /etc/grub.d/20_memtest86+ to support configurable serial port parameters, preferably taken from cues placed in /etc/default/grub. Thanks! -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990, 'stable'), (500, 'squeeze-updates') Architecture: i386 (i586) Kernel: Linux 2.6.37-net5501 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages memtest86+ depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy memtest86+ recommends no packages. Versions of packages memtest86+ suggests: ii grub-pc 1.98+20100804-14 GRand Unified Bootloader, version pn hwtools(no description available) pn kernel-patch-badram(no description available) pn memtest86 (no description available) ii memtester 4.1.3-1 A utility for testing the memory s pn mtools (no description available) -- Configuration Files: /etc/grub.d/20_memtest86+ changed [not included] -- debconf information excluded --- End Message --- --- Begin Message --- Source: memtest86+ Source-Version: 5.31b+dfsg-1 Done: Fabio Fantoni We believe that the bug you reported is fixed in the latest version of memtest86+, 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 612...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Fantoni (supplier of updated memtest86+ 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: Sun, 09 Jan 2022 21:41:58 +0100 Source: memtest86+ Architecture: source Version: 5.31b+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Fabio Fantoni Closes: 568176 612371 695246 783515 898636 977217 989030 Changes: memtest86+ (5.31b+dfsg-1) experimental; urgency=medium . [ Fabio Fantoni ] * QA upload. * New upstream version 5.31b (Closes: #989030, #977217) * Merge from ubuntu: - Use elf version by default that should works on major of system. - Drop the multiboot image from the GRUB menu for now, since it's experimental and has known problems detecting all memory on some systems at the moment. - Support localization of GRUB menu entries. - Don't present in GRUB menu on EFI systems, since it won't work. (Closes: #695246) - Close FD 3 when invoking update-grub. * Warn that don't support EFI instead of exit silently (LP: 1863940) * Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present in /etc/default/grub (LP: #420967) * Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL, enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS (Closes: #898636, #612371) * Specify on grub2 menu entries when elf and bin are used * d/control: Remove hwtools and kernel-patch-badram from suggests. * d/copyright: add Upstream-Name, Upstream-Contact and Source fields * Bumped Standards-Version to 4.6.0 * d/patches: - update multiboot patch from coreboot patch based on the one of Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176) - refresh memtest86+-5.01-O0.patch - disable memtest86+-5.01-array-size.patch and gcc-5 as seems not needed with newer upstream version - refresh serial-console-fix.patch - add test-random-cflags.patch: use CFLAGS with random.o for maintain flags like -fno-stack-protector - add fix-gcc8-freeze-crash.patch
Bug#695246: marked as done (grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails))
Your message dated Tue, 11 Jan 2022 01:18:31 +
with message-id
and subject line Bug#695246: fixed in memtest86+ 5.31b+dfsg-1
has caused the Debian Bug report #695246,
regarding grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot
also fails)
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.)
--
695246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-efi-amd64
Version: 2.00-7
Severity: normal
I've installed grub-efi-amd64 2.00-7 and memtest86+ 4.20-1.1 on this
Thinkpad x220. However, the memtest86+ boot options don't work:
* the normal memtest86+ stanza complains that there is no linux16
command.
* the "experimental multiboot" memtest86+ stanza turns the screen
black, and then reboots; no memory is tested.
any suggestions about how i can run memtest86+ on this platform from
grub-efi? Any more information i can provide to help debug?
--dkg
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/vg_alice0-root / ext4
rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_alice0-home /home ext4
rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_alice0-var /var ext4
rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/sda2 /boot ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/sda1 /boot/efi vfat
rw,nosuid,nodev,noexec,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if loadfont unicode ; then
set gfxmode=1024x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
c4425021-9542-4ff6-888c-548c08b4a69c
else
search --no-floppy --fs-uuid --set=root c4425021-9542-4ff6-888c-548c08b4a69c
fi
insmod png
if background_image /grub/.background_cache.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-5b7c89b1-cf26-4427-b8a9-8c74e4897111' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
c4425021-9542-4ff6-888c-548c08b4a69c
else
search --no-floppy --fs-uuid --set=root
c4425021-9542-4ff6-888c-548c08b4a69c
fi
echo'Loading Linux 3.2.0-4-amd64 ...'
linux /vmlinuz-3.2.0-4-amd64 root=/dev/mapper/vg_alice0-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-4-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option
'gnulinux-advanced-5b7c89b1-cf26-4427-b8a9-8c74e4897111' {
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian
--class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.2.0-4-amd64-
Bug#898636: marked as done (Adding code for toggling 'serial console' and 'multiboot' memtest86+ GRUB2 menu entries on and off)
Your message dated Tue, 11 Jan 2022 01:18:31 +
with message-id
and subject line Bug#898636: fixed in memtest86+ 5.31b+dfsg-1
has caused the Debian Bug report #898636,
regarding Adding code for toggling 'serial console' and 'multiboot' memtest86+
GRUB2 menu entries on and off
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.)
--
898636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: memtest86+
Version: 4.10-1.1
Severity: wishlist
Tags: patch
When installing the memtest86+ package, four GRUB menu entries get added
nowadays:
memtest86+
memtest86+, serial console 115200
memtest86+, experimental multiboot
memtest86+, serial console 115200, experimental multiboot
In order to reduce that, I've added two variables and some if-statements
to /etc/grub.d/20_memtest86+.
In /etc/default/grub:
GRUB_MEMTEST_ENABLE_SERIAL=[true|false]
GRUB_MEMTEST_ENABLE_MULTIBOOT=[true|false]
In addition, I've added a variable holding the memtest86+ serial params:
GRUB_MEMTEST_SERIAL_PARAMS="ttyS0,115200n8"
In /etc/grub.d/20_memtest86+:
Have a look at the patch file.
-- System Information:
Debian Release: 6.0.10
APT prefers oldoldstable-updates
APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-0.bpo.4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc1.98+20100804-14+squeeze1 GRand Unified Bootloader, version
pn hwtools(no description available)
pn kernel-patch-b (no description available)
pn memtest86 (no description available)
pn memtester (no description available)
ii mtools 4.0.12-1 Tools for manipulating MSDOS files
-- Configuration Files:
/etc/grub.d/20_memtest86+ changed:
set -e
if [ -f /usr/lib/grub/grub-mkconfig_lib ]; then
. /usr/lib/grub/grub-mkconfig_lib
LX=linux16
elif [ -f /usr/lib/grub/update-grub_lib ]; then
. /usr/lib/grub/update-grub_lib
LX=linux
else
# no grub file, so we notify and exit gracefully
echo "Cannot find grub config file, exiting." >&2
exit 0
fi
case ${GRUB_DEVICE_BOOT} in
/dev/loop/*|/dev/loop[0-9]) exit 0 ;;
esac
prepare_boot_cache="$(prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed
-e "s/^/\t/")"
if test -e /boot/memtest86+.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root "/boot/memtest86+.bin" )
echo "Found memtest86+ image: $MEMTESTPATH" >&2
cat << EOF
menuentry "Memory test (memtest86+)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
$LX $MEMTESTPATH
}
EOF
if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
cat << EOF
menuentry "Memory test (memtest86+, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
$LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
fi
if [ "${GRUB_MEMTEST_ENABLE_MULTIBOOT}" = "true" ]; then
if test -e /boot/memtest86+_multiboot.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root
"/boot/memtest86+_multiboot.bin" )
echo "Found memtest86+ multiboot image: $MEMTESTPATH" >&2
cat << EOF
menuentry "Memory test (memtest86+, experimental multiboot)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
multiboot $MEMTESTPATH
}
EOF
if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
cat << EOF
menuentry "Memory test (memtest86+, experimental multiboot, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
fi
fi
-- debconf information:
shared/memtest86-run-lilo: false
--- 20_memtest86+.orig 2018-05-14 00:52:58.719587898 +0200
+++ 20_memtest86+ 2015-02-18 17:47:52.0 +0100
@@ -30,16 +30,21 @@
cat << EOF
$LX $MEMTESTPATH
}
-menuentry "Memory test (memtest86+, serial console 115200)" {
+EOF
+ if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
+ cat << EOF
+menuentry "Memory test (memtest86+, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
- $LX $MEMTESTPATH console=ttyS0,115200n8
+ $LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
fi
Bug#783515: marked as done (memtest86+: please make package build reproducibly)
Your message dated Tue, 11 Jan 2022 01:18:31 + with message-id and subject line Bug#783515: fixed in memtest86+ 5.31b+dfsg-1 has caused the Debian Bug report #783515, regarding memtest86+: please make package build reproducibly 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.) -- 783515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: memtest86+ Version: 5.01-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps Control: block -1 by 783513 Hi! While working on the “reproducible builds” effort [1], we have noticed that memtest86+ could not be built reproducibly. The attached patch set the file and ISO image creation date. With this patch and the one submitted in #783513, memtest86+ can then be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: memtest86+ Source-Version: 5.31b+dfsg-1 Done: Fabio Fantoni We believe that the bug you reported is fixed in the latest version of memtest86+, 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 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Fantoni (supplier of updated memtest86+ 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: Sun, 09 Jan 2022 21:41:58 +0100 Source: memtest86+ Architecture: source Version: 5.31b+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Fabio Fantoni Closes: 568176 612371 695246 783515 898636 977217 989030 Changes: memtest86+ (5.31b+dfsg-1) experimental; urgency=medium . [ Fabio Fantoni ] * QA upload. * New upstream version 5.31b (Closes: #989030, #977217) * Merge from ubuntu: - Use elf version by default that should works on major of system. - Drop the multiboot image from the GRUB menu for now, since it's experimental and has known problems detecting all memory on some systems at the moment. - Support localization of GRUB menu entries. - Don't present in GRUB menu on EFI systems, since it won't work. (Closes: #695246) - Close FD 3 when invoking update-grub. * Warn that don't support EFI instead of exit silently (LP: 1863940) * Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present in /etc/default/grub (LP: #420967) * Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL, enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS (Closes: #898636, #612371) * Specify on grub2 menu entries when elf and bin are used * d/control: Remove hwtools and kernel-patch-badram from suggests. * d/copyright: add Upstream-Name, Upstream-Contact and Source fields * Bumped Standards-Version to 4.6.0 * d/patches: - update multiboot patch from coreboot patch based on the one of Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176) - refresh memtest86+-5.01-O0.patch - disable memtest86+-5.01-array-size.patch and gcc-5 as seems not needed with newer upstream version - refresh serial-console-fix.patch - add test-random-cflags.patch: use CFLAGS with random.o for maintain flags like -fno-stack-protector - add fix-gcc8-freeze-crash.patch: runtime fix for gcc>=8 freeze/crash - add discard-note_gnu_property.patch: discards the ".note.gnu.property" section that causes crash in some cases . [ Jérémy Bobbio ] * Make the package build reproducibly: - Add a patch to make ISO image reproducible. - Set the build date to the latest debian/changelog entry in debian/rules. (Closes: #783515) Checksums-Sha1: ccede9fb94a6db33aa012d3ab4f37ef549ec01ea 1906 memtest86+
Bug#977217: marked as done (New upstream release available, fixes stuck test on UEFI systems)
Your message dated Tue, 11 Jan 2022 01:18:31 + with message-id and subject line Bug#977217: fixed in memtest86+ 5.31b+dfsg-1 has caused the Debian Bug report #977217, regarding New upstream release available, fixes stuck test on UEFI systems 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.) -- 977217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: memtest86+ Version: 5.01-3.1 The version of memtest86+ shipped by Debian gets stuck on many UEFI systems (see other bug reports, google search). The latest upstream release (5.31b) fixes that. I was suspecting bad RAM when memtest86+ would get stuck shortly after start, however normally the system runs just fine. A brief internet search led to results suggesting that this is a bug in memtest86+ 5.01 that has been fixed upstream. I tried the latest .iso image provided by http://www.memtest.org and there the test ran with no errors or freezes. It would be great if you could update the package so that it no longer reports false positives on lots of systems! Best, Benjamin --- End Message --- --- Begin Message --- Source: memtest86+ Source-Version: 5.31b+dfsg-1 Done: Fabio Fantoni We believe that the bug you reported is fixed in the latest version of memtest86+, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Fantoni (supplier of updated memtest86+ 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: Sun, 09 Jan 2022 21:41:58 +0100 Source: memtest86+ Architecture: source Version: 5.31b+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Fabio Fantoni Closes: 568176 612371 695246 783515 898636 977217 989030 Changes: memtest86+ (5.31b+dfsg-1) experimental; urgency=medium . [ Fabio Fantoni ] * QA upload. * New upstream version 5.31b (Closes: #989030, #977217) * Merge from ubuntu: - Use elf version by default that should works on major of system. - Drop the multiboot image from the GRUB menu for now, since it's experimental and has known problems detecting all memory on some systems at the moment. - Support localization of GRUB menu entries. - Don't present in GRUB menu on EFI systems, since it won't work. (Closes: #695246) - Close FD 3 when invoking update-grub. * Warn that don't support EFI instead of exit silently (LP: 1863940) * Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present in /etc/default/grub (LP: #420967) * Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL, enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS (Closes: #898636, #612371) * Specify on grub2 menu entries when elf and bin are used * d/control: Remove hwtools and kernel-patch-badram from suggests. * d/copyright: add Upstream-Name, Upstream-Contact and Source fields * Bumped Standards-Version to 4.6.0 * d/patches: - update multiboot patch from coreboot patch based on the one of Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176) - refresh memtest86+-5.01-O0.patch - disable memtest86+-5.01-array-size.patch and gcc-5 as seems not needed with newer upstream version - refresh serial-console-fix.patch - add test-random-cflags.patch: use CFLAGS with random.o for maintain flags like -fno-stack-protector - add fix-gcc8-freeze-crash.patch: runtime fix for gcc>=8 freeze/crash - add discard-note_gnu_property.patch: discards the ".note.gnu.property" section that causes crash in some cases . [ Jérémy Bobbio ] * Make the package build reproducibly: - Add a patch to make ISO image reproducible. - Set the build date to the latest debian/changelog entry in debian/rules. (Closes: #783515) Checksums-Sha1: ccede9fb94a6db33aa012d3ab4f37ef549ec01ea 1906 memtest86+_5.31b+dfsg-1.dsc 5689804e55318543d881f49b28d3463a85d31d9d 181212 memtest86+_5.31
Bug#989030: marked as done (memtest86+: New upstream version available v5.31b)
Your message dated Tue, 11 Jan 2022 01:18:31 +
with message-id
and subject line Bug#989030: fixed in memtest86+ 5.31b+dfsg-1
has caused the Debian Bug report #989030,
regarding memtest86+: New upstream version available v5.31b
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.)
--
989030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: memtest86+
Version: 5.01-3.1
Severity: wishlist
Dear Maintainer,
According to memtest.org site, there's a new upstream version available for
testing.
https://www.memtest.org/#downcode
In diff I see something like:
+ }else if (mem_devs[i]->size == 0x7FFF){
+ // SMBIOS 2.7+
+ size_in_mb = mem_devs[i]->ext_size;
+ itoa(string, size_in_mb);
+ cprint(yof, POP2_X+4+18, st
so might be interesting.
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to ja_JP.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.75
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
pn grub-pc | grub-legacy
pn hwtools
pn kernel-patch-badram
pn memtest86
pn memtester
pn mtools
-- debconf information:
shared/memtest86-run-lilo: false
--- End Message ---
--- Begin Message ---
Source: memtest86+
Source-Version: 5.31b+dfsg-1
Done: Fabio Fantoni
We believe that the bug you reported is fixed in the latest version of
memtest86+, 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 989...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabio Fantoni (supplier of updated memtest86+ 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: Sun, 09 Jan 2022 21:41:58 +0100
Source: memtest86+
Architecture: source
Version: 5.31b+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Fabio Fantoni
Closes: 568176 612371 695246 783515 898636 977217 989030
Changes:
memtest86+ (5.31b+dfsg-1) experimental; urgency=medium
.
[ Fabio Fantoni ]
* QA upload.
* New upstream version 5.31b (Closes: #989030, #977217)
* Merge from ubuntu:
- Use elf version by default that should works on major of system.
- Drop the multiboot image from the GRUB menu for now, since it's
experimental and has known problems detecting all memory on some
systems at the moment.
- Support localization of GRUB menu entries.
- Don't present in GRUB menu on EFI systems, since it won't work.
(Closes: #695246)
- Close FD 3 when invoking update-grub.
* Warn that don't support EFI instead of exit silently (LP: 1863940)
* Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present
in /etc/default/grub (LP: #420967)
* Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL,
enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add
custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS
(Closes: #898636, #612371)
* Specify on grub2 menu entries when elf and bin are used
* d/control: Remove hwtools and kernel-patch-badram from suggests.
* d/copyright: add Upstream-Name, Upstream-Contact and Source fields
* Bumped Standards-Version to 4.6.0
* d/patches:
- update multiboot patch from coreboot patch based on the one of
Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176)
- refresh memtest86+-5.01-O0.patch
- disable memtest86+-5.01-array-size.patch and gcc-5 as seems not
needed with newer upstream version
- refresh serial-console-fix.patch
- add test-random-cflags.patch
Processing of memtest86+_5.31b+dfsg-1_source.changes
memtest86+_5.31b+dfsg-1_source.changes uploaded successfully to localhost along with the files: memtest86+_5.31b+dfsg-1.dsc memtest86+_5.31b+dfsg.orig.tar.xz memtest86+_5.31b+dfsg-1.debian.tar.xz memtest86+_5.31b+dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
memtest86+_5.31b+dfsg-1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Jan 2022 21:41:58 +0100 Source: memtest86+ Architecture: source Version: 5.31b+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Fabio Fantoni Closes: 568176 612371 695246 783515 898636 977217 989030 Changes: memtest86+ (5.31b+dfsg-1) experimental; urgency=medium . [ Fabio Fantoni ] * QA upload. * New upstream version 5.31b (Closes: #989030, #977217) * Merge from ubuntu: - Use elf version by default that should works on major of system. - Drop the multiboot image from the GRUB menu for now, since it's experimental and has known problems detecting all memory on some systems at the moment. - Support localization of GRUB menu entries. - Don't present in GRUB menu on EFI systems, since it won't work. (Closes: #695246) - Close FD 3 when invoking update-grub. * Warn that don't support EFI instead of exit silently (LP: 1863940) * Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present in /etc/default/grub (LP: #420967) * Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL, enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS (Closes: #898636, #612371) * Specify on grub2 menu entries when elf and bin are used * d/control: Remove hwtools and kernel-patch-badram from suggests. * d/copyright: add Upstream-Name, Upstream-Contact and Source fields * Bumped Standards-Version to 4.6.0 * d/patches: - update multiboot patch from coreboot patch based on the one of Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176) - refresh memtest86+-5.01-O0.patch - disable memtest86+-5.01-array-size.patch and gcc-5 as seems not needed with newer upstream version - refresh serial-console-fix.patch - add test-random-cflags.patch: use CFLAGS with random.o for maintain flags like -fno-stack-protector - add fix-gcc8-freeze-crash.patch: runtime fix for gcc>=8 freeze/crash - add discard-note_gnu_property.patch: discards the ".note.gnu.property" section that causes crash in some cases . [ Jérémy Bobbio ] * Make the package build reproducibly: - Add a patch to make ISO image reproducible. - Set the build date to the latest debian/changelog entry in debian/rules. (Closes: #783515) Checksums-Sha1: ccede9fb94a6db33aa012d3ab4f37ef549ec01ea 1906 memtest86+_5.31b+dfsg-1.dsc 5689804e55318543d881f49b28d3463a85d31d9d 181212 memtest86+_5.31b+dfsg.orig.tar.xz 0e00bc6d73765cd6c13746ae39f0c60da99d3bf0 20996 memtest86+_5.31b+dfsg-1.debian.tar.xz 555993d36a4e1b176380093a2857f01d111c1c30 5440 memtest86+_5.31b+dfsg-1_source.buildinfo Checksums-Sha256: b14835245a8975fef057293215d46b4c6be66647b5b4c203b3087f5fc0c2f394 1906 memtest86+_5.31b+dfsg-1.dsc b31025b00fddd35ec8794cbe832289562cdd9690a5d0062e9ac69eb655e2605f 181212 memtest86+_5.31b+dfsg.orig.tar.xz 709c2962bde409ce9047612f7f7e7d804a31826dce43083938a940b386a9ac48 20996 memtest86+_5.31b+dfsg-1.debian.tar.xz 2e7ecfd18a7eb5f762730f26874c047a0eecd9730675a71c7ed49018dbb30809 5440 memtest86+_5.31b+dfsg-1_source.buildinfo Files: 900732fd9845aba8044568a1162ccd2d 1906 misc optional memtest86+_5.31b+dfsg-1.dsc 75fdce14981f566e212667008877b889 181212 misc optional memtest86+_5.31b+dfsg.orig.tar.xz 1e7c755130ecc7b56c6ccb46e5196525 20996 misc optional memtest86+_5.31b+dfsg-1.debian.tar.xz c69e14a34b0dc32e57aa01a26e68b097 5440 misc optional memtest86+_5.31b+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmHc15sQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFOUKC/4vnGvlv5n4NxmyKVW95YQppUdpucbnNaMF jNHMPpOTMIujkvONmoG8GZROqqnzy0OQmAMKjYIJ6GybwvSbLQI7viFqWzcWi7YB 6Hsv97WfVx3cGtP5Mhd3u3FuCf/JGgGIId2EQxm7bgHxy4Vbn7MlEg6OyL5VjPMj jHaxAVcFY1N4CXDxskQ7qxnpfRCxEmBMqJgdMiyxXkr8yMFJUYGJmYbx5i52kB82 uXvNohdqsK4sSEHbFwzlN151oPXf6S3p5BSKNdT7SNjbtBKUAnRzI6wLDtBKM2I4 8g77TJhW+iwer88TQwzEfZaYM+huELHKKkAoS5oDsMGq4ryXxltmFAlmCW9OPPhM I/QxP+ZrIB41UkpcoyIR3HwNt/QyDVTec6YCSUUvOqUOAdmVkBSh9zDXdrU9uhgw S9yEpSpkXbsEeciy+JhMmvjg3vh+pibPhTl7LqKLtElCWA8AXs71ZA0Pwx69caHs VrDFQ0f1oE2yzvZBSq2NMhg1w4efH+w= =jkX9 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1003493: gadmin-openvpn-client: persistent files after uninstall of gadmin gui - killing otehers openvpn processes!
Package: gadmin-openvpn-client Version: 0.1.9-1 Severity: important Dear Maintainer, This affects gadmin-openvpn-client and server too. Once uninstalled you MUST delete these two persistent files too: gadmin-openvpn-client and gadmin-openvpn-server placed in /etc/init.d directory, otherwise any other openvpn precess set and launched as usual (without a gui) will be killed!! And you become crazy because there is not online help about this and it's like to find a needle in a haystack it's amazing. These files are not included in the package file list! Hope this can help. Ale -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/4 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.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 gadmin-openvpn-client depends on: ii libc6 2.31-13+deb11u2 ii libcrypt1 1:4.4.18-4 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-02.66.8-1 ii libgtk2.0-0 2.24.33-2 ii menu2.1.48 ii openvpn 2.5.1-3 gadmin-openvpn-client recommends no packages. gadmin-openvpn-client suggests no packages.
mcrypt is marked for autoremoval from testing
mcrypt 2.6.8-5 is marked for autoremoval from testing on 2022-02-08 It (build-)depends on packages with these RC bugs: 993033: libmcrypt: libmcrypt FTBFS: autoreconf failure https://bugs.debian.org/993033 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
lxctl is marked for autoremoval from testing
lxctl 0.3.1+debian-4 is marked for autoremoval from testing on 2022-02-08 It (build-)depends on packages with these RC bugs: 993716: bridge-utils: IPv6 network bridge fails after upgrading Buster to Bullseye https://bugs.debian.org/993716 998516: bridge-utils: Kernel assigns same MAC-address to the bridge on 2 similar network devices https://bugs.debian.org/998516 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
libguess is marked for autoremoval from testing
libguess 1.2-5 is marked for autoremoval from testing on 2022-02-08 It (build-)depends on packages with these RC bugs: 993033: libmcrypt: libmcrypt FTBFS: autoreconf failure https://bugs.debian.org/993033 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
dact is marked for autoremoval from testing
dact 0.8.42-5 is marked for autoremoval from testing on 2022-02-08 It (build-)depends on packages with these RC bugs: 993033: libmcrypt: libmcrypt FTBFS: autoreconf failure https://bugs.debian.org/993033 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
clipit is marked for autoremoval from testing
clipit 1.4.4+git20190202-2 is marked for autoremoval from testing on 2022-02-08
It (build-)depends on packages with these RC bugs:
1002722: python-rdflib-tools: python-rdflib-tools must depend on python3-rdflib
(= ${source:Version})
https://bugs.debian.org/1002722
997287: zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name
`pdata' does not exist in the context of `GLib.PtrArray*'
https://bugs.debian.org/997287
997652: sparql-wrapper-python: FTBFS: error in SPARQLWrapper setup command:
use_2to3 is invalid.
https://bugs.debian.org/997652
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
zeitgeist is marked for autoremoval from testing
zeitgeist 1.0.3-6 is marked for autoremoval from testing on 2022-02-08
It is affected by these RC bugs:
997287: zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name
`pdata' does not exist in the context of `GLib.PtrArray*'
https://bugs.debian.org/997287
It (build-)depends on packages with these RC bugs:
1002722: python-rdflib-tools: python-rdflib-tools must depend on python3-rdflib
(= ${source:Version})
https://bugs.debian.org/1002722
997652: sparql-wrapper-python: FTBFS: error in SPARQLWrapper setup command:
use_2to3 is invalid.
https://bugs.debian.org/997652
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
videotrans is marked for autoremoval from testing
videotrans 1.6.1-8 is marked for autoremoval from testing on 2022-02-08 It (build-)depends on packages with these RC bugs: 965865: vstream-client: Removal of obsolete debhelper compat 5 and 6 in bookworm https://bugs.debian.org/965865 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
qpsmtpd is marked for autoremoval from testing
qpsmtpd 0.94-4 is marked for autoremoval from testing on 2022-02-08 It (build-)depends on packages with these RC bugs: 1000896: libipc-shareable-perl: fails to migrate to testing for too long: autopkgtest regression https://bugs.debian.org/1000896 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
