Processed: forcibly merging 1017425 1017494
Processing commands for cont...@bugs.debian.org: > forcemerge 1017425 1017494 Bug #1017425 [src:linux] 5.10.0-17-686-pae: repeatedly crashes during initrd loading [PIII] Bug #1017494 [src:linux] linux-image-5.10.0-17-686-pae always attempts to kill idle task on Mobile P2 Merged 1017425 1017494 > thanks Stopping processing here. Please contact me if you need assistance. -- 1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425 1017494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017425: 5.10.0-17-686-pae: repeatedly crashes during initrd loading [PIII]
I have similar problem in Pentium III machine (DELL PowerEdge 1500SC). [Environment] CPU: Intel(R) Pentium(R) III CPU family (Tualatin) 1400MHz (SMP) Memory: 2GB Debian version: 11.4 linux-image-5.10.0-17-686-pae no longer boots correctly, while linux-image-5.10.0-16-686-pae works. In my case, the following kernel panic message is shown. [0.676076] Hardware name: Dell Computer Corporation PowerEdge 1500SC, BIOS A06 10/14/2004 [0.676134] EIP: __switch_to_asm+0x43/0x5c [0.676178] Code: 1d 54 45 ca c7 89 f6 bb 10 00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 e8 07 00 00 00 f3 90 0f ae e8 eb f9 83 c4 08 4b 75 e2 <0f> ae e8 e8 01 00 00 00 cc 83 c4 04 0f ae e8 9d 5e 5f 5b 5d e9 78 [0.676238] EAX: c7a94480 EBX: ECX: 28494125 EDX: c114b340 [0.676280] ESI: f6fcea40 EDI: c7a94480 EBP: c7a8de3c ESP: c1145f9c [0.676322] DS: 007b ES: 007b FS: 00d8 CS: 00e0 SS: 0068 EFLAGS: 00210046 [0.676365] CR0: 80050033 CR2: ff9ff000 CR3: 07cb2000 CR4: 06f0 [0.676405] Call Trace: [0.676445] Modules linked in: [0.676503] ---[ end trace 02deed42763c6547 ]--- [0.676544] EIP: __switch_to_asm+0x43/0x5c [0.676583] Code: 1d 54 45 ca c7 89 f6 bb 10 00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 e8 07 00 00 00 f3 90 0f ae e8 eb f9 83 c4 08 4b 75 e2 <0f> ae e8 e8 01 00 00 00 cc 83 c4 04 0f ae e8 9d 5e 5f 5b 5d e9 78 [0.676643) EAX: c7a94480 EBX: ECX: 28494125 EDX: c114b340 [0.676685] ESI: f6fcea40 EDI: c7a94480 EBP: c7a8de3c ESP: c1145f9c [0.676739] DS: 007b ES: 007b FS: 00d8 CS: 00e0 SS: 0068 EFLAGS: 00210046 [0.676793] CR0: 80050033 CR2: ff9ff000 CR3: 07cb2000 CR4: 06f0 [0.676847] Kernel panic - not syncing: Attempted to kill the idle task! [0.676989] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- I hope this information helps. -- Takashi Yano
Bug#1017495: libopenexr-dev: trying to overwrite '/usr/include/OpenEXR/Iex.h', which is also in package libilmbase-dev
Package: libopenexr-dev Version: 2.5.7-1 Severity: serious Dear Maintainer, I can't upgrade this package. , | Preconfiguring packages ... | (Reading database ... 325236 files and directories currently installed.) | Preparing to unpack .../libopenexr-dev_3.1.5-2_amd64.deb ... | Unpacking libopenexr-dev (3.1.5-2) over (2.5.7-1) ... | dpkg: error processing archive /var/cache/apt/archives/libopenexr-dev_3.1.5-2_amd64.deb (--unpack): | trying to overwrite '/usr/include/OpenEXR/Iex.h', which is also in package libilmbase-dev:amd64 2.5.7-2 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | /var/cache/apt/archives/libopenexr-dev_3.1.5-2_amd64.deb ` Christian -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.1 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopenexr-dev depends on: ii libilmbase-dev 2.5.7-2 ii libopenexr252.5.7-1 libopenexr-dev recommends no packages. libopenexr-dev suggests no packages. -- no debconf information
Bug#1017294: marked as done (xelb: FTBFS: make[1]: *** [Makefile:15: xcb-xinput.el] Error 255)
Your message dated Tue, 16 Aug 2022 23:28:51 +
with message-id
and subject line Bug#1017294: fixed in xelb 0.18-3
has caused the Debian Bug report #1017294,
regarding xelb: FTBFS: make[1]: *** [Makefile:15: xcb-xinput.el] Error 255
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.)
--
1017294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xelb
Version: 0.18-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
> Generating xcb-xproto.el...
> Using vacuous schema
>
> Generating xcb-bigreq.el...
> Generating xcb-render.el...
> Generating xcb-shape.el...
> Generating xcb-dpms.el...
> Generating xcb-dri2.el...
> Generating xcb-dri3.el...
> Generating xcb-ge.el...
> Generating xcb-glx.el...
> Using vacuous schema
>
> Generating xcb-sync.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Generating xcb-record.el...
> Generating xcb-res.el...
> Using vacuous schema
>
> Generating xcb-screensaver.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Generating xcb-shm.el...
> Generating xcb-xc_misc.el...
> Using vacuous schema
>
> Generating xcb-xevie.el...
> Using vacuous schema
>
> Generating xcb-xf86dri.el...
> Using vacuous schema
>
> Generating xcb-xf86vidmode.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Generating xcb-xinerama.el...
> Generating xcb-xkb.el...
> Using vacuous schema
>
> Generating xcb-xprint.el...
> Using vacuous schema
>
> Generating xcb-xselinux.el...
> Using vacuous schema
>
> Generating xcb-xtest.el...
> Using vacuous schema
>
> Generating xcb-xv.el...
> Using vacuous schema
>
> Generating xcb-xfixes.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Generating xcb-randr.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Using vacuous schema
>
> Generating xcb-xvmc.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Using vacuous schema
>
> Generating xcb-composite.el...
> Generating xcb-damage.el...
> Generating xcb-xinput.el...
> Using vacuous schema
>
> Generating xcb-present.el...
> Using vacuous schema
>
> Using vacuous schema
>
> Using vacuous schema
>
> Using vacuous schema
>
> Debugger entered--Lisp error: (error "Unsupported structure content:
> ")
> signal(error ("Unsupported structure content: "))
> error("Unsupported structure content: <%s>" length)
> (let ((x val)) (error "Unsupported structure content: <%s>" x))
> (cond ((eq val 'pad) (xelb-parse-pad node)) ((eq val 'required_start_align)
> (xelb-parse-required_start_align node)) ((eq val 'field) (xelb-parse-field
> node)) ((eq val 'fd) (xelb-parse-fd node)) ((eq val 'list) (xelb-parse-list
> node)) ((eq val 'exprfield) (xelb-parse-exprfield node)) ((eq val 'switch)
> (xelb-parse-switch node)) ((memq val '(doc comment)) nil) (t (let ((x val))
> (error "Unsupported structure content: <%s>" x
> (let* ((val (xelb-node-name node))) (cond ((eq val 'pad) (xelb-parse-pad
> node)) ((eq val 'required_start_align) (xelb-parse-required_start_align
> node)) ((eq val 'field) (xelb-parse-field node)) ((eq val 'fd) (xelb-parse-fd
> node)) ((eq val 'list) (xelb-parse-list node)) ((eq val 'exprfield)
> (xelb-parse-exprfield node)) ((eq val 'switch) (xelb-parse-switch node))
> ((memq val '(doc comment)) nil) (t (let ((x val)) (error "Unsupported
> structure content: <%s>" x)
> xelb-parse-structure-content((length nil (op ((op . "*")) (fieldref nil
> "len") (value nil "4"
> mapcar(xelb-parse-structure-content ((length nil (op ((op . "*")) (fieldref
> nil "len") (value nil "4"))) (field ((type . "CARD16") (name . "type") (enum
> . "DeviceClassType"))) (field ((type . "CARD16") (name . "len"))) (field
> ((type . "DeviceId") (name . "sourceid"))) (switch ((name . "data"))
> (fieldref nil "type") (required_start_align ((align . "4") (offset . "2")))
> (case ((name . "key")) (enumref ((ref . "DeviceClassType")) "Key")
> (required_start_align ((align . "4") (offset . "2"))) (field ((type .
> "CARD16") (name . "num_keys"))) (list ((type . "CARD32") (name . "keys"))
> (fieldref nil "num_keys"))) (case ((name . "button")) (enumref ((ref .
> "DeviceClassType")) "Button") (required_start_align ((align . "4") (offset .
> "2"))) (field ((type . "CARD16") (name . "num_buttons"))) (list ((type .
> "CARD32") (name . "state"))
Bug#1017491: gnome-maps: Switch to libsoup3
Source: gnome-maps Severity: serious Version: 42.3-2 Forwarded: https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/457 gnome-maps needs to switch to libsoup3. Currently it uses libsoup2.4 and depends on several libraries that are being switched to use libsoup3. It's not possible for an app to link against both libsoup2.4 and libsoup3. We also don't intend to maintain multiple copies of those libraries to preserve the libsoup2.4 build option. Therefore, I believe we will need to temporarily remove gnome-maps from Testing. I believe gnome-maps will be ported to libsoup3 in time for Debian 12. Thank you, Jeremy Bicha
Bug#1017329: marked as done (pencil2d: FTBFS: src/catch.hpp:8164:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’)
Your message dated Tue, 16 Aug 2022 23:06:48 +
with message-id
and subject line Bug#1017329: fixed in pencil2d 0.6.6-3
has caused the Debian Bug report #1017329,
regarding pencil2d: FTBFS: src/catch.hpp:8164:58: error: call to
non-‘constexpr’ function ‘long int sysconf(int)’
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.)
--
1017329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pencil2d
Version: 0.6.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -std=c++11 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -DGIT_TIMESTAMP=\"2021-02-21\" -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11
> -Wall -Wextra -D_REENTRANT -fPIC -DAPP_VERSION=\"0.6.6\"
> -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050600
> -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB
> -DQT_XML_LIB -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB -DQT_TESTLIB_LIB
> -DQT_CORE_LIB -DQT_TESTCASE_BUILDDIR='"/<>/tests"' -I.
> -I../core_lib/src/graphics -I../core_lib/src/graphics/bitmap
> -I../core_lib/src/graphics/vector -I../core_lib/src/interface
> -I../core_lib/src/structure -I../core_lib/src/tool -I../core_lib/src/util
> -I../core_lib/ui -I../core_lib/src/managers -I../core_lib/src
> -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtSvg
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
> -I/usr/include/x86_64-linux-gnu/qt5/QtMultimedia
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui
> -I/usr/include/x86_64-linux-gnu/qt5/QtXml
> -I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork
> -I/usr/include/x86_64-linux-gnu/qt5/QtTest
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/test_viewmanager.o
> src/test_viewmanager.cpp
> In file included from /usr/include/signal.h:328,
> from src/catch.hpp:5549,
> from src/main.cpp:18:
> src/catch.hpp:8164:58: error: call to non-‘constexpr’ function ‘long int
> sysconf(int)’
> 8164 | constexpr static std::size_t sigStackSize = 32768 >= MINSIGSTKSZ
> ? 32768 : MINSIGSTKSZ;
> | ^~~
> In file included from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24:
> /usr/include/unistd.h:640:17: note: ‘long int sysconf(int)’ declared here
> 640 | extern long int sysconf (int __name) __THROW;
> | ^~~
> src/catch.hpp:8223:45: error: size of array ‘altStackMem’ is not an integral
> constant-expression
> 8223 | char FatalConditionHandler::altStackMem[sigStackSize] = {};
> | ^~~~
> /usr/lib/qt5/bin/rcc -name tests data/tests.qrc -o qrc_tests.cpp
> g++ -c -pipe -std=c++11 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -DGIT_TIMESTAMP=\"2021-02-21\" -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11
> -Wall -Wextra -D_REENTRANT -fPIC -DAPP_VERSION=\"0.6.6\"
> -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050600
> -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB
> -DQT_XML_LIB -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB -DQT_TESTLIB_LIB
> -DQT_CORE_LIB -DQT_TESTCASE_BUILDDIR='"/<>/tests"' -I.
> -I../core_lib/src/graphics -I../core_lib/src/graphics/bitmap
> -I../core_lib/src/graphics/vector -I../core_lib/src/interface
> -I../core_lib/src/structure -I../core_lib/src/tool -I../core_lib/src/util
> -I../core_lib/ui -I../core_lib/src/managers -I../core_lib/src
> -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtSvg
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
> -I/usr/include/x86_64-linux-gnu/qt5/QtMultimedia
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui
> -I/usr/include/x86_64-linux-gnu/qt5/QtXml
> -I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork
> -I/usr/include/x86_64-linux-gnu/qt5/QtTest
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/qrc_tests.o
> qrc_tests.cpp
> make[2]: *** [Makefile:417: .obj/main.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/08/13/penci
Bug#1017490: gnome-recipes: uses libsoup2.4
Source: gnome-recipes Version: 2.0.4-1 Severity: serious Forwarded: https://gitlab.gnome.org/GNOME/recipes/-/issues/155 gnome-recipes uses libsoup2.4 and librest. The latest version of librest has switched to libsoup3. It's not possible for an app to link against both libsoup2.4 and libsoup3. I don't think we will package the old version of librest separately. gnome-recipes needs to switch to build with the new librest and libsoup3 to remain available in Debian. gnome-recipes remains available on Flathub https://flathub.org/apps/details/org.gnome.Recipes Thank you, Jeremy Bicha
Bug#1013490: marked as done (django-sass-processor: FTBFS: ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py))
Your message dated Tue, 16 Aug 2022 23:44:07 +0200 with message-id <41ace8d3-4f6f-d44d-2971-cc8687e47...@debian.org> and subject line Re: django-sass-processor: FTBFS: ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py) has caused the Debian Bug report #1013490, regarding django-sass-processor: FTBFS: ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py) 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.) -- 1013490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-sass-processor Version: 1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py config > running config > I: pybuild base:239: python3.10 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:239: /usr/bin/python3.9 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/apps.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/processor.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/storage.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/types.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/finders.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > copying sass_processor/utils.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor > creating > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/jinja2 > copying sass_processor/jinja2/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/jinja2 > copying sass_processor/jinja2/ext.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/jinja2 > creating > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/management > copying sass_processor/management/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/management > creating > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/templatetags > copying sass_processor/templatetags/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/templatetags > copying sass_processor/templatetags/sass_tags.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/templatetags > creating > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/management/commands > copying sass_processor/management/commands/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/management/commands > copying sass_processor/management/commands/compilescss.py -> > /<>/.pybuild/cpython3_3.9_django-sass-processor/build/sass_processor/management/commands > I: pybuild base:239: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/__init__.py -> > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/apps.py -> > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/processor.py -> > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/storage.py -> > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/types.py -> > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/finders.py -> > /<>/.pybuild/cpython3_3.10_django-sass-processor/build/sass_processor > copying sass_processor/utils.py -> > /<>/.pybuild/cpython3_3.1
Bug#1017325: marked as done (theseus: FTBFS: DLTutils.c:427:11: error: pointer ‘outfile’ used after ‘fclose’ [-Werror=use-after-free])
Your message dated Tue, 16 Aug 2022 21:36:17 + with message-id and subject line Bug#1017325: fixed in theseus 3.3.0-12 has caused the Debian Bug report #1017325, regarding theseus: FTBFS: DLTutils.c:427:11: error: pointer ‘outfile’ used after ‘fclose’ [-Werror=use-after-free] 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.) -- 1017325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: theseus Version: 3.3.0-11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops > -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result > -Wformat-truncation=0 -pthread -c DLTutils.c > DLTutils.c: In function ‘linefix’: > DLTutils.c:427:11: error: pointer ‘outfile’ used after ‘fclose’ > [-Werror=use-after-free] > 427 | return(outfile); > | ^ > DLTutils.c:425:5: note: call to ‘fclose’ here > 425 | fclose(outfile); > | ^~~ > cc1: all warnings being treated as errors > make[3]: *** [Makefile:10: DLTutils.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/theseus_3.3.0-11_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking 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: theseus Source-Version: 3.3.0-12 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of theseus, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated theseus 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: Tue, 16 Aug 2022 22:25:07 +0200 Source: theseus Architecture: source Version: 3.3.0-12 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Pierre Gruet Closes: 1017325 Changes: theseus (3.3.0-12) unstable; urgency=medium . * Team upload * Removing unused linefix function, which returns a resource just after releasing it (Closes: #1017325) * Raising Standards version to 4.6.1 (no change) * Removing now useless debian/dirs file * Updating d/watch URI, which is now secure Checksums-Sha1: 948e530ad384bcbf1313eb0e4edce706836e5117 2040 theseus_3.3.0-12.dsc b3420dd226d38a99b39d64c8042697e5b48669e6 16432 theseus_3.3.0-12.debian.tar.xz dac63871521ef5498036ef28e312f2c7ad731485 5768 theseus_3.3.0-12_source.buildinfo Checksums-Sha256: 9bb4e229cb8420b6e4e185dfd74a8f238de91c32b62529770fd1753e970361db 2040 theseus_3.3.0-12.dsc d088919c55e76788aefc20fe8da4c85afae59297ae296ad114d6ddee436fc4d0 16432 theseus_3.3.0-12.debian.tar.xz 4037938cb934e698684ef5be9b91b7f59393b6c63dfcd912c7d21851e1a67f50 5768 theseus_3.3.0-12_source.buildinfo Files: d42935fe3e88fe6fca701f8a36eda38f 2040 science optional theseus_3.3.0-12.dsc e515add6112fd576b5a779d7933d8ccf 16432 science optional theseus_3.3.0-12.debian.tar.xz 33ebf1295b27aba9c25c0ffd73ab652a 5768 science optional theseus_3.3.0-12_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmL7/fkACgkQYAMWptwn dHYZ3Q/9Fec5OxjrHPoeFd
Bug#1017484: marked as done (murano: autopkgtest regression: 'weakref' != 'ReferenceType')
Your message dated Tue, 16 Aug 2022 23:26:26 +0200
with message-id
and subject line Re: Bug#1017484: murano: autopkgtest regression: 'weakref' !=
'ReferenceType'
has caused the Debian Bug report #1017484,
regarding murano: autopkgtest regression: 'weakref' != 'ReferenceType'
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.)
--
1017484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: murano
Version: 1:13.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of python3-defaults on all
architectures. However, it turns out that your test very recently
regressed in testing, it now fails everywhere [1].
Paul
[0] https://ci.debian.net/packages/m/murano/
https://ci.debian.net/data/autopkgtest/testing/amd64/m/murano/24841381/log.gz
==
FAIL: murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
File
"/tmp/autopkgtest-lxc.1r4f_mqi/downtmp/build.c02/src/murano/tests/unit/dsl/test_helpers.py",
line 268, in test_weak_ref
self.assertEqual('weakref',
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
393, in assertEqual
self.assertThat(observed, matcher, message)
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
480, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 'weakref' != 'ReferenceType'
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Same thing for this package: the failing test has been disabled in debian
release -2.On Aug 16, 2022 22:22, Paul Gevers wrote:
>
> Source: murano
> Version: 1:13.0.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
> I looked at the results of the autopkgtest of you package because it was
> showing up as a regression for the upload of python3-defaults on all
> architectures. However, it turns out that your test very recently
> regressed in testing, it now fails everywhere [1].
>
> Paul
>
> [0] https://ci.debian.net/packages/m/murano/
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/m/murano/24841381/log.gz
>
> ==
> FAIL: murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
> murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
> --
> testtools.testresult.real._StringException: Traceback (most recent call
> last):
> File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
> return func(*newargs, **newkeywargs)
> File
> "/tmp/autopkgtest-lxc.1r4f_mqi/downtmp/build.c02/src/murano/tests/unit/dsl/test_helpers.py",
>
> line 268, in test_weak_ref
> self.assertEqual('weakref',
> File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
> 393, in assertEqual
> self.assertThat(observed, matcher, message)
> File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
> 480, in assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 'weakref' != 'ReferenceType'
>
--- End Message ---
Bug#1017485: marked as done (nova: autopkgtest regression: testtools.matchers._impl.MismatchError)
Your message dated Tue, 16 Aug 2022 23:00:48 +0200
with message-id
and subject line Re: Bug#1017485: nova: autopkgtest regression:
testtools.matchers._impl.MismatchError
has caused the Debian Bug report #1017485,
regarding nova: autopkgtest regression: testtools.matchers._impl.MismatchError
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.)
--
1017485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nova
Version: 2:25.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of python3-defaults on all
architectures. However, it turns out that your test very recently
regressed in testing, it now fails everywhere [1].
Paul
[0] https://ci.debian.net/packages/n/nova/
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nova/24841382/log.gz
==
FAIL:
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect
--
testtools.testresult.real._StringException: pythonlogging:'': {{{
2022-08-15 16:18:58,613 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-convert-json-to-yaml`` tool to convert existing
JSON-formatted policy file to YAML-formatted in backward compatible way:
https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
2022-08-15 16:18:58,614 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-convert-json-to-yaml`` tool to convert existing
JSON-formatted policy file to YAML-formatted in backward compatible way:
https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
2022-08-15 16:18:58,615 WARNING [oslo_policy.policy] Policy Rules
['os_compute_api:extensions', 'os_compute_api:os-floating-ip-pools',
'os_compute_api:os-quota-sets:defaults',
'os_compute_api:os-availability-zone:list', 'os_compute_api:limits',
'project_admin_api', 'project_member_api', 'project_reader_api',
'project_reader_or_admin', 'os_compute_api:limits:other_project',
'os_compute_api:os-lock-server:unlock:unlock_override',
'os_compute_api:servers:create:zero_disk_flavor',
'compute:servers:resize:cross_cell'] specified in policy files are the
same as the defaults provided by the service. You can remove these rules
from policy files which will make maintenance easier. You can detect
these redundant rules by ``oslopolicy-list-redundant`` tool also.
2022-08-15 16:18:58,616 INFO [nova.console.websocketproxy] WebSocket
server settings:
2022-08-15 16:18:58,617 INFO [nova.console.websocketproxy] - Listen on
:None
2022-08-15 16:18:58,617 INFO [nova.console.websocketproxy] - SSL/TLS
support
}}}
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.suspzscb/downtmp/build.Je5/src/nova/tests/unit/console/test_websocketproxy.py",
line 622, in test_reject_open_redirect
self.assertIn('400 URI must not start with //', result[0].decode())
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
399, in assertIn
self.assertThat(haystack, Contains(needle), message)
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
480, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: '400 URI must not start with //'
not in 'HTTP/1.1 301 Moved Permanently\r\n'
==
FAIL:
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect_3_slashes
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect_3_slashes
--
testtools.testresult.real._StringException: pythonlogging:'': {{{
2022-08-15 16:18:58,734 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-conve
Processed: bug 1015715 is forwarded to https://github.com/haampie/libtree/issues/78
Processing commands for cont...@bugs.debian.org: > forwarded 1015715 https://github.com/haampie/libtree/issues/78 Bug #1015715 [src:libtree] src:libtree: fails to migrate to testing for too long: FTBFS on most architectures Set Bug forwarded-to-address to 'https://github.com/haampie/libtree/issues/78'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017191: marked as done (murano: FTBFS: AttributeError: 'NoneType' object has no attribute 'object_store')
Your message dated Tue, 16 Aug 2022 20:47:07 +
with message-id
and subject line Bug#1017191: fixed in murano 1:13.0.0-2
has caused the Debian Bug report #1017191,
regarding murano: FTBFS: AttributeError: 'NoneType' object has no attribute
'object_store'
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.)
--
1017191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: murano
Version: 1:13.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ==
> FAIL: murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
> murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
> File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
> return func(*newargs, **newkeywargs)
> File "/<>/murano/tests/unit/dsl/test_helpers.py", line 268, in
> test_weak_ref
> self.assertEqual('weakref',
> File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 393, in
> assertEqual
> self.assertThat(observed, matcher, message)
> File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 480, in
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 'weakref' != 'ReferenceType'
>
>
> --
> Ran 1022 tests in 36.514s
>
> FAILED (failures=1, skipped=10)
> + echo ==> STESTR TEST SUITE FAILED FOR python3.10: displaying pip3
> freeze output...
> ==> STESTR TEST SUITE FAILED FOR python3.10: displaying pip3 freeze
> output...
> + [ -x /usr/bin/pip3 ]
> + pip3 freeze
> alabaster==0.7.12
> alembic==1.7.6.dev0
> amqp==5.1.0
> anyjson==0.3.3
> appdirs==1.4.4
> attrs==22.1.0
> autopage==0.4.0
> Babel==2.8.0
> bcrypt==3.2.0
> blinker==1.4
> cachetools==5.0.0
> castellan==3.10.2
> certifi==2020.6.20
> chardet==4.0.0
> charset-normalizer==2.0.6
> cliff==3.10.1
> cmd2==0.0.0
> colorama==0.4.5
> confluent-kafka==1.7.0
> coverage==6.2
> cryptography==3.4.8
> ddt==1.4.4
> debtcollector==2.5.0
> decorator==5.1.1
> deprecation==2.0.7
> dnspython==2.2.1
> docutils==0.17.1
> dogpile.cache==1.1.5
> dulwich==0.20.44
> eventlet==0.30.2
> extras==1.0.0
> fasteners==0.17.3
> fixtures==3.0.0
> flake8==4.0.1
> future==0.18.2
> futurist==2.4.0
> gabbi==2.4.0
> gevent==21.8.0
> greenlet==1.1.2
> hacking==4.1.0
> httplib2==0.20.4
> idna==3.3
> imagesize==1.4.1
> importlib-metadata==4.6.4
> iniconfig==1.1.1
> iso8601==1.0.2
> jeepney==0.8.0
> Jinja2==3.0.3
> jmespath==1.0.1
> jsonpatch==1.32
> jsonpath-rw==1.4.0
> jsonpath-rw-ext==1.2.2
> jsonpointer==2.2
> jsonschema==4.6.0
> keyring==23.8.2
> keystoneauth1==4.5.0
> keystonemiddleware==9.4.0
> kombu==5.2.4
> lxml==4.9.1
> Mako==1.1.3
> MarkupSafe==2.0.1
> mccabe==0.6.1
> monotonic==1.6
> more-itertools==8.10.0
> msgpack==1.0.3
> munch==2.5.0
> murano==13.0.0
> murano-pkg-check==0.3.0
> mysqlclient==1.4.6
> netaddr==0.8.0
> netifaces==0.11.0
> nose==1.3.7
> oauthlib==3.2.0
> openstackdocstheme==1.20.0
> openstacksdk==0.61.0
> os-api-ref==2.1.0
> os-client-config==2.1.0
> os-service-types==1.7.0
> os-testr==2.0.1
> osc-lib==2.5.0
> oslo.cache==2.10.1
> oslo.concurrency==4.5.0
> oslo.config==8.8.0
> oslo.context==4.1.0
> oslo.db==11.2.0
> oslo.i18n==5.1.0
> oslo.log==4.7.0
> oslo.messaging==12.13.0
> oslo.metrics==0.4.0
> oslo.middleware==4.5.1
> oslo.policy==3.11.0
> oslo.serialization==4.3.0
> oslo.service==2.8.0
> oslo.upgradecheck==1.5.0
> oslo.utils==4.12.3
> oslosphinx==4.18.0
> oslotest==4.5.0
> packaging==21.3
> paramiko==2.10.4
> Paste==3.5.0
> PasteDeploy==2.1.1
> pbr==5.8.1
> pep8==1.7.1
> pluggy==1.0.0+repack
> ply==3.11
> prettytable==2.5.0
> prometheus-client==0.9.0
> psutil==5.9.0
> psycopg2==2.9.3
> py==1.10.0
> pycadf==3.1.1
> pycodestyle==2.8.0
> pyflakes==2.4.0
> Pygments==2.12.0
> pyinotify==0.9.6
> PyJWT==2.4.0
> PyMySQL==1.0.2
> PyNaCl==1.5.0
> pyOpenSSL==21.0.0
> pyparsing==3.0.7
> pyperclip==1.8.2
> pyrsistent==0.18.1
> pytest==7.1.2
> python-barbicanclient==5.3.0
> python-binary-memcached==0.31.1
> python-dateutil==2.8.1
> python-glanceclient==3.6.0
> python-heatclient==2.5.1
> python-keystoneclient==4.4.0
> python-memcached==1.58
> python-mist
Bug#1017485: nova: autopkgtest regression: testtools.matchers._impl.MismatchError
Source: nova
Version: 2:25.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of python3-defaults on all
architectures. However, it turns out that your test very recently
regressed in testing, it now fails everywhere [1].
Paul
[0] https://ci.debian.net/packages/n/nova/
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nova/24841382/log.gz
==
FAIL:
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect
--
testtools.testresult.real._StringException: pythonlogging:'': {{{
2022-08-15 16:18:58,613 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-convert-json-to-yaml`` tool to convert existing
JSON-formatted policy file to YAML-formatted in backward compatible way:
https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
2022-08-15 16:18:58,614 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-convert-json-to-yaml`` tool to convert existing
JSON-formatted policy file to YAML-formatted in backward compatible way:
https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
2022-08-15 16:18:58,615 WARNING [oslo_policy.policy] Policy Rules
['os_compute_api:extensions', 'os_compute_api:os-floating-ip-pools',
'os_compute_api:os-quota-sets:defaults',
'os_compute_api:os-availability-zone:list', 'os_compute_api:limits',
'project_admin_api', 'project_member_api', 'project_reader_api',
'project_reader_or_admin', 'os_compute_api:limits:other_project',
'os_compute_api:os-lock-server:unlock:unlock_override',
'os_compute_api:servers:create:zero_disk_flavor',
'compute:servers:resize:cross_cell'] specified in policy files are the
same as the defaults provided by the service. You can remove these rules
from policy files which will make maintenance easier. You can detect
these redundant rules by ``oslopolicy-list-redundant`` tool also.
2022-08-15 16:18:58,616 INFO [nova.console.websocketproxy] WebSocket
server settings:
2022-08-15 16:18:58,617 INFO [nova.console.websocketproxy] - Listen on
:None
2022-08-15 16:18:58,617 INFO [nova.console.websocketproxy] - SSL/TLS
support
}}}
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.suspzscb/downtmp/build.Je5/src/nova/tests/unit/console/test_websocketproxy.py",
line 622, in test_reject_open_redirect
self.assertIn('400 URI must not start with //', result[0].decode())
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
399, in assertIn
self.assertThat(haystack, Contains(needle), message)
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
480, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: '400 URI must not start with //'
not in 'HTTP/1.1 301 Moved Permanently\r\n'
==
FAIL:
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect_3_slashes
nova.tests.unit.console.test_websocketproxy.NovaProxyRequestHandlerTestCase.test_reject_open_redirect_3_slashes
--
testtools.testresult.real._StringException: pythonlogging:'': {{{
2022-08-15 16:18:58,734 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-convert-json-to-yaml`` tool to convert existing
JSON-formatted policy file to YAML-formatted in backward compatible way:
https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
2022-08-15 16:18:58,735 WARNING [oslo_policy.policy] JSON formatted
policy_file support is deprecated since Victoria release. You need to
use YAML format which will be default in future. You can use
``oslopolicy-convert-json-to-yaml`` tool to convert existing
JSON-formatted policy file to YAML-formatted in backward compatible way:
https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
2022-08-15 16:18:58,736 WARNING [oslo_policy.policy] Policy Rules
['os_compute_api:extensions', 'os_compute_api:os-floating-ip-pools',
'os_compute_api:os-quota-sets:defaults',
'os_compute_api:os-availability-zone:list', 'os_compute_api:limits',
'proj
Bug#1017484: murano: autopkgtest regression: 'weakref' != 'ReferenceType'
Source: murano
Version: 1:13.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of python3-defaults on all
architectures. However, it turns out that your test very recently
regressed in testing, it now fails everywhere [1].
Paul
[0] https://ci.debian.net/packages/m/murano/
https://ci.debian.net/data/autopkgtest/testing/amd64/m/murano/24841381/log.gz
==
FAIL: murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
murano.tests.unit.dsl.test_helpers.TestDSLHelpers.test_weak_ref
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
File
"/tmp/autopkgtest-lxc.1r4f_mqi/downtmp/build.c02/src/murano/tests/unit/dsl/test_helpers.py",
line 268, in test_weak_ref
self.assertEqual('weakref',
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
393, in assertEqual
self.assertThat(observed, matcher, message)
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line
480, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 'weakref' != 'ReferenceType'
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1017483: loguru: autopkgtest regression: RecursionError: maximum recursion depth exceeded
Source: loguru Version: 0.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up as a regression for the upload of python3-defaults on all architectures. However, it turns out that your test very recently regressed in testing, it now fails everywhere [1]. Paul [0] https://ci.debian.net/packages/l/loguru/ https://ci.debian.net/data/autopkgtest/testing/amd64/l/loguru/24840388/log.gz === FAILURES === __ test_function_without_name __ monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7fe61feb48b0> > ??? tests/test_repr.py:119: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/loguru/_logger.py:792: in add elif iscoroutinefunction(sink) or iscoroutinefunction(getattr(sink, "__call__", None)): /usr/lib/python3.10/inspect.py:313: in iscoroutinefunction return _has_code_flag(obj, CO_COROUTINE) /usr/lib/python3.10/inspect.py:297: in _has_code_flag if not (isfunction(f) or _signature_is_functionlike(f)): /usr/lib/python3.10/inspect.py:2009: in _signature_is_functionlike if not callable(obj) or isclass(obj): tests/test_repr.py:117: in monkeypatch.setattr(builtins, "callable", lambda x: x is function or callable(x)) tests/test_repr.py:117: in monkeypatch.setattr(builtins, "callable", lambda x: x is function or callable(x)) E RecursionError: maximum recursion depth exceeded !!! Recursion detected (same locals & position) test_function_with_empty_name _ monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7fe61f87ba60> def test_function_with_empty_name(monkeypatch): function = Wrapper(lambda _: None, repr="", name="") monkeypatch.setattr(builtins, "callable", lambda x: x is function or callable(x)) > logger.add(function) tests/test_repr.py:128: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/loguru/_logger.py:792: in add elif iscoroutinefunction(sink) or iscoroutinefunction(getattr(sink, "__call__", None)): /usr/lib/python3.10/inspect.py:313: in iscoroutinefunction return _has_code_flag(obj, CO_COROUTINE) /usr/lib/python3.10/inspect.py:297: in _has_code_flag if not (isfunction(f) or _signature_is_functionlike(f)): /usr/lib/python3.10/inspect.py:2009: in _signature_is_functionlike if not callable(obj) or isclass(obj): tests/test_repr.py:126: in monkeypatch.setattr(builtins, "callable", lambda x: x is function or callable(x)) tests/test_repr.py:126: in monkeypatch.setattr(builtins, "callable", lambda x: x is function or callable(x)) E RecursionError: maximum recursion depth exceeded !!! Recursion detected (same locals & position) OpenPGP_signature Description: OpenPGP digital signature
Processed: numerical transition blocked by pmix
Processing commands for cont...@bugs.debian.org: > block 1016084 by 1017356 Bug #1016084 [release.debian.org] transition: petsc 1016084 was not blocked by any bugs. 1016084 was not blocking any bugs. Added blocking bug(s) of 1016084: 1017356 > thanks Stopping processing here. Please contact me if you need assistance. -- 1016084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017214: marked as done (git-annex: FTBFS: unsatisfiable build-dependencies)
Your message dated Tue, 16 Aug 2022 15:37:13 -0400 (EDT) with message-id and subject line Fixed by new release of criterion has caused the Debian Bug report #1017214, regarding git-annex: FTBFS: unsatisfiable build-dependencies 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.) -- 1017214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-annex Version: 10.20220504-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), ghc (>= 8.4.3), cabal-install, > libghc-mtl-dev (>= 2.1.1), libghc-split-dev, libghc-data-default-dev, > libghc-hslogger-dev, libghc-pcre-light-dev, libghc-cryptonite-dev (>= 0.23), > libghc-memory-dev, libghc-deepseq-dev, libghc-attoparsec-dev, > libghc-sandi-dev, libghc-utf8-string-dev, libghc-aws-dev (>= 0.20), > libghc-conduit-dev, libghc-resourcet-dev, libghc-quickcheck2-dev (>= 2.10.0), > libghc-monad-control-dev (>= 0.3), libghc-transformers-dev, > libghc-exceptions-dev (>= 0.6), libghc-unix-compat-dev, libghc-dlist-dev, > libghc-uuid-dev, libghc-aeson-dev, libghc-tagsoup-dev, > libghc-unordered-containers-dev, libghc-ifelse-dev, libghc-bloomfilter-dev > (>= 2.0.0), libghc-edit-distance-dev, libghc-hinotify-dev (>= 0.3.10), > libghc-dbus-dev (>= 0.10.7), libghc-fdo-notify-dev (>= 0.3), libghc-yesod-dev > (>= 1.2.6.1), libghc-yesod-core-dev (>= 1.6.0), libghc-yesod-form-dev (>= > 1.3.15), libghc-yesod-static-dev (>= 1.2.4), libghc-shakespeare-dev (>= > 2.0.0), libghc-clientsession-dev, libghc-warp-dev (>= 3.0.0.5), > libghc-warp-tls-dev, libghc-wai-dev, libghc-wai-extra-dev, libghc-dav-dev (>= > 1.0), libghc-persistent-dev (>= 2.8.1), libghc-persistent-template-dev, > libghc-persistent-sqlite-dev (>= 2.8.1), libghc-microlens-dev, > libghc-securemem-dev, libghc-byteable-dev, libghc-stm-chans-dev, > libghc-case-insensitive-dev, libghc-http-types-dev, libghc-http-conduit-dev, > libghc-http-client-restricted-dev, libghc-blaze-builder-dev, > libghc-crypto-api-dev, libghc-network-multicast-dev, libghc-network-info-dev, > libghc-safesemaphore-dev, libghc-async-dev, libghc-monad-logger-dev, > libghc-free-dev, libghc-feed-dev (>= 1.0.0), libghc-regex-tdfa-dev, > libghc-tasty-dev (>= 0.7), libghc-tasty-hunit-dev, > libghc-tasty-quickcheck-dev, libghc-tasty-rerun-dev, libghc-cabal-dev, > libghc-ansi-terminal-dev, libghc-optparse-applicative-dev (>= 0.11.0), > libghc-torrent-dev, libghc-concurrent-output-dev (>= 1.10), > libghc-disk-free-space-dev, libghc-mountpoints-dev, libghc-magic-dev, > libghc-socks-dev, libghc-vector-dev, libghc-unliftio-core-dev, > libghc-filepath-bytestring-dev, libghc-git-lfs-dev, libghc-criterion-dev, > lsof, ikiwiki, libimage-magick-perl, git (>= 1:2.22), rsync, curl, > openssh-client, git-remote-gcrypt (>= 0.20130908-6), gnupg, gpg-agent, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), ghc (>= 8.4.3), > cabal-install, libghc-mtl-dev (>= 2.1.1), libghc-split-dev, > libghc-data-default-dev, libghc-hslogger-dev, libghc-pcre-light-dev, > libghc-cryptonite-dev (>= 0.23), libghc-memory-dev, libghc-deepseq-dev, > libghc-attoparsec-dev, libghc-sandi-dev, libghc-utf8-string-dev, > libghc-aws-dev (>= 0.20), libghc-conduit-dev, libghc-resourcet-dev, > libghc-quickcheck2-dev (>= 2.10.0), libghc-monad-control-dev (>= 0.3), > libghc-transformers-dev, libghc-exceptions-dev (>= 0.6), > libghc-unix-compat-dev, libghc-dlist-dev, libghc-uuid-dev, libghc-aeson-dev, > libghc-tagsoup-dev, libghc-unordered-containers-dev, libghc-ifelse-dev, > libghc-bloomfilter-dev (>= 2.0.0), libghc-edit-distance-dev, > libghc-hinotify-dev (>= 0.3.10), libghc-dbus-dev (>= 0.10.7), > libghc-fdo-notify-dev (>= 0.3), libghc-yesod-dev (>= 1.2.6.1), > libghc-yesod-core-dev (>= 1.6.0), libghc-yesod-form-dev (>= 1.3.15), > libghc-yesod-static-dev (>= 1.2.4), libghc-shakespeare-dev (>= 2.0.0), > libghc-clientsession-dev, libghc-warp-dev (>= 3.0.0.5), libghc-warp-tls-dev, > libghc-wai-dev, libghc-wai-extra-dev, libghc-dav-dev
Processed: found 1016139 in 5.9+dfsg-3
Processing commands for cont...@bugs.debian.org:
> found 1016139 5.9+dfsg-3
Bug #1016139 {Done: Craig Small } [src:net-snmp] net-snmp:
CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806
CVE-2022-24805
Marked as found in versions net-snmp/5.9+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017441: debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles
Control: severity -1 wishlist On Tue, 2022-08-16 at 18:46 +0200, Adam Borowski wrote: > On Tue, Aug 16, 2022 at 03:13:35PM +0100, Luca Boccassi wrote: > > On Tue, 16 Aug 2022 13:13:53 +0200 Johannes Schauer Marin Rodrigues > > > The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the > > > dependency on "systemd | systemd-tmpfiles" and was compiled with > > > debhelper 13.6. > > > > > > This currently installs systemd on a systems that don't need it, > > which > > > is especially bad for minimal and embedded systems and/or containers. > > > Thus setting the severity to serious. Feel free to adjust. > > > This looks entirely correct to me. You can install the -standalone > > variant if you prefer a slightly smaller footprint, which is provided > > exactly for those non-default use cases. > > No, the "passwd" package does not need systemd (nor its -standalone subset > as evidenced by currently working fine). And the added dependency has > the tiny little effect of effectively dropping three official architectures > plus a number of unofficial but known to be worked on. > > Breaking machines that fail to boot with systemd, or are configured in a way > that doesn't work with it is also not nice. And minimal/embedded systems > really don't want the extra 460KB -standalone binary, either. > > > The regression here is commit 0e313c2f58df0f8ce6389380d735767dfaa936ab; > I've read changelogs of all packages that have since gained this automatic > dependency¹, and it appears none have a mention of relying on tmpfiles > on !systemd, with one exception -- tomcat9 -- which manually depends on > systemd-tmpfiles thus doesn't need the debhelper change. > > The stated reason for the change, roundcube (#1013969) hasn't been uploaded > yet thus it still works fine via cron. If the maintainer wants to migrate > to systemd ways, he can add the dependency on systemd-tmpfiles by hand, > just like tomcat9 does. That'd be a regression but oh well. > > > Thus, it doesn't appear like a revert would have any downsides - yes, the passwd package does need 'systemd | systemd-tmpfiles' as it ships a tmpfile, thus the dependency is entirely correct - no official architecture is dropped, both packages are available on all official release architecture plus a number of ports - as tmpfiles.d is ufficially supported, it is up to the 3 !linux unofficial ports to provide an alternative implementation if so they will, or to get src:systemd to build minimally there. With recent changes I've done to the Meson usage, it might even be quite simple to achieve, and might only require a couple of lines in d/rules of src:systemd that, if someone provided a MR for, I might be happy to include and maintain - for the millionth time, installing the systemd (or systemd-tmpfiles) package does not make a machine boot with systemd, that is done by the systemd-sysv package which is different and separate, and you know this perfectly well, so please kindly stop spreading this blatantly untrue piece of information Thus, this is a wishlist at best and most likely a close+wontfix like the half a dozen of identical ones that preceded it. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1017441: debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles
Processing control commands: > severity -1 wishlist Bug #1017441 [debhelper] debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles Severity set to 'wishlist' from 'serious' -- 1017441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): Re: Bug#1017467: Acknowledgement (libpam-systemd: upgrade broke unix_chkpwd fallback for root user)
Processing control commands: > reassign -1 pam 1.4.0-13 Bug #1017467 [libpam-systemd] libpam-systemd: upgrade broke unix_chkpwd fallback for root user Bug reassigned from package 'libpam-systemd' to 'pam'. No longer marked as found in versions systemd/251.4-1. Ignoring request to alter fixed versions of bug #1017467 to the same values previously set Bug #1017467 [pam] libpam-systemd: upgrade broke unix_chkpwd fallback for root user There is no source info for the package 'pam' at version '1.4.0-13' with architecture '' Unable to make a source version for version '1.4.0-13' Marked as found in versions 1.4.0-13. > user selinux-de...@lists.alioth.debian.org Unknown command or malformed arguments to command. > usertags selinux Unknown command or malformed arguments to command. -- 1017467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017441: marked as done (debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles)
On Tue, 2022-08-16 at 19:14 +0200, Adam Borowski wrote: > Control: reopen -1 > > On Tue, Aug 16, 2022 at 05:09:03PM +, Debian Bug Tracking System wrote: > > Your message dated Tue, 16 Aug 2022 19:06:12 +0200 > > with message-id <429a5094-bef5-3b75-bfce-684319dfa...@debian.org> > > and subject line Re: Bug#1017441: debhelper: building src:shadow wrongly > > makes passwd depend on systemd | systemd-tmpfiles > > has caused the Debian Bug report #1017441, > > regarding debhelper: building src:shadow wrongly makes passwd depend on > > systemd | systemd-tmpfiles > > to be marked as done. > > > From: Michael Biebl > > Am 16.08.22 um 16:13 schrieb Luca Boccassi: > > > This looks entirely correct to me. You can install the -standalone > > > variant if you prefer a slightly smaller footprint, which is provided > > > exactly for those non-default use cases. > > > > > > > Indeed, the passwd package installs a tmpfiles config and the generated > > maintainer scripts do call systemd-tmpfiles, so the generated dependency is > > correct. > > The standalone binaries, as mentioned can be used for more minimal > > environments, when a smaller disk footprint is desired. That said, > > installing the systemd package inside a container is totally fine as well. > > > > Anyway, nothing to fix here, thus closing. > > Please go away. Your autoclosure of bugs regardless of severity is not > helpful, and you keep trolling even severity:critical ones for years. Messages like this are completely out of line. Please stop and re- evaluate on a public mailing list. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1017441: marked as done (debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles)
Processing control commands:
> reopen -1
Bug #1017441 {Done: Michael Biebl } [debhelper] debhelper:
building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles
Bug reopened
Ignoring request to alter fixed versions of bug #1017441 to the same values
previously set
--
1017441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017441: marked as done (debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles)
Control: reopen -1 On Tue, Aug 16, 2022 at 05:09:03PM +, Debian Bug Tracking System wrote: > Your message dated Tue, 16 Aug 2022 19:06:12 +0200 > with message-id <429a5094-bef5-3b75-bfce-684319dfa...@debian.org> > and subject line Re: Bug#1017441: debhelper: building src:shadow wrongly > makes passwd depend on systemd | systemd-tmpfiles > has caused the Debian Bug report #1017441, > regarding debhelper: building src:shadow wrongly makes passwd depend on > systemd | systemd-tmpfiles > to be marked as done. > From: Michael Biebl > Am 16.08.22 um 16:13 schrieb Luca Boccassi: > > This looks entirely correct to me. You can install the -standalone > > variant if you prefer a slightly smaller footprint, which is provided > > exactly for those non-default use cases. > > > > Indeed, the passwd package installs a tmpfiles config and the generated > maintainer scripts do call systemd-tmpfiles, so the generated dependency is > correct. > The standalone binaries, as mentioned can be used for more minimal > environments, when a smaller disk footprint is desired. That said, > installing the systemd package inside a container is totally fine as well. > > Anyway, nothing to fix here, thus closing. Please go away. Your autoclosure of bugs regardless of severity is not helpful, and you keep trolling even severity:critical ones for years. Meow. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ You're alive. But that's just a phase. ⠈⠳⣄
Bug#1017441: marked as done (debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles)
Your message dated Tue, 16 Aug 2022 19:06:12 +0200 with message-id <429a5094-bef5-3b75-bfce-684319dfa...@debian.org> and subject line Re: Bug#1017441: debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles has caused the Debian Bug report #1017441, regarding debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles 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.) -- 1017441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debhelper Version: 13.9 Severity: serious X-Debbugs-Cc: jo...@debian.org Steps to reproduce: $ sbuild -d unstable shadow [...] [...] [...] passwd_4.11.1+dfsg1-2_amd64.deb --- new Debian package, version 2.0. size 944912 bytes: control archive=7432 bytes. 111 bytes, 6 lines conffiles 740 bytes,17 lines control██ 18406 bytes, 275 lines md5sums██ 1090 bytes,40 lines * postinst #!/bin/sh 172 bytes, 5 lines * postrm #!/bin/sh 172 bytes, 5 lines * preinst #!/bin/sh 172 bytes, 5 lines * prerm#!/bin/sh Package: passwd Source: shadow Version: 1:4.11.1+dfsg1-2 Architecture: amd64 Maintainer: Shadow package maintainers Installed-Size: 2761 Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.34), libcrypt1 (>= 1:4.1.0), libpam0g (>= 0.99.7.1), libselinux1 (>= 3.1~), libsemanage2 (>= 2.0.3), systemd | systemd-tmpfiles, libpam-modules The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the dependency on "systemd | systemd-tmpfiles" and was compiled with debhelper 13.6. This currently installs systemd on a systems that don't need it, which is especially bad for minimal and embedded systems and/or containers. Thus setting the severity to serious. Feel free to adjust. Thanks! cheers, josch --- End Message --- --- Begin Message --- Am 16.08.22 um 16:13 schrieb Luca Boccassi: On Tue, 16 Aug 2022 13:13:53 +0200 Johannes Schauer Marin Rodrigues wrote: Package: debhelper Version: 13.9 Severity: serious X-Debbugs-Cc: jo...@debian.org Steps to reproduce: $ sbuild -d unstable shadow [...] [...] [...] passwd_4.11.1+dfsg1-2_amd64.deb --- new Debian package, version 2.0. size 944912 bytes: control archive=7432 bytes. 111 bytes, 6 lines conffiles 740 bytes, 17 lines control██ 18406 bytes, 275 lines md5sums██ 1090 bytes, 40 lines * postinst #!/bin/sh 172 bytes, 5 lines * postrm #!/bin/sh 172 bytes, 5 lines * preinst #!/bin/sh 172 bytes, 5 lines * prerm #!/bin/sh Package: passwd Source: shadow Version: 1:4.11.1+dfsg1-2 Architecture: amd64 Maintainer: Shadow package maintainers Installed-Size: 2761 Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.34), libcrypt1 (>= 1:4.1.0), libpam0g (>= 0.99.7.1), libselinux1 (>= 3.1~), libsemanage2 (>= 2.0.3), systemd | systemd- tmpfiles, libpam-modules The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the dependency on "systemd | systemd-tmpfiles" and was compiled with debhelper 13.6. This currently installs systemd on a systems that don't need it, which is especially bad for minimal and embedded systems and/or containers. Thus setting the severity to serious. Feel free to adjust. Thanks! cheers, josch This looks entirely correct to me. You can install the -standalone variant if you prefer a slightly smaller footprint, which is provided exactly for those non-default use cases. Indeed, the passwd package installs a tmpfiles config and the generated maintainer scripts do call systemd-tmpfiles, so the generated dependency is correct. The standalone binaries, as mentioned can be used for more minimal environments, when a smaller disk footprint is desired. That said, installing the systemd package inside a container is totally fine as well. Anyway, nothing to fix here, thus closing. Michael OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Processed:
Processing control commands: > tags -1 wontfix Bug #1009308 [libopenexr-dev] libopenexr-dev: Missing Breaks/Replaces libilmbase-dev Added tag(s) wontfix. > tags -1 - patch Bug #1009308 [libopenexr-dev] libopenexr-dev: Missing Breaks/Replaces libilmbase-dev Ignoring request to alter tags of bug #1009308 to the same tags previously set > severity -1 normal Bug #1009308 [libopenexr-dev] libopenexr-dev: Missing Breaks/Replaces libilmbase-dev Severity set to 'normal' from 'serious' -- 1009308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009308:
Control: tags -1 wontfix Control: tags -1 - patch Control: severity -1 normal I am not sure I can integrate your patch since libimath-dev does Provide: libilmbase-dev. Also: % sudo apt install libimath-dev [...] The following packages will be REMOVED: libilmbase-dev The following NEW packages will be installed: libimath-dev 0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 117 kB of archives. After this operation, 342 kB of additional disk space will be used. I suspect there is something else going on wrong on your end. I am tempted to just close.
Bug#1017441: debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles
On Tue, Aug 16, 2022 at 03:13:35PM +0100, Luca Boccassi wrote: > On Tue, 16 Aug 2022 13:13:53 +0200 Johannes Schauer Marin Rodrigues > > The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the > > dependency on "systemd | systemd-tmpfiles" and was compiled with > > debhelper 13.6. > > > > This currently installs systemd on a systems that don't need it, > which > > is especially bad for minimal and embedded systems and/or containers. > > Thus setting the severity to serious. Feel free to adjust. > This looks entirely correct to me. You can install the -standalone > variant if you prefer a slightly smaller footprint, which is provided > exactly for those non-default use cases. No, the "passwd" package does not need systemd (nor its -standalone subset as evidenced by currently working fine). And the added dependency has the tiny little effect of effectively dropping three official architectures plus a number of unofficial but known to be worked on. Breaking machines that fail to boot with systemd, or are configured in a way that doesn't work with it is also not nice. And minimal/embedded systems really don't want the extra 460KB -standalone binary, either. The regression here is commit 0e313c2f58df0f8ce6389380d735767dfaa936ab; I've read changelogs of all packages that have since gained this automatic dependency¹, and it appears none have a mention of relying on tmpfiles on !systemd, with one exception -- tomcat9 -- which manually depends on systemd-tmpfiles thus doesn't need the debhelper change. The stated reason for the change, roundcube (#1013969) hasn't been uploaded yet thus it still works fine via cron. If the maintainer wants to migrate to systemd ways, he can add the dependency on systemd-tmpfiles by hand, just like tomcat9 does. That'd be a regression but oh well. Thus, it doesn't appear like a revert would have any downsides. Meow! [¹]. grep-aptavail -F Depends systemd-tmpfiles -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Collisions shmolisions, let's see them find a collision or second ⢿⡄⠘⠷⠚⠋⠀ preimage for double rot13! ⠈⠳⣄
Bug#1017428: src:libnanomsg-raw-perl: fails to migrate to testing for too long: FTBFS on s390x
On Tue, 16 Aug 2022 08:07:36 +0200, Paul Gevers wrote: > Your package src:libnanomsg-raw-perl has been trying to migrate for 61 > days [2]. Hence, I am filing this bug. Your package failed to build from > [2] https://qa.debian.org/excuses.php?package=libnanomsg-raw-perl Test failure: # Failed test at t/timeo.t line 30. # '0.125154' # <= # '0.12' # Failed test at t/timeo.t line 41. # '0.221393' # <= # '0.12' # Looks like you failed 2 tests of 12. t/timeo.t . ok 1 ok 2 ok 3 ok 4 ok 5 not ok 6 ok 7 ok 8 ok 9 ok 10 not ok 11 ok 12 1..12 Dubious, test returned 2 (wstat 512, 0x200) Failed 2/12 subtests t/timeo.t has a hardcoded timeout of 0.12, which seems a bit arbitrary to me. Going through the upstream git history is fun. The value started at 0.1010, then to 0.102. then to 0.11, and finally to 0.12, the second and the third increase mentioning "slow machines" in the commit messages. I guess we can either bump the value (to what?) or skip the test … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#979504: Debian libtext-string-hexconvert-perl package
Hi Cyril! Today I noticed that your package libtext-string-hexconvert-perl is no longer part of the stable or testing Debian distribution, because there exists an RC bug https://bugs.debian.org/979504, which states that your mail address is not valid. Since I need this package in my job, it hurt's me that it is no longer available in Debian. I'd like to step in take over the package maintenance (if possible under the perl team umbrella) or help as a co-maintainer. As far as I can see, the package needs some love and upgrading, there's an upstream update 0.02 existing for 6 years now and the Debian part also needs some polishing. Please tell me, whether it's okay for you if (and how) I can support you with the package maintenance. Greetings Roland signature.asc Description: PGP signature
Bug#1017471: greenbone-security-assistant connects to the internet during build
Source: greenbone-security-assistant Version: 21.4.4-1 Severity: serious Tags: ftbfs Justification: FTBFS greenbone-security-assistant launches yarnpkg install during build. Then it needs network to download its dependencies. Without network: make[1]: Entering directory '/<>' dh debian/rules dh_auto_build yarnpkg yarn install v1.22.19 warning You don't appear to have an internet connection. Try the --offline flag to use the cache for registry queries. [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... error An unexpected error occurred: "https://registry.yarnpkg.com/styled-components/-/styled-components-5.2.1.tgz: https://registry.yarnpkg.com/reactstrap/-/reactstrap-8.9.0.tgz: https://registry.yarnpkg.com/bootstrap/-/bootstrap-4.6.0.tgz: getaddrinfo EAI_AGAIN registry.yarnpkg.com". info If you think this is a bug, please open a bug report with the information provided in "/<>/yarn-error.log". info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: build] Error 2
Processed: Re: Bug#1012021: unreproducible here
Processing control commands: > tags -1 + moreinfo Bug #1012021 [webpack] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Added tag(s) moreinfo. -- 1012021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012021: unreproducible here
Control: tags -1 + moreinfo Hi, I don't understand why this bug has been assigned to webpack: * many packages use webpack without having any issue * problem happens during package download, what is the link to webpack? > yarn install v1.22.19 > [1/5] Validating package.json... > [2/5] Resolving packages... > [3/5] Fetching packages... (a yarnpkg install during build? Looks to be a bad idea) * react-scripts uses an old webpack (both installed by yarnpkg and launched by yarnpkg build), not Debian's webpack. This old webpack is broken with nodejs 18 (md4), not Debian's one. NB: greenbone-security-assistant requires an old react-scripts, that's why it uses an old webpack NB: react-scripts isn't packaged (and not easy to do) Cheers, Yadd
Bug#1016508: marked as done (rapiddisk,rapiddisk-dkms: both ship /usr/src/rapiddisk-8.2.0-2/*)
Your message dated Tue, 16 Aug 2022 15:24:11 + with message-id and subject line Bug#1016508: fixed in rapiddisk 8.2.0-3 has caused the Debian Bug report #1016508, regarding rapiddisk,rapiddisk-dkms: both ship /usr/src/rapiddisk-8.2.0-2/* 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.) -- 1016508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rapiddisk,rapiddisk-dkms Version: 8.2.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package rapiddisk-dkms. Preparing to unpack .../rapiddisk-dkms_8.2.0-2_all.deb ... Unpacking rapiddisk-dkms (8.2.0-2) ... dpkg: error processing archive /var/cache/apt/archives/rapiddisk-dkms_8.2.0-2_all.deb (--unpack): trying to overwrite '/usr/src/rapiddisk-8.2.0-2/Makefile', which is also in package rapiddisk 8.2.0-2 Errors were encountered while processing: /var/cache/apt/archives/rapiddisk-dkms_8.2.0-2_all.deb BTW, you should only use the upstream version without Debian revision for the path in /usr/src, i.e. /usr/src/rapiddisk-8.2.0/ cheers, Andreas rapiddisk=8.2.0-2_rapiddisk-dkms=8.2.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: rapiddisk Source-Version: 8.2.0-3 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of rapiddisk, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated rapiddisk 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: Tue, 16 Aug 2022 15:16:45 +0200 Source: rapiddisk Architecture: source Version: 8.2.0-3 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Closes: 1016508 Changes: rapiddisk (8.2.0-3) unstable; urgency=medium . * Stop double shipping of same files, only use upstream version. (Closes: #1016508) Checksums-Sha1: 6467df6a917d7695e8771d496fe636c3af994702 1952 rapiddisk_8.2.0-3.dsc ecef344d8699793a0d7039c61d0d8aef0d6ed4d5 2948 rapiddisk_8.2.0-3.debian.tar.xz d68e17c7a59c6e7085aaa00929a8d764c9bd50bf 8618 rapiddisk_8.2.0-3_source.buildinfo Checksums-Sha256: 0d4a3b245dfbb97fcb9ef99499959d3533fd8a81e8a2ecdefc468a0819cf01ce 1952 rapiddisk_8.2.0-3.dsc 32eda19ed89ba6eb7b805dc96265a965305d7ecaf02734aed75cc41f22ac9e3b 2948 rapiddisk_8.2.0-3.debian.tar.xz 1279eb1279e5ade19d742461def3621e4f0d4192c428feb980465cc452c4de75 8618 rapiddisk_8.2.0-3_source.buildinfo Files: 911872eb7367216a7aac6fd93f0df818 1952 kernel optional rapiddisk_8.2.0-3.dsc 6ebbdf7794cfd7dad32d721aaa93d4f8 2948 kernel optional rapiddisk_8.2.0-3.debian.tar.xz 176075b676fcf79b5206294825e59dbe 8618 kernel optional rapiddisk_8.2.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmL7nS8ACgkQEWhSvN91 FcAAog/+NUex7b/mzn7h1G9JXiV2oMUh7erax+iMbcB50dY4/PAFJD2yC8z4ybxM n+4zW33kKySN81MJOAzykElNscDyU/H+4v01Z90D/9FAtVOS98Pni8qIm5R7vTbE ipOy/J4RJwrfG5nyHbqRf3s4Oyaq/eKk45qzjsKHyrRdTYUDNlbbuoxSzvZ3zJBg IVc2Kkt8MCBzA4I2yeBqTIv8fh25FIRJrXaP+Jk6n+XuPk2tWOsQj08nDPnOETeG hHVbTgF02uOdf1/6l9P+ZbABVJ09SLQvL7N7ORH3GBZ5BjRBrtXQcIcLZGHx89/h +5W+PEQbpCPAEoeFy/d9+mpqybOHbNLSBpHCUDXOn3kCPvWZZ6pNQd2+CC72Sigl UAFYKj3SpAKKugmZUjNUwQOJHxzz2sP+ZYjgDp/gFtV3ZvWevPcozSqp68my5T3Q O+U/iYl1szccNfsoCkADcdHv0ms+HNGw7gTjKdHCFAN4e4yJMPh5LQmttyWlHCiE TXQkZd7Vt4Wk4zcrGOXbcGacHajCafR7tApIrn2H8vIqDr5MD4D+Xqt7DUYMUcuC 68AUd0fEOaDeS8K2LVqG3KvlAC3aLOCITNGpThZpr4NDLCPzW55b96Vj2no5E3pF E1AJ8KbTXxhpt2j0IYCegjw6YZArI+eXQgwC0R48aQ4pkDm0Q0M= =4Xfy -END PGP SIGNATURE End Message ---
Bug#1017312: marked as done (mypy: FTBFS: main:77: error: Name "y8" is not defined (diff))
Your message dated Tue, 16 Aug 2022 15:12:34 + with message-id and subject line Bug#1017312: fixed in mypy 0.971-1 has caused the Debian Bug report #1017312, regarding mypy: FTBFS: main:77: error: Name "y8" is not defined (diff) 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.) -- 1017312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mypy Version: 0.961-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > === short test summary info > > FAILED mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrus > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusConditionalTypeBinder > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusConditionalTypeCheck > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusConditionalTypeCheck2 > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusPartialTypes > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusAssignmentAndConditionScopeForLiteral > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusAssignmentAndConditionScopeForProperty > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusAssignmentAndConditionScopeForFunction > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusExpr > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusTypeGuard > FAILED > mypy/test/testcheck.py::TypeCheckSuite::check-python38.test::testWalrusRedefined > = 11 failed, 9997 passed, 375 skipped, 9 xfailed in 539.66s (0:08:59) > == > make[1]: *** [debian/rules:78: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/mypy_0.961-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking 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: mypy Source-Version: 0.971-1 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of mypy, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated mypy 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: Mon, 15 Aug 2022 14:41:00 +0200 Source: mypy Architecture: source Version: 0.971-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Michael R. Crusoe Closes: 1017145 1017312 Changes: mypy (0.971-1) unstable; urgency=medium . * New upstream version * debian/clean: add additional directories & files * debian/patches/walrus.patch: cherry-pick patch from upstream to fix the walrus tests. Closes: #1017145, #1017312 Checksums-Sha1: 908a80f9ffc40195351fe3edddf14f29a852a108 2678 mypy_0.971-1.dsc 6b42a1ff3edcda09adbe7900b28542f7ac115182 2757982 mypy_0.971.orig.tar.gz 3ec492220c4f7abc8e568cecd3376f87cbd66ff5 13612 mypy_0.971-1.debian.tar.xz 76b798c6913d5b8b10407aac32063cceb5b28bb5 10446 my
Bug#1017145: marked as done (mypy: FTBFS: main:77: error: Name "y8" is not defined (diff))
Your message dated Tue, 16 Aug 2022 15:12:34 + with message-id and subject line Bug#1017145: fixed in mypy 0.971-1 has caused the Debian Bug report #1017145, regarding mypy: FTBFS: main:77: error: Name "y8" is not defined (diff) 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.) -- 1017145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mypy Version: 0.961-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > === FAILURES > === > __ testWalrus > __ > [gw3] linux -- Python 3.10.6 /usr/bin/python3.10 > data: /<>/test-data/unit/check-python38.test:212: > /<>/mypy/test/testcheck.py:142: in run_case > self.run_case_once(testcase) > /<>/mypy/test/testcheck.py:230: in run_case_once > assert_string_arrays_equal(output, a, msg.format(testcase.file, > testcase.line)) > E AssertionError: Unexpected type checker output > (/<>/test-data/unit/check-python38.test, line 212) > - Captured stderr call > - > Expected: > main:6: note: Revealed type is "builtins.int" (diff) > main:9: note: Revealed type is "builtins.str" (diff) > main:12: note: Revealed type is "builtins.int" (diff) > main:13: note: Revealed type is "builtins.list[builtins.int]" (diff) > main:16: note: Revealed type is "builtins.list[builtins.int]" (diff) > main:17: note: Revealed type is "builtins.int" (diff) > main:20: note: Revealed type is "builtins.dict[builtins.str, builtins.int]" > (diff) > main:21: note: Revealed type is "builtins.int" (diff) > main:24: note: Revealed type is "builtins.dict[builtins.str, builtins.int]" > (diff) > main:25: note: Revealed type is "builtins.str" (diff) > main:26: note: Revealed type is "builtins.int" (diff) > main:29: note: Revealed type is "builtins.dict[builtins.str, builtins.int]" > (diff) > main:30: note: Revealed type is "builtins.int" (diff) > main:34: note: Revealed type is "builtins.int" (diff) > main:37: note: Revealed type is "builtins.str" (diff) > main:40: note: Revealed type is "builtins.int" (diff) > main:41: note: Revealed type is "builtins.int" (diff) > main:42: note: Revealed type is "builtins.int" (diff) > main:45: note: Revealed type is "builtins.int" (diff) > main:46: note: Revealed type is "builtins.list[builtins.int]" (diff) > main:49: note: Revealed type is "builtins.list[builtins.int]" (diff) > main:50: note: Revealed type is "builtins.int" (diff) > main:53: note: Revealed type is "builtins.dict[builtins.str, builtins.int]" > (diff) > main:54: note: Revealed type is "builtins.int" (diff) > main:57: note: Revealed type is "builtins.dict[builtins.str, builtins.int]" > (diff) > main:58: note: Revealed type is "builtins.str" (diff) > main:59: note: Revealed type is "builtins.int" (diff) > main:62: note: Revealed type is "builtins.dict[builtins.str, builtins.int]" > (diff) > main:63: note: Revealed type is "builtins.int" (diff) > main:67: note: Revealed type is "builtins.int" (diff) > main:70: note: Revealed type is "builtins.int" (diff) > main:71: note: Revealed type is "builtins.int" (diff) > main:74: note: Revealed type is "builtins.int" (diff) > main:76: note: Revealed type is "builtins.int" (diff) > main:77: error: Name "y8" is not defined (diff) > main:79: error: Incompatible types in assignment (expression has type > "float", variable has type "int") (diff) > main:80: error: Incompatible types in assignment (expression has type > "str", variable has type "int") (diff) > main:84: error: "int" not callable(diff) > main:85: error: Variable "NT" is not valid as a type (diff) > main:85: note: See > https://mypy.readthedocs.io/en/stable/common_issues.html#variables-vs-type-aliases > (diff) > main:88: error: Variable "Alias" is not valid as a type (diff) > main:88: note: See > https://mypy.readthedocs.io/en/stable/common_issues.html#variables-vs-type-aliases > (diff) > main:90: note: Revealed type is "Literal[3]?" (diff) > main:91: note: Revealed type is "builtins.int" (diff) > main:92: note: Revealed type is "builtins.int" (diff) > main:96: note: Revealed type is "builtins.int" (diff) > main:101: error: Ca
Bug#1017138: marked as done (gudhi: FTBFS: Skeleton_blocker_contractor.h:175:31: error: no type named ‘handle’ in ‘class CGAL::Modifiable_priority_queue
Your message dated Tue, 16 Aug 2022 15:02:10 + with message-id and subject line Bug#1017138: fixed in gudhi 3.5.0+dfsg-3 has caused the Debian Bug report #1017138, regarding gudhi: FTBFS: Skeleton_blocker_contractor.h:175:31: error: no type named ‘handle’ in ‘class CGAL::Modifiable_priority_queue, Gudhi::contraction::Skeleton_blocker_contractor > >::Compare_cost, Gudhi::contraction::Skeleton_blocker_contractor > >::Undirected_edge_id, CGAL::CGAL_BOOST_PENDING_MUTABLE_QUEUE>’ 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.) -- 1017138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gudhi Version: 3.5.0+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/build/userversion/src/Contraction/example && /usr/bin/c++ > -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -DBOOST_RESULT_OF_USE_DECLTYPE > -DBOOST_SYSTEM_NO_DEPRECATED -DCGAL_EIGEN3_ENABLED -DCGAL_USE_GMPXX=1 > -I/<>/build/userversion -I/<>/src/common/include > -I/<>/src/Alpha_complex/include > -I/<>/src/Bitmap_cubical_complex/include > -I/<>/src/Bottleneck_distance/include > -I/<>/src/Collapse/include > -I/<>/src/Contraction/include > -I/<>/src/Coxeter_triangulation/include > -I/<>/src/Cech_complex/include > -I/<>/src/Hasse_complex/include > -I/<>/src/Persistence_representations/include > -I/<>/src/Persistent_cohomology/include > -I/<>/src/Rips_complex/include > -I/<>/src/Simplex_tree/include > -I/<>/src/Skeleton_blocker/include > -I/<>/src/Spatial_searching/include > -I/<>/src/Subsampling/include > -I/<>/src/Tangential_complex/include > -I/<>/src/Toplex_map/include > -I/<>/src/Witness_complex/include > -I/<>/src/Nerve_GIC/include -isystem /usr/include/eigen3 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic > -frounding-math -std=gnu++14 -MD -MT > src/Contraction/example/CMakeFiles/RipsContraction.dir/Rips_contraction.cpp.o > -MF CMakeFiles/RipsContraction.dir/Rips_contraction.cpp.o.d -o > CMakeFiles/RipsContraction.dir/Rips_contraction.cpp.o -c > /<>/src/Contraction/example/Rips_contraction.cpp > In file included from > /<>/src/Contraction/include/gudhi/Edge_contraction.h:15, > from > /<>/src/Contraction/example/Rips_contraction.cpp:10: > /<>/src/Contraction/include/gudhi/Skeleton_blocker_contractor.h: > In instantiation of ‘class > Gudhi::contraction::Skeleton_blocker_contractor > > >’: > /<>/src/Contraction/example/Rips_contraction.cpp:65:33: > required from here > /<>/src/Contraction/include/gudhi/Skeleton_blocker_contractor.h:175:31: > error: no type named ‘handle’ in ‘class > CGAL::Modifiable_priority_queue long unsigned int>, > Gudhi::contraction::Skeleton_blocker_contractor > > >::Compare_cost, > Gudhi::contraction::Skeleton_blocker_contractor > > >::Undirected_edge_id, CGAL::CGAL_BOOST_PENDING_MUTABLE_QUEUE>’ > 175 | typedef typename PQ::handle pq_handle; > | ^ > In file included from /usr/include/boost/assert.hpp:58, > from /usr/include/boost/smart_ptr/shared_array.hpp:21, > from /usr/include/boost/shared_array.hpp:17, > from /usr/include/boost/graph/detail/d_ary_heap.hpp:20, > from /usr/include/boost/graph/named_function_params.hpp:27, > from /usr/include/boost/graph/depth_first_search.hpp:21, > from /usr/include/boost/graph/connected_components.hpp:15, > from > /<>/src/Skeleton_blocker/include/gudhi/Skeleton_blocker_complex.h:25, > from > /<>/src/Skeleton_blocker/include/gudhi/Skeleton_blocker.h:14, > from > /<>/src/Contraction/example/Rips_contraction.cpp:11: > /<>/src/Skeleton_blocker/include/gudhi/Skeleton_blocker_complex.h: > In instantiation of > ‘Gudhi::skeleton_blocker::Skeleton_blocker_complex::Graph_vertex& > > Gudhi::skeleton_blocker::Skeleton_blocker_complex::operator[](Vertex_handle) > [with SkeletonBlockerDS = > Gudhi::skeleton_blocker::Skeleton_blocker_simple_geometric_traits; > Graph_vertex = > Gudhi::skeleton_blocker::Skeleton_blocker_simple_geometric_traits::Simple_geometric_vertex; > Vertex_handle = > Gudhi::skeleton_blocker::Skeleton_blocker_simple_traits::Vertex_handle]’: > /<
Processed: Bug#1017191 marked as pending in murano
Processing control commands: > tag -1 pending Bug #1017191 [src:murano] murano: FTBFS: AttributeError: 'NoneType' object has no attribute 'object_store' Added tag(s) pending. -- 1017191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017191: marked as pending in murano
Control: tag -1 pending Hello, Bug #1017191 in murano 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/openstack-team/services/murano/-/commit/4b1842427ab16c256b7799daf7dda8f8bd65 Add neutralize-broken-test.patch (Closes: #1017191). (this message was generated automatically) -- Greetings https://bugs.debian.org/1017191
Processed: Re: generate-ninja: FTBFS: dwz: debian/generate-ninja/usr/bin/gn: Unknown debugging section .debug_addr
Processing control commands: > tags -1 patch Bug #1016330 [src:generate-ninja] generate-ninja: FTBFS: dwz: debian/generate-ninja/usr/bin/gn: Unknown debugging section .debug_addr Added tag(s) patch. -- 1016330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016330: generate-ninja: FTBFS: dwz: debian/generate-ninja/usr/bin/gn: Unknown debugging section .debug_addr
Package: generate-ninja Followup-For: Bug #1016330 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Hi, In Ubuntu, we fixed the FTBFS by forcing gn to build as DWARFv4 to remain compatible with dh_dwz: * debian/rules: Set -gdwarf-4 in CXXFLAGS to remain compatible with dh_dwz and fix FTBFS (LP: #1984224). Thanks, Nick diff -Nru generate-ninja-0.0~git20220314.bd99dbf/debian/rules generate-ninja-0.0~git20220314.bd99dbf/debian/rules --- generate-ninja-0.0~git20220314.bd99dbf/debian/rules 2022-03-21 02:51:44.0 -0400 +++ generate-ninja-0.0~git20220314.bd99dbf/debian/rules 2022-08-10 11:14:05.0 -0400 @@ -1,7 +1,7 @@ #!/usr/bin/make -f include /usr/share/dpkg/buildflags.mk export DEB_BUILD_MAINT_OPTIONS = hardening=+all -CXXFLAGS += $(CPPFLAGS) -fPIE +CXXFLAGS += $(CPPFLAGS) -fPIE -gdwarf-4 LDFLAGS += -pie include /usr/share/dpkg/architecture.mk
Bug#1017469: libxsmm: FTBFS with undefined reference to pthread_yield
Package: libxsmm
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Dear Maintainer,
With glibc >= 2.34, libxsmm FTBFS with an undefined reference to
pthread_yield. Fixes have been committed upstream, but not yet included
in a release.
In Ubuntu, we cherry-picked the upstream commits to fix the build:
* debian/patches: Cherry-pick upstream patches to fix undefined reference to
pthread_yield (LP: #1984111).
Thanks,
Nick
diff -Nru
libxsmm-1.17/debian/patches/0003-Issue-551-rely-on-sched_yield-rather-than-pthread_yi.patch
libxsmm-1.17/debian/patches/0003-Issue-551-rely-on-sched_yield-rather-than-pthread_yi.patch
---
libxsmm-1.17/debian/patches/0003-Issue-551-rely-on-sched_yield-rather-than-pthread_yi.patch
1969-12-31 19:00:00.0 -0500
+++
libxsmm-1.17/debian/patches/0003-Issue-551-rely-on-sched_yield-rather-than-pthread_yi.patch
2022-08-09 10:18:54.0 -0400
@@ -0,0 +1,25 @@
+Description: rely on sched_yield rather than pthread_yield (GLIBC 2.34 and
later).
+Author: Hans Pabst
+Origin: upstream,
https://github.com/libxsmm/libxsmm/commit/161ee78f1ccbbe6ce2c0439d6889221cca77ce13
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libxsmm/+bug/1984111
+Last-Update: 2022-08-09
+---
+
+--- a/include/libxsmm_sync.h
b/include/libxsmm_sync.h
+@@ -462,6 +462,10 @@
+ # define LIBXSMM_TLS_GETVALUE(KEY) pthread_getspecific(KEY)
+ # if defined(__APPLE__) && defined(__MACH__)
+ # define LIBXSMM_SYNC_YIELD pthread_yield_np()
++# elif defined(__GLIBC__) && defined(__GLIBC_MINOR__) \
++ && LIBXSMM_VERSION2(2, 34) <= LIBXSMM_VERSION2(__GLIBC__,
__GLIBC_MINOR__)
++ LIBXSMM_EXTERN int sched_yield(void); /* sched.h */
++# define LIBXSMM_SYNC_YIELD sched_yield()
+ # else
+ # if defined(__USE_GNU) || !defined(__BSD_VISIBLE)
+ LIBXSMM_EXTERN int pthread_yield(void) LIBXSMM_THROW;
+@@ -813,4 +817,3 @@
+ LIBXSMM_API unsigned int libxsmm_get_tid(void);
+
+ #endif /*LIBXSMM_SYNC_H*/
+-
diff -Nru
libxsmm-1.17/debian/patches/0004-Fixed-potential-issue-about-undefined-pthread_yield.patch
libxsmm-1.17/debian/patches/0004-Fixed-potential-issue-about-undefined-pthread_yield.patch
---
libxsmm-1.17/debian/patches/0004-Fixed-potential-issue-about-undefined-pthread_yield.patch
1969-12-31 19:00:00.0 -0500
+++
libxsmm-1.17/debian/patches/0004-Fixed-potential-issue-about-undefined-pthread_yield.patch
2022-08-09 10:18:54.0 -0400
@@ -0,0 +1,33 @@
+Description: Fixed potential issue about undefined pthread_yield (linkage).
+Author: Hans Pabst
+Origin: upstream,
https://github.com/libxsmm/libxsmm/commit/304de784a56c3d7763c92b1801e059c3d39e14dc
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libxsmm/+bug/1984111
+Last-Update: 2022-08-09
+---
+diff --git a/include/libxsmm_macros.h b/include/libxsmm_macros.h
+index 1795ce763..e4d31c9d3 100644
+--- a/include/libxsmm_macros.h
b/include/libxsmm_macros.h
+@@ -844,6 +844,7 @@ LIBXSMM_API_INLINE int libxsmm_nonconst_int(int i) {
return i; }
+ # include
+ # else
+ # include
++# include
+ # endif
+ #endif
+ #if !defined(LIBXSMM_ASSERT)
+diff --git a/include/libxsmm_sync.h b/include/libxsmm_sync.h
+index b64a55f09..d92dad2c8 100644
+--- a/include/libxsmm_sync.h
b/include/libxsmm_sync.h
+@@ -466,8 +466,8 @@ typedef enum libxsmm_atomic_kind {
+ # define LIBXSMM_TLS_GETVALUE(KEY) pthread_getspecific(KEY)
+ # if defined(__APPLE__) && defined(__MACH__)
+ # define LIBXSMM_SYNC_YIELD pthread_yield_np()
+-# elif defined(__GLIBC__) && defined(__GLIBC_MINOR__) \
+- && LIBXSMM_VERSION2(2, 34) <= LIBXSMM_VERSION2(__GLIBC__,
__GLIBC_MINOR__)
++# elif defined(_POSIX_PRIORITY_SCHEDULING) || (defined(__GLIBC__) &&
defined(__GLIBC_MINOR__) \
++ && LIBXSMM_VERSION2(2, 34) <= LIBXSMM_VERSION2(__GLIBC__,
__GLIBC_MINOR__))
+ LIBXSMM_EXTERN int sched_yield(void); /* sched.h */
+ # define LIBXSMM_SYNC_YIELD sched_yield()
+ # else
diff -Nru libxsmm-1.17/debian/patches/series libxsmm-1.17/debian/patches/series
--- libxsmm-1.17/debian/patches/series 2022-03-19 19:49:47.0 -0400
+++ libxsmm-1.17/debian/patches/series 2022-08-09 10:18:54.0 -0400
@@ -1,2 +1,4 @@
0001-Makefile-rebuild-fix.patch
0002-Makefile-fix-pkgconfigdir.patch
+0003-Issue-551-rely-on-sched_yield-rather-than-pthread_yi.patch
+0004-Fixed-potential-issue-about-undefined-pthread_yield.patch
Bug#1016411: ghdl FTBFS with LLVM 14 as default
Package: ghdl Followup-For: Bug #1016411 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, this patch was applied to fix the build with LLVM 14.0. Additionally, we opted to skip the build tests on armhf until upstream provides a solution[1]. * debian/patches/llvm14.0.patch: Allow building with LLVM 14.0 (LP: #1983908). * debian/rules: Skip testsuite on armhf (LP: #1984138). Thanks, Nick [1] https://github.com/ghdl/ghdl/issues/2170 diff -Nru ghdl-1.0.0+dfsg/debian/patches/llvm14.0.patch ghdl-1.0.0+dfsg/debian/patches/llvm14.0.patch --- ghdl-1.0.0+dfsg/debian/patches/llvm14.0.patch 1969-12-31 19:00:00.0 -0500 +++ ghdl-1.0.0+dfsg/debian/patches/llvm14.0.patch 2022-08-09 11:40:42.0 -0400 @@ -0,0 +1,33 @@ +Description: Enable building with LLVM 14.0 + Allow the configure script to handle LLVM 14.0, and use DWARFv4 format to remain + compatible with dwz. +Author: Nick Rosbrook +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ghdl/+bug/1983908 +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016411 +Forwarded: no, the DWARFv4 piece is packaging specific due to dh_dwz +Last-Update: 2022-08-08 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/configure b/configure +@@ -283,6 +283,7 @@ +check_version 11.1.0 $llvm_version || +check_version 12.0 $llvm_version || +check_version 13.0 $llvm_version || ++ check_version 14.0 $llvm_version || +false; then + echo "Debugging is enabled with llvm $llvm_version" + else +--- a/Makefile.in b/Makefile.in +@@ -59,6 +59,10 @@ + + VHDL_LIB_DIR=$(prefix)/$(libdirsuffix)/vhdl + ++ifeq "$(backend)" "llvm" ++ OPT_FLAGS+=-gdwarf-4 ++endif ++ + ifeq "$(enable_checks)" "true" + # Debug + checks + OPT_FLAGS+=-g diff -Nru ghdl-1.0.0+dfsg/debian/patches/series ghdl-1.0.0+dfsg/debian/patches/series --- ghdl-1.0.0+dfsg/debian/patches/series 2022-02-14 17:10:35.0 -0500 +++ ghdl-1.0.0+dfsg/debian/patches/series 2022-08-09 11:40:42.0 -0400 @@ -7,3 +7,4 @@ llvm12.0.patch llvm11.1.0.patch llvm13.0.patch +llvm14.0.patch diff -Nru ghdl-1.0.0+dfsg/debian/rules ghdl-1.0.0+dfsg/debian/rules --- ghdl-1.0.0+dfsg/debian/rules2022-02-14 17:10:35.0 -0500 +++ ghdl-1.0.0+dfsg/debian/rules2022-08-09 11:40:42.0 -0400 @@ -197,6 +197,9 @@ @echo @echo Run testsuite @echo +ifeq ($(DEB_HOST_ARCH),armhf) + @echo Skipping testsuite on armhf +else # With some paths patched for the Debian packaging, the tests will not # work right when run from the build directory. To keep it simple # simply install into a temporary location and tell the testsuite to @@ -219,6 +222,7 @@ ln -sf lib/ghdl/gcc/libexec $(TESTRUNDIR)/gcc/usr/libexec; \ debian/tests/ghdl-tests buildtest gcc; \ fi +endif override_dh_gencontrol: if [ -n "$(WITH_GCC)" ]; then \
Processed: Re: ghdl FTBFS with LLVM 14 as default
Processing control commands: > tags -1 patch Bug #1016411 [src:ghdl] ghdl FTBFS with LLVM 14 as default Added tag(s) patch. -- 1016411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017468: openfst: FTBFS in dh_auto_test due to excessive memory usage
Package: openfst Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Dear Maintainer, The openfst build was failing both locally and on Ubuntu build infrastructure[1] during dh_auto_test. In both situations, the build process was getting killed due to excessive memory usage. In Ubuntu, the attached patch was applied to reduce the memory usage during dh_auto_test. * debian/rules: Set --max-parallel=2 in override_dh_auto_test to avoid excessive memory usage resulting in FTBFS (LP: #1984137). Thanks, Nick [1] https://launchpadlibrarian.net/617386196/buildlog_ubuntu-kinetic-amd64.openfst_1.7.9-4_BUILDING.txt.gz diff -Nru openfst-1.7.9/debian/rules openfst-1.7.9/debian/rules --- openfst-1.7.9/debian/rules 2022-04-05 08:03:00.0 -0400 +++ openfst-1.7.9/debian/rules 2022-08-09 16:50:53.0 -0400 @@ -37,6 +37,9 @@ ifneq ($(findstring mips,$(DEB_BUILD_ARCH)),) override_dh_auto_test: # Tests disabled on MIPS +else +override_dh_auto_test: + dh_auto_test --max-parallel=2 endif override_dh_missing:
Processed: source-highlight: ftbfs with GCC-12
Processing control commands: > tags -1 + fixed-upstream patch Bug #1013041 [src:source-highlight] source-highlight: ftbfs with GCC-12 Added tag(s) patch and fixed-upstream. -- 1013041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013041: source-highlight: ftbfs with GCC-12
Control: tags -1 + fixed-upstream patch There's already an upstream commit [1] that fixes this issue. [1] https://git.savannah.gnu.org/cgit/src-highlite.git/commit/?id=ab9fe5cb9b85c5afab94f2a7f4b6d7d473c14ee9
Bug#1017441: debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles
On Tue, 16 Aug 2022 13:13:53 +0200 Johannes Schauer Marin Rodrigues wrote: > Package: debhelper > Version: 13.9 > Severity: serious > X-Debbugs-Cc: jo...@debian.org > > Steps to reproduce: > > $ sbuild -d unstable shadow > [...] > [...] > [...] > passwd_4.11.1+dfsg1-2_amd64.deb > --- > > new Debian package, version 2.0. > size 944912 bytes: control archive=7432 bytes. > 111 bytes, 6 lines conffiles > 740 bytes, 17 lines control██ > 18406 bytes, 275 lines md5sums██ > 1090 bytes, 40 lines * postinst #!/bin/sh > 172 bytes, 5 lines * postrm #!/bin/sh > 172 bytes, 5 lines * preinst #!/bin/sh > 172 bytes, 5 lines * prerm #!/bin/sh > Package: passwd > Source: shadow > Version: 1:4.11.1+dfsg1-2 > Architecture: amd64 > Maintainer: Shadow package maintainers > Installed-Size: 2761 > Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.34), libcrypt1 (>= 1:4.1.0), libpam0g (>= 0.99.7.1), > libselinux1 (>= 3.1~), libsemanage2 (>= 2.0.3), systemd | systemd- tmpfiles, libpam-modules > > > > The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the > dependency on "systemd | systemd-tmpfiles" and was compiled with > debhelper 13.6. > > This currently installs systemd on a systems that don't need it, which > is especially bad for minimal and embedded systems and/or containers. > Thus setting the severity to serious. Feel free to adjust. > > Thanks! > > cheers, josch This looks entirely correct to me. You can install the -standalone variant if you prefer a slightly smaller footprint, which is provided exactly for those non-default use cases. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: Bug#1017312 marked as pending in mypy
Processing control commands: > tag -1 pending Bug #1017312 [src:mypy] mypy: FTBFS: main:77: error: Name "y8" is not defined (diff) Added tag(s) pending. -- 1017312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1017145 marked as pending in mypy
Processing control commands: > tag -1 pending Bug #1017145 [src:mypy] mypy: FTBFS: main:77: error: Name "y8" is not defined (diff) Added tag(s) pending. -- 1017145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017145: marked as pending in mypy
Control: tag -1 pending Hello, Bug #1017145 in mypy 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/python-team/packages/mypy/-/commit/200e4d339946dde2037912fea4794c5d532a49be cherry-pick patch from upstream to fix the walrus tests Closes: #1017145, #1017312 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017145
Bug#1017312: marked as pending in mypy
Control: tag -1 pending Hello, Bug #1017312 in mypy 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/python-team/packages/mypy/-/commit/200e4d339946dde2037912fea4794c5d532a49be cherry-pick patch from upstream to fix the walrus tests Closes: #1017145, #1017312 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017312
Bug#1017171: marked as done (sfxr-qt: FTBFS: catch.hpp:10453:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’)
Your message dated Tue, 16 Aug 2022 13:02:56 +
with message-id
and subject line Bug#1017171: fixed in sfxr-qt 1.5.0+ds-2
has caused the Debian Bug report #1017171,
regarding sfxr-qt: FTBFS: catch.hpp:10453:58: error: call to non-‘constexpr’
function ‘long int sysconf(int)’
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.)
--
1017171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sfxr-qt
Version: 1.5.0+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++
> -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB
> -I/<>/obj-x86_64-linux-gnu/src/sfxr-qt_autogen/include
> -I/<>/src/ui -I/<>/src/core
> -I/<>/obj-x86_64-linux-gnu/src/core -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Woverloaded-virtual -fPIC -std=gnu++17 -MD -MT
> src/CMakeFiles/sfxr-qt.dir/qrc_qml.cpp.o -MF
> CMakeFiles/sfxr-qt.dir/qrc_qml.cpp.o.d -o
> CMakeFiles/sfxr-qt.dir/qrc_qml.cpp.o -c
> /<>/obj-x86_64-linux-gnu/src/qrc_qml.cpp
> In file included from /usr/include/signal.h:328,
> from
> /<>/3rdparty/catch2/single_include/catch2/catch.hpp:7712,
> from /<>/tests/tests.cpp:7:
> /<>/3rdparty/catch2/single_include/catch2/catch.hpp:10453:58:
> error: call to non-‘constexpr’ function ‘long int sysconf(int)’
> 10453 | static constexpr std::size_t sigStackSize = 32768 >= MINSIGSTKSZ
> ? 32768 : MINSIGSTKSZ;
> | ^~~
> In file included from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24:
> /usr/include/unistd.h:640:17: note: ‘long int sysconf(int)’ declared here
> 640 | extern long int sysconf (int __name) __THROW;
> | ^~~
> /<>/3rdparty/catch2/single_include/catch2/catch.hpp:10512:45:
> error: size of array ‘altStackMem’ is not an integral constant-expression
> 10512 | char FatalConditionHandler::altStackMem[sigStackSize] = {};
> | ^~~~
> [ 97%] Linking CXX executable sfxr-qt
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E
> cmake_link_script CMakeFiles/sfxr-qt.dir/link.txt --verbose=1
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now
> "CMakeFiles/sfxr-qt.dir/sfxr-qt_autogen/mocs_compilation.cpp.o"
> "CMakeFiles/sfxr-qt.dir/ui/main.cpp.o"
> "CMakeFiles/sfxr-qt.dir/ui/Generator.cpp.o"
> "CMakeFiles/sfxr-qt.dir/qrc_qml.cpp.o" -o sfxr-qt libsfxr-qtlib.a
> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.4
> /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.15.4
> /usr/lib/x86_64-linux-gnu/libQt5QmlModels.so.5.15.4 -lSDL
> /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.15.4
> /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.15.4
> /usr/lib/x86_64-linux-gnu/libQt5Concurrent.so.5.15.4
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.4
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.4
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 97%] Built target sfxr-qt
> make[3]: *** [tests/CMakeFiles/tests.dir/build.make:93:
> tests/CMakeFiles/tests.dir/tests.cpp.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/08/13/sfxr-qt_1.5.0+ds-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseve
Bug#1017449: nautilus-image-converter: Incompatible with Nautilus 43
Source: nautilus-image-converter Severity: serious Version: 0.3.1~git20110416-2 Tags: sid bookworm nautilus-image-converter is incompatible with Nautilus 43. It would need to be converted to GTK4 to continue to work. Thank you, Jeremy Bicha
Bug#1015090: marked as done (mrboom: FTBFS: libopenmpt-modplug-dev : Conflicts: libmodplug-dev but 1:0.8.9.0-3 is to be installed)
Your message dated Tue, 16 Aug 2022 12:53:28 + with message-id and subject line Bug#1015090: fixed in mrboom 5.2+ds-2 has caused the Debian Bug report #1015090, regarding mrboom: FTBFS: libopenmpt-modplug-dev : Conflicts: libmodplug-dev but 1:0.8.9.0-3 is to be installed 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.) -- 1015090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mrboom Version: 5.2+ds-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), libsdl2-dev, > libsdl2-mixer-dev, libminizip-dev, libopenmpt-modplug-dev | libmodplug-dev, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), libsdl2-dev, > libsdl2-mixer-dev, libminizip-dev, libopenmpt-modplug-dev, build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [413 B] > Get:5 copy:/<>/apt_archive ./ Packages [488 B] > Fetched 1858 B in 0s (153 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libopenmpt-modplug-dev : Conflicts: libmodplug-dev but 1:0.8.9.0-3 is to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2022/07/16/mrboom_5.2+ds-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking 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: mrboom Source-Version: 5.2+ds-2 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of mrboom, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated mrboom 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: Tue, 16 Aug 2022 13:45:34 +0200 Source: mrboom Architecture: source Version: 5.2+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Gürkan Myczko Closes: 1015090 Changes: mrboom (5.2+ds-2) unstab
Bug#1017213: marked as done (cross-toolchain-base: FTBFS: configure: error: cannot compute suffix of object files: cannot compile)
Your message dated Tue, 16 Aug 2022 12:35:41 + with message-id and subject line Bug#1017213: fixed in cross-toolchain-base 60 has caused the Debian Bug report #1017213, regarding cross-toolchain-base: FTBFS: configure: error: cannot compute suffix of object files: cannot compile 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.) -- 1017213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cross-toolchain-base Version: 59 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > --- > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc-11 > checking for suffix of object files... configure: error: in > `/<>/glibc-2.34/build-tree/amd64-libc': > configure: error: cannot compute suffix of object files: cannot compile > See `config.log' for more details > make[1]: *** [debian/rules.d/build.mk:78: > /<>/glibc-2.34/stamp-dir/configure_libc] Error 1 > make[1]: Leaving directory '/<>/glibc-2.34' > dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit > status 2 The full build log is available from: http://qa-logs.debian.net/2022/08/13/cross-toolchain-base_59_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking 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: cross-toolchain-base Source-Version: 60 Done: Dimitri John Ledkov We believe that the bug you reported is fixed in the latest version of cross-toolchain-base, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dimitri John Ledkov (supplier of updated cross-toolchain-base 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: Tue, 16 Aug 2022 13:17:09 +0100 Source: cross-toolchain-base Built-For-Profiles: noudeb Architecture: source Version: 60 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: Dimitri John Ledkov Closes: 1016829 1017213 Changes: cross-toolchain-base (60) unstable; urgency=medium . [ Debian Janitor ] * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Remove unnecessary XS-Testsuite field in debian/control. . [ Bastien Roucariès ] * Build using gcc 11.3.0-5 * Bug fix: "FTBFS: configure: error: cannot compute suffix of object files: cannot compile", thanks to Lucas Nussbaum (Closes: #1017213). . [ Dimitri John Ledkov ] * debian/tests/control: switch static build-depends list to @builddeps@ macro. * Switch to exact linux-source-$VER dependency. * Update ubuntu patches for glibc 2.36. * Drop unused CROSS_* substitutions from debian/rules control target that generating warnings and errors. * Update package versions for Debian and Ubuntu. (Closes: #1016829). * Build using glibc 2.34-3. * Build using linux 5.18.16. Checksums-Sha1: 33b0036021d5dc91e960f2961d877f1b0924404e 5674 cross-toolchain-base_60.dsc fe3cff3973be475b05e13f56637f595ed90137da 43692 cross-toolchain-base_60.tar.xz 7b232d9753c92362ce950475c21
Bug#1016829: marked as done (cross-toolchain-base: autopkgtest hardcodes glibc version which is transitioning now)
Your message dated Tue, 16 Aug 2022 12:35:41 + with message-id and subject line Bug#1016829: fixed in cross-toolchain-base 60 has caused the Debian Bug report #1016829, regarding cross-toolchain-base: autopkgtest hardcodes glibc version which is transitioning now 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.) -- 1016829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cross-toolchain-base Version: 59 Severity: serious Dear all, The glibc 2.34 transition started yesterday. However, the autopkgtest of cross-toolchain-base fails because it hardcodes: glibc-source (>= 2.33-1~), glibc-source (<< 2.34) which isn't available anymore. Please adapt your test for the new (and ideally future) glibc. Paul --- End Message --- --- Begin Message --- Source: cross-toolchain-base Source-Version: 60 Done: Dimitri John Ledkov We believe that the bug you reported is fixed in the latest version of cross-toolchain-base, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dimitri John Ledkov (supplier of updated cross-toolchain-base 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: Tue, 16 Aug 2022 13:17:09 +0100 Source: cross-toolchain-base Built-For-Profiles: noudeb Architecture: source Version: 60 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: Dimitri John Ledkov Closes: 1016829 1017213 Changes: cross-toolchain-base (60) unstable; urgency=medium . [ Debian Janitor ] * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Remove unnecessary XS-Testsuite field in debian/control. . [ Bastien Roucariès ] * Build using gcc 11.3.0-5 * Bug fix: "FTBFS: configure: error: cannot compute suffix of object files: cannot compile", thanks to Lucas Nussbaum (Closes: #1017213). . [ Dimitri John Ledkov ] * debian/tests/control: switch static build-depends list to @builddeps@ macro. * Switch to exact linux-source-$VER dependency. * Update ubuntu patches for glibc 2.36. * Drop unused CROSS_* substitutions from debian/rules control target that generating warnings and errors. * Update package versions for Debian and Ubuntu. (Closes: #1016829). * Build using glibc 2.34-3. * Build using linux 5.18.16. Checksums-Sha1: 33b0036021d5dc91e960f2961d877f1b0924404e 5674 cross-toolchain-base_60.dsc fe3cff3973be475b05e13f56637f595ed90137da 43692 cross-toolchain-base_60.tar.xz 7b232d9753c92362ce950475c21f5ce57088506f 11302 cross-toolchain-base_60_source.buildinfo Checksums-Sha256: 705b2b2d3c3d07e0b6f33c4faafba13b5a6d782465122d624b4245b8910d9846 5674 cross-toolchain-base_60.dsc 6d06aaa57ce9fc1e1bfbb24f10b3b37957bf16bc2ea0b2fc8e81eff807ebbbcf 43692 cross-toolchain-base_60.tar.xz 4775dfe5394eaa18117756e3a978a5a77e13025634002353c2306813a1c71190 11302 cross-toolchain-base_60_source.buildinfo Files: fda84c0a4192f26417fc0e2ce0ab341d 5674 devel optional cross-toolchain-base_60.dsc f8115f7712d4fa7ce638d8fde4ed0a01 43692 devel optional cross-toolchain-base_60.tar.xz 31e3379ee537b59e020385cdcecec7d0 11302 devel optional cross-toolchain-base_60_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAmL7iwUACgkQm47ISdXv cO1GLxAArZeXA+Z0BA65lDHUfJoufgHCSXT/uerWsdhT3Rdd9z4HP0ie4BVblWbe C8OLjoXET71SLOUQrgygVcBL6pXzInuvlvLIOC1M04QBlYnXQsQ35/nrKizgUqJ+ PQbRN9mWFa4zy4/RJIaLJfWVHbGWNRYb7QH/CAAhfDs6pk/vTMdpQj1rD/duklgn FQdNhpN6XToOPnQhvaJ6M9z+Bawwgby5WGAF36QYYqJU89hl4PpMJPHLZUvfL57V MpVozKhs8Bujj3DwqR2a0TUSkXey1cma9S9+0GZUwRHiRANkvKO1cLBVW5xF6yjW vq9YnM00gRRXsH2sTDjeF8Smk3oYpJ6og+e/5UYRMMovKeErGAK+Q7r+Jpry7vWS u/OsJ7OvnxC1WK+HK8A0aA87XEwjnxGeVdV67QYFuQ8o8grZjILHklfOmRPYlnxE jwXGo1fkentmUEoAilGgwKbNlvsbrqfBzvnm527vBieTPghQ09WBabkQQpHn6etW M2hVMH68lgGgv/NrTyhVG1YyB66qHZckA+d8o42OSUdEtAzCj1QYUeZtzsawRSPe OIejFliVXNKiYdXkL9+I6fkH2JQhZIpaTHpSGwrilnJQMDE4uNluuoe9QwehyWtV 2UI3XWzx4789ZbMZrih7FObxG30Tm0ulJ0vJqjVc2I2KWoDkTJo= =sq1y -END PGP SIGNATUR
Bug#1004801: marked as done (cloudcompare: FTBFS with ffmpeg 5.0)
Your message dated Tue, 16 Aug 2022 12:35:10 +
with message-id
and subject line Bug#1004801: fixed in cloudcompare 2.11.3-6
has caused the Debian Bug report #1004801,
regarding cloudcompare: FTBFS with ffmpeg 5.0
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.)
--
1004801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cloudcompare
Version: 2.11.3-4
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0
cloudcompare FTBFS with ffmpeg 5.0 in experimental:
cd /<>/obj-x86_64-linux-gnu/CC && /usr/lib/ccache/c++
-DCC_CORE_LIB_EXPORTS -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB
-DQT_NO_DEBUG -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DSCALAR_TYPE_FLOAT
-DUSE_QT -I/<>/obj-x86_64-linux-gnu/CC -I/<>/CC
-I/<>/obj-x86_64-linux-gnu/CC/CC_CORE_LIB_autogen/include
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport
-I/<>/CC/include -isystem /usr/include/x86_64-linux-gnu/qt5
-isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fPIC
-std=c++11 -fPIC -fopenmp -O3 -DNDEBUG -fPIC -fvisibility=hidden
-fvisibility-inlines-hidden -fPIC -MD -MT
CC/CMakeFiles/CC_CORE_LIB.dir/src/ChamferDistanceTransform.cpp.o -MF
CMakeFiles/CC_CORE_LIB.dir/src/ChamferDistanceTransform.cpp.o.d -o
CMakeFiles/CC_CORE_LIB.dir/src/ChamferDistanceTransform.cpp.o -c
/<>/CC/src/ChamferDistanceTransform.cpp
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:
In member function ‘bool QVideoEncoder::open(QString*)’:
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:120:9:
error: ‘av_register_all’ was not declared in this scope
120 | av_register_all();
| ^~~
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:142:47:
error: invalid conversion from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
142 | AVCodec *pCodec = avcodec_find_encoder(codec_id);
| ^~
| |
| const AVCodec*
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:194:28:
error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘codec’
194 | m_ff->videoStream->codec = m_ff->codecContext;
|^
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:
In member function ‘virtual bool QVideoEncoder::close()’:
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:270:31:
warning: ‘void av_init_packet(AVPacket*)’ is deprecated
[-Wdeprecated-declarations]
270 | av_init_packet(&pkt);
| ~~^~
In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
from
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:6:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
506 | void av_init_packet(AVPacket *pkt);
| ^~
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:273:27:
error: ‘avcodec_encode_video2’ was not declared in this scope; did you mean
‘avcodec_encode_subtitle’?
273 | int ret = avcodec_encode_video2(m_ff->codecContext,
&pkt, 0, &got_packet);
| ^
| avcodec_encode_subtitle
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:287:42:
error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘codec’
287 | avcodec_close(m_ff->videoStream->codec);
| ^
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/QVideoEncoder.cpp:293:60:
error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘codec’
293 | av_freep(&m_ff->formatContext->streams[i]->codec);
|^
/<>/plugins/core/Standard/qAnimation/src/QTFFmpegWrapper/Q
Bug#1017441: it also makes packages non-installable
Beside forcing a switch to systemd (or systemd-tmpfiles if the admin knows about this option, which is not given in any messages), this wrong dependency also makes Required packages non-installable on: * hurd * kfreebsd * musl ports (prepared by helmut as a part of rebootstrap, and by others) * derivatives Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ You're alive. But that's just a phase. ⠈⠳⣄
Bug#1017441: debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles
Package: debhelper Version: 13.9 Severity: serious X-Debbugs-Cc: jo...@debian.org Steps to reproduce: $ sbuild -d unstable shadow [...] [...] [...] passwd_4.11.1+dfsg1-2_amd64.deb --- new Debian package, version 2.0. size 944912 bytes: control archive=7432 bytes. 111 bytes, 6 lines conffiles 740 bytes,17 lines control██ 18406 bytes, 275 lines md5sums██ 1090 bytes,40 lines * postinst #!/bin/sh 172 bytes, 5 lines * postrm #!/bin/sh 172 bytes, 5 lines * preinst #!/bin/sh 172 bytes, 5 lines * prerm#!/bin/sh Package: passwd Source: shadow Version: 1:4.11.1+dfsg1-2 Architecture: amd64 Maintainer: Shadow package maintainers Installed-Size: 2761 Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.34), libcrypt1 (>= 1:4.1.0), libpam0g (>= 0.99.7.1), libselinux1 (>= 3.1~), libsemanage2 (>= 2.0.3), systemd | systemd-tmpfiles, libpam-modules The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the dependency on "systemd | systemd-tmpfiles" and was compiled with debhelper 13.6. This currently installs systemd on a systems that don't need it, which is especially bad for minimal and embedded systems and/or containers. Thus setting the severity to serious. Feel free to adjust. Thanks! cheers, josch
Bug#1017440: pahole: Several tools just segfault
Package: pahole Version: 1.23-2 Severity: serious Hi! Many of the tools simply segfault when executed. On a shared library with debugging symbols: $ codiff libsysfs.so.2.0.1 libsysfs.so.2.0.1 Segmentation fault (core dumped) $ dtagnames libsysfs.so.2.0.1 Segmentation fault (core dumped) $ prefcnt libsysfs.so.2.0.1 Segmentation fault (core dumped) $ scncopy -s data -o output libsysfs.so.2.0.1 Segmentation fault (core dumped) $ syscse libsysfs.so.2.0.1 Segmentation fault (core dumped) On a stripped library: $ codiff /usr/lib/x86_64-linux-gnu/libbsd.so.0 \ /usr/lib/x86_64-linux-gnu/libbsd.so.0 Segmentation fault (core dumped) $ dtagnames /usr/lib/x86_64-linux-gnu/libbsd.so.0 Segmentation fault (core dumped) $ prefcnt /usr/lib/x86_64-linux-gnu/libbsd.so.0 Segmentation fault (core dumped) $ scncopy -s data -o output /usr/lib/x86_64-linux-gnu/libbsd.so.0 Segmentation fault (core dumped) $ syscse /usr/lib/x86_64-linux-gnu/libbsd.so.0 Segmentation fault (core dumped) Some even with no arguments: $ dtagnames Segmentation fault (core dumped) $ prefcnt Segmentation fault (core dumped) Thanks, Guillem
Bug#1017283: marked as done (scilab: FTBFS: ../../modules/core/includes/pause.h:18:18: error: conflicting declaration of C function ‘void pause()’)
Your message dated Tue, 16 Aug 2022 10:46:26 + with message-id and subject line Bug#1017283: fixed in scilab 6.1.1+dfsg2-4 has caused the Debian Bug report #1017283, regarding scilab: FTBFS: ../../modules/core/includes/pause.h:18:18: error: conflicting declaration of C function ‘void pause()’ 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.) -- 1017283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scilab Version: 6.1.1+dfsg2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CXX --mode=compile g++ -std=c++17 > -DHAVE_CONFIG_H -I. -I../../modules/core/includes -I./includes/ -I./src/c/ > -I./src/cpp/ -I./src/cpp/hash -I../../modules/ast/includes/ast/ > -I../../modules/ast/includes/exps/ -I../../modules/ast/includes/operations/ > -I../../modules/ast/includes/parse/ -I../../modules/ast/includes/symbol/ > -I../../modules/ast/includes/system_env/ -I../../modules/ast/includes/types/ > -I../../modules/ast/includes/analysis/ -I../../modules/call_scilab/includes/ > -I../../modules/api_scilab/includes/ -I../../modules/action_binding/includes/ > -I../../modules/output_stream/includes/ > -I../../modules/localization/includes/ > -I../../modules/functions_manager/includes/ > -I../../modules/elementary_functions/includes/ -I../../modules/io/includes/ > -I../../modules/tclsci/includes/ -I../../modules/dynamic_link/includes/ > -I../../modules/elementary_functions/includes/ > -I../../modules/string/includes/ -I../../modules/fileio/includes/ > -I../../modules/console/includes/ -I../../modules/threads/includes/ > -I../../modules/history_manager/includes/ > -I../../modules/preferences/includes/ > -I../../modules/external_objects/includes/ -I../../modules/jvm/includes/ > -I../../modules/jvm/src/c/ -I../../modules/gui/includes/ > -I../../modules/graphics/includes/ -I../../modules/hdf5/includes/ > -I../../modules/fftw/includes/ -I../../modules/ui_data/includes/ > -I/usr/include/hdf5/serial -I/usr/include/libxml2 -I/usr/include/tcl > -I/usr/include/tk -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g1 -O2 > -fno-stack-protector -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -MT > src/cpp/libscicore_algo_la-pause.lo -MD -MP -MF > src/cpp/.deps/libscicore_algo_la-pause.Tpo -c -o > src/cpp/libscicore_algo_la-pause.lo `test -f 'src/cpp/pause.cpp' || echo > './'`src/cpp/pause.cpp > libtool: compile: g++ -std=c++17 -DHAVE_CONFIG_H -I. > -I../../modules/core/includes -I./includes/ -I./src/c/ -I./src/cpp/ > -I./src/cpp/hash -I../../modules/ast/includes/ast/ > -I../../modules/ast/includes/exps/ -I../../modules/ast/includes/operations/ > -I../../modules/ast/includes/parse/ -I../../modules/ast/includes/symbol/ > -I../../modules/ast/includes/system_env/ -I../../modules/ast/includes/types/ > -I../../modules/ast/includes/analysis/ -I../../modules/call_scilab/includes/ > -I../../modules/api_scilab/includes/ -I../../modules/action_binding/includes/ > -I../../modules/output_stream/includes/ > -I../../modules/localization/includes/ > -I../../modules/functions_manager/includes/ > -I../../modules/elementary_functions/includes/ -I../../modules/io/includes/ > -I../../modules/tclsci/includes/ -I../../modules/dynamic_link/includes/ > -I../../modules/elementary_functions/includes/ > -I../../modules/string/includes/ -I../../modules/fileio/includes/ > -I../../modules/console/includes/ -I../../modules/threads/includes/ > -I../../modules/history_manager/includes/ > -I../../modules/preferences/includes/ > -I../../modules/external_objects/includes/ -I../../modules/jvm/includes/ > -I../../modules/jvm/src/c/ -I../../modules/gui/includes/ > -I../../modules/graphics/includes/ -I../../modules/hdf5/includes/ > -I../../modules/fftw/includes/ -I../../modules/ui_data/includes/ > -I/usr/include/hdf5/serial -I/usr/include/libxml2 -I/usr/include/tcl > -I/usr/include/tk -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g1 -O2 > -fno-stack-protector -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -MT > src/cpp/libscicore_algo_la-pause.lo -MD -MP -MF > src/cpp/.deps/libscicore_algo_la-pause.Tpo -c src/cpp/pause.cpp -fPIC -DPIC > -o src/cpp/.libs/libscicore_algo_la-pause.o > In file included from src/cpp/pause.cpp:19: > ../../modules
Bug#1016732: marked as done (node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp)
Your message dated Tue, 16 Aug 2022 10:09:52 + with message-id and subject line Bug#1016732: fixed in node-sockjs 0.3.24+~0.3.33-2 has caused the Debian Bug report #1016732, regarding node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp 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.) -- 1016732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-sockjs Version: 0.3.24+~0.3.33-1 Severity: serious X-Debbugs-Cc: e...@ericebrown.com Hi, On running shiny-server with 0.3.24+~0.3.33-1 it chokes with: | [2022-08-06T04:59:03.613] [ERROR] shiny-server - Uncaught exception: TypeError: Cannot read properties of undefined (reading 'addEventListener') | [2022-08-06T04:59:03.614] [ERROR] shiny-server - TypeError: Cannot read properties of undefined (reading 'addEventListener') |at WebSocketReceiver.setUp (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) |at new WebSocketReceiver (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) |at WebSocket.dispatchEvent (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) |at WebSocket._open (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) |at Hybi. (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) |at Hybi.emit (node:events:513:28) |at Hybi._open (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) |at Hybi.start (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) | [2022-08-06T04:59:03.615] [INFO] shiny-server - Stopping listener on http://[::]:3838 | [2022-08-06T04:59:03.615] [INFO] shiny-server - Shutting down worker processes (with notification) | /usr/lib/shiny-server/lib/main.js:391 | throw err; | ^ | | TypeError: Cannot read properties of undefined (reading 'addEventListener') |at WebSocketReceiver.setUp (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) |at new WebSocketReceiver (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) |at WebSocket.dispatchEvent (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) |at WebSocket._open (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) |at Hybi. (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) |at Hybi.emit (node:events:513:28) |at Hybi._open (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) |at Hybi.start (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) | | Node.js v18.6.0 While it is running perfectly ok _with 0.3.24-2_. Since this is not a new release, there is a regression with the new changelog revision. In particular, it seems that something is off with the coffeescript generated files. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-sockjs depends on: pn node-faye-websocket ii node-uuid 8.3.2+~8.3.3-2 pn node-websocket-driver node-sockjs recommends no packages. node-sockjs suggests no packages. --- End Message --- --- Begin Message --- Source: node-sockjs Source-Version: 0.3.24+~0.3.33-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-sockjs, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-sockjs 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 ftp
Bug#1016732: [Pkg-javascript-devel] Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp
On 11/08/2022 07:25, Yadd wrote: On 10/08/2022 19:32, Nilesh Patra wrote: Hi, Sorry to bother you over this again, but would you have any idea? I'd be OK with a workaround if you don't have the bandwidth at the moment, but this seems to come from coffee related modifications only. Hi, not enough time this week, I'll try next one. Cheers, Yadd Hi, I just fix this (at least the test you give passed). Please reopen this issue if there is still a bug. Cheers, Yadd
Processed: python-etelemetry: server offline, DEP8 tests fail
Processing commands for cont...@bugs.debian.org: > severity 1017070 serious Bug #1017070 [python-etelemetry] python-etelemetry: server offline, DEP8 tests fail Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017434: speedtest-cli: error message "Cannot retrieve speedtest configuration"
Package: speedtest-cli Version: 2.1.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, Attempts to run the package from several Debian 11.4 systems produces: farfalle$ speedtest --csv Cannot retrieve speedtest configuration ERROR: HTTP Error 403: Forbidden farfalle$ (Attempts to run from Debian 10.12 in another country show only cosmetic differences from this behaviour.) This is a relatively recent change in behaviour and, as such, I think it more likely to be caused by the server speedtest is talking to. I tried also '--simple' and '--list' but the results are the same. -- System Information: Debian Release: 11.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-17-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages speedtest-cli depends on: ii ca-certificates20210119 ii python33.9.2-3 ii python3-pkg-resources 52.0.0-4 speedtest-cli recommends no packages. speedtest-cli suggests no packages. -- no debconf information
Bug#1016343: marked as done (pgloader: FTBFS: make[2]: *** [Makefile:125: regress/out/csv-districts.out] Error 1)
Your message dated Tue, 16 Aug 2022 10:41:52 +0200 with message-id and subject line Re: Bug#1016343: pgloader: FTBFS: make[2]: *** [Makefile:125: regress/out/csv-districts.out] Error 1 has caused the Debian Bug report #1016343, regarding pgloader: FTBFS: make[2]: *** [Makefile:125: regress/out/csv-districts.out] Error 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.) -- 1016343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgloader Version: 3.6.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/test' > dropdb -U user42 pgloader > dropdb: error: database removal failed: ERROR: database "pgloader" does not > exist > make[2]: [Makefile:67: prepare] Error 1 (ignored) > dropdb -U user42 stocks > dropdb: error: database removal failed: ERROR: database "stocks" does not > exist > make[2]: [Makefile:68: prepare] Error 1 (ignored) > dropdb -U user42 ip4r > dropdb: error: database removal failed: ERROR: database "ip4r" does not exist > make[2]: [Makefile:69: prepare] Error 1 (ignored) > createuser -U user42 --superuser `whoami` > createdb -U user42 -O `whoami` pgloader > createdb -U user42 -O `whoami` stocks > createdb -U user42 -O `whoami` ip4r > psql -d pgloader -c 'create schema expected' > CREATE SCHEMA > psql -U user42 -d pgloader -c 'create extension ip4r' > CREATE EXTENSION > psql -U user42 -d ip4r -c 'create extension ip4r' > CREATE EXTENSION > psql -d stocks -f bossa.sql > psql:bossa.sql:7: NOTICE: table "intf_derivatives" does not exist, skipping > psql:bossa.sql:7: NOTICE: table "intf_stocks" does not exist, skipping > DROP TABLE > CREATE TABLE > CREATE TABLE > rm -f regress/out/* > pgloader --regress allcols.load > 2022-07-29T09:27:36.012000Z LOG pgloader version "3.6.3~devel" > 2022-07-29T09:27:36.016000Z LOG Parsing commands from file > #P"/<>/test/allcols.load" > 2022-07-29T09:27:36.048000Z WARNING pgloader always talk to PostgreSQL in > utf-8, client_encoding has been forced to 'utf8'. > 2022-07-29T09:27:36.156000Z WARNING Target table "\"public\".\"allcols\"" has > 1 indexes defined against it. > 2022-07-29T09:27:36.156000Z WARNING That could impact loading performance > badly. > 2022-07-29T09:27:36.156000Z WARNING Consider the option 'drop indexes'. > 2022-07-29T09:27:36.212000Z WARNING pgloader always talk to PostgreSQL in > utf-8, client_encoding has been forced to 'utf8'. > 2022-07-29T09:27:36.216000Z LOG Comparing loaded data against > (#P"/<>/test/regress/expected/allcols.out") > 2022-07-29T09:27:36.22Z WARNING PostgreSQL warning: table "allcols" does > not exist, skipping > 2022-07-29T09:27:36.26Z LOG report summary reset > table name errors rows bytes total time > --- - - - -- > fetch 0 0 0.004s > before load 0 2 0.008s > --- - - - -- > "public"."allcols" 0 8 0.2 kB 0.024s >"expected"."allcols" 0 8 0.2 kB 0.004s > --- - - - -- > Files Processed 0 2 0.024s > COPY Threads Completion 0 4 0.028s > --- - - - -- > Total import time ✓ 16 0.4 kB 0.052s > 2022-07-29T09:27:36.292000Z LOG Regress pass. > touch regress/out/allcols.out > pgloader --regress csv-before-after.load > 2022-07-29T09:27:37.008000Z LOG pgloader version "3.6.3~devel" > 2022-07-29T09:27:37.34Z LOG Comparing loaded data against > (#P"/<>/test/regress/expected/csv-before-after.out") > 2022-07-29T09:27:37.34Z WARNING PostgreSQL warning: table "blocks" does > not exist, skipping > 2022-07-29T09:27:37.428000Z LOG report summary reset > table name errors rows bytes total time > --- - - - -- > fetch 0 0 0.004s > before load 0 6 0.008s >
Processed: reassign 1016309 to acorn, affects 1016309, fixed 1016309 in 8.8.0+ds+~cs24.17.6-2, closing 1016309
Processing commands for cont...@bugs.debian.org: > reassign 1016309 acorn Bug #1016309 [src:node-astw] node-astw: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Bug reassigned from package 'src:node-astw' to 'acorn'. No longer marked as found in versions node-astw/2.2.0-8. Ignoring request to alter fixed versions of bug #1016309 to the same values previously set > affects 1016309 node-astw Bug #1016309 [acorn] node-astw: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added indication that 1016309 affects node-astw > fixed 1016309 8.8.0+ds+~cs24.17.6-2 Bug #1016309 [acorn] node-astw: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 There is no source info for the package 'acorn' at version '8.8.0+ds+~cs24.17.6-2' with architecture '' Unable to make a source version for version '8.8.0+ds+~cs24.17.6-2' Marked as fixed in versions 8.8.0+ds+~cs24.17.6-2. > close 1016309 Bug #1016309 [acorn] node-astw: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1016309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017328: marked as done (arduino-ctags: FTBFS: cdefs.h:310:61: error: missing ')' after "__has_attribute")
Your message dated Tue, 16 Aug 2022 08:34:35 +
with message-id
and subject line Bug#1017328: fixed in arduino-ctags 5.8-arduino11-2
has caused the Debian Bug report #1017328,
regarding arduino-ctags: FTBFS: cdefs.h:310:61: error: missing ')' after
"__has_attribute"
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.)
--
1017328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arduino-ctags
Version: 5.8-arduino11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -I. -I../.. -DHAVE_CONFIG_H -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -c ../../c.c
> In file included from /usr/include/features.h:489,
> from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/stdio.h:27,
> from ../../args.c:17:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:310:61: error: missing ')' after
> "__has_attribute"
> 310 | #if __GNUC_PREREQ (2,7) || __glibc_has_attribute (__unused__)
> | ^
> In file included from /usr/include/features.h:489,
> from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/string.h:26,
> from ../../ant.c:17:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:310:61: error: missing ')' after
> "__has_attribute"
> 310 | #if __GNUC_PREREQ (2,7) || __glibc_has_attribute (__unused__)
> | ^
> ../../general.h:60:36: error: missing binary operator before token "("
>60 | # define __unused__ __attribute__((unused))
> |^
> In file included from /usr/include/features.h:489,
> from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/string.h:26,
> from ../../asm.c:18:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:310:61: error: missing ')' after
> "__has_attribute"
> 310 | #if __GNUC_PREREQ (2,7) || __glibc_has_attribute (__unused__)
> | ^
> ../../general.h:60:36: error: missing binary operator before token "("
>60 | # define __unused__ __attribute__((unused))
> |^
> In file included from /usr/include/features.h:489,
> from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/string.h:26,
> from ../../asp.c:18:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:310:61: error: missing ')' after
> "__has_attribute"
> 310 | #if __GNUC_PREREQ (2,7) || __glibc_has_attribute (__unused__)
> | ^
> ../../general.h:60:36: error: missing binary operator before token "("
>60 | # define __unused__ __attribute__((unused))
> |^
> In file included from /usr/include/features.h:489,
> from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/string.h:26,
> from ../../awk.c:17:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:310:61: error: missing ')' after
> "__has_attribute"
> 310 | #if __GNUC_PREREQ (2,7) || __glibc_has_attribute (__unused__)
> | ^
> ../../general.h:60:36: error: missing binary operator before token "("
>60 | # define __unused__ __attribute__((unused))
> |^
> In file included from /usr/include/features.h:489,
> from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/string.h:26,
> from ../../basic.c:20:
> /usr/include/x86_64-linux-gnu/sys/cdefs.h:310:61: error: missing ')' after
> "__has_attribute"
> 310 | #if __GNUC_PREREQ (2,7) || __glibc_has_attribute (__unused__)
> | ^
> ../../general.h:60:36: error: missing binary operator before token "("
>60 | # define __unused__ __attribute__((unused))
> |
Bug#1017432: horizon-eda: zmq.hpp now in cppzmq-dev
Source: horizon-eda Version: 2.2.0-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: stephanlach...@debian.org The zmq.hpp header moved from libzmq3-dev to cppzmq-dev. To fix this just replace libzmq3-dev with cppzmq-dev in d/control. Regards, Stephan -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1012909: marked as done (darkradiant: ftbfs with GCC-12)
Your message dated Tue, 16 Aug 2022 07:48:55 + with message-id and subject line Bug#1012909: fixed in darkradiant 2.14.0-5 has caused the Debian Bug report #1012909, regarding darkradiant: ftbfs with GCC-12 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.) -- 1012909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:darkradiant Version: 2.14.0-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/darkradiant_2.14.0-4_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cd /<>/obj-x86_64-linux-gnu/radiant && /usr/bin/c++ -DFMT_HEADER_ONLY -DHAVE_CONFIG_H -DHAVE_STD_FILESYSTEM -DPOSIX -DWXINTL_NO_GETTEXT_MACRO -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/libs -I/<>/libs/libfmt -I/<>/include -I/<>/obj-x86_64-linux-gnu -I/<>/radiant/. -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem /usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/eigen3 -I/usr/include/libxml2 -I/usr/include/FTGL -fPIC -std=gnu++17 -Winvalid-pch -include /<>/obj-x86_64-linux-gnu/radiant/CMakeFiles/darkradiant.dir/cmake_pch.hxx -MD -MT radiant/CMakeFil es/darkradiant.dir/ui/PointFileChooser.cpp.o -MF CMakeFiles/darkradiant.dir/ui/PointFileChooser.cpp.o.d -o CMakeFiles/darkradiant.dir/ui/PointFileChooser.cpp.o -c /<>/radiant/ui/PointFileChooser.cpp [ 76%] Building CXX object radiant/CMakeFiles/darkradiant.dir/ui/prefabselector/PrefabSelector.cpp.o cd /<>/obj-x86_64-linux-gnu/radiant && /usr/bin/c++ -DFMT_HEADER_ONLY -DHAVE_CONFIG_H -DHAVE_STD_FILESYSTEM -DPOSIX -DWXINTL_NO_GETTEXT_MACRO -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/libs -I/<>/libs/libfmt -I/<>/include -I/<>/obj-x86_64-linux-gnu -I/<>/radiant/. -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem /usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/eigen3 -I/usr/include/libxml2 -I/usr/include/FTGL -fPIC -std=gnu++17 -Winvalid-pch -include /<>/obj-x86_64-linux-gnu/radiant/CMakeFiles/darkradiant.dir/cmake_pch.hxx -MD -MT radiant/CMakeFil es/darkradiant.dir/ui/prefabselector/PrefabSelector.cpp.o -MF CMakeFiles/darkradiant.dir/ui/prefabselector/PrefabSelector.cpp.o.d -o CMakeFiles/darkradiant.dir/ui/prefabselector/PrefabSelector.cpp.o -c /<>/radiant/ui/prefabselector/PrefabSelector.cpp [ 76%] Building CXX object radiant/CMakeFiles/darkradiant.dir/ui/prefdialog/GameSetupDialog.cpp.o cd /<>/obj-x86_64-linux-gnu/radiant && /usr/bin/c++ -DFMT_HEADER_ONLY -DHAVE_CONFIG_H -DHAVE_STD_FILESYSTEM -DPOSIX -DWXINTL_NO_GETTEXT_MACRO -DWXUSINGDLL -D_FILE_OFFSE
