Bug#1036869: marked as done (ghostscript: Needs commitment for Debian downstream maintenance)
Your message dated Sat, 06 Jan 2024 07:51:41 + with message-id and subject line Bug#1036869: fixed in ghostscript 10.02.1~dfsg-2 has caused the Debian Bug report #1036869, regarding ghostscript: Needs commitment for Debian downstream maintenance 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.) -- 1036869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript Version: 10.0.0~dfsg-11 Severity: serious Justification: commitment for maintenance X-Debbugs-Cc: car...@debian.org, t...@security.debian.org Hi ghostscript is orphaned and unter the Debian QA group. ghostscript beeing a package with recurring need of maintenance and in particular which from time to time needs addressing CVEs needs active maintainership. This bug serves to make the package appear on the radar of packages requiring active maintainers. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.02.1~dfsg-2 Done: Steve M. Robbins We believe that the bug you reported is fixed in the latest version of ghostscript, 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 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated ghostscript 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: SHA256 Format: 1.8 Date: Sat, 06 Jan 2024 01:16:23 -0600 Source: ghostscript Architecture: source Version: 10.02.1~dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Steve M. Robbins Closes: 1022718 1036869 1052652 Changes: ghostscript (10.02.1~dfsg-2) unstable; urgency=medium . [ Steve Robbins ] * [4b077b5] Incorporate upstream patch to fix PageList processing in PDF handler. Closes: #1052652 * [b4524f9] New maintainer. Closes: #1022718, #1036869. Checksums-Sha1: ae9781f26b563ab31a53d89486100405812517fe 2796 ghostscript_10.02.1~dfsg-2.dsc 9c6b50e94fcc37df3bc9b099fc89b55bc584e667 84104 ghostscript_10.02.1~dfsg-2.debian.tar.xz 33c3ec652346e411d3335d13e5e7a55f79dda450 9 ghostscript_10.02.1~dfsg-2_source.buildinfo Checksums-Sha256: dd11e44c3dbcb869185d8ae302e0d8bfd25404c9026791960e2fba1edde2e82b 2796 ghostscript_10.02.1~dfsg-2.dsc 708069c7bf630c96b13b96b190bc0b232f81050cbd740a7fac97b8afe9fbe30c 84104 ghostscript_10.02.1~dfsg-2.debian.tar.xz 63d46e3099ff99452c7bd380326d631789090c12e88bb89f4d666926958b28d8 9 ghostscript_10.02.1~dfsg-2_source.buildinfo Files: 7ef616956e367d3e7f12f496e731a206 2796 text optional ghostscript_10.02.1~dfsg-2.dsc 467630e7c9bf91dee8ed5dcf4f742683 84104 text optional ghostscript_10.02.1~dfsg-2.debian.tar.xz fe5d162e0dab3e3882bb2fc57ce4701c 9 text optional ghostscript_10.02.1~dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAmWZAX8PHHNtckBkZWJp YW4ub3JnAAoJEMnlXi+tyPS51KkP/AyK2XWCdz/kJqnlP/j8Ma/QntAkr2N8XvXM felY/tnbvRdreYqeYyoCLEBihXocLCX47VTIIQcvcPTpSIA3sWR8xOE4FBSgZCD0 zog0AkoR8ZAT6y8uwStfLkcVA/SNrfTroOOEyh0+VsItekTU0PXtyuDzN8qPmHa5 E29grsT4ABVyznOJBoG5VhzZzS6BpGsOUGSq6UlR8fRUcP4q+9EXgSNrnJqebIEZ 0wio+3Ih1Kvx5im3uhYwf3NKraJRCcBilf3kdiX8H4L5juSyqIfj2EKpW3btB9a8 CwN8CS36ORQNh2eKtdDEI+J592tmqe0vxnEgTguSeykRt0omCMmvhclWEdE9y/vk UTB/FDos+s3n5tqdUEMQ5rxxJT+99JOAZjWT09KVPJKaS7qeFKWy8VjzZMccRAbc OeBrAYmta6dW+lbG0Px0kxTM/iLhP7WHAU8qdJez1I11fahFkeKeWNHDzCP0iYj4 Z14IGARjjGv/cZrtCqIy2O3prNVy4YYozot4d76kphM+vVETwWRl8mo3Zd4Caby8 nYtrq/KKDnmzPeDAL16ZKwym6Eb6ojZ0xWxskS847b55kjOTAvBK2wpAQR2ky/+v xQ1laY2yqa5Vz6CXqcvRrjyON5ITnoNY8uvkXJx+oyL9xmMtKbtWB9ivzI6mSr98 lKLqwlhA =iPoq -END PGP SIGNATURE End Message ---
Bug#1055550: Removal of Python3 package of redland-bindings breaks mozilla-devscripts
Hi Doko, thanks for working on the QA upload to fix #100 and #1056518 of redland-bindings by simply removing the Python3 support. Unfortunately it breaks mozilla-devscripts and thus it cant migrate to testing[1]. Kind regards Andreas. [1] https://qa.debian.org/excuses.php?package=redland-bindings -- http://fam-tille.de
Bug#1052724: marked as done (u-boot: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for this target)
Your message dated Sat, 06 Jan 2024 03:08:28 +
with message-id
and subject line Bug#1052724: fixed in u-boot 2024.01~rc6+dfsg-1
has caused the Debian Bug report #1052724,
regarding u-boot: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported
for this target
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.)
--
1052724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: u-boot
Version: 2023.07+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/debian/build/qemu_arm'
> make -f /<>/Makefile syncconfig
> make -f /<>/scripts/Makefile.build obj=scripts/basic
> ln -fsn /<> source
> /bin/bash /<>/scripts/mkmakefile /<>
> GEN Makefile
> rm -f .tmp_quiet_recordmcount
> make -f /<>/scripts/Makefile.build obj=scripts/kconfig syncconfig
> scripts/kconfig/conf --syncconfig Kconfig
> make -f /<>/scripts/Makefile.autoconf || \
> { rm -f include/config/auto.conf; false; }
> mkdir -p include/asm
> if [ -d /<>/arch/arm/mach-/include/mach ]; then \
> dest=arch/arm/mach-/include/mach; \
> else \
> dest=arch/arm/include/asm/arch-armv7; \
> fi; \
> ln -fsn /<>/$dest include/asm/arch
> set -e; mkdir -p include/;(echo "/* Automatically generated - do not edit
> */"; echo \#define CFG_BOARDDIR board/emulation/qemu-arm; echo \#include
> \; echo \#include \; echo \#include
> \; echo \#include \;) <
> /<>/scripts/Makefile.autoconf > include/config.h.tmp; if [ -r
> include/config.h ] && cmp -s include/config.h include/config.h.tmp; then rm
> -f include/config.h.tmp; else : ' UPD include/config.h'; mv -f
> include/config.h.tmp include/config.h; fi
> arm-linux-gnueabihf-gcc -E -Wall -Wstrict-prototypes -Wno-format-security
> -fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing
> -fno-PIE -fno-stack-protector -fno-delete-null-pointer-checks
> -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds
> -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized
> -ffile-prefix-map=/<>/= -gdwarf-4 -fstack-usage
> -Wno-format-nonliteral -Wno-address-of-packed-member
> -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned
> -D__KERNEL__ -D__UBOOT__ -D__ARM__ -marm -mno-thumb-interwork
> -mabi=aapcs-linux -mword-relocations -fno-pic -mno-unaligned-access
> -ffunction-sections -fdata-sections -fno-common -ffixed-r9 -msoft-float
> -mgeneral-regs-only-pipe -Iinclude -I/<>/include
> -I/<>/arch/arm/include -include
> /<>/include/linux/kconfig.h -nostdinc -isystem
> /usr/lib/gcc-cross/arm-linux-gnueabihf/13/include -DDO_DEPS_ONLY -dM
> /<>/include/common.h > u-boot.cfg.tmp && { grep 'define CONFIG_'
> u-boot.cfg.tmp | sed '/define CONFIG_IS_ENABLED(/d;/define
> CONFIG_IF_ENABLED_INT(/d;/define CONFIG_VAL(/d;' > u-boot.cfg; rm
> u-boot.cfg.tmp; } || { rm u-boot.cfg.tmp; false; }
> arm-linux-gnueabihf-gcc -x c -DDO_DEPS_ONLY -M -MP -Wall
> -Wstrict-prototypes -Wno-format-security -fno-builtin -ffreestanding
> -std=gnu11 -fshort-wchar -fno-strict-aliasing -fno-PIE -fno-stack-protector
> -fno-delete-null-pointer-checks -Wno-pointer-sign -Wno-stringop-truncation
> -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow
> -Wno-maybe-uninitialized -ffile-prefix-map=/<>/= -gdwarf-4
> -fstack-usage -Wno-format-nonliteral -Wno-address-of-packed-member
> -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned
> -D__KERNEL__ -D__UBOOT__ -D__ARM__ -marm -mno-thumb-interwork
> -mabi=aapcs-linux -mword-relocations -fno-pic -mno-unaligned-access
> -ffunction-sections -fdata-sections -fno-common -ffixed-r9 -msoft-float
> -mgeneral-regs-only-pipe -Iinclude -I/<>/include
> -I/<>/arch/arm/include -include
> /<>/include/linux/kconfig.h -nostdinc -isystem
> /usr/lib/gcc-cross/arm-linux-gnueabihf/13/include -MQ
> include/config/auto.conf /<>/include/common.h >
> include/autoconf.mk.dep || { rm include/autoconf.mk.dep; false; }
> sed -n -f /<>/tools/scripts/define2mk.sed u-boot.cfg | while
> read line; do if [ -n "" ] || ! grep -q "${line%=*}="
> include/config/auto.conf; then echo "$line"; fi; done > include/autoconf.mk
> touch
Bug#1059657: circuits: autopkgtest failure with Python 3.12
Hi, Made a patch to fix the autopkgtest issue with Py 3.12. Attaching the debdiff file. Cheers! diff -Nru circuits-3.2.2/debian/changelog circuits-3.2.2/debian/changelog --- circuits-3.2.2/debian/changelog 2022-12-14 16:15:09.0 + +++ circuits-3.2.2/debian/changelog 2024-01-06 01:27:18.0 + @@ -1,3 +1,11 @@ +circuits (3.2.2-1.1) UNRELEASED; urgency=medium + + * Non-maintainer/Team upload. (Closes: #1059657) + * Included a patch for /circuits/core/utils.py to replace +deprecated imp with importlib to fix autopkgtest in Py3.12. + + -- Yogeswaran Umasankar Sat, 06 Jan 2024 01:27:18 + + circuits (3.2.2-1) unstable; urgency=medium * New upstream version 3.2.2 (Closes: #1024860) diff -Nru circuits-3.2.2/debian/patches/06_replace-imp-with-importlib.patch circuits-3.2.2/debian/patches/06_replace-imp-with-importlib.patch --- circuits-3.2.2/debian/patches/06_replace-imp-with-importlib.patch 1970-01-01 00:00:00.0 + +++ circuits-3.2.2/debian/patches/06_replace-imp-with-importlib.patch 2024-01-06 01:21:32.0 + @@ -0,0 +1,27 @@ +Description: Implemented importlib to fix autopkgtest failure with Python 3.12. +Author: Yogeswaran Umasankar +Last-Update: 2024-01-06 + +--- a/circuits/core/utils.py b/circuits/core/utils.py +@@ -3,7 +3,7 @@ + This module defines utilities used by circuits. + """ + import sys +-from imp import reload ++import importlib + + + def flatten(root, visited=None): +@@ -53,9 +53,9 @@ def safeimport(name): + modules = sys.modules.copy() + try: + if name in sys.modules: +-return reload(sys.modules[name]) ++return importlib.reload(sys.modules[name]) + else: +-return __import__(name, globals(), locals(), [""]) ++return importlib.import_module(name) + except Exception: + for name in sys.modules.copy(): + if name not in modules: diff -Nru circuits-3.2.2/debian/patches/series circuits-3.2.2/debian/patches/series --- circuits-3.2.2/debian/patches/series2022-12-14 16:15:09.0 + +++ circuits-3.2.2/debian/patches/series2024-01-06 01:15:42.0 + @@ -2,3 +2,4 @@ 03_disable-address-check.patch 04_remove-google-adsense.patch 05_remove-privacy-breach-badges.patch +06_replace-imp-with-importlib.patch signature.asc Description: PGP signature
Bug#1057929: marked as done (buildbot: FTBFS: locale.Error: unsupported locale setting)
Your message dated Sat, 06 Jan 2024 01:16:30 +
with message-id
and subject line Bug#1057929: fixed in buildbot 3.10.1-1
has caused the Debian Bug report #1057929,
regarding buildbot: FTBFS: locale.Error: unsupported locale setting
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.)
--
1057929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:buildbot
Version: 3.9.2-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with python3,bash-completion,sphinxdoc
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=pybuild --sourcedirectory=master \
--package=buildbot
pybuild --configure -i python{version} -p 3.11 --dir master
I: pybuild base:310: python3.11 setup.py config
/<>/master/setup.py:27: DeprecationWarning: pkg_resources is
deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
import pkg_resources
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly:
Normalizing '3.9.2-2' to '3.9.2.post2'
self.metadata.version = self._normalize_version(
running config
dh_auto_configure --buildsystem=pybuild --sourcedirectory=worker \
--package=buildbot-worker
pybuild --configure -i python{version} -p 3.11 --dir worker
I: pybuild base:310: python3.11 setup.py config
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly:
Normalizing '3.9.2-2' to '3.9.2.post2'
self.metadata.version = self._normalize_version(
running config
make[1]: Leaving directory '/<>'
rm -f debian/buildbot-worker.debhelper.log debian/buildbot.debhelper.log
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build --buildsystem=pybuild --sourcedirectory=master \
--package=buildbot
pybuild --build -i python{version} -p 3.11 --dir master
I: pybuild base:310: /usr/bin/python3 setup.py build
/<>/master/setup.py:27: DeprecationWarning: pkg_resources is
deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
import pkg_resources
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly:
Normalizing '3.9.2-2' to '3.9.2.post2'
self.metadata.version = self._normalize_version(
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/__init__.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/pbutil.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/asyncio.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/scheduler.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/warnings.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/errors.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/buildbot_net_usage_data.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/locks.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/revlinks.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/buildrequest.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/manhole.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/interfaces.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/master.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot
creating /<>/.pybuild/cpython3_3.11/build/buildbot/configurators
copying buildbot/configurators/__init__.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/configurators
copying buildbot/configurators/janitor.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/configurators
creating /<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/local.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/__init__.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/docker.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/latent.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/marathon.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/kubernetes.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/base.py ->
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/openstack.py
Processed: tagging 1060105, tagging 1058997
Processing commands for cont...@bugs.debian.org: > tags 1060105 + sid trixie Bug #1060105 [src:pcl] pcl: FTBFS on i386: failed tests Added tag(s) trixie and sid. > tags 1058997 + sid trixie Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058997 1060105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: cmake ftbfs on ppc64el (and ppc64)
Processing control commands: > severity -1 normal Bug #1057717 [src:cmake] cmake ftbfs on ppc64el (and ppc64) Severity set to 'normal' from 'serious' > affects -1 + src:cmake Bug #1057717 [src:cmake] cmake ftbfs on ppc64el (and ppc64) Added indication that 1057717 affects src:cmake > reassign -1 libuv1 1.46.0-2 Bug #1057717 [src:cmake] cmake ftbfs on ppc64el (and ppc64) Bug reassigned from package 'src:cmake' to 'libuv1'. No longer marked as found in versions cmake/3.28.0-1. Ignoring request to alter fixed versions of bug #1057717 to the same values previously set Bug #1057717 [libuv1] cmake ftbfs on ppc64el (and ppc64) Marked as found in versions libuv1/1.46.0-2. -- 1057717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057717: cmake ftbfs on ppc64el (and ppc64)
Control: severity -1 normal Control: affects -1 + src:cmake Control: reassign -1 libuv1 1.46.0-2 The ppc64 related segfaults seems to have suddenly vanished again with libuv1 1.46.0-3. After some discussion and bug hunting with upstream [1], which could not reproduce the bug on their end, I think this was either caused by a tainted ppc64el build of libuv1 in Debian, or this points to a very well hidden bug in libuv1 that needs very specific conditions to trigger. In either case, I find it justified to lower the severity and reassign the bug to libuv1. I suggest we keep this bug open for now, in case the problem resurfaces on our buildds. Cheers Timo [1] https://gitlab.kitware.com/cmake/cmake/-/issues/25500 On Thu, 7 Dec 2023 15:02:33 +0100 Matthias Klose wrote: Package: src:cmake Version: 3.28.0-1 Severity: serious Tags: sid trixie cmake ftbfs on ppc64el (and ppc64): [...] 99% tests passed, 5 tests failed out of 697 Label Time Summary: CMake = 1205.59 sec*proc (290 tests) CUDA = 90.91 sec*proc (11 tests) HIP= 17.89 sec*proc (6 tests) ISPC = 60.92 sec*proc (6 tests) Label1 = 0.06 sec*proc (1 test) Label2 = 0.06 sec*proc (1 test) Qt5= 678.18 sec*proc (49 tests) command= 6.93 sec*proc (23 tests) policy = 81.42 sec*proc (42 tests) run= 1198.66 sec*proc (267 tests) Total Test time (real) = 436.62 sec The following tests FAILED: 108 - LibName (SEGFAULT) 241 - CMakeCommands.add_link_options (SEGFAULT) 264 - CTestTestDepends (Failed) 393 - RunCMake.FPHSA (SEGFAULT) 467 - RunCMake.cmake_path (SEGFAULT) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 make[2]: Leaving directory '/<>/Build' -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1060107: urweb: FTBFS: http.c:119:32: error: pointer ‘buf’ may be used after ‘realloc’
Source: urweb Version: 20170720+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=urweb=ppc64el=20170720%2Bdfsg-2%2Bb1=1704495164=0 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../include/urweb -I./../../include/urweb -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wimplicit -Wall -Werror -Wno-deprecated-declarations -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-code-hoisting -c -o static.lo static.c http.c: In function ‘worker’: http.c:119:32: error: pointer ‘buf’ may be used after ‘realloc’ [-Werror=use-after-free] 119 | back = new_buf + (back - buf); | ~~^~ http.c:111:19: note: call to ‘realloc’ here 111 | new_buf = realloc(buf, new_buf_size); | ^~ http.c:184:32: error: pointer ‘buf’ may be used after ‘realloc’ [-Werror=use-after-free] 184 | s = new_buf + (s - buf); | ~~~^~ http.c:173:25: note: call to ‘realloc’ here 173 | new_buf = realloc(buf, new_buf_size); | ^~ http.c:183:38: error: pointer ‘buf’ may be used after ‘realloc’ [-Werror=use-after-free] 183 | body = new_buf + (body - buf); |~~^~ http.c:173:25: note: call to ‘realloc’ here 173 | new_buf = realloc(buf, new_buf_size); | ^~ http.c:182:38: error: pointer ‘buf’ may be used after ‘realloc’ [-Werror=use-after-free] 182 | back = new_buf + (back - buf); |~~^~ http.c:173:25: note: call to ‘realloc’ here 173 | new_buf = realloc(buf, new_buf_size); | ^~ Cheers -- Sebastian Ramacher
Processed: found 1059869 in 0.5.1-2, notfound 1059869 in 5.0.1-2
Processing commands for cont...@bugs.debian.org: > found 1059869 0.5.1-2 Bug #1059869 [src:plakativ] autopkgtest fails Marked as found in versions plakativ/0.5.1-2. > notfound 1059869 5.0.1-2 Bug #1059869 [src:plakativ] autopkgtest fails The source 'plakativ' and version '5.0.1-2' do not appear to match any binary packages No longer marked as found in versions plakativ/5.0.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1059671
Processing commands for cont...@bugs.debian.org: > tags 1059671 + sid trixie Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no module named 'distutils' Added tag(s) trixie and sid. > found 1059671 4.0.2-5 Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no module named 'distutils' Marked as found in versions capstone/4.0.2-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1060076, tagging 1060067, tagging 1059842, tagging 1059802
Processing commands for cont...@bugs.debian.org: > tags 1060076 + sid trixie Bug #1060076 [src:alberta] alberta: FTBFS on ppc64el: error: incompatible function pointer types passing 'int (char *, char *, int)' to parameter of type 'int (*)(void *, void *, int)' Added tag(s) sid and trixie. > tags 1060067 + sid trixie Bug #1060067 [fuse3] fuse3: FTBFS: dh_missing: error: missing files, aborting Added tag(s) trixie and sid. > tags 1059842 + sid trixie Bug #1059842 [python3-hdf5plugin] FTBFS: test fails: ZFP lib not compiled with -DBIT_STREAM_WORD_TYPE=uint8 Added tag(s) trixie and sid. > tags 1059802 + sid trixie Bug #1059802 [troffcvt] troffcvt: Broken with groff 1.23.0: .de1 etc. unimplemented Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059802 1059842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059842 1060067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060067 1060076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1058997
Processing commands for cont...@bugs.debian.org: > tags 1058997 + help Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1058997 is serious
Processing commands for cont...@bugs.debian.org: > severity 1058997 serious Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060106: astc-encoder: FTBFS on i386: failed tests
Source: astc-encoder Version: 4.5.0+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=astc-encoder=i386=4.5.0%2Bds-2%2Bb1=1704479091=0 ./Source/UnitTest/test_simd.cpp:976: Failure Value of: any(r2 == vfloat4(l0 + l1 + l2 + l3)) Actual: true Expected: false [ FAILED ] vfloat4.dot (0 ms) [ RUN ] vfloat4.dot_s ./Source/UnitTest/test_simd.cpp:1001: Failure Expected: (r2) != (l0 + l1 + l2 + l3), actual: 1.24359033e+11 vs 1.24359033e+11 [ FAILED ] vfloat4.dot_s (0 ms) Cheers -- Sebastian Ramacher
Bug#1060105: pcl: FTBFS on i386: failed tests
Source: pcl Version: 1.13.0+dfsg-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=pcl=i386=1.13.0%2Bdfsg-3%2Bb1=1704477640=0 Total Test time (real) = 255.84 sec The following tests FAILED: 18 - common_eigen (Failed) 98 - a_octree_test (Failed) Errors while running CTest Output from these tests are in: /<>/obj-i686-linux-gnu/test/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. Cheers -- Sebastian Ramacher
Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Source: dcmtk Version: 3.6.7-9 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=dcmtk=armel=3.6.7-9%2Bb1=1704494616=0 [ 90%] Building CXX object dcmpstat/libsrc/CMakeFiles/dcmpstat.dir/dcmpstat.cc.o cd /<>/obj-arm-linux-gnueabi/dcmpstat/libsrc && /usr/bin/c++ -DDCMTK_BUILD_IN_PROGRESS -DDCMTK_HAVE_POLL=1 -DUSE_NULL_SAFE_OFSTRING -D_REENTRANT -Ddcmpstat_EXPORTS -I/<>/obj-arm-linux-gnueabi/config/include -I/<>/ofstd/include -I/<>/oflog/include -I/<>/dcmdata/include -I/<>/dcmimgle/include -I/<>/dcmimage/include -I/<>/dcmjpeg/include -I/<>/dcmjpls/include -I/<>/dcmtls/include -I/<>/dcmnet/include -I/<>/dcmsr/include -I/<>/dcmsign/include -I/<>/dcmwlm/include -I/<>/dcmqrdb/include -I/<>/dcmpstat/include -I/<>/dcmrt/include -I/<>/dcmiod/include -I/<>/dcmfg/include -I/<>/dcmseg/include -I/<>/dcmtract/include -I/<>/dcmpmap/include -I/<>/dcmect/include -I/usr/include/libxml2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -DENABLE_DCMJPLS_INTERLEAVE_NONE -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_BSD_COMPAT -D_OSF_SOURCE -D_POSIX_C_SOURCE=199506L -std=gnu++17 -fPIC -Wall -MD -MT dcmpstat/libsrc/CMakeFiles/dcmpstat.dir/dcmpstat.cc.o -MF CMakeFiles/dcmpstat.dir/dcmpstat.cc.o.d -o CMakeFiles/dcmpstat.dir/dcmpstat.cc.o -c /<>/dcmpstat/libsrc/dcmpstat.cc /tmp/ccm0eYhx.s: Assembler messages: /tmp/ccm0eYhx.s:537: Error: bad immediate value for offset (4100) make[4]: *** [dcmrt/tests/CMakeFiles/drttest.dir/build.make:79: dcmrt/tests/CMakeFiles/drttest.dir/drttest.cc.o] Error 1 make[4]: Leaving directory '/<>/obj-arm-linux-gnueabi' make[3]: *** [CMakeFiles/Makefile2:5064: dcmrt/tests/CMakeFiles/drttest.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs [ 90%] Building CXX object dcmpstat/libsrc/CMakeFiles/dcmpstat.dir/dviface.cc.o Cheers -- Sebastian Ramacher
Bug#1060102: boost1.74: do not release with trixie
Source: boost1.74 Version: 1.74.0+ds1-23 Severity: serious X-Debbugs-Cc: sramac...@debian.org With boost 1.83 now as default, let's release trixie without boost 1.74. The current list of blockers is: Checking reverse dependencies... # Broken Depends: cctbx: libcctbx0 [amd64 arm64 ppc64el s390x] python3-cctbx [amd64 arm64 ppc64el s390x] ceph: ceph-common ceph-mgr ceph-mon ceph-osd librados-dev librados2 librgw2 radosgw fenics-dolfinx: libdolfinx-complex0.7 [amd64 arm64 mips64el ppc64el s390x] libdolfinx-real0.7 [amd64 arm64 mips64el ppc64el s390x] freecad: libfreecad-python3-0.20 gnuradio: gnuradio gnuradio-dev libgnuradio-audio3.10.8 libgnuradio-blocks3.10.8 libgnuradio-iio3.10.8 libgnuradio-network3.10.8 libgnuradio-runtime3.10.8 libgnuradio-uhd3.10.8 gr-gsm: gr-gsm [armhf] graph-tool: python3-graph-tool [amd64 arm64 ppc64el s390x] gyoto: gyoto-bin libgyoto8 i2pd: i2pd lomiri-thumbnailer: liblomiri-thumbnailer-qt1.0 [mips64el] lomiri-thumbnailer-service macaulay2: macaulay2 pcl: libpcl-io1.13 [i386] libpcl-outofcore1.13 [i386] libpcl-recognition1.13 [i386] libpcl-visualization1.13 [i386] pcl-tools [i386] pycuda/contrib: python3-pycuda [amd64 arm64 ppc64el] pytango: python3-tango [amd64 arm64 armel armhf i386 mips64el ppc64el] # Broken Build-Depends: brewtarget: libboost1.74-dev dmrgpp: libboost1.74-dev Cheers -- Sebastian Ramacher
Bug#1060101: boost1.81: do not release with trixie
Source: boost1.81 Version: 1.81.0-7 Severity: serious X-Debbugs-Cc: sramac...@debian.org With boost 1.83 now as the default, let's try get boost 1.81 out of trixie. Current blockers are: Checking reverse dependencies... # Broken Depends: r-cran-bh: r-cran-bh # Broken Build-Depends: filezilla: libboost-regex1.81-dev pbcopper: libboost1.81-dev r-cran-openmx: libboost-system1.81-dev Cheers -- Sebastian Ramacher
Processed: closing 1054676
Processing commands for cont...@bugs.debian.org: > # benchmark fixed, ros2-performance-test-fixture binNMUed > close 1054676 Bug #1054676 [src:ros2-performance-test-fixture] ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060099: telegram-desktop: FTBFS on mips64el: ./obj-mips64el-linux-gnuabi64/Telegram/./obj-mips64el-linux-gnuabi64/Telegram/gen/scheme.cpp:16435:(.text+0x1600a0): relocation truncated to fit: R_MI
Source: telegram-desktop Version: 4.13.1+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=telegram-desktop=mips64el=4.13.1%2Bds-1=1703877441=0 100%] Linking CXX executable ../telegram-desktop cd /<>/obj-mips64el-linux-gnuabi64/Telegram && /usr/bin/cmake -E cmake_link_script CMakeFiles/Telegram.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ftemplate-backtrace-limit=0 -Wdate-time -D_FORTIFY_SOURCE=2 -Werror=invalid-pch -Wl,-z,relro -Wl,-z,now -Wno-alloc-size-larger-than -Wno-stringop-overflow -Wno-odr -Wno-inline -pthread -Wl,--as-needed CMakeFiles/Telegram.dir/Telegram_autogen/mocs_compilation.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_attached_stickers.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_authorizations.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_blocked_peers.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_bot.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_chat_filters.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_chat_invite.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_chat_participants.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_cloud_password.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_common.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_confirm_phone.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_editing.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_global_privacy.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_hash.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_invite_links.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_media.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_messages_search.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_messages_search_merged.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_peer_colors.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_peer_photo.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_polls.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_premium.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_premium_option.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_report.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_ringtones.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_self_destruct.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_send_progress.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_sending.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_sensitive_content.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_single_message_search.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_statistics.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_text_entities.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_toggling_media.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_transcribes.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_unread_things.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_updates.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_user_names.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_user_privacy.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_views.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_websites.cpp.o CMakeFiles/Telegram.dir/SourceFiles/api/api_who_reacted.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/filters/edit_filter_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/filters/edit_filter_chats_list.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/filters/edit_filter_links.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/add_bot_to_chat_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/add_participants_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/choose_peer_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_contact_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_forum_topic_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_linked_chat_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_members_visible.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_participant_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_participants_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_color_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_info_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_invite_link.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_invite_links.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_permissions_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_reactions.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_requests_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_type_box.cpp.o CMakeFiles/Telegram.dir/SourceFiles/boxes/peers/edit_peer_usernames_list.cpp.o
Bug#1060100: r-cran-rstanarm: FTBFS: Error: segfault from C stack overflow
Source: r-cran-rstanarm
Version: 2.26.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=r-cran-rstanarm=mips64el=2.26.1-2=1704150178=0
"/usr/lib/R/bin/Rscript" -e "source(file.path('..', 'tools', 'make_cc.R'));
make_cc(commandArgs(TRUE))" stan_files/jm.stan
code for methods in class "Rcpp_model_base" was not checked for suspicious
field assignments (recommended package 'codetools' not available?)
code for methods in class "Rcpp_model_base" was not checked for suspicious
field assignments (recommended package 'codetools' not available?)
code for methods in class "Rcpp_stan_fit" was not checked for suspicious field
assignments (recommended package 'codetools' not available?)
code for methods in class "Rcpp_stan_fit" was not checked for suspicious field
assignments (recommended package 'codetools' not available?)
Error: segfault from C stack overflow
Execution halted
make[1]: *** [Makevars:24: stan_files/jm.cc] Error 1
Cheers
--
Sebastian Ramacher
Processed: Re: Bug#1059801: click: autopkgtests are failing
Processing control commands: > tags -1 ftbfs trixie sid Bug #1059801 [src:click] click: autopkgtests are failing Added tag(s) trixie, sid, and ftbfs. > severity -1 serious Bug #1059801 [src:click] click: autopkgtests are failing Severity set to 'serious' from 'important' -- 1059801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060098: qbs: FTBFS on mips64el: FAIL! : TestBlackbox::pluginDependency() qbs did not run correctly
Source: qbs Version: 2.1.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=qbs=mips64el=2.1.2-2=1704035753=0 3: QDEBUG : TestBlackbox::pluginDependency() Restoring build graph from disk 3: Building for configuration default 3: /usr/bin/g++ -g -O0 -Wall -Wextra -pipe -fexceptions -fvisibility=default -fPIC -DUSING_HELPER2 -o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/3a52ce780950d4d9/helper1.cpp.o -c /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/helper1.cpp 3: /usr/bin/g++ -g -O0 -Wall -Wextra -pipe -fexceptions -fvisibility=default -fPIC -DUSING_HELPER2 -o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/myapp.94e7d341/3a52ce780950d4d9/main.cpp.o -c /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/main.cpp 3: /usr/bin/g++ -Wl,-soname=libhelper1.so,--as-needed -shared -o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/libhelper1.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/3a52ce780950d4d9/helper1.cpp.o 3: /usr/bin/g++ -o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/myapp.94e7d341/myapp /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/myapp.94e7d341/3a52ce780950d4d9/main.cpp.o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/plugin4.bc129f88/libplugin4.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/plugin3.eea51762/libplugin3.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/libhelper1.so 3: Build done for configuration default. 3: 3: QDEBUG : TestBlackbox::pluginDependency() Restoring build graph from disk 3: Resolving project for configuration default 3: Building for configuration default 3: Build done for configuration default. 3: 3: QDEBUG : TestBlackbox::pluginDependency() Restoring build graph from disk 3: Building for configuration default 3: /usr/bin/g++ -o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/myapp.94e7d341/myapp /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/myapp.94e7d341/3a52ce780950d4d9/main.cpp.o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/plugin4.bc129f88/libplugin4.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/plugin3.eea51762/libplugin3.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/plugin2.35094eff/libplugin2.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/libhelper1.so 3: Build done for configuration default. 3: 3: QDEBUG : TestBlackbox::pluginDependency() Restoring build graph from disk 3: Resolving project for configuration default 3: Building for configuration default 3: /usr/bin/g++ -Wl,-soname=libhelper1.so,--as-needed -shared -o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/libhelper1.so /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper1.da71a942/3a52ce780950d4d9/helper1.cpp.o /<>/obj-mips64el-linux-gnuabi64/tests/auto/blackbox/testWorkDir/plugin-dependency/default/helper2.e2ec051f/libhelper2.so 3: Build done for configuration default. 3: 3: QDEBUG : TestBlackbox::pluginDependency() Restoring build graph from disk 3: Cleaning up for configuration default 3: 3: FAIL! : TestBlackbox::pluginDependency() qbs did not run correctly 3:Loc: [./tests/auto/blackbox/tst_blackboxbase.cpp(103)] Cheers -- Sebastian Ramacher
Bug#1060097: pytorch: FBFS: /<>/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp:249:103: error: cannot convert ‘dnnl::memory::data_type’ to ‘const ideep::dims&’ {aka ‘const std::ve
Source: pytorch Version: 2.0.1+dfsg-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=pytorch=amd64=2.0.1%2Bdfsg-5%2Bb1=1704146824=0 [589/1843] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DFMT_HEADER_ONLY=1 -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx -DUSE_C10D_GLOO -DUSE_DISTRIBUTED -DUSE_EXTERNAL_MZCRC -DUSE_RPC -DUSE_TENSORPIPE -D_FILE_OFFSET_BITS=64 -Dtorch_cpu_EXPORTS -I/<>/build/aten/src -I/<>/aten/src -I/<>/build -I/<> -I/<>/cmake/../third_party/benchmark/include -I/<>/debian/foxi -I/<>/build/debian/foxi -I/<>/torch/csrc/api -I/<>/torch/csrc/api/include -I/<>/caffe2/aten/src/TH -I/<>/build/caffe2/aten/src/TH -I/<>/build/caffe2/aten/src -I/<>/build/caffe2/../aten/src -I/<>/torch/csrc -I/<>/third_party/miniz-2.1.0 -I/<>/debian/kineto/libkineto/include -I/<>/debian/kineto/libkineto/src -I/<>/aten/../third_party/catch/single_include -I/<>/aten/src/ATen/.. -I/<>/c10/.. -I/<>/aten/src/ATen/native/quantized/cpu/qnnpack/include -I/<>/aten/src/ATen/native/quantized/cpu/qnnpack/src -I/<>/aten/src/ATen/native/quantized/cpu/qnnpack/deps/clog/include -I/<>/third_party/flatbuffers/include -isystem /<>/build/third_party/gloo -isystem /<>/cmake/../third_party/gloo -isystem /<>/cmake/../third_party/googletest/googlemock/include -isystem /<>/cmake/../third_party/googletest/googletest/include -isystem /usr/include/opencv4 -isystem /usr/include/eigen3 -isystem /<>/caffe2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -gsplit-dwarf -Wno-dangling-reference -I/usr -D_GLIBCXX_USE_CXX11_ABI=1 -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -DUSE_KINETO -DLIBKINETO_NOCUPTI -DLIBKINETO_NOROCTRACER -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wall -Wextra -Werror=return-type -Werror=non-virtual-dtor -Werror=range-loop-construct -Werror=bool-operation -Wnarrowing -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O2 -g -DNDEBUG -std=gnu++17 -fPIC -DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wall -Wextra -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-missing-field-initializers -Wno-write-strings -Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds -Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-missing-braces -Wno-maybe-uninitialized -fvisibility=hidden -O2 -DCAFFE2_BUILD_MAIN_LIB -fopenmp -Wno-deprecated-declarations -MD -MT caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp.o -MF caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp.o.d -o caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp.o -c /<>/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp FAILED: caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp.o /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DFMT_HEADER_ONLY=1 -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx -DUSE_C10D_GLOO -DUSE_DISTRIBUTED -DUSE_EXTERNAL_MZCRC -DUSE_RPC -DUSE_TENSORPIPE -D_FILE_OFFSET_BITS=64 -Dtorch_cpu_EXPORTS -I/<>/build/aten/src -I/<>/aten/src -I/<>/build -I/<> -I/<>/cmake/../third_party/benchmark/include -I/<>/debian/foxi -I/<>/build/debian/foxi -I/<>/torch/csrc/api -I/<>/torch/csrc/api/include -I/<>/caffe2/aten/src/TH -I/<>/build/caffe2/aten/src/TH -I/<>/build/caffe2/aten/src -I/<>/build/caffe2/../aten/src -I/<>/torch/csrc -I/<>/third_party/miniz-2.1.0 -I/<>/debian/kineto/libkineto/include -I/<>/debian/kineto/libkineto/src -I/<>/aten/../third_party/catch/single_include -I/<>/aten/src/ATen/.. -I/<>/c10/.. -I/<>/aten/src/ATen/native/quantized/cpu/qnnpack/include -I/<>/aten/src/ATen/native/quantized/cpu/qnnpack/src -I/<>/aten/src/ATen/native/quantized/cpu/qnnpack/deps/clog/include -I/<>/third_party/flatbuffers/include -isystem /<>/build/third_party/gloo -isystem /<>/cmake/../third_party/gloo
Bug#1060096: hiredes: FTBFS: #118 Returns I/O error on socket timeout: ␛[0;32mPAShiredis-test: test.c:2199: test_async_polling: Assertion `c->err == 0' failed.
Source: hiredis Version: 1.2.0-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=hiredis=amd64=1.2.0-5=1704389545=0 Testing against Unix socket connection (/tmp/tmp.L5kzBjtVQg/hiredis-test-redis.sock): #95 Is able to deliver commands: ␛[0;32mPASSED␛[0;0m #96 Is a able to send commands verbatim: ␛[0;32mPASSED␛[0;0m #97 %s String interpolation works: ␛[0;32mPASSED␛[0;0m #98 %b String interpolation works: ␛[0;32mPASSED␛[0;0m #99 Binary reply length is correct: ␛[0;32mPASSED␛[0;0m #100 Can parse nil replies: ␛[0;32mPASSED␛[0;0m #101 Can parse integer replies: ␛[0;32mPASSED␛[0;0m #102 Can parse multi bulk replies: ␛[0;32mPASSED␛[0;0m #103 Can handle nested multi bulk replies: ␛[0;32mPASSED␛[0;0m #104 Send command by passing argc/argv: ␛[0;32mPASSED␛[0;0m #105 Can pass NULL to redisGetReply: ␛[0;32mPASSED␛[0;0m #106 We set a default RESP3 handler for redisContext: ␛[0;32mPASSED␛[0;0m #107 We don't set a default RESP3 push handler for redisAsyncContext: ␛[0;32mPASSED␛[0;0m #108 Our REDIS_OPT_NO_PUSH_AUTOFREE flag works: ␛[0;32mPASSED␛[0;0m #109 We can use redisOptions to set a custom PUSH handler for redisContext: ␛[0;32mPASSED␛[0;0m #110 We can use redisOptions to set a custom PUSH handler for redisAsyncContext: ␛[0;32mPASSED␛[0;0m #111 We can use redisOptions to set privdata: ␛[0;32mPASSED␛[0;0m #112 Our privdata destructor fires when we free the context: ␛[0;32mPASSED␛[0;0m #113 Successfully completes a command when the timeout is not exceeded: ␛[0;32mPASSED␛[0;0m #114 Does not return a reply when the command times out: ␛[0;32mPASSED␛[0;0m #115 Reconnect properly reconnects after a timeout: ␛[0;32mPASSED␛[0;0m #116 Reconnect properly uses owned parameters: ␛[0;32mPASSED␛[0;0m #117 Returns I/O error when the connection is lost: ␛[0;32mPASSED␛[0;0m #118 Returns I/O error on socket timeout: ␛[0;32mPAShiredis-test: test.c:2199: test_async_polling: Assertion `c->err == 0' failed. Aborted make[2]: *** [Makefile:271: check] Error 134 Cheers -- Sebastian Ramacher
Processed: Bug#1058286 marked as pending in ncrack
Processing control commands: > tag -1 pending Bug #1058286 [src:ncrack] ncrack: FTBFS: configure: error: *** zlib too old - check config.log *** Added tag(s) pending. -- 1058286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058286: marked as pending in ncrack
Control: tag -1 pending Hello, Bug #1058286 in ncrack reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/ncrack/-/commit/f4d07967032a4c9142532857b2d7b09f2ef7dc49 Allow zlib versions with two-part version number (Closes: #1058286) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058286
Processed: Re: gtkextra: unmaintained upstream since 2018
Processing control commands: > severity -1 serious Bug #967851 [src:gtkextra] gtkextra: unmaintained upstream since 2018 Severity set to 'serious' from 'important' -- 967851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877016: Time to drop cpufrequtils?
Am Fri, Jan 05, 2024 at 12:08:54PM +0100 schrieb Chris Hofstaedtler: > On Sun, Sep 03, 2023 at 08:26:00PM +0200, Moritz Mühlenhoff wrote: > > severity 877016 serious > > thanks > > > > Am Thu, Sep 28, 2017 at 06:51:30AM -0700 schrieb Mattia Dongili: > > > On Wed, Sep 27, 2017 at 03:16:52PM -0400, Phil Susi wrote: > > > > Package: cpufrequtils > > > > Version: 008-1 > > > ... > > > > is the case, should cpufrequtils not be removed now? > > > > > > Yes, indeed it should. Thanks for nagging. > > > > Bumping the severity to RC to move forward with this for trixie. > > > > $ dak rm -nR cpufrequtils > Will remove the following packages from unstable: > > cpufrequtils | 008-2 | source, amd64, arm64, armel, armhf, i386, > mips64el, s390x > libcpufreq-dev | 008-2 | amd64, arm64, armel, armhf, i386, mips64el, > ppc64el, s390x > libcpufreq-dev | 008-2+b1 | riscv64 > libcpufreq0 | 008-2 | amd64, arm64, armel, armhf, i386, mips64el, > ppc64el, s390x > libcpufreq0 | 008-2+b1 | riscv64 > > Maintainer: Seunghun Han > > --- Reason --- > > -- > > Checking reverse dependencies... > No dependency problem found. > > Seems like it's good to go? Given the original bug to suggest it's removal is from 2017, I think it's safe to say that anyone had a chance to object to it's removal :-) Cheers, Moritz
Bug#1058448: marked as done (xphyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 05 Jan 2024 17:54:40 +
with message-id
and subject line Bug#1058448: fixed in xphyle 4.4.4-1
has caused the Debian Bug report #1058448,
regarding xphyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
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.)
--
1058448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xphyle
Version: 4.4.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure -i python{version} -p "3.12 3.11"
> I: pybuild base:310: python3.12 setup.py config
> /usr/lib/python3/dist-packages/setuptools/dist.py:744:
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
>
>
>
> Usage of dash-separated 'description-file' will not be supported in
> future
> versions. Please use the underscore name 'description_file' instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/dist.py:744:
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
>
>
>
> Usage of dash-separated 'description-file' will not be supported in
> future
> versions. Please use the underscore name 'description_file' instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> opt = self.warn_dash_deprecation(opt, section)
> running config
> I: pybuild base:310: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/dist.py:744:
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
>
>
>
> Usage of dash-separated 'description-file' will not be supported in
> future
> versions. Please use the underscore name 'description_file' instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
The patch is only on git - no one has yet uploaded it to the archive to formally resolve the bug yet.Before January 16 it needs to be uploaded. I can probably mark it as hold on the bug tracker when I have my reference for tags at home.Between us we should be able to manage! Either I’ll pull something together for a sponsored upload on Sunday or I’ll have an idea on my new member process before then!CheersDHOn 5 Jan 2024, at 17:35, David Ranch wrote:
Hello Dave,
I received the following email yesterday which gives me the
impression that your patch wasn't accepted. What needs to be done
here by Jan 16th?
--
linpac 0.28-2 is marked for autoremoval from testing on 2024-01-16
It is affected by these RC bugs:
1057573: linpac: FTBFS: error: invalid use of incomplete type âWINDOWâ {aka âstruct _win_stâ}
https://bugs.debian.org/1057573
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
--
On 01/01/2024 08:55 AM, Dave Hibberd
wrote:
Hi there!
Yeah I’ve pushed his patch already to our git, so if anyone
else on the team wants to upload it they can - I am still
waiting on our account managers to finalise my Debian developer
application before I have free reign to upload things, and I’ll
switch this package to fall under my ownership like a collection
of other packet things to make life a little easier going
forward.
Cheers
DH
On 1 Jan 2024, at 16:46, David Ranch
wrote:
Hello DaveH,
I have pushed the required fixes to the develop branch of
Linpac. I do plan on adding some other enhancements to
Linpac before publishing an new official release but I
don't know if getting out this fix is important to the
Debian release process. Maybe the similar third party fix
offered by Sven is good enough for
now to keep Linpac in the Debian Unstable/Testing repos?
--David
KI6ZHD
On 12/18/2023 02:40 AM, Dave
Hibberd wrote:
Hi
both,
I'll
prepare a team upload for this in advance of the new
upstream release (thanks David), and upload it
independently or with support depending on the outcome
of the DAM stage of my NM process (https://nm.debian.org/process/1224/)
Cheers
DH
--
Hibby
MM0RFN
On Sat, 16 Dec 2023, at 6:32 PM, David Ranch wrote:
Hello Sven, Debian
team,
I was about to apply a very similar fix to the
"develop" branch of Linpac at https://sourceforge.net/p/linpac/linpac/ci/develop/tree
though my changes didn't include the "-1" at the end
of the changes. Not sure if that's needed /
important. Regardless, I am planning to eventually
merge the develop branch into the Master branch and
releae 0.29 in the near future which will include
this and other fixes.
--David
KI6ZHD
On 12/16/2023 10:01 AM,
Sven Joachim wrote:
Control: tags -1 + patch
On 2023-12-05 23:07 +0100, Santiago Vila wrote:
Package: src:linpac
Version: 0.28-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
g++ -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o mail_screen.o mail_screen.cc
mail_screen.cc: In function ‘void init_main_screen()’:
mail_screen.cc:39:16: error: invalid use of
Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
Hello Dave,
I received the following email yesterday which gives me the impression
that your patch wasn't accepted. What needs to be done here by Jan 16th?
--
linpac 0.28-2 is marked for autoremoval from testing on 2024-01-16
It is affected by these RC bugs:
1057573: linpac: FTBFS: error: invalid use of incomplete type âWINDOWâ {aka
âstruct _win_stâ}
https://bugs.debian.org/1057573
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
--
On 01/01/2024 08:55 AM, Dave Hibberd wrote:
Hi there!
Yeah I’ve pushed his patch already to our git, so if anyone else on
the team wants to upload it they can - I am still waiting on our
account managers to finalise my Debian developer application before I
have free reign to upload things, and I’ll switch this package to
fall under my ownership like a collection of other packet things to
make life a little easier going forward.
Cheers
DH
On 1 Jan 2024, at 16:46, David Ranch wrote:
Hello DaveH,
I have pushed the required fixes to the develop branch of Linpac. I
do plan on adding some other enhancements to Linpac before publishing
an new official release but I don't know if getting out this fix is
important to the Debian release process. Maybe the similar third
party fix offered by Svenis good enough for now to keep Linpac in the
Debian Unstable/Testing repos?
--David
KI6ZHD
On 12/18/2023 02:40 AM, Dave Hibberd wrote:
Hi both,
I'll prepare a team upload for this in advance of the new upstream
release (thanks David), and upload it independently or with support
depending on the outcome of the DAM stage of my NM process
(https://nm.debian.org/process/1224/)
Cheers
DH
--
Hibby
MM0RFN
On Sat, 16 Dec 2023, at 6:32 PM, David Ranch wrote:
Hello Sven, Debian team,
I was about to apply a very similar fix to the "develop" branch of
Linpac at https://sourceforge.net/p/linpac/linpac/ci/develop/tree
though my changes didn't include the "-1" at the end of the
changes. Not sure if that's needed / important. Regardless, I am
planning to eventually merge the develop branch into the Master
branch and releae 0.29 in the near future which will include this
and other fixes.
--David
KI6ZHD
On 12/16/2023 10:01 AM, Sven Joachim wrote:
Control: tags -1 + patch
On 2023-12-05 23:07 +0100, Santiago Vila wrote:
Package: src:linpac
Version: 0.28-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
g++ -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o
mail_screen.o mail_screen.cc
mail_screen.cc: In function ‘void init_main_screen()’:
mail_screen.cc:39:16: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
39 | maxx = stdscr->_maxx;
|^~
In file included from mail_screen.cc:13:
/usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
‘struct _win_st’}
442 | typedef struct _win_st WINDOW;
|^~~
mail_screen.cc:40:16: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
40 | maxy = stdscr->_maxy;
|^~
/usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
‘struct _win_st’}
442 | typedef struct _win_st WINDOW;
|^~~
mail_screen.cc: In function ‘void redraw()’:
mail_screen.cc:70:15: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
70 |main_window->_clear = TRUE;
| ^~
/usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
‘struct _win_st’}
442 | typedef struct _win_st WINDOW;
The attached patch, which can be added to the series file fixes, these
errors and two additional ones in src/linpac.cc, but I have only tested
that the package builds, not if it works. Note that getmaxx(win)
returns win->_maxx + 1, and similar for getmaxy.
Cheers,
Sven
Bug#1060061: marked as done (grub-efi-amd64-bin: out of memory when loading initial ramdisk)
Your message dated Fri, 5 Jan 2024 18:33:02 +0100
with message-id
and subject line Re: Bug#1060061: grub-efi-amd64-bin: out of memory when
loading initial ramdisk
has caused the Debian Bug report #1060061,
regarding grub-efi-amd64-bin: out of memory when loading initial ramdisk
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.)
--
1060061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-efi-amd64-bin
Version: 2.06-3~deb11u6
Severity: critical
Tags: upstream
Justification: breaks the whole system
X-Debbugs-Cc: mtilje...@uber.com
Dear Maintainer,
On certain system, in this case an Ice Lake based server running an AMI
bios (version 3219BS01.021), GRUB will sporadically fail to boot with
the following:
>> Booting `Debian GNU/Linux, with Linux 5.10.113-1'Booting `Debian
>> GNU/Linux, with Linux 5.10.113-1'
>>
>>
>>
>> Loading Linux 5.10.113-1 ...Loading Linux 5.10.113-1 ...
>>
>> Loading initial ramdisk ...Loading initial ramdisk ...
>>
>> error: out of memory.
>> error: out of memory.
This error is sporadic and appears maybe 90% of the time, so I can
barely get the system up and running for testing purposes.
I believe this is related to memory management in GRUB and similar to
https://bugs.launchpad.net/oem-priority/+bug/1842320
which is apparently caused by an upstream bug
https://savannah.gnu.org/bugs/?61058
>From digging around it appears this has been fixed in Redhat/Fedora with
https://src.fedoraproject.org/rpms/grub2/c/098a8a9e99d4b32576e7af518e8e195059f985b9?branch=f33
but apparently this patch applies to previous memory subsystem patches,
so I haven't been able to backport these patches.
I've successfully backported grub 2.12~rc1-12 from sid by changing the
compiler back to gcc-10 and building from source. This version works and
boots every time without issue.
I've also tried to backport grub 2.06-13+deb12u1 from bookworm, but this
does not help. I hence believe this problem affects both Debian
bullseye and bookworm.
Best,
Morten Hein Tiljeset
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/nvme0n1p1 / ext4 rw,noatime,errors=panic 0 0
/dev/nvme1n1p1 /opt ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /var/log ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme0n1p12 /boot/efi vfat
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
/dev/nvme1n1p1 /var/lib/systemd/coredump ext4 rw,noatime,errors=panic,stripe=64
0 0
/dev/nvme1n1p1 /var/log/containers ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /opt/system/log/containers ext4
rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /var/log/pods ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /opt/system/log/pods ext4 rw,noatime,errors=panic,stripe=64 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
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set
default="gnulinux-5.10.113-1-advanced-5a78d20e-e0e5-44b7-b2a6-363a3b536fc9"
fi
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
}
serial --speed=115200
terminal_input console serial
terminal_output console serial
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=0
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/04_unrestricted ###
menuentry_id_option="--unrestricted
Bug#1059237: dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’?
Control: forwarded -1 https://github.com/UbuntuDDE/dde-store/pull/33 Control: tags -1 +patch + uptream Ubuntu has cherry-picked the upstream pull request to fix this issue. Thank you, Jeremy Bícha
Processed (with 1 error): Re: dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’?
Processing control commands: > forwarded -1 https://github.com/UbuntuDDE/dde-store/pull/33 Bug #1059237 [src:dde-store] dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’? Set Bug forwarded-to-address to 'https://github.com/UbuntuDDE/dde-store/pull/33'. > tags -1 +patch + uptream Unknown tag/s: uptream. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky forky-ignore. Bug #1059237 [src:dde-store] dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’? Added tag(s) patch. Bug #1059237 [src:dde-store] dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’? Requested to add no tags; doing nothing. -- 1059237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060076: alberta: FTBFS on ppc64el: error: incompatible function pointer types passing 'int (char *, char *, int)' to parameter of type 'int (*)(void *, void *, int)'
Source: alberta Version: 3.0.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=alberta=ppc64el=3.0.3-1%2Bb1=1703410988=0 libtool: compile: clang -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I./../0d -I./../1d -I./../2d -I./../3d -I./../Common -I../../../alberta_util/src -I../../../alberta_util/src -I../../../gnu-compat -I../Common -D_FORTIFY_SOURCE=2 -Wdate-time -DDIM_OF_WORLD=1 -DALBERTA_DEBUG=0 -DALBERTA_PROFILE=0 -D_FORTIFY_SOURCE=2 -Wdate-time -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -I/usr/include/tirpc -c ../Common/gauss-quad.c -fPIC -DPIC -o .libs/libalberta_1d_la-gauss-quad.o In file included from ../Common/dof_admin.c:46: In file included from ../Common/eval.c:40: In file included from ./../Common/alberta_intern.h:51: In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:25: /usr/include/features.h:195:3: warning: "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-W#warnings] # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" ^ In file included from ./../Common/alberta_intern.h:51: In file included from ../Common/gauss-quad.cIn file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:25: /usr/include/features.h:195:3: warning: "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-W#warnings] :86: In file included from ./../Common/alberta_intern.h:51: In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:25: /usr/include/features.h:195:3# warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" ^ : warning: "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-W#warnings] # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" ^ libtool: compile: clang -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I./../0d -I./../1d -I./../2d -I./../3d -I./../Common -I../../../alberta_util/src -I../../../alberta_util/src -I../../../gnu-compat -I../Common -D_FORTIFY_SOURCE=2 -Wdate-time -DDIM_OF_WORLD=1 -DALBERTA_DEBUG=0 -DALBERTA_PROFILE=0 -D_FORTIFY_SOURCE=2 -Wdate-time -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -I/usr/include/tirpc -c ../Common/element.c -fPIC -DPIC -o .libs/libalberta_1d_la-element.o In file included from ../Common/bas_fct.c:31: In file included from ./../Common/alberta_intern.h:51: In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:25: /usr/include/features.h:195:3: warning: "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-W#warnings] # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" ^ In file included from ../Common/macro.c:50: In file included from ./../Common/alberta_intern.h:51: In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:25: /usr/include/features.h:195:3: warning: "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-W#warnings] # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" ^ ../Common/macro.c:1077:19: error: incompatible function pointer types passing 'int (char *, char *, int)' to parameter of type 'int (*)(void *, void *, int)' [-Wincompatible-function-pointer-types] read_xdr_file, write_xdr_file); ^ /usr/include/tirpc/rpc/xdr.h:362:14: note: passing argument to parameter here int (*)(void *, void *, int), ^ ../Common/macro.c:1077:34: error: incompatible function pointer types passing 'int (char *, char *, int)' to parameter of type 'int (*)(void *, void *, int)' [-Wincompatible-function-pointer-types] read_xdr_file, write_xdr_file); ^~ /usr/include/tirpc/rpc/xdr.h:363:14: note: passing argument to parameter here int (*)(void *, void *, int)); ^ 1 warning and 2 errors generated. make[6]: *** [Makefile:1897: libalberta_1d_la-macro.lo] Error 1 make[6]: *** Waiting for unfinished jobs Cheers -- Sebastian Ramacher
Bug#1059983: marked as done (gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable)
Your message dated Fri, 05 Jan 2024 16:50:06 + with message-id and subject line Bug#1059983: fixed in gnome-software 45.3-1 has caused the Debian Bug report #1059983, regarding gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable 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.) -- 1059983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-software Version: 45.2-1 Severity: serious Tags: ftbfs trixie sid gnome-software fails to build from source in unstable when built with the nocheck build profile. A build ends as follows: | ../data/metainfo/meson.build:11:16: ERROR: Program 'appstreamcli' not found or not executable | dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 -Dgsettings_desktop_schemas=enabled -Dpackagekit=true -Dpackagekit_autoremove=true -Drpm_ostree=false -Dapt=true -Dfwupd=false -Dflatpak=false -Dgudev=false -Dmalcontent=false -Dflatpak=true -Dmalcontent=true -Dgudev=true -Dfwupd=true -Dsnap=true returned exit code 1 | make[1]: *** [debian/rules:58: override_dh_auto_configure] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:55: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Presumably, the appstream dependency is incorrectly tagged . I note that since trixie, failing to build from source with the nocheck profile is considered a release critical bug by the release team, because incorrectly tagged dependencies may misguide the autoremover. Helmut --- End Message --- --- Begin Message --- Source: gnome-software Source-Version: 45.3-1 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of gnome-software, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated gnome-software 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: Fri, 05 Jan 2024 11:36:47 -0500 Source: gnome-software Built-For-Profiles: noudeb Architecture: source Version: 45.3-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1059983 Changes: gnome-software (45.3-1) unstable; urgency=medium . * New upstream release * Stop using debian/control.in and dh_gnome_clean * Drop nocheck annotation from appstream Build-Depends (Closes: #1059983) Checksums-Sha1: 447d98727db23ca1e4fc2de581de82ed62cd28b0 3687 gnome-software_45.3-1.dsc 5f8d9e12db5da6b9e82b2cd7ec23768e5ac3df0c 2477736 gnome-software_45.3.orig.tar.xz bb638d6e0ca3cf7e7ceacf964682497488f6d279 18152 gnome-software_45.3-1.debian.tar.xz 63909314df4ee6681f3e322362d42038965a69b2 14355 gnome-software_45.3-1_source.buildinfo Checksums-Sha256: 65d353800c4edf98bf30518250dc62b04ab6c2922815f2ed229d5410a70d1992 3687 gnome-software_45.3-1.dsc d6b9245b22237da7bd1739dd28c23cc8f3835f99fa10c1037d9dd7635335251c 2477736 gnome-software_45.3.orig.tar.xz 68303939bb679af10a2b4d93652f8ad54975b864f15a1fae772dec6330930284 18152 gnome-software_45.3-1.debian.tar.xz 198b3cabe36dfce1ca8cbdb67e942ba9e4286216ddeb170df6d28b8e48db8189 14355 gnome-software_45.3-1_source.buildinfo Files: 6277393b38bee3b049b8af408b015c08 3687 gnome optional gnome-software_45.3-1.dsc 6db44b62c2e764df2832fbeaff660ef4 2477736 gnome optional gnome-software_45.3.orig.tar.xz 3bb07e9af3a5f9e5d58f95f84f243dcb 18152 gnome optional gnome-software_45.3-1.debian.tar.xz d6d9f94708d99478a6ada0d55434fca0 14355 gnome optional gnome-software_45.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmWYMDkACgkQ5mx3Wuv+ bH32kg//VI6djK09HZP51MBoPpplXSQ7V1POwiaetyCSRYH6SML5QCJKvw0cGpxb mgnG3PxQHhOApZJsi8ogO0h3YZebq/YsbSZXblb2j2tEdtl1l9g7ebp3y8ATra1g
Bug#1059819: marked as done (g2clib/experimental FTBFS: Could NOT find libaec)
Your message dated Fri, 05 Jan 2024 16:49:52 + with message-id and subject line Bug#1059819: fixed in g2clib 1.8.0-2 has caused the Debian Bug report #1059819, regarding g2clib/experimental FTBFS: Could NOT find libaec 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.) -- 1059819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: g2clib Version: 1.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=g2clib=1.8.0-1 ... CMake Error at /usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find libaec (missing: LIBAEC_LIBRARIES LIBAEC_INCLUDE_DIRS) (Required is at least version "1.0.6") Call Stack (most recent call first): /usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) cmake/Findlibaec.cmake:25 (find_package_handle_standard_args) CMakeLists.txt:100 (find_package) -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: g2clib Source-Version: 1.8.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of g2clib, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated g2clib 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: SHA256 Format: 1.8 Date: Sat, 16 Dec 2023 09:20:44 + Source: g2clib Binary: libg2c-dev libg2c0 libg2c0-dbgsym Architecture: source arm64 Version: 1.8.0-2 Distribution: experimental Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: libg2c-dev - NCEP GRIB2 library - development files libg2c0- NCEP GRIB2 encoder/decoder library Closes: 1059819 Changes: g2clib (1.8.0-2) experimental; urgency=medium . * Build-dep on libaec-dev. Closes: #1059819 Checksums-Sha1: 6def9283ed1f0169bd2ccfc50d6efc8fc1d94cdc 1987 g2clib_1.8.0-2.dsc cf13663ea077dcab6c864d691bf3df20b1e04d8e 4432 g2clib_1.8.0-2.debian.tar.xz 519d7e242b30a9cdfe248d8c660b936db74d8263 8577 g2clib_1.8.0-2_arm64.buildinfo 55857351190ba45dd94115f189937dba38bf6c3f 57172 libg2c-dev_1.8.0-2_arm64.deb 6d098bf4134ca4fd1774992cfbf600c60aee3bca 103580 libg2c0-dbgsym_1.8.0-2_arm64.deb a7b7cd1979ed6e7ebe984200f15c4018fca9ee3b 45172 libg2c0_1.8.0-2_arm64.deb Checksums-Sha256: 4c5bcff0a49e90e28c3a915dd214db4d13c9f87dd8396f1f231631f30b41b48e 1987 g2clib_1.8.0-2.dsc fe6aa81280d10bf9e1005bce1eeeb65debe9f23651e8f1947a1b5bd4c7400d86 4432 g2clib_1.8.0-2.debian.tar.xz 345dee8a2e86430b1476605ccff1cd2b76aac919fc76bf331bcaa4f0db9cc18e 8577 g2clib_1.8.0-2_arm64.buildinfo 9b9bab6f47fadf8e80b0ce8a83182bdc4c84df38d1c707df5beca14ec13514da 57172 libg2c-dev_1.8.0-2_arm64.deb a361bb948fa787449fbf884302b6b30eaf8ca8acc5caef5221be1f7f304ba8da 103580 libg2c0-dbgsym_1.8.0-2_arm64.deb dfd1c6ae1ace58b6d72c0fa66dcdd84e7f412c843660f1a1ea383549aee140d6 45172 libg2c0_1.8.0-2_arm64.deb Files: 5cac0ad324f83f694b59a14a096cf6af 1987 utils optional g2clib_1.8.0-2.dsc 98682a3040db9049f45ecd0182067e20 4432 utils optional g2clib_1.8.0-2.debian.tar.xz 35503009f1249a23f7ab2bd0173c1883 8577 utils optional g2clib_1.8.0-2_arm64.buildinfo 93dbd41ca8124d0c2d731cdc7fc49f03 57172 libdevel optional libg2c-dev_1.8.0-2_arm64.deb c789454cc35042f86609ae39dafa05cc 103580 debug optional libg2c0-dbgsym_1.8.0-2_arm64.deb f278ff2d93a42d6899a27084e9910dd1 45172 libs optional libg2c0_1.8.0-2_arm64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmWYLV4ACgkQy+a7Tl2a 06WEMA//dexInBUI+Q3BBGlqrliT6jbtJXibiLHau1J0HmEwNjzzkB0kkJOkUrtG POZ+g6Ltcnpqjf1gSqg3d90QeoaiBaOZ1cNzf4/MujkClhGON7CaIdNHRct7fSj4 vZxTdF1E+72cq++uGqeWXRv0Q9HjhquaUR9TNjnrTF9tJi9Ao9FQxIyRqELqBPUD PiyGOcCpS3s2GJ7OAq1TFnYs5uANDK3BGHHjyIncfdnjTxhPLRwKaU4Qu9IgCP0V +CAVZA3MjuN3ypuhBtKAun96mmgB/TXRqnp9s3vb+TV1Q9YQSYXm0tVdlMbrkbje 3aBMODhlv9RUcBkNMn0ujtY4Pd3S49fz0xD6m5Ws5IPZ6Dcf4y3cz8zwHsyYToqu 4oXr0M7krFbuh46aNluE89zN+s3rEllAwxyn7G7iNmFkM3OquAAePFf/75JIxdxS
Bug#1056177: marked as done (librust-tikv-jemalloc-ctl-dev: depends on missing packages)
Your message dated Fri, 5 Jan 2024 18:35:23 +0200 with message-id and subject line Re: Bug#1056177: librust-tikv-jemalloc-ctl-dev: depends on missing packages has caused the Debian Bug report #1056177, regarding librust-tikv-jemalloc-ctl-dev: depends on missing packages 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.) -- 1056177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-tikv-jemalloc-ctl-dev Version: 0.5.4-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Depends on packages librust-tikv-jemalloc-sys-0.5+default-dev and librust-tikv-jemalloc-sys-0.5+disable-initial-exec-tls-dev that are missing in Debian. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVYhIgACgkQLHwxRsGg ASFjNg//cqyOhnOtJOazDOwLT/Ix+Xc1/kmpB4K7uRe1VjPh9s2p62AgGD8jgNhM LzsDnRvU6LXcYekRNfSUyTxEsU7A0L8xcw+hkgS2daY67PEnWI1HYltLJt//Ncq0 O8Ee8nNZ8ZZfIKoL241851jMO6awFvsrsRQ9ukKuKq//S7pz4y798s68QjoGISrT XSjPLRGVGenDzLdLAa4VaqSR7FAo9gVaTWW/n5h93vChHmDgrls03LXDbZsCbp7v y20BslCFnzRBcYX+QhC5OItrmDgq11yvLb4F8ZU000n46Dxu15ASbyZruCvnrNv5 jqWb/1bkaEOPKD0AqX9yilNJArzmvf8zQSWTmAPZurDKJVsM505pLQ3UWdEl1W2i KxXhcp6whujtyBbAHqjistGFdmERc9nXrFZ2ZPrUbkNIbFcO4N+D5ZbZbYg6s8V1 UrHITbW9SgYdd+K2L8ohzQ44Y6avgGlY1Ks2XBok6hKXRCHgTph/WQ2gII1oNmwx kxicT5WBfJ+c6Py3sOp2vWBmSDxAu1gaYEGLIEF815ZNst7FNqqiBCGWZHRv7rcc rlpP8HmBV74KgBkuQh+ntTAeoOb647HIOeF7ZkDK5Rqw9yjm9X9N0iIh6QAoaZMD 6W/YJeDm8oeMU4btskDUIinZJidQNkzNNGgUtsSu5Ofz/OSz7zY= =h8JL -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On Sat, Nov 18, 2023 at 11:43:39AM +0100, Andreas Henriksson wrote: >... > On Sat, Nov 18, 2023 at 10:31:56AM +0100, Jonas Smedegaard wrote: > > Package: librust-tikv-jemalloc-ctl-dev > > Version: 0.5.4-1 > > Severity: grave > > Justification: renders package unusable > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Depends on packages librust-tikv-jemalloc-sys-0.5+default-dev and > > librust-tikv-jemalloc-sys-0.5+disable-initial-exec-tls-dev that are > > missing in Debian. > > tikv-jemalloc-sys is currently stuck in NEW (since a month, wonder if > there's a reason for it taking so long?). > > Looks like this problem should resolve itself once it's accepted. This has now happened, closing. > Regards, > Andreas Henriksson cu Adrian--- End Message ---
Bug#1060072: RM: fheroes2-pkg -- RoQA; Replaced by DFSG-free fheroes2
Source: fheroes-pkg Severity: serious Please file a removal bug for fheroes2-pkg. The fheroes2 package has just entered Debian main and should be considered the successor of this package. If nobody acts or comments on this suggestion, I am going to file a RM bug as soon as fheroes2-pkg is autoremoved from testing.
Bug#1059970: fitspng: autopkgtest regression in testing
Dear Graham, I think the fail is result of linking of different versions of zlib via dependent libraries. Correct me, if I'm wrong, fitspng has the dependences: Build-Depends: debhelper-compat (= 13), libcfitsio-dev, libpng-dev zlib is indirectly linked via both libraries. Currently, in unstable, libcfitsio-dev runtime depends on libcfitsio10, which depends on zlib1g (>= 1:1.1.4) while, libpng-dev on zlib1g-dev so zlib1g (= 1:1.3.dfsg-3) The status is a little bit complicated, libpng16-16 has also dependence on zlib1g (>= 1:1.2.11.dfsg). I have no idea how to solve the trouble, and if it is solvable due potential dependence both the libraries on a particulal version of zlib. Regards, FH -- F. Hroch , Masaryk University, Dept. of theor. physics and astrophysics, Brno, Moravia, CZ -- F. Hroch , Masaryk University, Dept. of theor. physics and astrophysics, Brno, Moravia, CZ
Bug#1013584: octave-iso2mesh: FTBFS: dh_missing: error: missing files, aborting
Source: octave-iso2mesh Version: 1.9.6+ds-7 Severity: serious Justification: FTBFS Tags: sid ftbfs Dear octave-iso2mesh Maintainer, About the issue reported, there is a solution that add "not-installed" file to /debian. This solution refers to Bug Report #964666. More details can be found in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964666 and https://salsa.debian.org/multimedia-team/libopenshot/-/commit/43689f7b3b058dfd0ee83dd7ff6a6bc863a02004#1823cfdb97f631de92d185f9a7ef6c1f58bc9147 The dh_missing error is caused by *.m exists in debian/tmp but is not installed to anywhere, so the solution is effective.I have tested it successfully in local. Please let me know if the solution accepted. The "not-installed" file is in the attachment. not-installed Description: Binary data
Processed: Bug#1059983 marked as pending in gnome-software
Processing control commands: > tag -1 pending Bug #1059983 [src:gnome-software] gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable Added tag(s) pending. -- 1059983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059983: marked as pending in gnome-software
Control: tag -1 pending Hello, Bug #1059983 in gnome-software reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-software/-/commit/edeab91e541f2dbe2882e360b5b2e06764505419 Drop nocheck annotation from appstream Build-Depends Closes: #1059983 (this message was generated automatically) -- Greetings https://bugs.debian.org/1059983
Processed: severity of 1055999 is grave
Processing commands for cont...@bugs.debian.org: > severity 1055999 grave Bug #1055999 [src:python-asyncssh] python-asyncssh: CVE-2023-46446 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1055999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060067: fuse3: FTBFS: dh_missing: error: missing files, aborting
Package: fuse3 Version: 3.14.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, fuse3 fails to build with error in dh_missing. From my build log on amd64: | dh_fixperms | chmod a-x debian/libfuse3-dev/usr/share/doc/libfuse3-dev/examples/cuse_client.c | make[1]: Leaving directory '/<>' |debian/rules override_dh_missing | make[1]: Entering directory '/<>' | dh_missing --fail-missing | dh_missing: warning: usr/lib/udev/rules.d/99-fuse3.rules exists in debian/tmp but is not installed to anywhere | dh_missing: error: missing files, aborting | The following debhelper tools have reported what they installed (with files per package) |* dh_install: fuse3 (3), fuse3-udeb (2), libfuse3-3 (2), libfuse3-3-udeb (2), libfuse3-dev (4) |* dh_installdocs: fuse3 (0), libfuse3-3 (3), libfuse3-dev (0) |* dh_installexamples: fuse3 (0), libfuse3-3 (0), libfuse3-dev (21) |* dh_installman: fuse3 (2), libfuse3-3 (0), libfuse3-dev (0) | If the missing files are installed by another tool, please file a bug against it. | When filing the report, if the tool is not part of debhelper itself, please reference the | "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). | (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz) | Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built | If the omission is intentional or no other helper can take care of this consider adding the | paths to debian/not-installed. | make[1]: *** [debian/rules:73: override_dh_missing] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:76: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 A full build log on riscv64 is available there: https://buildd.debian.org/status/fetch.php?pkg=fuse3=riscv64=3.14.0-4%2Bb1=1704460936=0 A full build log on arm64 is also available from reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/fuse3_3.14.0-4.rbuild.log.gz Regards Aurelien
Processed: Re: gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable
Processing commands for cont...@bugs.debian.org: > found 1059983 45.1-1 Bug #1059983 [src:gnome-software] gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable Marked as found in versions gnome-software/45.1-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1059983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060063: pysph: autopkgtest failure with Python 3.12
Source: pysph Version: 1.0~b1-7 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer pysph's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/pysph/testing/amd64/ 70s autopkgtest [13:23:33]: test pysph-test-elliptical: [--- 70s === python3.12 === 70s Traceback (most recent call last): 70s File "/tmp/tmp.9lI1hBJWqm/test.py", line 12, in 70s from pysph.base.utils import get_particle_array 70s File "/usr/lib/python3/dist-packages/pysph/base/utils.py", line 7, in 70s from .particle_array import ParticleArray, \ 70s File "pysph/base/particle_array.pyx", line 25, in init pysph.base.particle_array 70s File "/usr/lib/python3/dist-packages/compyle/array.py", line 11, in 70s from .sort import radix_sort 70s File "/usr/lib/python3/dist-packages/compyle/sort.py", line 5, in 70s from .transpiler import Transpiler, convert_to_float_if_needed 70s File "/usr/lib/python3/dist-packages/compyle/transpiler.py", line 12, in 70s from .ext_module import ExtModule 70s File "/usr/lib/python3/dist-packages/compyle/ext_module.py", line 3, in 70s from distutils.sysconfig import get_config_vars 70s ModuleNotFoundError: No module named 'distutils' 71s autopkgtest [13:23:34]: test pysph-test-elliptical: ---] 71s pysph-test-elliptical FAIL non-zero exit status 1
Bug#963777: marked as done (condor: CVE-2019-18823)
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#963777: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #963777, regarding condor: CVE-2019-18823 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.) -- 963777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: condor Version: 8.6.8~dfsg.1-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 8.4.11~dfsg.1-1 Hi, The following vulnerability was published for condor. CVE-2019-18823[0]: | HTCondor up to and including stable series 8.8.6 and development | series 8.9.4 has Incorrect Access Control. It is possible to use a | different authentication method to submit a job than the administrator | has specified. If the administrator has configured the READ or WRITE | methods to include CLAIMTOBE, then it is possible to impersonate | another user to the condor_schedd. (For example to submit or remove | jobs) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-18823 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18823 Regards, Salvatore --- End Message --- --- Begin Message --- Source: condor Source-Version: 23.2.0+dfsg-1 Done: Tim Theisen We believe that the bug you reported is fixed in the latest version of condor, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Theisen (supplier of updated condor 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: Wed, 27 Dec 2023 20:30:00 -0600 Source: condor Binary: condor condor-annex-ec2 condor-dbgsym condor-dev condor-doc condor-kbdd condor-kbdd-dbgsym condor-test condor-test-dbgsym condor-upgrade-checks condor-vm-gahp condor-vm-gahp-dbgsym htcondor htcondor-annex-ec2 htcondor-dev htcondor-doc htcondor-test htcondor-upgrade-checks minicondor minihtcondor Architecture: source amd64 all Version: 23.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Tim Theisen Description: condor - distributed workload management system condor-annex-ec2 - distributed workload management system - single node configuratio condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation condor-kbdd - distributed workload management system - single node configuratio condor-test - distributed workload management system - single node configuratio condor-upgrade-checks - distributed workload management system - single node configuratio condor-vm-gahp - distributed workload management system - single node configuratio htcondor - transitional dummy package htcondor-annex-ec2 - transitional dummy package htcondor-dev - transitional dummy package htcondor-doc - transitional dummy package htcondor-test - transitional dummy package htcondor-upgrade-checks - transitional dummy package minicondor - distributed workload management system - single node configuratio minihtcondor - transitional dummy package Closes: 671467 790545 925657 936323 963777 966726 982050 995838 1000130 1002540 1008634 1020692 Changes: condor (23.2.0+dfsg-1) unstable; urgency=medium . [ Tim Theisen ] * Add backward compatible overrides for old lintian used by ftp-masters * new upstream feature release (Closes: #982050, #995838, #1020692) * Fixes for CVE-2019-18823 (Closes: #963777) * Fixes for CVE-2021-25311 * Fixes for CVE-2021-25312 * Fixes for CVE-2021-45101 (Closes: #1002540) * Fixes for CVE-2021-45102 * Fixes for CVE-2021-45103 * Fixes for CVE-2021-45104 * Fixes for CVE-2022-26110 (Closes: #1008634) * Builds with GCC 12 (Closes: #925657) * Python bindings for Python 3 (Closes: #790545, #936323, #966726) * Port to libpcre2 (Closes: #1000130) * Remove globus support (upstream change)
Bug#966726: marked as done (condor: Unversioned Python removal in sid/bullseye)
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#966726: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #966726, regarding condor: Unversioned Python removal in sid/bullseye 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.) -- 966726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:condor Version: 8.6.8~dfsg.1-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: condor Source-Version: 23.2.0+dfsg-1 Done: Tim Theisen We believe that the bug you reported is fixed in the latest version of condor, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Theisen (supplier of updated condor 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: Wed, 27 Dec 2023 20:30:00 -0600 Source: condor Binary: condor condor-annex-ec2 condor-dbgsym condor-dev condor-doc condor-kbdd condor-kbdd-dbgsym condor-test condor-test-dbgsym condor-upgrade-checks condor-vm-gahp condor-vm-gahp-dbgsym htcondor htcondor-annex-ec2 htcondor-dev htcondor-doc htcondor-test htcondor-upgrade-checks minicondor minihtcondor Architecture: source amd64 all Version: 23.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Tim Theisen Description: condor - distributed workload management system condor-annex-ec2 - distributed workload management system - single node configuratio condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation condor-kbdd - distributed workload management system - single node configuratio condor-test - distributed workload management system - single node configuratio condor-upgrade-checks - distributed workload management system - single node configuratio condor-vm-gahp - distributed workload management system - single node configuratio htcondor - transitional dummy package htcondor-annex-ec2 - transitional dummy package htcondor-dev - transitional dummy package htcondor-doc - transitional dummy package htcondor-test - transitional dummy package htcondor-upgrade-checks - transitional dummy package minicondor - distributed workload management system - single node configuratio minihtcondor - transitional dummy package Closes: 671467 790545 925657 936323 963777 966726 982050 995838 1000130 1002540 1008634 1020692 Changes: condor (23.2.0+dfsg-1) unstable; urgency=medium . [ Tim Theisen ] * Add backward compatible overrides for old lintian used by ftp-masters * new upstream feature release (Closes: #982050, #995838, #1020692) * Fixes for CVE-2019-18823 (Closes: #963777) * Fixes for CVE-2021-25311 * Fixes for CVE-2021-25312 * Fixes for CVE-2021-45101 (Closes: #1002540) * Fixes for CVE-2021-45102 * Fixes for CVE-2021-45103 * Fixes for CVE-2021-45104 * Fixes for CVE-2022-26110 (Closes: #1008634) * Builds with GCC 12 (Closes: #925657)
Bug#936323: marked as done (condor: Python2 removal in sid/bullseye)
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#936323: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #936323, regarding condor: Python2 removal in sid/bullseye 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.) -- 936323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:condor Version: 8.6.8~dfsg.1-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:condor If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: condor Source-Version: 23.2.0+dfsg-1 Done: Tim Theisen We believe that the bug you reported is fixed in the latest version of condor, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Theisen (supplier of updated condor 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: Wed, 27 Dec 2023 20:30:00 -0600 Source: condor Binary: condor condor-annex-ec2 condor-dbgsym condor-dev condor-doc condor-kbdd condor-kbdd-dbgsym condor-test condor-test-dbgsym condor-upgrade-checks condor-vm-gahp condor-vm-gahp-dbgsym htcondor htcondor-annex-ec2 htcondor-dev htcondor-doc htcondor-test htcondor-upgrade-checks minicondor minihtcondor Architecture: source amd64 all Version: 23.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Tim Theisen Description: condor - distributed workload management system condor-annex-ec2 - distributed workload management system - single node configuratio condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation condor-kbdd - distributed workload management system - single node configuratio condor-test - distributed workload management system - single node
Bug#925657: marked as done (condor: ftbfs with GCC-9)
Your message dated Fri, 05 Jan 2024 13:00:12 +
with message-id
and subject line Bug#925657: fixed in condor 23.2.0+dfsg-1
has caused the Debian Bug report #925657,
regarding condor: ftbfs with GCC-9
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.)
--
925657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:condor
Version: 8.6.8~dfsg.1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/condor_8.6.8~dfsg.1-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.
To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html
GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.
[...]
| ^~~~
[100%] Building CXX object
src/gce_gahp/CMakeFiles/gce_gahp.dir/gcegahp_common.cpp.o
cd "/<>/obj-x86_64-linux-gnu/src/gce_gahp" && /usr/bin/c++
-DBUILD_DATE="\"Mar 26 2019\"" -DCONDOR_VERSION=\"8.6.8\" -DGLIBC228=GLIBC228
-DGLIBC=GLIBC -DHAVE_CONFIG_H -DLINUX=\"LINUX_4.9.0-8-AMD64\"
-DPLATFORM=\"X86_64-Debian_\" -DPRE_RELEASE_STR="\" Debian-8.6.8~dfsg.1-2\""
-DWITH_OPENSSL -DX86_64=X86_64
-I"/<>/obj-x86_64-linux-gnu/bld_external/classads-8.6.8/install/include"
-I/usr/include/globus -I/usr/lib64/globus/include -I/usr/lib/globus/include
-I/usr/local/globus/include/globus -I"/<>/src/condor_includes"
-I"/<>/obj-x86_64-linux-gnu/src/condor_includes"
-I"/<>/src/condor_utils"
-I"/<>/obj-x86_64-linux-gnu/src/condor_utils"
-I"/<>/src/condor_daemon_core.V6"
-I"/<>/src/condor_daemon_client" -I"/<>/src/ccb"
-I"/<>/src/condor_io" -I"/<>/src/h"
-I"/<>/obj-x86_64-linux-gnu/src/h"
-I"/<>/obj-x86_64-linux-gnu/src/cla
ssad" -I"/<>/src/classad" -I"/<>/src/safefile"
-I"/<>/obj-x86_64-linux-gnu/src/safefile"
-I"/<>/src/gce_gahp"
-I"/<>/obj-x86_64-linux-gnu/src/gce_gahp" -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fopenmp -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp -Wall -W
-Wextra -Wfloat-equal -Wendif-labels -Wpointer-arith -Wcast-qual -Wcast-align
-Wvolatile-register-var -Wno-error=unused-local-typedefs
-Wdeprecated-declarations -Wno-error=deprecated-declarations
-Wno-nonnull-compare -Wno-error=nonnull-compare -fstack-protector -rdynamic -g
-o CMakeFiles/gce_gahp.dir/gcegahp_common.cpp.o -c
"/<>/src/gce_gahp/gcegahp_common.cpp"
In file included from /<>/src/gce_gahp/gcegahp_common.cpp:22:
/<>/src/condor_includes/condor_config.h: In member function
'HASHITER& HASHITER::operator=(const HASHITER&)':
/<>/src/condor_includes/condor_config.h:371:100: warning: 'void*
memcpy(void*, const void*, size_t)' writing to an object of type 'class
HASHITER' with no trivial copy-assignment; use copy-assignment or
copy-initialization instead [-Wclass-memaccess]
371 | HASHITER& operator=(const HASHITER& rhs) { if (this != ) {
memcpy(this, , sizeof(HASHITER)); } return *this; }
|
^
/<>/src/condor_includes/condor_config.h:364:7: note: 'class
HASHITER' declared here
364 | class HASHITER {
| ^~~~
/<>/src/gce_gahp/gcegahp_common.cpp: In function 'std::string
create_output_string(int, const char**, int)':
Bug#1008634: marked as done (condor: CVE-2022-26110 / HTCONDOR-2022-0003)
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1008634: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1008634, regarding condor: CVE-2022-26110 / HTCONDOR-2022-0003 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.) -- 1008634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: condor Version: 8.6.8~dfsg.1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for condor. CVE-2022-26110[0], HTCONDOR-2022-0003 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-26110 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26110 [1] https://htcondor.org/security/vulnerabilities/HTCONDOR-2022-0003 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: condor Source-Version: 23.2.0+dfsg-1 Done: Tim Theisen We believe that the bug you reported is fixed in the latest version of condor, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Theisen (supplier of updated condor 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: Wed, 27 Dec 2023 20:30:00 -0600 Source: condor Binary: condor condor-annex-ec2 condor-dbgsym condor-dev condor-doc condor-kbdd condor-kbdd-dbgsym condor-test condor-test-dbgsym condor-upgrade-checks condor-vm-gahp condor-vm-gahp-dbgsym htcondor htcondor-annex-ec2 htcondor-dev htcondor-doc htcondor-test htcondor-upgrade-checks minicondor minihtcondor Architecture: source amd64 all Version: 23.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Tim Theisen Description: condor - distributed workload management system condor-annex-ec2 - distributed workload management system - single node configuratio condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation condor-kbdd - distributed workload management system - single node configuratio condor-test - distributed workload management system - single node configuratio condor-upgrade-checks - distributed workload management system - single node configuratio condor-vm-gahp - distributed workload management system - single node configuratio htcondor - transitional dummy package htcondor-annex-ec2 - transitional dummy package htcondor-dev - transitional dummy package htcondor-doc - transitional dummy package htcondor-test - transitional dummy package htcondor-upgrade-checks - transitional dummy package minicondor - distributed workload management system - single node configuratio minihtcondor - transitional dummy package Closes: 671467 790545 925657 936323 963777 966726 982050 995838 1000130 1002540 1008634 1020692 Changes: condor (23.2.0+dfsg-1) unstable; urgency=medium . [ Tim Theisen ] * Add backward compatible overrides for old lintian used by ftp-masters * new upstream feature release (Closes: #982050, #995838, #1020692) * Fixes for CVE-2019-18823 (Closes: #963777) * Fixes for CVE-2021-25311 * Fixes for CVE-2021-25312 * Fixes for CVE-2021-45101 (Closes: #1002540) * Fixes for CVE-2021-45102 * Fixes for CVE-2021-45103 * Fixes for CVE-2021-45104 * Fixes for CVE-2022-26110 (Closes: #1008634) * Builds with GCC 12 (Closes: #925657) * Python bindings for Python 3 (Closes: #790545, #936323, #966726) * Port to libpcre2 (Closes: #1000130) * Remove globus support (upstream change) (Closes: #671467) * add minihtcondor package * add htcondor-annex-ec2 package * restore openstack_gahp sources * Squash lintian errors and warnings * Too many to mention see online documentation: -
Bug#1002540: marked as done (condor: CVE-2021-45101)
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1002540: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1002540, regarding condor: CVE-2021-45101 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.) -- 1002540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: condor Version: 8.6.8~dfsg.1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for condor. CVE-2021-45101[0]: | An issue was discovered in HTCondor before 8.8.15, 9.0.x before 9.0.4, | and 9.1.x before 9.1.2. Using standard command-line tools, a user with | only READ access to an HTCondor SchedD or Collector daemon can | discover secrets that could allow them to control other users' jobs | and/or read their data. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-45101 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45101 [1] https://research.cs.wisc.edu/htcondor/security/vulnerabilities/HTCONDOR-2021-0003/ [2] https://github.com/htcondor/htcondor/8b311dee6dee6be518e65381e020fb74848b552b Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: condor Source-Version: 23.2.0+dfsg-1 Done: Tim Theisen We believe that the bug you reported is fixed in the latest version of condor, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Theisen (supplier of updated condor 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: Wed, 27 Dec 2023 20:30:00 -0600 Source: condor Binary: condor condor-annex-ec2 condor-dbgsym condor-dev condor-doc condor-kbdd condor-kbdd-dbgsym condor-test condor-test-dbgsym condor-upgrade-checks condor-vm-gahp condor-vm-gahp-dbgsym htcondor htcondor-annex-ec2 htcondor-dev htcondor-doc htcondor-test htcondor-upgrade-checks minicondor minihtcondor Architecture: source amd64 all Version: 23.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Tim Theisen Description: condor - distributed workload management system condor-annex-ec2 - distributed workload management system - single node configuratio condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation condor-kbdd - distributed workload management system - single node configuratio condor-test - distributed workload management system - single node configuratio condor-upgrade-checks - distributed workload management system - single node configuratio condor-vm-gahp - distributed workload management system - single node configuratio htcondor - transitional dummy package htcondor-annex-ec2 - transitional dummy package htcondor-dev - transitional dummy package htcondor-doc - transitional dummy package htcondor-test - transitional dummy package htcondor-upgrade-checks - transitional dummy package minicondor - distributed workload management system - single node configuratio minihtcondor - transitional dummy package Closes: 671467 790545 925657 936323 963777 966726 982050 995838 1000130 1002540 1008634 1020692 Changes: condor (23.2.0+dfsg-1) unstable; urgency=medium . [ Tim Theisen ] * Add backward compatible overrides for old lintian used by ftp-masters * new upstream feature release (Closes: #982050, #995838, #1020692) * Fixes for CVE-2019-18823 (Closes: #963777) * Fixes for CVE-2021-25311 * Fixes for CVE-2021-25312 * Fixes for CVE-2021-45101 (Closes: #1002540) * Fixes for CVE-2021-45102 * Fixes for CVE-2021-45103 * Fixes for CVE-2021-45104 * Fixes for CVE-2022-26110 (Closes: #1008634) * Builds with GCC 12 (Closes: #925657) * Python bindings for
Bug#1000130: marked as done (condor: depends on obsolete pcre3 library)
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1000130: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1000130, regarding condor: depends on obsolete pcre3 library 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.) -- 1000130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: condor Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: condor Source-Version: 23.2.0+dfsg-1 Done: Tim Theisen We believe that the bug you reported is fixed in the latest version of condor, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Theisen (supplier of updated condor 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: Wed, 27 Dec 2023 20:30:00 -0600 Source: condor Binary: condor condor-annex-ec2 condor-dbgsym condor-dev condor-doc condor-kbdd condor-kbdd-dbgsym condor-test condor-test-dbgsym condor-upgrade-checks condor-vm-gahp condor-vm-gahp-dbgsym htcondor htcondor-annex-ec2 htcondor-dev htcondor-doc htcondor-test htcondor-upgrade-checks minicondor minihtcondor Architecture: source amd64 all Version: 23.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Tim Theisen Description: condor - distributed workload management system condor-annex-ec2 - distributed workload management system - single node configuratio condor-dev - distributed workload management system - development files condor-doc - distributed workload management system - documentation condor-kbdd - distributed workload management system - single node configuratio condor-test - distributed workload management system - single node configuratio condor-upgrade-checks - distributed workload management system - single node configuratio condor-vm-gahp - distributed workload management system - single node configuratio htcondor - transitional dummy package htcondor-annex-ec2 - transitional dummy package htcondor-dev - transitional dummy package htcondor-doc - transitional dummy package htcondor-test - transitional dummy package htcondor-upgrade-checks - transitional dummy package minicondor - distributed workload management system - single node configuratio minihtcondor - transitional dummy package Closes: 671467 790545 925657 936323 963777 966726 982050 995838 1000130 1002540 1008634 1020692 Changes: condor (23.2.0+dfsg-1) unstable; urgency=medium . [ Tim Theisen ] * Add backward compatible overrides for old lintian used by ftp-masters * new upstream feature release (Closes: #982050, #995838, #1020692) * Fixes for CVE-2019-18823 (Closes: #963777) * Fixes for CVE-2021-25311 * Fixes for CVE-2021-25312 * Fixes for CVE-2021-45101 (Closes: #1002540) * Fixes for CVE-2021-45102 * Fixes for CVE-2021-45103 * Fixes for CVE-2021-45104 * Fixes for CVE-2022-26110 (Closes: #1008634) * Builds with GCC 12 (Closes: #925657) * Python bindings for Python 3 (Closes: #790545, #936323, #966726) *
Bug#1060061: grub-efi-amd64-bin: out of memory when loading initial ramdisk
Package: grub-efi-amd64-bin
Version: 2.06-3~deb11u6
Severity: critical
Tags: upstream
Justification: breaks the whole system
X-Debbugs-Cc: mtilje...@uber.com
Dear Maintainer,
On certain system, in this case an Ice Lake based server running an AMI
bios (version 3219BS01.021), GRUB will sporadically fail to boot with
the following:
>> Booting `Debian GNU/Linux, with Linux 5.10.113-1'Booting `Debian
>> GNU/Linux, with Linux 5.10.113-1'
>>
>>
>>
>> Loading Linux 5.10.113-1 ...Loading Linux 5.10.113-1 ...
>>
>> Loading initial ramdisk ...Loading initial ramdisk ...
>>
>> error: out of memory.
>> error: out of memory.
This error is sporadic and appears maybe 90% of the time, so I can
barely get the system up and running for testing purposes.
I believe this is related to memory management in GRUB and similar to
https://bugs.launchpad.net/oem-priority/+bug/1842320
which is apparently caused by an upstream bug
https://savannah.gnu.org/bugs/?61058
>From digging around it appears this has been fixed in Redhat/Fedora with
https://src.fedoraproject.org/rpms/grub2/c/098a8a9e99d4b32576e7af518e8e195059f985b9?branch=f33
but apparently this patch applies to previous memory subsystem patches,
so I haven't been able to backport these patches.
I've successfully backported grub 2.12~rc1-12 from sid by changing the
compiler back to gcc-10 and building from source. This version works and
boots every time without issue.
I've also tried to backport grub 2.06-13+deb12u1 from bookworm, but this
does not help. I hence believe this problem affects both Debian
bullseye and bookworm.
Best,
Morten Hein Tiljeset
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/nvme0n1p1 / ext4 rw,noatime,errors=panic 0 0
/dev/nvme1n1p1 /opt ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /var/log ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme0n1p12 /boot/efi vfat
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
/dev/nvme1n1p1 /var/lib/systemd/coredump ext4 rw,noatime,errors=panic,stripe=64
0 0
/dev/nvme1n1p1 /var/log/containers ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /opt/system/log/containers ext4
rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /var/log/pods ext4 rw,noatime,errors=panic,stripe=64 0 0
/dev/nvme1n1p1 /opt/system/log/pods ext4 rw,noatime,errors=panic,stripe=64 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
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set
default="gnulinux-5.10.113-1-advanced-5a78d20e-e0e5-44b7-b2a6-363a3b536fc9"
fi
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
}
serial --speed=115200
terminal_input console serial
terminal_output console serial
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=0
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/04_unrestricted ###
menuentry_id_option="--unrestricted $menuentry_id_option"
### END /etc/grub.d/04_unrestricted ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/05_header ###
### END /etc/grub.d/05_header ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux, with Linux 6.1.53-1' --class debian --class
gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-6.1.53-1-advanced-5a78d20e-e0e5-44b7-b2a6-363a3b536fc9' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root
5a78d20e-e0e5-44b7-b2a6-363a3b536fc9
echo'Loading Linux
Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco
* Chris Knadle [2024-01-02 16:53]: The way to orphan a package is to do an upload and setting the maintainer to be . Until that's done the package ends up in maintainership limbo. See the bottom of Policy 3.3, and Developer's Reference section 5.9.4. Agreed but I think that is something for the Maintainer: to do, who seems to be active in Debian, otherwise. I may be able to prepare an updated version to upload as an NMU (i.e. it would be Debian version 1.13.0-0.1), but I can't take over maintaining this package long-term because I don't use it and am not familiar with it -- I only maintain a package that has it as a required build dependency. I also haven't maintained a library yet, but I've been in this situation of needing to upload a newer version of a library before so I might be able to figure out what's required to prepare an upload. It would be interesting to upload a new version as an NMU with the maintainer marked as but strangely that seems to be what's called for here. Feel free to ask if you have questions regarding maintaining a library. Cheers Jochen signature.asc Description: PGP signature
Bug#1056031: marked as done (rust-rstest-test: autopkgtest failure)
Your message dated Fri, 5 Jan 2024 07:11:06 -0500
with message-id
and subject line Fixed in 0.11.0-2
has caused the Debian Bug report #1056031,
regarding rust-rstest-test: autopkgtest failure
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.)
--
1056031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rstest-test
Version: 0.11.0-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rstest-test/39198638/log.gz
...
84s more_tests::case_2_contains stdout
84s Stderr: debian cargo wrapper: options, profiles, parallel: ['parallel=64']
[] ['-j64']
84s debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
84s debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '+stable', '-Zavoid-dev-deps', 'test', '--verbose',
'--verbose', '-j64', '--target', 'x86_64-unknown-linux-gnu'],) {}
84s error: no such subcommand: `+stable`
84s
84sCargo does not handle `+toolchain` directives.
84sDid you mean to invoke `cargo` through `rustup` instead?
84s
84s thread 'more_tests::case_2_contains' panicked at 'Empty stdout!',
/usr/share/cargo/registry/rstest-test-0.11.0/src/utils.rs:308:13
84s stack backtrace:
84s0: std::panicking::begin_panic
84s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:610:12
84s1: rstest_test::utils::TestResults::assert
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/src/utils.rs:308:13
84s2: framework::more_tests
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:87:5
84s3: framework::more_tests::case_2_contains
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:58:1
84s4: framework::more_tests::case_2_contains::{{closure}}
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:58:1
84s5: core::ops::function::FnOnce::call_once
84s at
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
84s6: core::ops::function::FnOnce::call_once
84s at
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
84s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
84s
84s
84s failures:
84s add_local_dependency
84s more_tests::case_1_default_conf
84s more_tests::case_2_contains
84s nocapture_in_tests
84s one_fail::case_1_default_conf
84s one_fail::case_2_contains
84s one_success::case_1_default_conf
84s one_success::case_2_contains
84s should_check_just_contains_conf
84s should_check_just_contains_on_some_test
84s should_check_some_tests_as_contains
84s should_detect_wrong_contains
84s tests_with_should_panic::case_1_default_conf
84s tests_with_should_panic::case_2_contains
84s
84s test result: FAILED. 1 passed; 14 failed; 0 ignored; 0 measured; 0
filtered out; finished in 0.79s
84s
84s error: test failed, to rerun pass `--test framework`
85s autopkgtest [21:27:08]: test librust-rstest-test-dev::
---]
85s autopkgtest [21:27:08]: test librust-rstest-test-dev:: - - - - - - - - -
- results - - - - - - - - - -
85s librust-rstest-test-dev: FAIL non-zero exit status 101
85s autopkgtest [21:27:08]: summary
85s rust-rstest-test:@ FAIL non-zero exit status 101
85s librust-rstest-test-dev:default FAIL non-zero exit status 101
85s librust-rstest-test-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Version: 0.11.0-2
I've fixed the test suite in version 0.11.0-2. package is now in unstable
--
regards,
Reinhard
--- End Message ---
Bug#1037606: clog: diff for NMU version 1.3.0-1.1
Control: tags 1037606 + pending Dear maintainer, I've prepared an NMU for clog (versioned as 1.3.0-1.1) and uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Regards. -- Sudip diff -Nru clog-1.3.0/debian/changelog clog-1.3.0/debian/changelog --- clog-1.3.0/debian/changelog 2016-07-07 23:14:04.0 +0100 +++ clog-1.3.0/debian/changelog 2024-01-05 11:40:11.0 + @@ -1,3 +1,11 @@ +clog (1.3.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with gcc13 by adding a missing include. (Closes: #1037606) +- Thanks Mate Kukri and Jonathan Bergh. (LP: #2048084) + + -- Sudip Mukherjee Fri, 05 Jan 2024 11:40:11 + + clog (1.3.0-1) unstable; urgency=medium * New upstream release. diff -Nru clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch --- clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch 1970-01-01 01:00:00.0 +0100 +++ clog-1.3.0/debian/patches/json2_cstdint_ftbfs.patch 2024-01-05 11:40:07.0 + @@ -0,0 +1,15 @@ +Description: Fix FTBFS by adding cstdint include to JSON2.h +Author: Mate Kukri +Last-Update: 2024-01-04 +--- + +--- a/src/libshared/src/JSON2.h b/src/libshared/src/JSON2.h +@@ -27,6 +27,7 @@ + #ifndef INCLUDED_JSON2 + #define INCLUDED_JSON2 + ++#include + #include + + class JSON2 diff -Nru clog-1.3.0/debian/patches/series clog-1.3.0/debian/patches/series --- clog-1.3.0/debian/patches/series2016-07-07 23:01:34.0 +0100 +++ clog-1.3.0/debian/patches/series2024-01-05 10:55:20.0 + @@ -1 +1,2 @@ FixManMinusSign.diff +json2_cstdint_ftbfs.patch
Processed: clog: diff for NMU version 1.3.0-1.1
Processing control commands: > tags 1037606 + pending Bug #1037606 [src:clog] clog: ftbfs with GCC-13 Added tag(s) pending. -- 1037606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877016: Time to drop cpufrequtils?
On Sun, Sep 03, 2023 at 08:26:00PM +0200, Moritz Mühlenhoff wrote: > severity 877016 serious > thanks > > Am Thu, Sep 28, 2017 at 06:51:30AM -0700 schrieb Mattia Dongili: > > On Wed, Sep 27, 2017 at 03:16:52PM -0400, Phil Susi wrote: > > > Package: cpufrequtils > > > Version: 008-1 > > ... > > > is the case, should cpufrequtils not be removed now? > > > > Yes, indeed it should. Thanks for nagging. > > Bumping the severity to RC to move forward with this for trixie. > $ dak rm -nR cpufrequtils Will remove the following packages from unstable: cpufrequtils | 008-2 | source, amd64, arm64, armel, armhf, i386, mips64el, s390x libcpufreq-dev | 008-2 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x libcpufreq-dev | 008-2+b1 | riscv64 libcpufreq0 | 008-2 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x libcpufreq0 | 008-2+b1 | riscv64 Maintainer: Seunghun Han --- Reason --- -- Checking reverse dependencies... No dependency problem found. Seems like it's good to go? C
Bug#1041814: marked as done (python-mechanicalsoup: CVE-2023-34457)
Your message dated Fri, 05 Jan 2024 10:50:50 + with message-id and subject line Bug#1041814: fixed in python-mechanicalsoup 1.3.0-1 has caused the Debian Bug report #1041814, regarding python-mechanicalsoup: CVE-2023-34457 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.) -- 1041814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-mechanicalsoup Version: 0.10.0-6 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.10.0-4 Hi, The following vulnerability was published for python-mechanicalsoup. The severity choosen for the bugreport might be slightly overrated, but I am aiming to understand if the package is actively maintained and might rather be removed from testing if not updated to a more recent version. CVE-2023-34457[0]: | MechanicalSoup is a Python library for automating interaction with | websites. Starting in version 0.2.0 and prior to version 1.3.0, a | malicious web server can read arbitrary files on the client using a | `` inside HTML form. All users of | MechanicalSoup's form submission are affected, unless they took very | specific (and manual) steps to reset HTML form field values. Version | 1.3.0 contains a patch for this issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-34457 https://www.cve.org/CVERecord?id=CVE-2023-34457 [1] https://github.com/MechanicalSoup/MechanicalSoup/security/advisories/GHSA-x456-3ccm-m6j4 [2] https://github.com/MechanicalSoup/MechanicalSoup/commit/d57c4a269bba3b9a0c5bfa20292955b849006d9e Regards, Salvatore --- End Message --- --- Begin Message --- Source: python-mechanicalsoup Source-Version: 1.3.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-mechanicalsoup, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-mechanicalsoup 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: Fri, 05 Jan 2024 11:24:14 +0100 Source: python-mechanicalsoup Architecture: source Version: 1.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Alexandre Detiste Closes: 1040429 1041814 Changes: python-mechanicalsoup (1.3.0-1) unstable; urgency=medium . * New upstream version 1.3.0 (Closes: #1041814, #1040429) * add myself as uploader * remove old dependency on python3-six * set Rules-Requires-Root: no * use new dh-sequence-python3 * bump Standards-Version to 4.6.2, no further change needed * tests: * delete old patches, not needed anymore * autopkgtest needs python3-pytest-httpbin * disable tests failing likely due to changes on http://httpbin.org/: * new_control * get_request_kwargs * submit_online * submit_set Checksums-Sha1: f2ae7c92579896d1deb9112c066b9169ae839572 2365 python-mechanicalsoup_1.3.0-1.dsc e56008e44027d0f88bf6aadaa74f89d1d91ba1b1 50826 python-mechanicalsoup_1.3.0.orig.tar.gz 5ff026c2f4232b4fd6ded048133ba55a89ed3471 3672 python-mechanicalsoup_1.3.0-1.debian.tar.xz d3f4caf8d06ed1db53700a88651623442686c38c 7169 python-mechanicalsoup_1.3.0-1_source.buildinfo Checksums-Sha256: daee5d9dfe55c223d1166bb2db81ae2395ca402d01b63cf4d4bb6427bf2ccbfb 2365 python-mechanicalsoup_1.3.0-1.dsc 38e8748f62fd9455a0818701a9e2dbfa549639d09f829f3fdd03665c825e7ce1 50826 python-mechanicalsoup_1.3.0.orig.tar.gz f4498aece4dcdd927d68635307ed3faa02dafc729b6bd76a924d432eece7fcff 3672 python-mechanicalsoup_1.3.0-1.debian.tar.xz 33b134d5586e0e65f85963e27f1d7536b6da6f44c9dc7c1bcaf364511993d73b 7169 python-mechanicalsoup_1.3.0-1_source.buildinfo Files: dbe1cf7481ad73671fba22473f60ad99 2365 python optional python-mechanicalsoup_1.3.0-1.dsc b144e9f9b4e3c19f9d06dc62343a960d 50826 python optional
Processed: Re: Bug#1060052: cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce
Processing control commands: > severity -1 normal Bug #1060052 [cifs-utils] cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce Severity set to 'normal' from 'grave' > merge 1060005 -1 Bug #1060005 [cifs-utils] cifs-utils: Copy file with cp, hangs with a kernel NULL pointer dereference. Bug #1060052 [cifs-utils] cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce Merged 1060005 1060052 -- 1060005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060005 1060052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060052: cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce
Control: severity -1 normal Control: merge 1060005 -1 FWIW, this is kernel bug, not cifs-utils bug, - guess it's 6.1.0-17 regression. /mjt
Bug#1060052: cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce
Package: cifs-utils Version: 2:7.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, * Pristine up2date Bookworm install (no GUI, only SSH, cifs-utils, rsyslog installed) * Mount smb/cifs share (/mnt/truenas) * All works fine if I do same from Win-10 or Win-11 OS * I have run below commands on clean Debian Bookworm install in bash shell: sudo mount -t cifs //truenas.fritz.box/mount -o username=user /mnt/truenas user@server:/mnt/truenas/temp$ sudo cp main.cf main.cf.1 Killed -rwxr-xr-x 1 root root 1332 Jul 28 17:25 main.cf -rwxr-xr-x 1 root root 0 Jan 5 09:40 main.cf.1 resulting in a kernel NULL pointer derefernce Shell hangs if I try to remove the empty file. SYSLOG 2024-01-05T10:06:35.361488+01:00 server kernel: [ 85.532965] CIFS: Attempting to mount \\truenas.fritz.box\share 2024-01-05T10:07:45.994338+01:00 server kernel: [ 156.163492] BUG: kernel NULL pointer dereference, address: 2024-01-05T10:07:45.994348+01:00 server kernel: [ 156.163524] #PF: supervisor read access in kernel mode 2024-01-05T10:07:45.994350+01:00 server kernel: [ 156.163539] #PF: error_code(0x) - not-present page 2024-01-05T10:07:45.994350+01:00 server kernel: [ 156.163553] PGD 0 P4D 0 2024-01-05T10:07:45.994352+01:00 server kernel: [ 156.163565] Oops: [#1] PREEMPT SMP PTI 2024-01-05T10:07:45.994353+01:00 server kernel: [ 156.163578] CPU: 3 PID: 621 Comm: cp Not tainted 6.1.0-17-amd64 #1 Debian 6.1.69-1 2024-01-05T10:07:45.994354+01:00 server kernel: [ 156.163598] Hardware name: /DZ68DB, BIOS DBZ6810H.86A.0048.2018.1024.1605 10/24/2018 2024-01-05T10:07:45.994354+01:00 server kernel: [ 156.163617] RIP: 0010:cifs_flush_folio+0x3f/0x100 [cifs] 2024-01-05T10:07:45.994355+01:00 server kernel: [ 156.163683] Code: d2 41 54 49 89 cc 31 c9 55 48 89 f5 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 e8 8d 0a 5d dd 48 3d 00 f0 ff ff 0f 87 a5 00 00 00 <48> 8b 10 48 89 c3 b8 00 10 00 00 f7 c2 00 00 01 00 74 07 0f b6 4b 2024-01-05T10:07:45.994356+01:00 server kernel: [ 156.163721] RSP: 0018:ab5dc0833c88 EFLAGS: 00010207 2024-01-05T10:07:45.994357+01:00 server kernel: [ 156.163736] RAX: RBX: 0534 RCX: 2024-01-05T10:07:45.994357+01:00 server kernel: [ 156.163754] RDX: RSI: RDI: 9a3e21e3 2024-01-05T10:07:45.994358+01:00 server kernel: [ 156.163771] RBP: R08: 0001 R09: 2024-01-05T10:07:45.994359+01:00 server kernel: [ 156.163789] R10: 0533 R11: 9a3e0a189c00 R12: ab5dc0833cf8 2024-01-05T10:07:45.994360+01:00 server kernel: [ 156.163806] R13: ab5dc0833cf0 R14: 9a3e05945410 R15: 0001 2024-01-05T10:07:45.994361+01:00 server kernel: [ 156.163824] FS: 7f46b32ba500() GS:9a410fb8() knlGS: 2024-01-05T10:07:45.994361+01:00 server kernel: [ 156.163844] CS: 0010 DS: ES: CR0: 80050033 2024-01-05T10:07:45.994362+01:00 server kernel: [ 156.163859] CR2: CR3: 000108a5c005 CR4: 000606e0 2024-01-05T10:07:45.994363+01:00 server kernel: [ 156.163876] Call Trace: 2024-01-05T10:07:45.994364+01:00 server kernel: [ 156.163887] 2024-01-05T10:07:45.994364+01:00 server kernel: [ 156.163897] ? __die_body.cold+0x1a/0x1f 2024-01-05T10:07:45.994365+01:00 server kernel: [ 156.163913] ? page_fault_oops+0xd2/0x2b0 2024-01-05T10:07:45.994366+01:00 server kernel: [ 156.163928] ? exc_page_fault+0x70/0x170 2024-01-05T10:07:45.994367+01:00 server kernel: [ 156.163942] ? asm_exc_page_fault+0x22/0x30 2024-01-05T10:07:45.994367+01:00 server kernel: [ 156.163958] ? cifs_flush_folio+0x3f/0x100 [cifs] 2024-01-05T10:07:45.994368+01:00 server kernel: [ 156.164011] ? cifs_flush_folio+0x33/0x100 [cifs] 2024-01-05T10:07:45.994369+01:00 server kernel: [ 156.164062] ? cifs_precopy_set_eof+0x2b/0x150 [cifs] 2024-01-05T10:07:45.994369+01:00 server kernel: [ 156.164115] cifs_remap_file_range+0x16d/0x680 [cifs] 2024-01-05T10:07:45.994370+01:00 server kernel: [ 156.164169] do_clone_file_range+0xe9/0x230 2024-01-05T10:07:45.994371+01:00 server kernel: [ 156.164185] vfs_clone_file_range+0x37/0x140 2024-01-05T10:07:45.994371+01:00 server kernel: [ 156.164199] ioctl_file_clone+0x49/0xb0 2024-01-05T10:07:45.994372+01:00 server kernel: [ 156.164213] do_vfs_ioctl+0x77/0x910 2024-01-05T10:07:45.994372+01:00 server kernel: [ 156.164226] __x64_sys_ioctl+0x6e/0xd0 2024-01-05T10:07:45.994373+01:00 server kernel: [ 156.164239] do_syscall_64+0x5b/0xc0 2024-01-05T10:07:45.994374+01:00 server kernel: [ 156.164253] ? syscall_exit_to_user_mode+0x27/0x40 2024-01-05T10:07:45.994374+01:00 server kernel: [ 156.164268] ? do_syscall_64+0x67/0xc0 2024-01-05T10:07:45.994375+01:00 server kernel: [ 156.164281] ? syscall_exit_to_user_mode+0x27/0x40 2024-01-05T10:07:45.994376+01:00 server kernel: [ 156.164296] ?
Processed: severity of 1059007 is grave
Processing commands for cont...@bugs.debian.org: > severity 1059007 grave Bug #1059007 [src:python-asyncssh] python-asyncssh: CVE-2023-48795 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Hello Julian, Am 04.01.24 um 10:23 schrieb Julian Gilbey: ... The build of src:flask is depending on python3-werkzeug >= 3.x, which has itself a dependency on python3-markupsafe, so if you spot a missing direct dependency I'm interested how this comes to play as Markupsafe should be around at build time. In the debian/experimental branch of python-werkzeug, debian/control does not mention python3-markupsafe, but it should do. hmm, you were talking about Werkzeug, I was within the src:flask package. A bit of misunderstanding. If you spot a issue in src:python-werkzeug than of course that's great you fixed this! -- Regards Carsten
Bug#1059971: marked as done (libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1)
Your message dated Fri, 05 Jan 2024 09:36:39 + with message-id and subject line Bug#1059971: fixed in mesa 23.3.2-2 has caused the Debian Bug report #1059971, regarding libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-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.) -- 1059971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgl1-mesa-dri Version: 23.2.1-1 Severity: important After doing my usual `apt-get dist-upgrade` this morning & reboot, I could not get into gdm anymore. Downgrading to 23.2.1-1 all the mesa packages makes it work again. I have seen similar bugs, but they are old, I don't know if they are related or not. Happy new year! Pierre -- Xorg log file: [ 9.482] (--) Log file renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2683.log" to "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" [ 9.482] X.Org X Server 1.21.1.10 X Protocol Version 11, Revision 0 [ 9.482] Current Operating System: Linux XX 6.6.9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.9-1 (2024-01-01) x86_64 [ 9.482] Kernel command line: BOOT_IMAGE=/vmlinuz-6.6.9-amd64 root=XX ro quiet splash ibt=off panic=0 [ 9.482] xorg-server 2:21.1.10-1 (https://www.debian.org/support) [ 9.482] Current version of pixman: 0.42.2 [ 9.482]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 9.482] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 9.482] (==) Log file: "/var/lib/gdm3/.local/share/xorg/Xorg.0.log", Time: Thu Jan 4 09:29:04 2024 [ 9.482] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 9.482] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 9.482] (==) No Layout section. Using the first Screen section. [ 9.482] (==) No screen section available. Using defaults. [ 9.482] (**) |-->Screen "Default Screen Section" (0) [ 9.482] (**) | |-->Monitor "" [ 9.482] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 9.482] (**) | |-->Device "Intel" [ 9.482] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 9.482] (==) Automatically adding devices [ 9.482] (==) Automatically enabling devices [ 9.482] (==) Automatically adding GPU devices [ 9.482] (==) Automatically binding GPU devices [ 9.482] (==) Max clients allowed: 256, resource mask: 0x1f [ 9.482] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 9.482]Entry deleted from font path. [ 9.482] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 9.483] (==) ModulePath set to "/usr/lib/xorg/modules" [ 9.483] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 9.483] (II) Loader magic: 0x55e3c5e2ff00 [ 9.483] (II) Module ABI versions: [ 9.483]X.Org ANSI C Emulation: 0.4 [ 9.483]X.Org Video Driver: 25.2 [ 9.483]X.Org XInput driver : 24.4 [ 9.483]X.Org Server Extension : 10.0 [ 9.483] (++) using VT number 1 [ 9.487] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c6 [ 9.489] (II) xfree86: Adding drm device (/dev/dri/card0) [ 9.489] (II) Platform probe for /sys/devices/pci:00/:00:02.0/drm/card0 [ 9.489] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 14 paused 0 [ 9.489] (II) xfree86: Adding drm device (/dev/dri/card1) [ 9.489] (II) Platform probe for /sys/devices/platform/evdi.0/drm/card1 [ 9.489] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 15 paused 0 [ 9.490] (II) xfree86: Adding drm device (/dev/dri/card2) [ 9.490] (II) Platform probe for /sys/devices/platform/evdi.1/drm/card2 [ 9.490] (II) systemd-logind: got fd for /dev/dri/card2 226:2 fd 16 paused 0 [ 9.490] (II) xfree86: Adding drm device (/dev/dri/card3) [ 9.490] (II) Platform probe for /sys/devices/platform/evdi.2/drm/card3 [ 9.490] (II)
Bug#1060017: marked as done (xvfb: Failed to start)
Your message dated Fri, 05 Jan 2024 09:36:39 + with message-id and subject line Bug#1060017: fixed in mesa 23.3.2-2 has caused the Debian Bug report #1060017, regarding xvfb: Failed to start 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.) -- 1060017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xvfb Version: 2:21.1.10-1 Severity: critical Tags: ftbfs Control: affects -1 src: rhythmbox xvfb is failing to start in Debian Unstable. This is making many packages fail to build from source. See for instance https://buildd.debian.org/status/package.php?p=rhythmbox Build log excerpt: xvfb-run: error: Xvfb failed to start Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: mesa Source-Version: 23.3.2-2 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of mesa, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated mesa 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: Fri, 05 Jan 2024 11:07:26 +0200 Source: mesa Built-For-Profiles: noudeb Architecture: source Version: 23.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1059971 1060017 Changes: mesa (23.3.2-2) unstable; urgency=medium . * patches: Revert two commits on d3d12 that regressed at least swrast. (Closes: #1059971, #1060017) Checksums-Sha1: 462c25132bc8427150a4f068d19e58752df04b77 5748 mesa_23.3.2-2.dsc 4f1e2b82a518d07f66d505e284d8d3c4181796be 138730 mesa_23.3.2-2.diff.gz 8dac8b87a3986f346968d6ecfee781c3b443 10097 mesa_23.3.2-2_source.buildinfo Checksums-Sha256: 86bd236e80580ed17c421789865d64b09328314cd9557ab6af90aac2b30de1e9 5748 mesa_23.3.2-2.dsc f13b033510bb3afd15be0b119599cb6b6e11cee6dfb64c61cbd563ed932d01ed 138730 mesa_23.3.2-2.diff.gz ddf93dab87914e3fab8c8abdbe4e5ecfffb9cca884d1ee8b1a6d44f41db7bc83 10097 mesa_23.3.2-2_source.buildinfo Files: 321f3db397cebdda221daea358114490 5748 graphics optional mesa_23.3.2-2.dsc 06e1fe09ee00d36112b8c027aea4b263 138730 graphics optional mesa_23.3.2-2.diff.gz db55407823a6a5ed8a0ebf64cfd5d0cc 10097 graphics optional mesa_23.3.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmWXxt4ACgkQy3AxZaiJ hNy0/RAAlIMl0Z7fwyUYUUW5inrk8mfJ+LZbkQuMOZSXOjSN60Rp2xAZipVIu6Gt AOgn4A92weuMVdANM9STSM4quMVEkRpGI5t4Pon1jL2qPOP4MwUwBf6or2hkdnuO T6eWTXH6EHZQ28u3lUWiNGxV+kd/h2ccMA79B9lYlpIkgJivNl9XuBOHyeu50pAL W3BbyZdkj57PWNhsPZl50BOO0X5Y1K8wzWhAogv9bH7ujnPTsEZ9rmbend3WhWVI dr/6TwnLVwnrmbshN+FvR7sqDI7WUxeIYg1wDM4/dX2D7UCyZeGmIakJUTn3DgMz eyPo1hwpvupfkwXiM/Bitm3Oue/tYhSTkcB3S4FnQqFpCFCAZ5lmtdHV6GEi5RiQ tgnTITHzbZSRD+s7aCQiwPGF/CsFF1DyaUmjG0UVurI6aNMYbAlFkUJQXu+aXeLG IGmwJylozKbqRKa5b+Vp6QBFwIndcCwFssoeKKVlS7wtprTDIs/FvNC+fBSDp0Mq g1H3pPyh6Ta+4g9x2I1K60Ps2UVViu19wcyUJSjKIyyjiA0VVdd09YBg7BsNbGdM T1qmgOuoWmvBa0SZDGlMEfasJ1rhSG/sX1VtKx0xkX496Gcfxa0vtId1a6Sp8hnd 8LTwy0TJhhViPDPYvJqB8JYzeYu/frKEoKdbYX3RE3oeJVNCHv0= =UtGr -END PGP SIGNATURE End Message ---
Bug#1059971: libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1
> Pierre Erraud kirjoitti 4.1.2024 klo 11.20: > > Package: libgl1-mesa-dri > > Version: 23.3.2-1 > > Severity: important > > > > After doing my usual `apt-get dist-upgrade` this morning & reboot, > > I could not get into gdm anymore. Downgrading to 23.2.1-1 all the > > mesa packages makes it work again. I have seen similar bugs, but > > they are old, I don't know if they are related or not. > > > > Happy new year! > > > > Pierre > > [ 9.518] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux- > > gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux- > > gnu/dri/i965_dri.so: cannot open shared object file: No such file > > or directory) > > [ 9.518] (EE) AIGLX error: unable to load driver i965 > > That driver is not from mesa, but mesa-amber, which isn't even in > Debian > (yet). > > Yes the error is not there. I looked at a Xorg.0.log when I am using mesa 23.2.1, and I have the same error with the i965 driver, as you said: ... [ 303.274] (II) Initializing extension GLX [ 303.274] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux- gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object file: No such file or directory) [ 303.274] (EE) AIGLX error: unable to load driver i965 [ 303.289] (II) IGLX: Loaded and initialized swrast [ 303.289] (II) GLX: Initialized DRISWRAST GL provider for screen 0 ... My error here is not related to the i965 driver, it's the segfault just after in OsLookupColor. I will try to do a backtrace to understand what's happening exactly.
Bug#1058108: marked as done (pokrok: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)
Your message dated Fri, 05 Jan 2024 08:55:44 +
with message-id
and subject line Bug#1058108: fixed in pokrok 0.2.0-5
has caused the Debian Bug report #1058108,
regarding pokrok: FTBFS: AttributeError: module 'configparser' has no attribute
'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)
--
1058108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pokrok
Version: 0.2.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence
> '\s'
> LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
> File "/<>/setup.py", line 16, in
> version=versioneer.get_version(),
>
> File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
> File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
> ^^
> File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
> ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'.
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:9: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/pokrok_0.2.0-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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 ---
Source: pokrok
Source-Version: 0.2.0-5
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
pokrok, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated pokrok 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: SHA256
Format: 1.8
Date: Fri, 05 Jan 2024 09:19:21 +0100
Source: pokrok
Architecture: source
Version: 0.2.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 1058108
Changes:
pokrok (0.2.0-5) unstable; urgency=medium
.
* Team upload.
* Standards-Version: 4.6.2 (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
* Adapt versioneer.py to Python3.12
Closes: #1058108
* Proper capitalisation in description
* DEP3
* Check DEB_BUILD_OPTIONS in d/rules
* Fix watch file
Checksums-Sha1:
3702f9b91a4bd5e9fb99578caf890d18ec903209 2047 pokrok_0.2.0-5.dsc
f239e7c43eb8d5fa5366b7649a8012cc7653c878 3552 pokrok_0.2.0-5.debian.tar.xz
c5aed9f5fb20c32afcf86a52e29433deccfcd1e9 6853 pokrok_0.2.0-5_amd64.buildinfo
Checksums-Sha256:
a1781c615afd01698490f9802ec17c23df17226e89318d3f370192578a86bc1b 2047
pokrok_0.2.0-5.dsc
