Processed (with 5 errors): your mail
Processing commands for cont...@bugs.debian.org: > tags #995212 security fixed upstream Bug #995212 [chromium] chromium: Update to version 94.0.4606.61 (security-fixes) Added tag(s) upstream, security, and fixed. > severity #995212 critical Bug #995212 [chromium] chromium: Update to version 94.0.4606.61 (security-fixes) Severity set to 'critical' from 'normal' > security vulnerabilities with critical risk: Unknown command or malformed arguments to command. > CVE-2021-37974 Unknown command or malformed arguments to command. > CVE-2021-37975 Unknown command or malformed arguments to command. > CVE-2021-37976 Unknown command or malformed arguments to command. > https://www.cybersecurity-help.cz/vdb/SB2021093018 Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 995212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997530:
Hi Lucas, Thanks for reporting! I've investigated this and found that the error comes from building against a version of the package "cv_bridge" (libcv-bridge-dev) which wasn't yet rebuilt against the latest opencv 4.5.4, but for the older 4.5.3. Does this still qualify as a FTBFS error in mrpt? "libcv-bridge-dev" is already listed in d/control... (?). Best, JL
Bug#997507: marked as done (unburden-home-dir: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2)
Your message dated Sun, 24 Oct 2021 03:18:47 + with message-id and subject line Bug#997507: fixed in unburden-home-dir 0.4.1.3 has caused the Debian Bug report #997507, regarding unburden-home-dir: FTBFS: dh_auto_test: error: make -j4 test returned exit code 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.) -- 997507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unburden-home-dir Version: 0.4.1.2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > perl -c bin/unburden-home-dir > checkbashisms Xsession.d/* share/*.sh > script Xsession.d/25unburden-home-dir-xdg does not appear to have a #! > interpreter line; > you may get strange results > bin/unburden-home-dir syntax OK > prove -j4 t/*.t > script Xsession.d/95unburden-home-dir does not appear to have a #! > interpreter line; > you may get strange results > script share/common.sh does not appear to have a #! interpreter line; > you may get strange results > t/check-symlinks-without-trailing-slash.t .. ok > t/create-empty-directories-dryrun.t ok > t/create-empty-directories.t ... ok > t/check-symlinks-in-path.t . ok > t/create-empty-files-dryrun.t .. ok > t/create-empty-files.t . ok > t/emptying-directory.t . ok > t/emptying-directory-dryrun.t .. ok > t/emptying-file-dryrun.t ... ok > t/emptying-file.t .. ok > t/help-option.t ok > t/expand_environment_variables.t ... ok > t/filter.t . ok > t/find-per-user-stuff.t ok > t/lsof-force.t . ok > t/lsof.t ... ok > t/moving-to-existing-subdir.t .. ok > t/replacement-order-dryrun.t ... ok > t/parse-comments-and-blank-lines.t . ok > t/replacement-order.t .. ok > t/trailing-blanks.t ok > t/skip-non-home.t .. ok > t/undo-dryrun.t ok > t/undo-unexpected-symlink-target.t . ok > t/undo.t ... ok > t/version.t ok > > # Failed test 'Call '/bin/run-parts --list t/ZngWxktU0h/Xsession.d'' > # at t/lib/Test/UBH.pm line 164. > > # Failed test 'Check run-parts STDERR' > # at t/lib/Test/UBH.pm line 285. > # --- Got > # +++ Expected > # @@ -1,2 +1 @@ > # -'sh: 1: /bin/run-parts: not found > # +'' > # -' > > # Failed test 'Check run-parts STDOUT' > # at t/lib/Test/UBH.pm line 285. > # --- Got > # +++ Expected > # @@ -1 +1,2 @@ > # -'' > # +'t/ZngWxktU0h/Xsession.d/25unburden-home-dir-xdg > # +' > # Looks like you failed 3 tests of 25. > t/xsession-d-xdg.t . > Dubious, test returned 3 (wstat 768, 0x300) > Failed 3/25 subtests > > # Failed test 'Call '/bin/run-parts --list t/abWhCGhjXC/Xsession.d'' > # at t/lib/Test/UBH.pm line 164. > > # Failed test 'Check run-parts STDERR' > # at t/lib/Test/UBH.pm line 285. > # --- Got > # +++ Expected > # @@ -1,2 +1 @@ > # -'sh: 1: /bin/run-parts: not found > # +'' > # -' > > # Failed test 'Check run-parts STDOUT' > # at t/lib/Test/UBH.pm line 285. > # --- Got > # +++ Expected > # @@ -1 +1,2 @@ > # -'' > # +'t/abWhCGhjXC/Xsession.d/95unburden-home-dir > # +' > # Looks like you failed 3 tests of 25. > t/xsession-d.t . > Dubious, test returned 3 (wstat 768, 0x300) > Failed 3/25 subtests > t/perlcritic.t . ok > t/unexpected-cases.t ... ok > > Test Summary Report > --- > t/xsession-d-xdg.t (Wstat: 768 Tests: 25 Failed: 3) > Failed tests: 10-11, 13 > Non-zero exit status: 3 > t/xsession-d.t (Wstat: 768 Tests: 25 Failed: 3) > Failed tests: 10-11, 13 > Non-zero exit status: 3 > Files=30, Tests=546,
Bug#997488: [Debian-med-packaging] Bug#997488: q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: tags -1 + confirmed
Aloha,
From looking up ci.debian.net [1], this q2cli issue seems
related to a recent upgrade of python-click 8.0.2.
[1]: https://ci.debian.net/packages/q/q2cli/testing/amd64/
The multiple failures are probably all related to the following
issue, which can be simply triggered with the --version flag:
$ qiime --version
Traceback (most recent call last):
File "/usr/bin/qiime", line 33, in
sys.exit(load_entry_point('q2cli==2021.8.0', 'console_scripts',
'qiime')())
File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in
__call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1050, in
main
with self.make_context(prog_name, args, **extra) as ctx:
File "/usr/lib/python3/dist-packages/click/core.py", line 912, in
make_context
self.parse_args(ctx, args)
File "/usr/lib/python3/dist-packages/q2cli/click/command.py", line
43, in parse_args
return super().parse_args(ctx, args)
File "/usr/lib/python3/dist-packages/click/core.py", line 1613, in
parse_args
rest = super().parse_args(ctx, args)
File "/usr/lib/python3/dist-packages/click/core.py", line 1364, in
parse_args
parser = self.make_parser(ctx)
File "/usr/lib/python3/dist-packages/q2cli/click/command.py", line
33, in make_parser
param.add_to_parser(parser, ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 2639, in
add_to_parser
parser.add_option(
File "/usr/lib/python3/dist-packages/q2cli/click/parser.py", line
126, in add_option
option = Q2Option(opts, dest, action=action, nargs=nargs,
TypeError: __init__() got multiple values for argument 'obj'
Have a good night, :)
--
Étienne Mollier
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from my alarm clock
signature.asc
Description: PGP signature
Processed: Re: Bug#997031: nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup
Processing control commands: > found -1 11.2.152~11.2.2-3 Bug #997031 [nvidia-cuda-gdb] nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup Marked as found in versions nvidia-cuda-toolkit/11.2.2-3. > found -1 11.3.109~11.3.1-4 Bug #997031 [nvidia-cuda-gdb] nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup Marked as found in versions nvidia-cuda-toolkit/11.3.1-4. > retitle -1 nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if > libpython2.7 is installed Bug #997031 [nvidia-cuda-gdb] nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup Changed Bug title to 'nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if libpython2.7 is installed' from 'nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup'. -- 997031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997031: nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup
Control: found -1 11.2.152~11.2.2-3 Control: found -1 11.3.109~11.3.1-4 Control: retitle -1 nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if libpython2.7 is installed On 22/10/2021 19.11, Tim Trant wrote: "gdb /usr/bin/cuda-gdb" and "strings /usr/bin/cuda-gdb" suggest that there's a hidden use of libpython2.7.so.1 which is failing. cuda-gdb is (after some patching) built against python3, but nvidia has made changes that attempt to dlopen the libpythonX.Y.so.1, but only for 2.Y. So if libpython2.7 is installed, it will crash, since 2.7 and 3.x do not seem to be binary compatible. If it is not installed, python support will simply not work. In experimental (based on gdb 10.1) it does at least not segfault, but python seems to work neither. At least for stable (and propagating to oldstable-backports) I'll just build without python support ... Andreas
Bug#997325: [Debian-med-packaging] Bug#997325: python-sqlsoup: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13
Control: tag -1 confirmed Greetings, Lucas Nussbaum, on 2021-10-23: > > Failure: ImportError (cannot import name 'MapperExtension' from > > 'sqlalchemy.orm.interfaces' > > (/usr/lib/python3/dist-packages/sqlalchemy/orm/interfaces.py)) ... ERROR This one has the same symptom as the autopkgtest failure documented in #995781, although not at the same stage. I'm tempted to merge both, as once the issue is fixed on one end, the other one will be fixed as well. The most likely outcome is that the package drops from Testing though, given that a fix seems non-trivial, and the package is not maintained upstream any more. Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
I have now 'patched' the upstream setting of GSL_AGE, this results (as kindly analysed by Sebastian) in new sonames '26' so I prepared a new version which just went out to unstable. Unless I am mistaken, I need to get the release team on board for a proper transition. Correct? Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#997238: lordsawar: FTBFS: gatomic.h:113:19: error: argument 2 of ‘__atomic_load’ must not be a pointer to a ‘volatile’ type
On Sat, 23 Oct 2021 at 21:53:34 +0100, Simon McVittie wrote:
> I suspect that applying the change from
> https://gitlab.gnome.org/GNOME/gstreamermm/-/merge_requests/4 in
> gstreamermm-1.0 would allow lordsawar to be built successfully against it
> (test-builds in progress).
Yes, confirmed via a test-build of lordsawar. Please consider the attached
patch.
smcv
>From 699d47eb51831b207a749e4351e3ebc7285a749b Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Sat, 23 Oct 2021 21:51:27 +0100
Subject: [PATCH] Add patch from upstream to fix FTBFS of dependent packages
This misuse of 'volatile' caused build failures triggered by gcc 11
and/or GLib 2.68.
Closes: #997238
---
.../patches/Fix-build-against-glib-2.68.patch | 41 +++
debian/patches/series | 1 +
2 files changed, 42 insertions(+)
create mode 100644 debian/patches/Fix-build-against-glib-2.68.patch
diff --git a/debian/patches/Fix-build-against-glib-2.68.patch b/debian/patches/Fix-build-against-glib-2.68.patch
new file mode 100644
index 000..2048840
--- /dev/null
+++ b/debian/patches/Fix-build-against-glib-2.68.patch
@@ -0,0 +1,41 @@
+From: Dominique Leuenberger
+Date: Tue, 13 Jul 2021 10:32:30 +
+Subject: Fix build against glib 2.68
+
+volatile has been misused in the past
+
+Bug: https://gitlab.gnome.org/GNOME/gstreamermm/-/issues/11
+Bug-Debian: https://bugs.debian.org/997238
+Reference: https://gitlab.gnome.org/GNOME/glib/-/issues/600
+Reference: http://c.isvolatileusefulwiththreads.com/
+---
+ gstreamer/gstreamermm/register.h| 2 +-
+ tests/integration/test-integration-seekonstartup.cc | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/gstreamer/gstreamermm/register.h b/gstreamer/gstreamermm/register.h
+index db66d17..a7ab3a6 100644
+--- a/gstreamer/gstreamermm/register.h
b/gstreamer/gstreamermm/register.h
+@@ -110,7 +110,7 @@ register_mm_type(const gchar * type_name)
+ /* The typedef for GType may be gulong or gsize, depending on the
+ * system and whether the compiler is c++ or not. The g_once_init_*
+ * functions always take a gsize * though ... */
+-static volatile gsize gonce_data = 0;
++static gsize gonce_data = 0;
+ if (g_once_init_enter (_data)) {
+ GTypeInfo info;
+
+diff --git a/tests/integration/test-integration-seekonstartup.cc b/tests/integration/test-integration-seekonstartup.cc
+index 247ac49..cd43a12 100644
+--- a/tests/integration/test-integration-seekonstartup.cc
b/tests/integration/test-integration-seekonstartup.cc
+@@ -18,7 +18,7 @@ RefPtr mainloop;
+ RefPtr bus;
+ RefPtr pipeline;
+ RefPtr sink_pad;
+-static volatile gint counter;
++static gint counter;
+ bool prerolled = false;
+ gboolean was_check = 0;
+
diff --git a/debian/patches/series b/debian/patches/series
index 9a0a29d..3c80c41 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
01-disable-tests.patch
02-do-not-compile-examples.patch
+Fix-build-against-glib-2.68.patch
--
2.33.0
Bug#995968: marked as done (gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent)
Your message dated Sat, 23 Oct 2021 22:48:34 + with message-id and subject line Bug#995968: fixed in gkrellm-leds 0.8.0-1.4 has caused the Debian Bug report #995968, regarding gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent 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.) -- 995968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gkrellm-leds Version: 0.8.0-1.3+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: re...@cs.unibo.it Dear Maintainer, There is a shared library linking problem. Bugfix: add --no-as-needed linker option. --- gkrellm-leds-0.8.0/Makefile 2021-10-09 10:28:38.0 +0200 +++ gkrellm-leds-0.8.0.fix/Makefile 2021-10-09 10:31:35.547270111 +0200 @@ -8,7 +8,7 @@ LIBS = $(GTK_LIB) $(X11_LIB) DEFINES = -LFLAGS = -shared +LFLAGS = -shared -Wl,--no-as-needed INCLUDES = $(GTK_INCLUDE) CFLAGS = -ansi -pedantic -Wall -O2 -fPIC CC = gcc -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gkrellm-leds depends on: ii gkrellm 2.3.11-2 ii libc62.32-4 gkrellm-leds recommends no packages. gkrellm-leds suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gkrellm-leds Source-Version: 0.8.0-1.4 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of gkrellm-leds, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated gkrellm-leds 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, 18 Oct 2021 23:33:29 +0200 Source: gkrellm-leds Architecture: source Version: 0.8.0-1.4 Distribution: unstable Urgency: medium Maintainer: Mike Markley Changed-By: Christoph Biedl Closes: 995968 Changes: gkrellm-leds (0.8.0-1.4) unstable; urgency=medium . * Non-maintainer upload * Fix startup error, thanks Renzo Davoli. Closes: #995968 Checksums-Sha1: 8fe0390e238e644db5d51ebbe2d4a015b797746c 1760 gkrellm-leds_0.8.0-1.4.dsc 0e04ed009de9487533d395d9ab5fe0e2ae3f7778 2342 gkrellm-leds_0.8.0-1.4.diff.gz 32d6d7548e06e661d3ffa58eec81b2055792c0b4 10988 gkrellm-leds_0.8.0-1.4_powerpc.buildinfo Checksums-Sha256: 6dd5d0ffb69346560806fe330fe4028540d7f45ca6ee20120886ad67932edb61 1760 gkrellm-leds_0.8.0-1.4.dsc f11940246c30d98555689a5b313d1c296d0e6e750bca04031a709410115b0710 2342 gkrellm-leds_0.8.0-1.4.diff.gz 3c7beb21455cc13dc121515a05249cd0ada6878f1c0db1bb857575d224a9b8fa 10988 gkrellm-leds_0.8.0-1.4_powerpc.buildinfo Files: cdc0997189c33f58cd13114c65ab93b7 1760 x11 extra gkrellm-leds_0.8.0-1.4.dsc e13e83149b328652e49e1743d337d055 2342 x11 extra gkrellm-leds_0.8.0-1.4.diff.gz 214b8c515ff0fcd497fbdd85d7f5d047 10988 x11 extra gkrellm-leds_0.8.0-1.4_powerpc.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmFt8KAACgkQxCxY61kU kv3yXBAAmGHhBXCCgmRVBvA3XfXuysIPt6odj1gpK3oxReTk2ZU6PVKtxDDMCa1h gFhqlOL0QDY+Qqk6QtN7syCbUrSLQ9+q+n/WBd3hwS8DLBLfzsgQZUWxqhKTI/1h YQLq3dqqOWG3sBTWyylWMVzY1So1Sq2BBvi5C//mm7XeGue371iTi3tjxUeaYUAh ogpfB7RtAeMh/WHykkIotcROHSxjUF+56SrKue1NCAFI7f9XvIDpk8hWhGuDPs+j QLqLgx6pRcPcqHq+biqhNfhO+O/Yul6aJWrM2YHPhZFj8cm2uOXow6YIYKYcspRF g/xIzOji5VbJHTn8UNBzSw84c7xR77pqsu9xqG4DsG7VIRmam5CaKMf+HZGqTKOI 4K9CWrLd2efEZUbNVS+3YdSwKrwatfVzHrCKe2mUj02aQrF43tVN5Cxx7Se1NF5o zNyJZchxeAGOtipRS4LqABWXKQBMoFBIMaAgkVS/uca8tiNJ48ExSx+QNfbSLiXU a343SB0Zsc2sO9Q1QGAmv/psBv+Xt2dEBKbzgHwHrXrfeEmnS8xmI4nSILCPHYpH HiIKctPLyKNAWnGdL/y5MkplXbqhqRSG6lJmpsQsSmP7QjlNhWCZTvVJmu/pw01O ZGAvQQdR9GxWDkIOvPnBX+5TyGmjeTqGgrDS7FZz479kOJqKX0s=
Processed: Re: [Debian-med-packaging] Bug#997488: q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> tags -1 + confirmed
Bug #997488 [src:q2cli] q2cli: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) confirmed.
--
997488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997240: lives: FTBFS: htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file or directory
The line causing the error message can safely be removed as it is
redundant. The correction appears in the most recent stable release, 3.2.0
On Sat, 23 Oct 2021, 16:24 Lucas Nussbaum, wrote:
> Source: lives
> Version: 3.0.2-1.1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > gcc -DPACKAGE_NAME=\"LiVES\" -DPACKAGE_TARNAME=\"lives\"
> -DPACKAGE_VERSION=\"3.0.2\" -DPACKAGE_STRING=\"LiVES\ 3.0.2\"
> -DPACKAGE_BUGREPORT=\"https://github.com/salsaman/LiVES/issues\;
> -DPACKAGE_URL=\"http://lives-video.com\; -DPACKAGE=\"lives\"
> -DVERSION=\"3.0.2\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1
> -DHAVE_SYS_PARAM_H=1 -DSTDC_HEADERS=1 -D_ALL_SOURCE=1 -D_DARWIN_C_SOURCE=1
> -D_GNU_SOURCE=1 -D_HPUX_ALT_XOPEN_SOCKET_API=1 -D_NETBSD_SOURCE=1
> -D_OPENBSD_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1
> -D__STDC_WANT_IEC_60559_ATTRIBS_EXT__=1 -D__STDC_WANT_IEC_60559_BFP_EXT__=1
> -D__STDC_WANT_IEC_60559_DFP_EXT__=1 -D__STDC_WANT_IEC_60559_FUNCS_EXT__=1
> -D__STDC_WANT_IEC_60559_TYPES_EXT__=1 -D__STDC_WANT_LIB_EXT2__=1
> -D__STDC_WANT_MATH_SPEC_FUNCS__=1 -D_TANDEM_SOURCE=1 -D__EXTENSIONS__=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_PTHREAD_PRIO_INHERIT=1
> -DHAVE_PTHREAD=1 -DGETTEXT_PACKAGE=\"lives\"
> -DLOCALEDIR=\"\$\{datarootdir\}/locale\" -DPREFIX=\"/usr\"
> -DLiVES_VERSION=\"3.0.2\" -DHAVE_VISIBILITY=1
> -DHAVE_STDINT_H_WITH_UINTMAX=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1
> -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DINTDIV0_RAISES_SIGFPE=1
> -DHAVE_INTTYPES_H_WITH_UINTMAX=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1
> -DHAVE_UINTMAX_T=1 -DHAVE_INTTYPES_H=1 -DUSE_POSIX_THREADS=1
> -DUSE_POSIX_THREADS_WEAK=1 -DHAVE_PTHREAD_RWLOCK=1
> -DHAVE_PTHREAD_MUTEX_RECURSIVE=1 -DHAVE_BUILTIN_EXPECT=1 -DHAVE_ARGZ_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_SYS_PARAM_H=1 -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1
> -DHAVE_GETGID=1 -DHAVE_GETUID=1 -DHAVE_MEMPCPY=1 -DHAVE_MUNMAP=1
> -DHAVE_STPCPY=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRTOUL=1
> -DHAVE_TSEARCH=1 -DHAVE_ARGZ_COUNT=1 -DHAVE_ARGZ_STRINGIFY=1
> -DHAVE_ARGZ_NEXT=1 -DHAVE___FSETLOCKING=1 -DHAVE_DECL_FEOF_UNLOCKED=1
> -DHAVE_DECL_FGETS_UNLOCKED=1 -DHAVE_ICONV=1 -DICONV_CONST=
> -DHAVE_NL_LOCALE_NAME=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_WCHAR_T=1
> -DHAVE_WINT_T=1 -DHAVE_INTMAX_T=1 -DHAVE_POSIX_PRINTF=1 -DHAVE_STDINT_H=1
> -DHAVE_STDINT_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_ASPRINTF=1 -DHAVE_FWPRINTF=1 -DHAVE_PUTENV=1 -DHAVE_SETENV=1
> -DHAVE_SETLOCALE=1 -DHAVE_SNPRINTF=1 -DHAVE_WCSLEN=1
> -DHAVE_DECL__SNPRINTF=0 -DHAVE_DECL__SNWPRINTF=0
> -DHAVE_DECL_GETC_UNLOCKED=1 -DHAVE_LANGINFO_CODESET=1 -DHAVE_LC_MESSAGES=1
> -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DHAVE_LIBDL=1
> -DHAVE_POSIX_MEMALIGN=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_POSIX_FALLOCATE=1
> -DHAVE_SYS_PRCTL_H=1 -DHAVE_LINUX_JOYSTICK_H=1 -DHAVE_JACK_JACK_H=1
> -DHAVE_JACK_TRANSPORT_H=1 -DHAVE_LINUX_VIDEODEV2_H=1 -DHAVE_FREI0R_H=1
> -DHAVE_LIBRAW1394_RAW1394_H=1 -DHAVE_LIBAVC1394_AVC1394_H=1
> -DHAVE_LIBAVC1394_ROM1394_H=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I..
> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -fcommon -Wall -c -o sendOSC-sendOSC.o
> `test -f 'sendOSC.c' || echo './'`sendOSC.c
> > htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file or directory
> >41 | #include
> > | ^~~
> > compilation terminated.
> > make[3]: *** [Makefile:605: sendOSC-htmsocket.o] Error 1
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2021/10/23/lives_3.0.2-1.1_unstable.log
>
> 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.
>
>
Bug#997275: marked as done (sundials: FTBFS: ld: cannot find -lHYPRE_core)
Your message dated Sun, 24 Oct 2021 00:21:38 +0200 with message-id and subject line sundials hypre has caused the Debian Bug report #997275, regarding sundials: FTBFS: ld: cannot find -lHYPRE_core 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.) -- 997275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sundials Version: 5.7.0+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DCMAKE_Fortran_COMPILER=gfortran > -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_STATIC_LIBS:BOOL=ON > -DBUILD_FORTRAN77_INTERFACE:BOOL=ON -DENABLE_MPI:BOOL=ON > -DENABLE_LAPACK:BOOL=OFF -DEXAMPLES_ENABLE_C:BOOL=ON > -DEXAMPLES_ENABLE_CXX:BOOL=ON -DEXAMPLES_ENABLE_F77:BOOL=ON > -DEXAMPLES_INSTALL:BOOL=ON -DENABLE_OPENMP:BOOL=ON -DENABLE_PTHREAD:BOOL=ON > -DENABLE_KLU:BOOL=ON -DKLU_INCLUDE_DIR=/usr/include/suitesparse > -DKLU_LIBRARY_DIR=/usr/lib/x86_64-linux-gnu -DENABLE_PETSC:BOOL=ON > -DENABLE_HYPRE:BOOL=ON -DHYPRE_INCLUDE_DIR=/usr/include/hypre > -DHYPRE_LIBRARY=-lHYPRE_core -DCMAKE_C_FLAGS=-fcommon > -DENABLE_SUPERLUMT:BOOL=OFF > cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_Fortran_COMPILER=gfortran -DBUILD_SHARED_LIBS:BOOL=ON > -DBUILD_STATIC_LIBS:BOOL=ON -DBUILD_FORTRAN77_INTERFACE:BOOL=ON > -DENABLE_MPI:BOOL=ON -DENABLE_LAPACK:BOOL=OFF -DEXAMPLES_ENABLE_C:BOOL=ON > -DEXAMPLES_ENABLE_CXX:BOOL=ON -DEXAMPLES_ENABLE_F77:BOOL=ON > -DEXAMPLES_INSTALL:BOOL=ON -DENABLE_OPENMP:BOOL=ON -DENABLE_PTHREAD:BOOL=ON > -DENABLE_KLU:BOOL=ON -DKLU_INCLUDE_DIR=/usr/include/suitesparse > -DKLU_LIBRARY_DIR=/usr/lib/x86_64-linux-gnu -DENABLE_PETSC:BOOL=ON > -DENABLE_HYPRE:BOOL=ON -DHYPRE_INCLUDE_DIR=/usr/include/hypre > -DHYPRE_LIBRARY=-lHYPRE_core -DCMAKE_C_FLAGS=-fcommon > -DENABLE_SUPERLUMT:BOOL=OFF ../.. > -- The C compiler identification is GNU 11.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Looking for sys/types.h > -- Looking for sys/types.h - found > -- Looking for stdint.h > -- Looking for stdint.h - found > -- Looking for stddef.h > -- Looking for stddef.h - found > -- Check size of int64_t > -- Check size of int64_t - done > -- Using int64_t for indices > -- The Fortran compiler identification is GNU 11.2.0 > -- Detecting Fortran compiler ABI info > -- Detecting Fortran compiler ABI info - done > -- Check for working Fortran compiler: /usr/bin/gfortran - skipped > -- Checking whether /usr/bin/gfortran supports Fortran 90 > -- Checking whether /usr/bin/gfortran supports Fortran 90 - yes > -- Determining Fortran name-mangling scheme... OK > -- The CXX compiler identification is GNU 11.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- CXX standard set to 11 > CMake Warning (dev) at > /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:438 > (message): > The package name passed to `find_package_handle_standard_args` (PkgConfig) > does not match the name of the calling package (MPI). This can lead to > problems in calling code that expects `find_package` result variables > (e.g., `_FOUND`) to follow a certain pattern. > Call Stack (most recent call first): > /usr/share/cmake-3.21/Modules/FindPkgConfig.cmake:70 > (find_package_handle_standard_args) > /usr/share/cmake-3.21/Modules/FindMPI.cmake:270 (include) > cmake/tpl/SundialsMPI.cmake:71 (find_package) > cmake/SundialsSetupTPLs.cmake:22 (include) > CMakeLists.txt:171 (include) > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") > -- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found > suitable version "3.1",
Bug#996951: linux-image-5.14.0-3-amd64: iouring looses requests
Control: Forwarded -1 https://lore.kernel.org/linux-block/cabvffennj8jkp7etuutqi+vkjdbfu37w1uxe4q3cb7-ixxh...@mail.gmail.com/ On Saturday, 23 October 2021 23:29:21 CEST Daniel Black wrote: > https://marc.info/?l=linux-block=163489378723217=2 Looked up your upstream message on lore.k.o and set 'Forwarded' to that. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#996951: linux-image-5.14.0-3-amd64: iouring looses requests
Processing control commands: > Forwarded -1 > https://lore.kernel.org/linux-block/cabvffennj8jkp7etuutqi+vkjdbfu37w1uxe4q3cb7-ixxh...@mail.gmail.com/ Bug #996951 [src:linux] linux-image-5.14.0-3-amd64: iouring looses requests Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-block/cabvffennj8jkp7etuutqi+vkjdbfu37w1uxe4q3cb7-ixxh...@mail.gmail.com/'. -- 996951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997270: marked as done (ovn: FTBFS: | ./conftest.c:48: undefined reference to `pow')
Your message dated Sun, 24 Oct 2021 00:23:57 +0200
with message-id <08f39ab1-35cb-e1c7-5dd4-24fcae5d3...@debian.org>
and subject line Re: Bug#997270: ovn: FTBFS: | ./conftest.c:48: undefined
reference to `pow'
has caused the Debian Bug report #997270,
regarding ovn: FTBFS: | ./conftest.c:48: undefined reference to `pow'
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.)
--
997270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ovn
Version: 21.06.0+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> set /bin/bash './tests/testsuite' -C tests
> AUTOTEST_PATH=/<>/ovs/utilities:/<>/ovs/vswitchd:/<>/ovs/ovsdb:/<>/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic;
> \
> "$@" --recheck || \
> (test -z "$(find /<>/tests/testsuite.dir -name 'asan.*')" && \
> test X'' = Xyes && "$@" --recheck)
> ## --- ##
> ## ovn 21.06.0 test suite. ##
> ## --- ##
> 624: ovn -- ACL with Port Group conjunction flow efficiency -- ovn-northd --
> dp-groups=no FAILED (--wait=hv)
>
> ## - ##
> ## Test results. ##
> ## - ##
>
> ERROR: 1 test was run,
> 1 failed unexpectedly.
> ## -- ##
> ## testsuite.log was created. ##
> ## -- ##
>
> Please send `tests/testsuite.log' and all information you think might help:
>
>To:
>Subject: [ovn 21.06.0] testsuite: 624 failed
>
> You may investigate any problem if you feel able to do so, in which
> case the test suite provides a good starting point. Its output may
> be found below `tests/testsuite.dir'.
>
> make[4]: *** [Makefile:3432: check-local] Error 1
> make[4]: Leaving directory '/<>'
> make[3]: *** [Makefile:2732: check-am] Error 2
> make[3]: Leaving directory '/<>'
> make[2]: *** [Makefile:2734: check] Error 2
> make[2]: Leaving directory '/<>'
> ## --- ##
> ## ovn 21.06.0 test suite. ##
> ## --- ##
>
> testsuite: command line was:
> $ ./tests/testsuite -C tests
> AUTOTEST_PATH=/<>/ovs/utilities:/<>/ovs/vswitchd:/<>/ovs/ovsdb:/<>/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic
> --recheck
>
> ## - ##
> ## Platform. ##
> ## - ##
>
> hostname = ip-172-31-6-99
> uname -m = x86_64
> uname -r = 4.19.0-6-cloud-amd64
> uname -s = Linux
> uname -v = #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
>
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
>
> /bin/arch = unknown
> /usr/bin/arch -k = unknown
> /usr/convex/getsysinfo = unknown
> /usr/bin/hostinfo = unknown
> /bin/machine = unknown
> /usr/bin/oslevel = unknown
> /bin/universe = unknown
>
> PATH: /<>/ovs/utilities/
> PATH: /<>/ovs/vswitchd/
> PATH: /<>/ovs/ovsdb/
> PATH: /<>/ovs/vtep/
> PATH: /<>/tests/
> PATH: /<>/
> PATH: /<>/controller-vtep/
> PATH: /<>/northd/
> PATH: /<>/utilities/
> PATH: /<>/controller/
> PATH: /<>/ic/
> PATH: /usr/local/sbin/
> PATH: /usr/local/bin/
> PATH: /usr/sbin/
> PATH: /usr/bin/
> PATH: /sbin/
> PATH: /bin/
> PATH: /usr/games/
>
> testsuite: atconfig:
> | # Configurable variable values for building test suites.
> | # Generated by ./config.status.
> | # Copyright (C) 2021 Free Software Foundation, Inc.
> |
> | # The test suite will define top_srcdir=/../.. etc.
> | at_testdir='tests'
> | abs_builddir='/<>/tests'
> | at_srcdir='.'
> | abs_srcdir='/<>/tests'
> | at_top_srcdir='..'
> | abs_top_srcdir='/<>'
> | at_top_build_prefix='../'
> | abs_top_builddir='/<>'
> |
> | # Backward compatibility with Autotest <= 2.59b:
> | at_top_builddir=$at_top_build_prefix
> |
> |
> | EXEEXT=''
> | AUTOTEST_PATH='tests'
> |
> | SHELL=${CONFIG_SHELL-'/bin/bash'}
>
> testsuite: atlocal:
> | # -*- shell-script -*-
> | HAVE_OPENSSL='yes'
> | OPENSSL_SUPPORTS_SNI='yes'
> | HAVE_UNBOUND='yes'
> | EGREP='/bin/grep -E'
> |
> | if test x"$PYTHON3" = x; then
> | PYTHON3='/usr/bin/python3'
> | PYTHON='/usr/bin/python3'
> | # PYTHONCOERCECLOCALE=0 disables the Unicode compatibility warning on
> | # stderr that breaks almost any Python3 test (PEP 0538)
> | PYTHONCOERCECLOCALE=0
> | export PYTHONCOERCECLOCALE
> | fi
> |
> | PYTHONPATH=$ovs_srcdir/python:$abs_top_builddir/tests:$PYTHONPATH
> | export PYTHONPATH
> |
> | PYTHONIOENCODING=utf_8
> | export PYTHONIOENCODING
> |
> | #
Processed: tagging 997507
Processing commands for cont...@bugs.debian.org: > # Fsck usrmerge! > tags 997507 + pending Bug #997507 [src:unburden-home-dir] unburden-home-dir: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sundials hypre
Processing commands for cont...@bugs.debian.org: > fixed 997275 5.8.0+dfsg-1~exp1 Bug #997275 [src:sundials] sundials: FTBFS: ld: cannot find -lHYPRE_core The source 'sundials' and version '5.8.0+dfsg-1~exp1' do not appear to match any binary packages Marked as fixed in versions sundials/5.8.0+dfsg-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 997275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 997507
Processing commands for cont...@bugs.debian.org: > # Fsck usrmerge! > tags 997507 + confirmed Bug #997507 [src:unburden-home-dir] unburden-home-dir: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 997507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997146: marked as done (beautifulsoup4: FTBFS: error in beautifulsoup4 setup command: use_2to3 is invalid.)
Your message dated Sat, 23 Oct 2021 22:18:32 +
with message-id
and subject line Bug#997146: fixed in beautifulsoup4 4.10.0-1
has caused the Debian Bug report #997146,
regarding beautifulsoup4: FTBFS: error in beautifulsoup4 setup command:
use_2to3 is invalid.
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.)
--
997146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: beautifulsoup4
Version: 4.9.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in beautifulsoup4 setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/beautifulsoup4_4.9.3-1_unstable.log
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: beautifulsoup4
Source-Version: 4.10.0-1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
beautifulsoup4, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated beautifulsoup4
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: Sat, 23 Oct 2021 15:04:48 -0700
Source: beautifulsoup4
Architecture: source
Version: 4.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Stefano Rivera
Closes: 997146
Changes:
beautifulsoup4 (4.10.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #997146)
* Add upstream metadata.
* Switch watch file to PyPI, the author's home page is currently out of
date.
* Bump copyright years.
* Adjust autopkgtest to handle bs4.tests not being shipped in the installed
package.
* Bump Standards-Version to 4.6.0, no changes needed.
* Bump debhelper compat level to 13.
Checksums-Sha1:
a962785f9518478db6a788c7621bae94accecdc8 1749 beautifulsoup4_4.10.0-1.dsc
4fcafb012dd6dfad556dc144cffa64ee72ebe316 399890
beautifulsoup4_4.10.0.orig.tar.gz
f00218dc67f934b3ad8a27b5f70c2b659230f71c 6832
beautifulsoup4_4.10.0-1.debian.tar.xz
c950cf5188b1712f895b6107969c86bd5d386c68 6739
beautifulsoup4_4.10.0-1_source.buildinfo
Checksums-Sha256:
6c35918707f8dbdbf3e9102d24f371ba626f8a1c8397d4a151ce07923cfb4ec9 1749
beautifulsoup4_4.10.0-1.dsc
c23ad23c521d818955a4151a67d81580319d4bf548d3d49f4223ae041ff98891 399890
beautifulsoup4_4.10.0.orig.tar.gz
278e75a8743f4c173ccaef130e1c26696871c03d7b1939183543b4223297af7f 6832
beautifulsoup4_4.10.0-1.debian.tar.xz
3648b883290a48e1337490e03bab0a427c2fb5412137470b080180f8a685d87a 6739
beautifulsoup4_4.10.0-1_source.buildinfo
Files:
5f72b03eab0d3cac337d2265d0fe2f09 1749 python optional
beautifulsoup4_4.10.0-1.dsc
e754242642253dd31d249d00358d552e 399890 python optional
beautifulsoup4_4.10.0.orig.tar.gz
bf592ed6aa70797f8daa58135c30ad0c 6832 python optional
beautifulsoup4_4.10.0-1.debian.tar.xz
a6bcbe285d74ffd214c7becf155f296f 6739 python optional
beautifulsoup4_4.10.0-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYXSHJRQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2FBtAP9+hdf2iui6LNWZmt3wLkiKI8I9t6B7
Bug#997082: qemu: FTBFS: usb.c:200:23: error: array subscript ‘device_descriptor_t[0]’ is partly outside array bounds of ‘u8[8]’ {aka ‘unsigned char[8]’} [-Werror=array-bounds]
23.10.2021 19:33, Lucas Nussbaum wrote:
Source: qemu
Version: 1:6.1+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
powerpc64-linux-gnu-gcc $EXTRACFLAGS -m32 -mcpu=604 -msoft-float -fno-builtin-bcopy -fno-builtin-log2 -Os -g
-DNATIVE_BITWIDTH_EQUALS_HOST_BITWIDTH -USWAP_ENDIANNESS -Wall -Wredundant-decls -Wshadow -Wpointer-arith
-Wstrict-prototypes -Wmissing-declarations -Wundef -Wendif-labels -Wstrict-aliasing -Wwrite-strings
-Wmissing-prototypes -Wnested-externs -Werror -MMD -MP -MT target/drivers/usbohci_rh.o -MF
'target/drivers/usbohci_rh.d' -I/<>/roms/openbios/include
-I/<>/roms/openbios/kernel/include -I./target/include -c -o target/drivers/usbohci_rh.o
/<>/roms/openbios/drivers/usbohci_rh.c
/<>/roms/openbios/drivers/usb.c: In function ‘get_descriptor’:
/<>/roms/openbios/drivers/usb.c:200:23: error: array subscript
‘device_descriptor_t[0]’ is partly outside array bounds of ‘u8[8]’ {aka ‘unsigned char[8]’}
[-Werror=array-bounds]
200 | if (dd->bMaxPacketSize0 != 0)
| ^~
/<>/roms/openbios/drivers/usb.c:181:12: note: while referencing
‘buf’
181 | u8 buf[8];
|^~~
This is interesting. And I'm not really sure what to do with this.
The code is right, and gcc is too picky there. The thing is,
while the buffer is indeed smaller than the size of the structure
to which it is casted there, but the actual code does not access
past the buffer, bMaxPacketSize0 is byte #7 (counting from 0) there
which is exactly the last byte of buf[] array.
I haven't seen this warning before, it must be some new gcc
addition, and gcc is being too smart there :)
I agree the code is cloudy there, it can have been written
more clearly. So I can't say this is really a bug in gcc,
it is like classic "variable can be used uninitialized" while
it actually is not, for example because all relevant switch(){}
statements leads to return but gcc can not figure it out.
Thanks,
/mjt
Bug#997107: marked as done (xiphos: FTBFS: type_traits:44:3: error: template with C linkage)
Your message dated Sat, 23 Oct 2021 22:10:14 +
with message-id
and subject line Bug#997107: fixed in xiphos 4.2.1+dfsg1-6
has caused the Debian Bug report #997107,
regarding xiphos: FTBFS: type_traits:44:3: error: template with C linkage
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.)
--
997107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xiphos
Version: 4.2.1+dfsg1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
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/main && /usr/bin/c++
> -DHAVE_CONFIG_H -I/<>/obj-x86_64-linux-gnu
> -I/<>/src -I/<>/src/main/Threads::Threads
> -I/<>/src/main/PkgConfig::Core
> -I/<>/src/main/PkgConfig::Gtk
> -I/<>/src/main/PkgConfig::Gnome
> -I/<>/src/main/PkgConfig::Sword
> -I/<>/src/main/PkgConfig::Biblesync -isystem
> /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include
> -isystem /usr/include/uuid -isystem /usr/include/webkitgtk-4.0 -isystem
> /usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem
> /usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem
> /usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /usr/include/gio-unix-2.0
> -isystem /usr/include/cairo -isystem /usr/include/pango-1.0 -isystem
> /usr/include/harfbuzz -isystem /usr/include/fribidi -isystem
> /usr/include/atk-1.0 -isystem /usr/include/pixman-1 -isystem
> /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem
> /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libsoup-2.4 -isystem
> /usr/include/libxml2 -isystem /usr/include/libmount -isystem
> /usr/include/blkid -isystem /usr/include/minizip -isystem /usr/include/sword
> -isystem /usr/include/biblesync -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fno-delete-null-pointer-checks -pthread -MD -MT
> src/main/CMakeFiles/main.dir/display.cc.o -MF
> CMakeFiles/main.dir/display.cc.o.d -o CMakeFiles/main.dir/display.cc.o -c
> /<>/src/main/display.cc
> [ 17%] Generating da.gmo
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o
> /<>/obj-x86_64-linux-gnu/po/da.gmo
> /<>/obj-x86_64-linux-gnu/po/da.po
> [ 17%] Generating de.gmo
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o
> /<>/obj-x86_64-linux-gnu/po/de.gmo
> /<>/obj-x86_64-linux-gnu/po/de.po
> [ 18%] Generating en_GB.gmo
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o
> /<>/obj-x86_64-linux-gnu/po/en_GB.gmo
> /<>/obj-x86_64-linux-gnu/po/en_GB.po
> [ 18%] Generating es.gmo
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o
> /<>/obj-x86_64-linux-gnu/po/es.gmo
> /<>/obj-x86_64-linux-gnu/po/es.po
> [ 19%] Generating fa.gmo
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o
> /<>/obj-x86_64-linux-gnu/po/fa.gmo
> /<>/obj-x86_64-linux-gnu/po/fa.po
> In file included from /usr/include/glib-2.0/glib/glib-typeof.h:39,
> from /usr/include/glib-2.0/glib/gatomic.h:28,
> from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/gtk-3.0/gdk/gdkconfig.h:13,
> from /usr/include/gtk-3.0/gdk/gdk.h:30,
> from /usr/include/gtk-3.0/gtk/gtk.h:30,
> from /<>/src/main/sword.h:28,
> from /<>/src/main/configs.cc:28:
> /usr/include/c++/11/type_traits:44:3: error: template with C linkage
>44 | template
> | ^~~~
> In file included from /<>/src/main/configs.cc:28:
> /<>/src/main/sword.h:26:1: note: ‘extern "C"’ linkage started
> here
>26 | extern "C" {
> | ^~
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/xiphos_4.2.1+dfsg1-5_unstable.log
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: xiphos
Source-Version: 4.2.1+dfsg1-6
Done: Bastian Germann
We believe that the bug you reported is
Processed: quick patch… which may be needed to add to past releases?
Processing commands for cont...@bugs.debian.org: > # via https://bugzilla.redhat.com/show_bug.cgi?id=1943274 > forwarded 997628 > https://gitlab.freedesktop.org/xorg/util/cf/-/merge_requests/2 Bug #997628 [xutils-dev] imake: uses “ar clq” by default, which recent binutils broke in an incompatible way Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/util/cf/-/merge_requests/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 997628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997059: [Debian-med-packaging] Bug#997059: intake FTBFS on IPV6-only buildds
Oh, hold on! I'm not sure I have the same definition of "ipv6 only" as the buildd. Mine involves not having ipv4 loopback at all, which does not raise the issue documented in the bug report, but tornado errors on binding to 127.0.0.1 instead. If my ipv6 only host gets back an ipv4 loopback, then I reproduce the initial problem, independently of the changes in python3-tornado, which is unsurprising since the initial traceback does not involve the tornado module at all. I'm not sure how to proceed from there… :( -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/6, please excuse my verbosity. signature.asc Description: PGP signature
Bug#997508: marked as done (libbenchmark-timer-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Sat, 23 Oct 2021 22:03:52 + with message-id and subject line Bug#997508: fixed in libbenchmark-timer-perl 0.7112-2 has caused the Debian Bug report #997508, regarding libbenchmark-timer-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 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.) -- 997508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbenchmark-timer-perl Version: 0.7112-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', > 'blib/arch')" t/*.t > t/000_standard__compile.t ... > 1..1 > ok 1 - blib/lib/Benchmark/Timer.pm compiles > ok > Can't locate UNIVERSAL/require.pm in @INC (you may need to install the > UNIVERSAL::require module) (@INC contains: /<>/inc > /<>/blib/lib /<>/blib/arch /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 > /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 > /usr/share/perl/5.32 /usr/local/lib/site_perl .) at > t/000_standard__perl_critic.t line 8. > BEGIN failed--compilation aborted at t/000_standard__perl_critic.t line 8. > t/000_standard__perl_critic.t ... > Dubious, test returned 2 (wstat 512, 0x200) > No subtests run > t/000_standard__pod.t ... skipped: Test::Pod required for testing POD > t/000_standard__pod_coverage.t .. skipped: Test::Pod::Coverage required for > testing POD coverage > t/01_basic.t > 1..11 > ok 1 - use Benchmark::Timer; > ok 2 - Construct Benchmark::Timer > ok 3 - reset > ok 4 - Start/stop a tag > ok 5 - Nonzero single result > ok 6 - Multiple results > ok 7 - 'Array ref results' isa 'ARRAY' > ok 8 - tag data array > ok 9 - 'Array ref data' isa 'ARRAY' > ok 10 - all tags data array > ok 11 - 'all tags data ref' isa 'ARRAY' > ok > t/02_skip.t . > 1..5 > ok 1 - Data size two tags > ok 2 - Data size skip 1 > ok 3 - Data size 1 trial only > ok 4 - Data size no trials > ok 5 - Data size no trials (n+1) > ok > t/03_statistical.t .. skipped: Statistics::PointEstimation is not > installed > t/04_reports.t .. > 1..10 > ok 1 - Start/stop a tag > ok 2 - Single timing report > ok 3 - Multiple timing report > ok 4 - Multiple timing report--scalar > ok 5 - Multiple timing report--hash > ok 6 - Single timing report--last tag used > ok 7 - Multiple timing report--scalar > ok 8 - Multiple timing report--hash > ok 9 - Multiple timing report--hash element 1 > ok 10 - Multiple timing report--hash element 2 > ok > t/99_errors.t ... > 1..6 > ok 1 - Must call start first > ok 2 - Out of sync > ok 3 - Argument skip 1 > ok 4 - Argument skip 2 > ok 5 - Argument skip 3 > ok 6 - Invalid argument > ok > > Test Summary Report > --- > t/000_standard__perl_critic.t (Wstat: 512 Tests: 0 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > Files=9, Tests=33, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.37 cusr 0.04 > csys = 0.44 CPU) > Result: FAIL > Failed 1/9 test programs. 0/33 subtests failed. > make[1]: *** [Makefile:769: test_dynamic] Error 255 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/libbenchmark-timer-perl_0.7112-1.1_unstable.log 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
Bug#997628: imake: uses an argument to ar(1) which recent binutils changed in an incompatible way, causing packages using imake to FTBFS (was Re: Bug#997628: mgp: FTBFS: ar: libdeps specified more tha
# imake reassign 997628 xutils-dev found 997628 1:7.7+5 retitle 997628 imake: uses “ar clq” by default, which recent binutils broke in an incompatible way # causes an FTBFS, cannot be workarounded in mgp affects 997628 src:mgp # root bug is in binutils block 997628 by 981072 # at least, if not more severity 981072 important thanks Lucas Nussbaum dixit: >> ar clq libmgpimage.a imagetypes.o send.o zio.o zoom.o new.o compress.o >> reduce.o value.o misc.o rotate.o rle.o rlelib.o smooth.o halftone.o >> clip.o dither.o path.o bright.o window.o imlib_loader.o >> ar: libdeps specified more than once WTF, what does that even mean? *researches* This is #981072, an incompatible(!) change in binutils, which I’d consider of a rather serious severity but is tagged wontfix. Basically, ar(1) in bullseye documents the ‘l’ modifier as… l This modifier is accepted but not used. … and ar(1) in sid reuses it in an incompatible way, with no deprecation/warning period, instead of doing the sensible thing and using a different, not currently used, flag. Robert Luberda dixit: >Quick search on sources of packages showed that there are about 30 >other packages that also call "ar clq", see [2] - that's why I'm writing No, it’s far more than your search shows. I’m tempted to reassign to binutils, but this would probably be ignored. But I’ve got to reassign it anyway since the clq is injected by imake(1). Which version(s) of binutils contain this breaking change? (That is, does imake need a change in a stable release?) Doko, I urge you to request the upstream developers to change this and use a currently-unused flag for their new feature. I know getting them to do that, therefore admitting a mistake, is going to be hard, but considering this is embedded in *so* many build systems, they’re not going to make any friends by breaking this. bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
Bug#997515: marked as done (libfilehandle-unget-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Sat, 23 Oct 2021 21:49:15 + with message-id and subject line Bug#997515: fixed in libfilehandle-unget-perl 0.1634-2 has caused the Debian Bug report #997515, regarding libfilehandle-unget-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 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.) -- 997515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libfilehandle-unget-perl Version: 0.1634-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', > 'blib/arch')" t/*.t > t/000_standard__compile.t .. > 1..1 > ok 1 - blib/lib/FileHandle/Unget.pm compiles > ok > Can't locate UNIVERSAL/require.pm in @INC (you may need to install the > UNIVERSAL::require module) (@INC contains: /<>/inc > /<>/blib/lib /<>/blib/arch /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 > /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 > /usr/share/perl/5.32 /usr/local/lib/site_perl .) at > t/000_standard__perl_critic.t line 8. > BEGIN failed--compilation aborted at t/000_standard__perl_critic.t line 8. > t/000_standard__perl_critic.t .. > Dubious, test returned 2 (wstat 512, 0x200) > No subtests run > t/000_standard__pod.t .. skipped: Test::Pod required for testing POD > Under windows, calling binmode after eof exposes a bug that exists in some > versions of Perl. > t/binmode_bug.t > 1..2 > ok 1 > ok 2 > ok > t/buffer.t . > 1..3 > ok 1 > ok 2 > ok 3 > ok > t/class_pipe.t . > 1..2 > ok 1 - Fork succeeded > ok 2 - Child output > ok > t/core_pipe.t .. > 1..2 > ok 1 - Fork succeeded > ok 2 - Child output > ok > t/dumper.t . > 1..1 > ok 1 - Dumped Filehandle::Unget > ok > t/eof.t > 1..4 > ok 1 - Read first line > ok 2 - Read second line > ok 3 - EOF getline > ok 4 - EOF getlines > ok > t/filehandle.t . > 1..13 > ok 1 - No eol separator > ok 2 - Input line number at start > ok 3 - First line > ok 4 - Input line number at middle > ok 5 - Getlines size > ok 6 - First line > ok 7 - Second line > ok 8 - EOF > ok 9 - read() function > ok 10 - Number of bytes read > ok 11 - read() method > ok 12 - Number of bytes read > ok 13 - new from fd > ok > t/fileno.t . > 1..1 > ok 1 - fileno() > ok > t/gensym.t . > 1..12 > ok 1 - syswrite() > ok 2 - input_line_number() > ok 3 - getline() > ok 4 - input_line_number() after reading > ok 5 - getlines() size > ok 6 - First line > ok 7 - Second line > ok 8 - EOF > ok 9 - read() function > ok 10 - Number of bytes read > ok 11 - read() method > ok 12 - Number of bytes read > ok > t/input_record_separator.t . > 1..7 > ok 1 - First line > ok 2 - No eol separator > ok 3 - First line > ok 4 - Second line > ok 5 - Newline end of file > ok 6 - First line > ok 7 - Undef end of line > ok > t/loop_bug.t ... > 1..1 > ok 1 - Loop bug > ok > t/memory_leak.t > 1..1 > ok 1 - Memory leak > ok > t/multiple_handles.t ... > 1..4 > ok 1 - Unget 1 > ok 2 - Unget 2 > ok 3 - Get 1 > ok 4 - Get 2 > ok > t/new.t > 1..12 > ok 1 - syswrite() > ok 2 - input_line_number() > ok 3 - First line > ok 4 - Second line > ok 5 - getlines() > ok 6 - First line > ok 7 - Second line > ok 8 - EOF > ok 9 - read() function (filehandle) > ok 10 - Number of bytes read (filehandle) > ok 11 - read() method (filehandle) > ok 12 - Number of bytes read (filehandle) > ok > t/overridden_p
Bug#997437: marked as done (fmtlib: FTBFS: dh_sphinxdoc: error: DOCUMENTATION_OPTIONS does not define URL_ROOT)
Your message dated Sat, 23 Oct 2021 21:48:45 + with message-id and subject line Bug#997437: fixed in fmtlib 7.1.3+ds1-6 has caused the Debian Bug report #997437, regarding fmtlib: FTBFS: dh_sphinxdoc: error: DOCUMENTATION_OPTIONS does not define URL_ROOT 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.) -- 997437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fmtlib Version: 7.1.3+ds1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > dh_install > dh_sphinxdoc > dh_sphinxdoc: error: DOCUMENTATION_OPTIONS does not define URL_ROOT > make[1]: *** [debian/rules:33: override_dh_install-indep] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/fmtlib_7.1.3+ds1-5_unstable.log 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: fmtlib Source-Version: 7.1.3+ds1-6 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of fmtlib, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated fmtlib 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: Sun, 24 Oct 2021 05:34:53 +0800 Source: fmtlib Architecture: source Version: 7.1.3+ds1-6 Distribution: unstable Urgency: medium Maintainer: Shengjing Zhu Changed-By: Shengjing Zhu Closes: 997437 Changes: fmtlib (7.1.3+ds1-6) unstable; urgency=medium . * Fix FTBFS with dh_sphinxdoc (Closes: #997437) dh_sphinxdoc: error: DOCUMENTATION_OPTIONS does not define URL_ROOT Checksums-Sha1: da8c2dad4b815e0ea6aa99f92e8adac96aece610 1480 fmtlib_7.1.3+ds1-6.dsc 7b1162a3e8d1a9f60be4624e6e9bd546ce40c4cc 14160 fmtlib_7.1.3+ds1-6.debian.tar.xz 8cc066b9a85b28695f43450f0a425878a8e2e630 8889 fmtlib_7.1.3+ds1-6_amd64.buildinfo Checksums-Sha256: 3f1a46c3996e4acb477f8ec7d130abdeb546cb9401a1eba1cf1faa20ded1293d 1480 fmtlib_7.1.3+ds1-6.dsc 33b04624144320e904001585b53d0969137da3dbe0a72d8fdab2eeeabc5b9981 14160 fmtlib_7.1.3+ds1-6.debian.tar.xz cfbb8a9309ba17237c29906dc5afd08c6413b132bf5753674b6410740551437a 8889 fmtlib_7.1.3+ds1-6_amd64.buildinfo Files: 18b9484a9d996b260c7087e6a20eb178 1480 devel optional fmtlib_7.1.3+ds1-6.dsc e5326a69ee18a99defa942bb7b8c83c5 14160 devel optional fmtlib_7.1.3+ds1-6.debian.tar.xz f670f4d1c14aeee6bee3833beef85096 8889 devel optional fmtlib_7.1.3+ds1-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCYXSAkxAcemhzakBkZWJp YW4ub3JnAAoJEH9E+iXqVRTLCeMBAJUjzW9mplTJIsVO5HKORyKRjtqCMBNursRA 6NJgfLNsAQDbpqHljNDoVXOXiBHXt3VaMc52A9Uli1CtJpRZhmYnAQ== =+beQ -END PGP SIGNATURE End Message ---
Bug#997190: marked as done (qrq: FTBFS: qrq.c:1073:31: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Sat, 23 Oct 2021 21:49:37 +
with message-id
and subject line Bug#997190: fixed in qrq 0.3.3-4
has caused the Debian Bug report #997190,
regarding qrq: FTBFS: qrq.c:1073:31: error: format not a string literal and no
format arguments [-Werror=format-security]
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.)
--
997190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qrq
Version: 0.3.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -D DESTDIR=\"/usr\" -D VERSION=\"0.3.3\" -I. -D PA
> -pthread -c pulseaudio.c
> qrq.c: In function ‘main’:
> qrq.c:262:24: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 2 has type ‘long unsigned int’ [-Wformat=]
> 262 | printw("done. %d calls read.\n\n", nrofcalls);
> | ~^ ~
> || |
> |int long unsigned int
> | %ld
> qrq.c: In function ‘update_parameter_dialog’:
> qrq.c:765:40: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 6 has type ‘long unsigned int’ [-Wformat=]
> 765 | mvwprintw(conf_w,11,2, "Callsign database: %-15s"
> |^~
> 766 | " d (%d)",
> basename(cbfilename),nrofcalls);
> |
>~
> |
>|
> |
>long unsigned int
> qrq.c:766:52: note: format string is defined here
> 766 | " d (%d)",
> basename(cbfilename),nrofcalls);
> | ~^
> ||
> |int
> | %ld
> qrq.c: In function ‘close_summary_file’:
> qrq.c:1073:31: error: format not a string literal and no format arguments
> [-Werror=format-security]
> 1073 | mvwprintw(mid_w,14,2, filename);
> | ^~~~
> qrq.c: In function ‘update_score’:
> qrq.c:1086:41: warning: too many arguments for format [-Wformat-extra-args]
> 1086 | mvwprintw(top_w, 1, 27, "[training mode]", score);
> | ^
> qrq.c: In function ‘read_config’:
> qrq.c:1395:60: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 3 has type ‘long int’ [-Wformat=]
> 1395 | printw(" line %2d: sample rate: %d\n",
> line, samplerate);
> | ~^
> ~~
> ||
> |
> |int
> long int
> | %ld
> qrq.c: In function ‘find_files’:
> qrq.c:1896:40: warning: too many arguments for format [-Wformat-extra-args]
> 1896 | printw("Files copied. You might want
> to edit "
> |
> ^~~
> qrq.c: In function ‘check_toplist’:
> qrq.c:1752:9: warning: ignoring return value of ‘fgets’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 1752 | fgets(tmp, 35, fh);
> | ^~
> qrq.c: In function ‘statistics’:
> qrq.c:1979:17: warning: ignoring return value of ‘system’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 1979 | system("gnuplot -p /tmp/qrq-plot 2> /dev/null &");
> | ^
> qrq.c: In function ‘display_toplist’:
> qrq.c:967:16: warning: ignoring return value of ‘fgets’ declared with
> attribute ‘warn_unused_result’
Processed: affects 997650, merging 994276 997650
Processing commands for cont...@bugs.debian.org: > affects 997650 xtel Bug #997650 [xutils-dev] xtel: FTBFS: ar: libdeps specified more than once Added indication that 997650 affects xtel > merge 994276 997650 Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Bug #997650 [xutils-dev] xtel: FTBFS: ar: libdeps specified more than once Marked as found in versions xutils-dev/1:7.7+5. Added tag(s) patch. Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Added tag(s) sid and bookworm. Merged 994276 997650 > thanks Stopping processing here. Please contact me if you need assistance. -- 994276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994276 997650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#997508 marked as pending in libbenchmark-timer-perl
Processing control commands: > tag -1 pending Bug #997508 [src:libbenchmark-timer-perl] libbenchmark-timer-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 997508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997508: marked as pending in libbenchmark-timer-perl
Control: tag -1 pending Hello, Bug #997508 in libbenchmark-timer-perl 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/perl-team/modules/packages/libbenchmark-timer-perl/-/commit/d3111d11a889f92d7847b66764ae669f648dacf7 Add build dependency on libuniversal-require-perl. Closes: #997508 (this message was generated automatically) -- Greetings https://bugs.debian.org/997508
Bug#997332: marked as done (sitecopy: FTBFS: configure: error: could not use external neon library)
Your message dated Sat, 23 Oct 2021 21:36:28 + with message-id and subject line Bug#997332: fixed in sitecopy 1:0.16.6-10 has caused the Debian Bug report #997332, regarding sitecopy: FTBFS: configure: error: could not use external neon library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sitecopy Version: 1:0.16.6-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for ar... ar > checking for ranlib... ranlib > checking for neon-config... /usr/bin/neon-config > checking linking against neon... yes > configure: incompatible neon library version 0.32.1: wanted 0.24 25 26 27 28 > 31 > configure: error: could not use external neon library > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2021/10/23/sitecopy_0.16.6-9_unstable.log 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: sitecopy Source-Version: 1:0.16.6-10 Done: Christian Marillat We believe that the bug you reported is fixed in the latest version of sitecopy, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Marillat (supplier of updated sitecopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Oct 2021 23:15:14 +0200 Source: sitecopy Architecture: source Version: 1:0.16.6-10 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Closes: 997332 Changes: sitecopy (1:0.16.6-10) unstable; urgency=medium . * Add neon 32 as suported version (Closes: #997332) Checksums-Sha1: fb6940ccc891f409e9a0bdf2428ba31bfb2527d2 1795 sitecopy_0.16.6-10.dsc c5d8605e471f346b24c8cdf3f505c6a33532ce3a 36436 sitecopy_0.16.6-10.debian.tar.xz 5b67a261d5ea3c9c26180de36041396f2692bed6 6582 sitecopy_0.16.6-10_source.buildinfo Checksums-Sha256: 8a591e6621c5469b91e68787546d6703395718b985d3467ae158274b3b55a861 1795 sitecopy_0.16.6-10.dsc 068c3b1ede4d2894845da2dc4d4193098e5101f1f45cc0976947345056f6f1e4 36436 sitecopy_0.16.6-10.debian.tar.xz 6d494a473b39a8e0e994d6daacd0a3ac1f8c011f51b93466eb64a83341212b6a 6582 sitecopy_0.16.6-10_source.buildinfo Files: 6432442fd343d53f866b0235b23e9f33 1795 web extra sitecopy_0.16.6-10.dsc 0ea0e68ac20a14fb265bcef1558314e3 36436 web extra sitecopy_0.16.6-10.debian.tar.xz 4f8898154bd56650b9cc80774ca8df41 6582 web extra sitecopy_0.16.6-10_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEpAH/mTaPofmBUt51XICMK2VVgRcFAmF0fA4ACgkQXICMK2VV gRelNxAAzUAQ+ioV6Z40jC0vfWVuZhWLx+G/pIxLNnKeZIF8PnIqCQ5A1zV2RJQ6 n33Bw73sWP25tAQey71YbG9tJO0yc0jpZCIlr+3/ngb7mjdPngtIjNhLL2hQ6DK0 0FYWRaVckrgPXA2wo1Pm3fCD0LaE3YyDGZMQzI0EF200mxofVyCllyMPeuLMuZty OWdOQCPtxVh8Ax8v9XNhXTs3yORgnIWTinERVlcnkqqiXcgm6w/WWSzCkqf5yjCm j6pGA4IqY9qXA47CL6XQ6SH2sAxt4ljdsVdIHT49FY0W2H/JKLsfjCTH6Rx+suJD e6uPHbgb9TtkcwApLd2vXzih+5O7g9KMMK938efYZaod0u4fBWdh4XX7Nap1xBR7 xYQucpGLB39crBBSMykg91LA/Me3rGq6Pock3C4TdL6x4KXcepVTPyVptzl7SYMo +SoB9v3h8wnOD9yhSsHiQGPWn1Je99Xc4fw/ETjt9N2Jplg/AZ5q/9vFzRxIrssW ksALI/F6MWVSqzw1qaxfnk+6dYUFqCEKXuG0SY/S9OtciqHphYVPBeW/O2fpf4rW Of2UGJ+G8widVaudxQ3bvN1CAQicrTTzcWjhQqxiTRUfQZadqtNuvXAJ//YrAH9X lAha+OkNLpLopya5fZcky/zLzDY+sBhO4uM93YGQVkLCq/WE/jQ= =W6pg -END PGP SIGNATURE End Message ---
Bug#996795: marked as done (silversearcher-ag-el: should drop dependencies on elpa-dash-functional)
Your message dated Sat, 23 Oct 2021 21:36:22 + with message-id and subject line Bug#996795: fixed in silversearcher-ag-el 0.48-1.1 has caused the Debian Bug report #996795, regarding silversearcher-ag-el: should drop dependencies on elpa-dash-functional 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.) -- 996795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-ag Version: 0.48-1 Severity: serious Justification: not installable in sid due to package removal Hello, Per [1] dash-functional.el is obsolete and elpa-dash-functional has been removed from unstable. It should be sufficient simply to patch out any `require' calls or similar and require dash.el 2.18.0 or newer. [1] https://github.com/magnars/dash.el/wiki/Obsoletion-of-dash-functional.el -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: silversearcher-ag-el Source-Version: 0.48-1.1 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of silversearcher-ag-el, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated silversearcher-ag-el 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, 18 Oct 2021 13:43:54 -0700 Source: silversearcher-ag-el Architecture: source Version: 0.48-1.1 Distribution: unstable Urgency: medium Maintainer: Hajime Mizuno Changed-By: Sean Whitton Closes: 996795 Changes: silversearcher-ag-el (0.48-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop build-dep on elpa-dash-functional & require elpa-dash >= 2.18.0 (Closes: #996795). * Set autopkgtest_keep in debian/elpa-test. Otherwise, the ert_eval generates an error and the autopkgtest fails. Checksums-Sha1: ff655c37d0ab5e41e15c92fd155c54d2e9fe8b37 2054 silversearcher-ag-el_0.48-1.1.dsc 485f6ddde1c11cc9cd3fe1996cc9cf6bafdd4bd4 3168 silversearcher-ag-el_0.48-1.1.debian.tar.xz Checksums-Sha256: 33fbf9d4ee571a769ebd093f60cbafa9884a979b3078b7da06dbcdffc28810dd 2054 silversearcher-ag-el_0.48-1.1.dsc e6e06bea4c84f0114af698751708da789b7a07c6b567712e7638eeb529cb78b4 3168 silversearcher-ag-el_0.48-1.1.debian.tar.xz Files: e69f38421d4e6cb019300f5ef38e811c 2054 editors optional silversearcher-ag-el_0.48-1.1.dsc d92622f953e2565e0977748546f76a1c 3168 editors optional silversearcher-ag-el_0.48-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmFt3SMACgkQaVt65L8G YkCtSQ//a2aFEcpc3bPYzBMKI2fEfpmOaVSV2gb3w2YroPbnTY/JGdQNOvmdsj77 eHTOIccGuTD8vGuRhNnDLpjTwEp4jkczu7Nu+IZjKSLMH4Er42vw3x5/HxpkqiiN yA1KCxV75gaDxrxM+WQVLGuiAzRiT9/agxJhKRsQFL71qvRDQsruXAqcQTaSTVKz dK+ltCx/cW2jmZd4jznnSXiLS1lqQHnfyMxha0+JnZkR5Vs1mWhffwWqNMnF/EHz Jtg4FpGLwbXMiPlZ49OntDJMpypUB47b23/5cJNVnayBSkKXQOvLWmWq4W0qzN4p /z97EBygAp5eTlwUcTttdzPKSF9TEf/sQWRKBoa7Yb+wrhCuRdQDhtPQ2q41l8eC yIFjiakx1nxXtyQLbkm3omciCyugvKpoxB46zK2sG9avGGpDJQXmQ4dmctIwVmea 4Pp32ywJjtw17LBHV+OOkHYaqO6OJ4aAR1sCNRDnTFVARFLj4gJ2vDD/P/3uHrI/ BvnOSpjliDUFuwHIWZS5+AVvkNUo+mtVyv/zNVairHca2yMCdoSUO/O5vb/cMXWw 6mqGL0EnCH3tW0PSZi2KsXgwtP2tZ6BhI4fkEXVfzytYP6eMHt+UEt+vQT7+f40M J2MWlp/KfQn20/knNZO6riEL1GFT4NWExWM1YrgfZnAqnhspZ6U= =zm4j -END PGP SIGNATURE End Message ---
Bug#996620: marked as done (FTBFS: error: cannot bind non-const lvalue reference of type ‘temp_string&’ to an rvalue of type ‘temp_string’)
Your message dated Sat, 23 Oct 2021 21:36:42 +
with message-id
and subject line Bug#996620: fixed in wp2latex 3.100+ds-2
has caused the Debian Bug report #996620,
regarding FTBFS: error: cannot bind non-const lvalue reference of type
‘temp_string&’ to an rvalue of type ‘temp_string’
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.)
--
996620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wp2latex
Version: 3.100-1
Severity: serious
Tags: upstream
Justification: 4.
Dear Maintainer,
the package fails to build from source since gcc-11 is the default compiler:
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -fno-rtti
-fno-exceptions -DUSE_TEMP_STRINGS -D_REENTRANT -fpermissive -DPOINTER_SIZE=64
-O2 -Dpng_sizeof=sizeof -Wall -I../atoms/include/ -DERROR_HANDLER -c cpbldr.cc
-o cpbldr.o
In file included from cplib.cc:8,
from cpbldr.cc:8:
../atoms/include/stringa.h:191:30: warning: friend declaration of ‘temp_string
del(const string&, int, int)’ specifies default arguments and isn’t a
definition [-fpermissive]
191 | friend temp_string del(const string ,int from, int len=1);
| ^~~
../atoms/include/stringa.h: In member function ‘string&
string::operator*=(unsigned int)’:
../atoms/include/stringa.h:269:63: error: cannot bind non-const lvalue
reference of type ‘temp_string&’ to an rvalue of type ‘temp_string’
269 | inline string & string::operator*=(unsigned n)
{*this=multiply(*this,n);return(*this);}
| ^
../atoms/include/stringa.h:90:42: note: initializing argument 1 of ‘string&
string::operator=(temp_string&)’
90 | string =(temp_string );
| ~^
In file included from ../atoms/include/dbllist.h:12,
from cplib.cc:9,
from cpbldr.cc:8:
../atoms/include/lists.h: At global scope:
../atoms/include/lists.h:99:23: warning: friend declaration of ‘int
AddSTRSorted(list&, TSorter, const char*, int)’ specifies default arguments and
isn’t a definition [-fpermissive]
99 |friend int AddSTRSorted(list & l,TSorter sorter, const char
*str, int AllowDupl=0);
| ^~~~
cpbldr.cc: In function ‘doublelist ReadCodeGenerator(const char*)’:
cpbldr.cc:47:17: error: cannot bind non-const lvalue reference of type
‘temp_string&’ to an rvalue of type ‘temp_string’
47 | key = copy(s,1,i-1);
| ^
In file included from cplib.cc:8,
from cpbldr.cc:8:
../atoms/include/stringa.h:90:42: note: initializing argument 1 of ‘string&
string::operator=(temp_string&)’
90 | string =(temp_string );
| ~^
cpbldr.cc:56:21: error: cannot bind non-const lvalue reference of type
‘temp_string&’ to an rvalue of type ‘temp_string’
56 | key = copy(key,0, Semicolon-key());
| ^~~~
In file included from cplib.cc:8,
from cpbldr.cc:8:
../atoms/include/stringa.h:90:42: note: initializing argument 1 of ‘string&
string::operator=(temp_string&)’
90 | string =(temp_string );
| ~^
cpbldr.cc:80:24: error: cannot bind non-const lvalue reference of type
‘temp_string&’ to an rvalue of type ‘temp_string’
80 | key = copy(s,1,i-1);
|^
In file included from cplib.cc:8,
from cpbldr.cc:8:
../atoms/include/stringa.h:90:42: note: initializing argument 1 of ‘string&
string::operator=(temp_string&)’
90 | string =(temp_string );
| ~^
cpbldr.cc:87:28: error: cannot bind non-const lvalue reference of type
‘temp_string&’ to an rvalue of type ‘temp_string’
87 | key = copy(key,0, Semicolon-key());
|^~~~
In file included from cplib.cc:8,
from cpbldr.cc:8:
../atoms/include/stringa.h:90:42: note: initializing argument 1 of ‘string&
string::operator=(temp_string&)’
90 | string =(temp_string );
| ~^
cpbldr.cc: In function ‘string CheckPlainString(const string&)’:
cpbldr.cc:149:27: error: cannot bind non-const lvalue
Bug#997515: marked as pending in libfilehandle-unget-perl
Control: tag -1 pending Hello, Bug #997515 in libfilehandle-unget-perl 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/perl-team/modules/packages/libfilehandle-unget-perl/-/commit/723d13889c1dd0bee0769951bf99197e48370d79 Add build dependency on libuniversal-require-perl. Closes: #997515 (this message was generated automatically) -- Greetings https://bugs.debian.org/997515
Processed: Bug#997515 marked as pending in libfilehandle-unget-perl
Processing control commands: > tag -1 pending Bug #997515 [src:libfilehandle-unget-perl] libfilehandle-unget-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 997515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Debian-med-packaging] Bug#997325: python-sqlsoup: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> tag -1 confirmed
Bug #997325 [src:python-sqlsoup] python-sqlsoup: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13
Added tag(s) confirmed.
--
997325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996951: linux-image-5.14.0-3-amd64: iouring looses requests
https://marc.info/?l=linux-block=163489378723217=2
Processed (with 1 error): reassign 997650 to xutils-dev, merging 994276 997650
Processing commands for cont...@bugs.debian.org: > reassign 997650 xutils-dev Bug #997650 [src:xtel] xtel: FTBFS: ar: libdeps specified more than once Bug reassigned from package 'src:xtel' to 'xutils-dev'. No longer marked as found in versions xtel/3.3.0-24. Ignoring request to alter fixed versions of bug #997650 to the same values previously set > merge 994276 997650 Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Unable to merge bugs because: affects of #997650 is '' not 'xtel' Failed to merge 994276: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 994276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994276 997650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997438: marked as done (speech-tools: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sat, 23 Oct 2021 21:22:08 + with message-id and subject line Bug#997438: fixed in speech-tools 1:2.5.0-12 has caused the Debian Bug report #997438, regarding speech-tools: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 997438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: speech-tools Version: 1:2.5.0-11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > find -name make.depend -print0 | xargs -0r rm -f > find -name make.include -print0 | xargs -0r rm -f > find bin/ \( -name SCCS -o -name RCS -o -name CVS \) -prune \ > -o -type f ! -name Makefile -print0 | xargs -0r rm -f > dh_clean > make[1]: Leaving directory '/<>' > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building speech-tools using existing > ./speech-tools_2.5.0.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file configure, use > --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > speech-tools-2.5.0/config.guess > speech-tools-2.5.0/config.sub > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/speech-tools_2.5.0-11.diff.bAuHse > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2021-10-23T07:11:36Z The full build log is available from: http://qa-logs.debian.net/2021/10/23/speech-tools_2.5.0-11_unstable.log 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: speech-tools Source-Version: 1:2.5.0-12 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of speech-tools, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated speech-tools 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: Sat, 23 Oct 2021 22:42:38 +0200 Source: speech-tools Architecture: source Version: 1:2.5.0-12 Distribution: unstable Urgency: medium Maintainer: Debian Accessibility Team Changed-By: Samuel Thibault Closes: 997438 Changes: speech-tools (1:2.5.0-12) unstable; urgency=medium . * rules: Drop ddeb-migration rules, now useless * rules: Do not try to mess with autoreconf in clean target (Closes: Bug#997438) * rules: set cross-build CC and CXX. Checksums-Sha1: a97210c367dde89ab33cf42d67c950049c5c23b5 2457 speech-tools_2.5.0-12.dsc 7ecd8208cab0e8e53b266dbc1284812a46733767 42612 speech-tools_2.5.0-12.debian.tar.xz c2bf227de822436b014a1005bbcb2d0cab6425b9 10617 speech-tools_2.5.0-12_source.buildinfo Checksums-Sha256: 056fc581814caad469e916d2c9fe180bccd983c094461f144db253465c0c6356 2457 speech-tools_2.5.0-12.dsc 796292b77ebce869cd2fc7e16ff456caa3c329426b29818732c5e2777f8036f0 42612 speech-tools_2.5.0-12.debian.tar.xz d5e8283076094f98657b130a791848805cc82448dad7bf0f95759b069d531196 10617 speech-tools_2.5.0-12_source.buildinfo Files: 8ab5e31a8c4ae11e192c12ee2de40e13 2457 so
Processed: reduce noise while assessing the situation on ipv6 only setup
Processing commands for cont...@bugs.debian.org: > # It's probably preferable to reduce autorm range of effect > # while assessing the situation on ipv6 only configuration > # regarding the building of src:intake. > reassign 997059 src:intake Bug #997059 [python3-tornado] python3-tornado: hardcodes ipv4 binding in testing.py Bug reassigned from package 'python3-tornado' to 'src:intake'. Ignoring request to alter found versions of bug #997059 to the same values previously set Ignoring request to alter fixed versions of bug #997059 to the same values previously set > retitle 997059 intake FTBFS on IPV6-only buildds Bug #997059 [src:intake] python3-tornado: hardcodes ipv4 binding in testing.py Changed Bug title to 'intake FTBFS on IPV6-only buildds' from 'python3-tornado: hardcodes ipv4 binding in testing.py'. > tags 997059 - patch Bug #997059 [src:intake] intake FTBFS on IPV6-only buildds Removed tag(s) patch. > # Sorry for the noise > thank you Stopping processing here. Please contact me if you need assistance. -- 997059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997661: binutils-mingw-w64: FTBFS: patching fails
Source: binutils-mingw-w64 Version: 8.11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > tar xf /usr/src/binutils/binutils-2.37.tar.* > rm -rf /<>/upstream > mv binutils-* /<>/upstream > patch -d /<>/upstream -R -p1 < > /usr/src/binutils/patches/001_ld_makefile_patch.patch > patching file ld/Makefile.am > patching file ld/Makefile.in > Hunk #1 succeeded at 564 (offset 2 lines). > QUILT_SERIES=debian/patches/series QUILT_PATCHES=debian/patches quilt push -a > Applying patch debian/patches/testsuite-timeout.patch > patching file upstream/gas/testsuite/lib/gas-defs.exp > > Applying patch debian/patches/specify-timestamp.patch > patching file upstream/bfd/peXXigen.c > Hunk #1 succeeded at 73 with fuzz 2 (offset -4 lines). > Hunk #2 succeeded at 854 (offset -25 lines). > patching file upstream/ld/pe-dll.c > Hunk #2 succeeded at 1221 (offset 1 line). > patching file upstream/ld/emultempl/pe.em > Hunk #1 succeeded at 318 (offset 14 lines). > patching file upstream/ld/emultempl/pep.em > Hunk #1 succeeded at 337 (offset 14 lines). > > Applying patch debian/patches/dont-run-objcopy.patch > patching file upstream/binutils/testsuite/binutils-all/objcopy.exp > Hunk #1 succeeded at 668 (offset 13 lines). > > Applying patch debian/patches/disable-flags.patch > patching file upstream/ld/emultempl/pe.em > Hunk #1 succeeded at 262 (offset 3 lines). > Hunk #2 FAILED at 273. > Hunk #3 FAILED at 344. > Hunk #4 FAILED at 353. > Hunk #5 FAILED at 487. > Hunk #6 FAILED at 864. > 5 out of 6 hunks FAILED -- rejects in file upstream/ld/emultempl/pe.em > patching file upstream/ld/emultempl/pep.em > Hunk #1 succeeded at 241 (offset 4 lines). > Hunk #2 FAILED at 251. > Hunk #3 succeeded at 332 (offset 14 lines). > Hunk #4 FAILED at 333. > Hunk #5 FAILED at 454. > Hunk #6 FAILED at 815. > 4 out of 6 hunks FAILED -- rejects in file upstream/ld/emultempl/pep.em > Patch debian/patches/disable-flags.patch does not apply (enforce with -f) > make[1]: *** [debian/rules:50: unpack-stamp] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/binutils-mingw-w64_8.11_unstable.log 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.
Bug#997660: calibre: FTBFS: -c: Unable to find file "QtWidgets/QtWidgetsmod.sip"
Source: calibre
Version: 5.29.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> blhc: ignore-line-regexp: \tCompiling form /.+\.ui
> blhc: ignore-line-regexp: .+ -dM -E -o moc_predefs\.h
> /usr/lib/[^/]+/qt5/mkspecs/features/data/dummy\.cpp
> [ -d build ] || python3.9 setup.py build
>
> *
> * Running build
> *
>
> Building 24 extensions
> Compiling 35 files...
> g++ -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -std=c++11
> -DCALIBRE_MODINIT_FUNC=extern "C" __attribute__ ((visibility ("default")))
> PyObject* -I/usr/include/hunspell -c
> /<>/src/calibre/utils/spell/hunspell_wrapper.cpp -o
> /<>/build/objects/hunspell/hunspell_wrapper.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -std=c99 -DCALIBRE_MODINIT_FUNC=
> __attribute__ ((visibility ("default"))) PyObject* -c
> /<>/src/calibre/utils/hyphenation/hyphen.c -o
> /<>/build/objects/hyphen/hyphen.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -std=c99 -DCALIBRE_MODINIT_FUNC=
> __attribute__ ((visibility ("default"))) PyObject* -c
> /<>/src/unicode_names/unicode_names.c -o
> /<>/build/objects/unicode_names/unicode_names.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__
> ((visibility ("default"))) PyObject* -c
> /<>/src/calibre/utils/speedup.c -o
> /<>/build/objects/speedup/speedup.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__
> ((visibility ("default"))) PyObject* -c
> /<>/src/calibre/gui2/tweak_book/editor/syntax/html.c -o
> /<>/build/objects/html_syntax_highlighter/html.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__
> ((visibility ("default"))) PyObject* -c
> /<>/src/tinycss/tokenizer.c -o
> /<>/build/objects/tokenizer/tokenizer.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__
> ((visibility ("default"))) PyObject* -c
> /<>/src/calibre/gui2/tweak_book/diff/_patiencediff_c.c -o
> /<>/build/objects/_patiencediff_c/_patiencediff_c.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__
> ((visibility ("default"))) PyObject* -c
> /<>/src/calibre/utils/icu.c -o
> /<>/build/objects/icu/icu.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__
> ((visibility ("default"))) PyObject* -c
> /<>/src/calibre/utils/matcher.c -o
> /<>/build/objects/matcher/matcher.o
>
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g
Bug#997658: botan: FTBFS: tests failed
Source: botan Version: 2.18.1+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > LD_LIBRARY_PATH=. /<>/botan-test > Testing Botan 2.18.1 (unreleased, revision unknown, distribution Debian) > CPU flags: sse2 ssse3 sse41 sse42 avx2 avx512f avx512dq avx512bw rdtsc bmi1 > bmi2 adx aes_ni clmul rdrand rdseed > Starting tests drbg_seed:16B097975A637739 > block: > AES-128 ran 34470 tests in 53.80 msec all ok > AES-192 ran 40500 tests in 63.88 msec all ok > AES-256 ran 46260 tests in 74.17 msec all ok > ARIA-128 ran 30 tests in 0.06 msec all ok > ARIA-192 ran 30 tests in 0.06 msec all ok > ARIA-256 ran 30 tests in 0.06 msec all ok > Blowfish ran 1860 tests in 21.24 msec all ok > CAST-128 ran 1440 tests in 2.10 msec all ok > CAST-256 ran 195 tests in 0.34 msec all ok > Camellia-128 ran 180 tests in 0.27 msec all ok > Camellia-192 ran 90 tests in 0.13 msec all ok > Camellia-256 ran 150 tests in 0.23 msec all ok > Cascade(Serpent,AES-256) ran 30 tests in 0.08 msec all ok > Cascade(Serpent,CAST-128) ran 15 tests in 0.04 msec all ok > Cascade(Serpent,Twofish) ran 45 tests in 0.17 msec all ok > DES ran 9630 tests in 13.49 msec all ok > DESX ran 135 tests in 0.20 msec all ok > GOST-28147-89(R3411_94_TestParam) ran 270 tests in 0.52 msec all ok > GOST-28147-89(R3411_CryptoPro) ran 150 tests in 0.28 msec all ok > IDEA ran 16260 tests in 33.14 msec all ok > KASUMI ran 45 tests in 0.07 msec all ok > Lion(SHA-160,RC4,64) ran 15 tests in 0.10 msec all ok > MISTY1 ran 465 tests in 0.65 msec all ok > Noekeon ran 15450 tests in 21.44 msec all ok > SEED ran 120 tests in 0.19 msec all ok > SHACAL2 ran 46035 tests in 79.69 msec all ok > SM4 ran 45 tests in 0.09 msec all ok > Serpent ran 47070 tests in 76.78 msec all ok > Threefish-512 ran 150 tests in 0.29 msec all ok > TripleDES ran 1680 tests in 2.70 msec all ok > Twofish ran 16545 tests in 31.26 msec all ok > XTEA ran 1020 tests in 1.67 msec all ok > stream: > CTR-BE(AES-128) ran 648 tests in 1.91 msec all ok > CTR-BE(AES-128,4) ran 12 tests in 0.05 msec all ok > CTR-BE(AES-128,5) ran 12 tests in 0.03 msec all ok > CTR-BE(AES-128,6) ran 12 tests in 0.03 msec all ok > CTR-BE(AES-128,8) ran 12 tests in 0.04 msec all ok > CTR-BE(AES-192) ran 768 tests in 1.90 msec all ok > CTR-BE(AES-256) ran 804 tests in 2.00 msec all ok > CTR-BE(Blowfish) ran 12 tests in 0.17 msec all ok > CTR-BE(DES) ran 588 tests in 1.57 msec all ok > CTR-BE(Noekeon) ran 2304 tests in 6.18 msec all ok > CTR-BE(Serpent) ran 2100 tests in 5.73 msec all ok > CTR-BE(TripleDES) ran 2556 tests in 11.61 msec all ok > CTR-BE(XTEA) ran 1452 tests in 3.72 msec all ok > ChaCha(12) ran 72 tests in 0.17 msec all ok > ChaCha(20) ran 3096 tests in 8.30 msec all ok > ChaCha(8) ran 717 tests in 1.90 msec all ok > MARK-4 ran 120 tests in 0.25 msec all ok > OFB(AES-128) ran 132 tests in 0.34 msec all ok > OFB(AES-192) ran 12 tests in 0.03 msec all ok > OFB(AES-256) ran 12 tests in 0.03 msec all ok > OFB(DES) ran 48 tests in 0.14 msec all ok > RC4 ran 1656 tests in 4.55 msec all ok > RC4(3) ran 24 tests in 0.05 msec all ok > SHAKE-128 ran 13740 tests in 25.10 msec all ok > Salsa20 ran 143 tests in 0.34 msec all ok > hash: > Adler32 ran 266 tests in 0.19 msec all ok > BLAKE2b(224) ran 2547 tests in 2.44 msec all ok > BLAKE2b(256) ran 2547 tests in 2.42 msec all ok > BLAKE2b(384) ran 2547 tests in 2.56 msec all ok > BLAKE2b(512) ran 2675 tests in 3.25 msec all ok > CRC24 ran 284 tests in 0.14 msec all ok > CRC32 ran 266 tests in 0.14 msec all ok > Comb4P(MD4,MD5) ran 10 tests in 0.05 msec all ok > Comb4P(SHA-160,RIPEMD-160) ran 10 tests in 0.03 msec all ok > GOST-R-34.11-94 ran 95 tests in 0.55 msec all ok > Keccak-1600(224) ran 2667 tests in 3.88 msec all ok > Keccak-1600(256) ran 2667 tests in 3.95 msec all ok > Keccak-1600(384) ran 2667 tests in 4.38 msec all ok > Keccak-1600(512) ran 2667 tests in 5.00 msec all ok > MD4 ran 1500 tests in 0.74 msec all ok > MD5 ran 1520 tests in 0.85 msec all ok > Parallel(MD5,SHA-160) ran 13 tests in 0.03 msec all ok > Parallel(SHA-256,SHA-512) ran 15 tests in 0.04 msec all ok > RIPEMD-160 ran 1486 tests in 0.98 msec all ok > SHA-160 ran 3060 tests in 2.44 msec all ok > SHA-224 ran 100 tests in 0.08 msec all ok > SHA-256 ran 15572 tests in 11.60 msec all ok > SHA-3(224) ran 1994 tests in 3.32 msec all ok > SHA-3(256) ran 1994 tests in 3.28 msec all ok > SHA-3(384) ran 1994 tests in 3.23 msec all ok > SHA-3(512) ran 1994 tests in 6.49 msec all ok > SHA-384 ran 252 tests in 0
Bug#997659: earlyoom: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules'
Source: earlyoom Version: 1.6.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > cc -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -pedantic -Wall -Wextra -Wformat-security > -Wconversion -DVERSION=\"v1.6.2\" -g -fstack-protector-all -std=gnu99 -o > earlyoom globals.c kill.c main.c meminfo.c msg.c > pandoc MANPAGE.md -s -t man > earlyoom.1 > sed "s|:TARGET:|/usr/bin|g;s|:SYSCONFDIR:|/etc|g" earlyoom.service.in > > earlyoom.service > make[1]: Leaving directory '/<>' >debian/rules override_dh_auto_test > make[1]: Entering directory '/<>' > go version | grep -qF gcc || HOME=$PWD go test -v > go: go.mod file not found in current directory or any parent directory; see > 'go help modules' > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/earlyoom_1.6.2-1_unstable.log 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.
Bug#997657: cgreen: FTBFS: Icon font not found for set: fas
Source: cgreen Version: 1.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/build' > [ 1%] asciidoctor-pdf cgreen-guide-en > cd /<>/build/doc && /usr/bin/asciidoctor-pdf -a toc -a > VERSION=1.3.0 -a docinfo -o cgreen-guide-en.pdf > /<>/doc/cgreen-guide-en.asciidoc > Icon font not found for set: fas > Use --trace for backtrace > make[4]: *** [doc/CMakeFiles/cgreen-guide-en-pdf.dir/build.make:77: > doc/cgreen-guide-en.pdf-pdf] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/cgreen_1.3.0-2_unstable.log 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.
Bug#997656: xfsprogs: FTBFS: mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied
Source: xfsprogs Version: 5.13.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > Installing libfrog-install > Installing libxfs-install > ../install-sh -o root -g root -m 755 -d /usr/include/xfs > mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied > mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied > gmake[2]: *** [Makefile:124: install] Error 1 > make[1]: *** [Makefile:148: libxfs-install] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/xfsprogs_5.13.0-1_unstable.log 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.
Bug#997655: diodon: FTBFS: autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?
Source: diodon Version: 1.11.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 --buildsystem=meson --with gir >dh_update_autotools_config -O--buildsystem=meson >dh_autoreconf -O--buildsystem=meson > autoreconf: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > autoreconf: error: configure.in: AC_INIT not found; not an autoconf script? > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:8: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/diodon_1.11.1-1_unstable.log 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.
Bug#997653: caribou: FTBFS: Caribou-1.0.gir:In NullAdapter: error: Can't resolve type '_Caribou.DisplayAdapter' for field Caribou.NullAdapter.parent_instance
Source: caribou Version: 0.4.21-7.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/libcaribou' > Makefile:883: warning: overriding recipe for target 'caribou-1.0.vapi' > Makefile:868: warning: ignoring old recipe for target 'caribou-1.0.vapi' > rm -f libcaribou_la_vala.stamp && echo stamp > libcaribou_la_vala.stamp-t > /usr/bin/valac -H caribou.h --vapi caribou-1.0.vapi -h caribou-internals.h > --vapidir=../vapi --pkg xtst --pkg gee-0.8 --pkg gdk-x11-3.0 --pkg libxml-2.0 > --pkg libxklavier --pkg external-libs --internal-vapi > caribou-internals-1.0.vapi --library caribou-1.0 --gir _Caribou-1.0.gir > --symbols libcaribou.symbols -C display-adapter.vala xadapter.vala > keyboard-model.vala keyboard-service.vala group-model.vala level-model.vala > row-model.vala key-model.vala column-model.vala scanner.vala > iscannable-item.vala iscannable-group.vala scannable-group.vala > ikeyboard-object.vala xml-deserializer.vala > xadapter.vala:170.37-170.68: warning: `Gdk.x11_get_default_root_xwindow' has > been deprecated since vala-0.24. Use Gdk.X11.get_default_root_xwindow > xadapter.vala:174.35-174.66: warning: `Gdk.x11_get_default_root_xwindow' has > been deprecated since vala-0.24. Use Gdk.X11.get_default_root_xwindow > xadapter.vala:218.30-218.51: warning: `Gdk.Keymap.get_default' has been > deprecated since 3.22 > xadapter.vala:32.29-32.42: warning: `Gdk.X11Display' has been deprecated > since vala-0.24. Use Gdk.X11.Display > xadapter.vala:33.19-33.31: warning: `Gdk.X11Window' has been deprecated since > vala-0.24. Use Gdk.X11.Window > scannable-group.vala:62.21-62.62: warning: Access to possible `null'. Perform > a check or use an unsafe cast. > (item as ScannableGroup).get_scan_children(); > ^^ > keyboard-service.vala:7.9-7.48: warning: DBus methods are recommended to > throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' > public abstract void set_cursor_location(int x, int y, int w, int h); > > keyboard-service.vala:8.9-8.47: warning: DBus methods are recommended to > throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' > public abstract void set_entry_location(int x, int y, int w, int h); > ^^^ > keyboard-service.vala:9.9-9.33: warning: DBus methods are recommended to > throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' > public abstract void show(uint32 timestamp); > ^ > keyboard-service.vala:10.9-10.33: warning: DBus methods are recommended to > throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' > public abstract void hide(uint32 timestamp); > ^ > Compilation succeeded - 10 warning(s) > mv -f libcaribou_la_vala.stamp-t libcaribou_la_vala.stamp > /bin/bash ../libtool --tag=CC --mode=compile gcc > -DPACKAGE_NAME=\"caribou\" -DPACKAGE_TARNAME=\"caribou\" > -DPACKAGE_VERSION=\"0.4.21\" -DPACKAGE_STRING=\"caribou\ 0.4.21\" > -DPACKAGE_BUGREPORT=\"https://bugzilla.gnome.org/enter_bug.cgi\?product=caribou\; > -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DPACKAGE=\"caribou\" -DVERSION=\"0.4.21\" > -DGETTEXT_PACKAGE=\"caribou\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 > -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DENABLE_NLS=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 > -DG_LOG_DOMAIN=\"caribou\" -I.. -pthread -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi > -I/usr/include/harfbuzz -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include/x86_64-linux-gnu -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libxml2 -I/usr/include/gee-0.8 -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o libcaribou_la-display-ad
Bug#997654: billiard: FTBFS: Configuration error: There is a syntax error in your configuration file: invalid syntax (conf.py, line 173)
Source: billiard Version: 3.6.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > PYTHONPATH=. python3 -m sphinx -b html -N Doc > /<>/debian/python-billiard-doc/usr/share/doc/python-billiard-doc/html > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: invalid syntax (conf.py, > line 173) > > make[1]: *** [debian/rules:17: override_dh_sphinxdoc] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/billiard_3.6.4.0-1_unstable.log 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.
Bug#997651: python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not callable
Source: python-ara Version: 1.4.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > PYTHON=python3 python3 -m sphinx -b html doc/source > debian/python-ara-doc/usr/share/doc/python-ara-doc/html > Running Sphinx v4.2.0 > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 18 source files that are out of date > updating environment: [new config] 18 added, 0 changed, 0 removed > reading sources... [ 5%] ansible-configuration > reading sources... [ 11%] ansible-role-ara-api > reading sources... [ 16%] ansible-role-ara-web > reading sources... [ 22%] api-configuration > reading sources... [ 27%] api-documentation > reading sources... [ 33%] api-security > reading sources... [ 38%] api-usage > reading sources... [ 44%] ara-api-lookup > reading sources... [ 50%] ara-manage > reading sources... [ 55%] ara-plugin-configuration > reading sources... [ 61%] ara-record > reading sources... [ 66%] container-images > reading sources... [ 72%] contributing > reading sources... [ 77%] distributed-sqlite-backend > reading sources... [ 83%] faq > reading sources... [ 88%] index > reading sources... [ 94%] installation > reading sources... [100%] playbook-names-and-labels > > /<>/doc/source/ara-manage.rst:25: WARNING: Command 'ara-manage > --help' failed: [Errno 2] No such file or directory: 'ara-manage' > /<>/doc/source/ara-manage.rst:32: WARNING: Command 'ara-manage > prune --help' failed: [Errno 2] No such file or directory: 'ara-manage' > /<>/doc/source/ara-manage.rst:41: WARNING: Command 'ara-manage > changepassword --help' failed: [Errno 2] No such file or directory: > 'ara-manage' > /<>/doc/source/ara-manage.rst:48: WARNING: Command 'ara-manage > createsuperuser --help' failed: [Errno 2] No such file or directory: > 'ara-manage' > /<>/doc/source/ara-manage.rst:55: WARNING: Command 'ara-manage > makemigrations --help' failed: [Errno 2] No such file or directory: > 'ara-manage' > /<>/doc/source/ara-manage.rst:64: WARNING: Command 'ara-manage > migrate --help' failed: [Errno 2] No such file or directory: 'ara-manage' > /<>/doc/source/ara-manage.rst:76: WARNING: Command 'ara-manage > runserver --help' failed: [Errno 2] No such file or directory: 'ara-manage' > /<>/doc/source/ara-manage.rst:86: WARNING: Command 'ara-manage > generate --help' failed: [Errno 2] No such file or directory: 'ara-manage' > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > writing output... [ 5%] ansible-configuration > writing output... [ 11%] ansible-role-ara-api > > Exception occurred: > File "/usr/lib/python3/dist-packages/sphinx/highlighting.py", line 127, in > get_lexer > lexer = lexer_classes[lang](**opts) > TypeError: 'AnsibleYamlJinjaLexer' object is not callable > The full traceback has been saved in /tmp/sphinx-err-9sp7oh5b.log, if you > want to report the issue to the developers. > Please also report this if it was a user error, so that a better error > message can be provided next time. > A bug report can be filed in the tracker at > <https://github.com/sphinx-doc/sphinx/issues>. Thanks! > make[1]: *** [debian/rules:19: override_dh_sphinxdoc] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-ara_1.4.3-1_unstable.log 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.
Bug#997652: sparql-wrapper-python: FTBFS: error in SPARQLWrapper setup command: use_2to3 is invalid.
Source: sparql-wrapper-python
Version: 1.8.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package sparql-wrapper-python
> dpkg-buildpackage: info: source version 1.8.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Sandro Tosi
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'use_2to3_fixers'
> warnings.warn(msg)
> error in SPARQLWrapper setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:15: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/sparql-wrapper-python_1.8.5-1_unstable.log
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.
Bug#997650: xtel: FTBFS: ar: libdeps specified more than once
Source: xtel Version: 3.3.0-24 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/Videotex' > gcc -g -O2 -DUSE_MOTIF -DUSE_SYSLOG-DDONT_USE_POPUP -Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o Videotex.o Videotex.c > In file included from /usr/include/malloc.h:22, > from Videotex.c:25: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > Videotex.c: In function ‘alloc_DRCS’: > Videotex.c:545:9: warning: implicit declaration of function ‘exit’ > [-Wimplicit-function-declaration] > 545 | exit (1); > | ^~~~ > Videotex.c:31:1: note: include ‘’ or provide a declaration of ‘exit’ >30 | #include "VideotexP.h" > +++ |+#include >31 | > Videotex.c:545:9: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 545 | exit (1); > | ^~~~ > Videotex.c:545:9: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c:551:13: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 551 | exit (1); > | ^~~~ > Videotex.c:551:13: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c:555:13: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 555 | exit (1); > | ^~~~ > Videotex.c:555:13: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c: In function ‘atoni’: > Videotex.c:3868:13: warning: implicit declaration of function ‘atoi’; did you > mean ‘atoni’? [-Wimplicit-function-declaration] > 3868 | return (atoi(buf)); > | ^~~~ > | atoni > Videotex.c: In function ‘Initialize’: > Videotex.c:4203:9: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 4203 | exit(1); > | ^~~~ > Videotex.c:4203:9: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c:4207:9: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 4207 | exit(1); > | ^~~~ > Videotex.c:4207:9: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c:4211:9: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 4211 | exit(1); > | ^~~~ > Videotex.c:4211:9: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c:4219:9: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 4219 | exit(1); > | ^~~~ > Videotex.c:4219:9: note: include ‘’ or provide a declaration of > ‘exit’ > Videotex.c: In function ‘reconnaissance_commande’: > Videotex.c:1057:21: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 1057 | write(pv->fd_connexion, "\023", 1); > | ^~ > Videotex.c:1058:21: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 1058 | write(pv->fd_connexion, > commandes_minitel[i].code, 1); > | > ^ > Videotex.c:1077:13: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 1077 | write(pv->fd_connexion, chaine, strlen(chaine)); > | ^~~ > Videotex.c:1097:17: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 1097 | write(pv->fd_connexion,
Bug#997649: feedparser: FTBFS: error in feedparser setup command: use_2to3 is invalid.
Source: feedparser
Version: 5.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean
> error in feedparser setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:11: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/feedparser_5.2.1-3_unstable.log
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.
Bug#997648: pyvirtualdisplay: FTBFS: error in PyVirtualDisplay setup command: use_2to3 is invalid.
Source: pyvirtualdisplay
Version: 0.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'use_2to3_exclude_fixers'
> warnings.warn(msg)
> error in PyVirtualDisplay setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pyvirtualdisplay_0.2.1-3_unstable.log
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.
Bug#997647: pystache: FTBFS: error in pystache setup command: use_2to3 is invalid.
Source: pystache
Version: 0.5.4-6.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 8 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 8 in use)
> I: pybuild base:232: python3.9 setup.py clean
> pystache: using: version '58.2.0' of '/usr/lib/python3/dist-packages/setuptools/__init__.py'>
> Warning: 'classifiers' should be a list, got type 'tuple'
> error in pystache setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:9: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pystache_0.5.4-6.1_unstable.log
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.
Bug#997646: ssvnc: FTBFS: ar: libdeps specified more than once
Source: ssvnc Version: 1.0.29-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/vnc_unixsrc/libvncauth' > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security-I. -I../include -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o vncauth.o vncauth.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from vncauth.c:24: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security-I. -I../include -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o d3des.o d3des.c > rm -f libvncauth.a > ar clq libvncauth.a vncauth.o d3des.o > ar: libdeps specified more than once > make[2]: *** [Makefile:1053: libvncauth.a] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ssvnc_1.0.29-5_unstable.log 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.
Bug#997645: python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is invalid.
Source: python-slimmer
Version: 0.1.30-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in slimmer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:7: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-slimmer_0.1.30-8_unstable.log
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.
Bug#997643: ctwm: FTBFS: ar: libdeps specified more than once
Source: ctwm Version: 3.7-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO-DUSEM4 -DGNOME -DXPM -DJPEG -DX11R6 -DSOUNDS -DI18N > -DUSE_GNU_REGEX `dpkg-buildflags --get CPPFLAGS` -c -o libctwm.o libctwm.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from libctwm.c:26: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f libctwm.a > ar clq libctwm.a libctwm.o > ar: libdeps specified more than once > make[1]: *** [Makefile:1245: libctwm.a] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ctwm_3.7-5_unstable.log 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.
Bug#997644: rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid.
Source: rnc2rng
Version: 2.6.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in rnc2rng setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/rnc2rng_2.6.4-1_unstable.log
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.
Bug#997642: jquery-tablesorter: FTBFS: DefaultsError: `ie8` is not a supported option
Source: jquery-tablesorter Version: 1:2.31.3+dfsg1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > dh_auto_build > grunt --verbose > Initializing > Command-line options: --verbose, --gruntfile=/<>/Gruntfile.js > > Reading "Gruntfile.js" Gruntfile...OK > > Registering Gruntfile tasks. > Reading package.json...OK > Parsing package.json...OK > Initializing config...OK > > Registering "grunt-contrib-clean" local Npm module tasks. > Reading /usr/share/nodejs/grunt-contrib-clean/package.json...OK > Parsing /usr/share/nodejs/grunt-contrib-clean/package.json...OK > Loading "clean.js" tasks...OK > + clean > > Registering "grunt-contrib-jshint" local Npm module tasks. > >> Local Npm module "grunt-contrib-jshint" not found. Is it installed? > > Registering "grunt-htmlhint" local Npm module tasks. > >> Local Npm module "grunt-htmlhint" not found. Is it installed? > > Registering "grunt-contrib-qunit" local Npm module tasks. > >> Local Npm module "grunt-contrib-qunit" not found. Is it installed? > > Registering "grunt-contrib-concat" local Npm module tasks. > Reading /usr/share/nodejs/grunt-contrib-concat/package.json...OK > Parsing /usr/share/nodejs/grunt-contrib-concat/package.json...OK > Loading "concat.js" tasks...OK > + concat > > Registering "grunt-contrib-uglify" local Npm module tasks. > Reading /usr/share/nodejs/grunt-contrib-uglify/package.json...OK > Parsing /usr/share/nodejs/grunt-contrib-uglify/package.json...OK > Loading "uglify.js" tasks...OK > + uglify > > Registering "grunt-contrib-copy" local Npm module tasks. > Reading /usr/share/nodejs/grunt-contrib-copy/package.json...OK > Parsing /usr/share/nodejs/grunt-contrib-copy/package.json...OK > Loading "copy.js" tasks...OK > + copy > > Registering "grunt-contrib-watch" local Npm module tasks. > >> Local Npm module "grunt-contrib-watch" not found. Is it installed? > > Registering "grunt-contrib-cssmin" local Npm module tasks. > >> Local Npm module "grunt-contrib-cssmin" not found. Is it installed? > > Registering "grunt-jscs" local Npm module tasks. > >> Local Npm module "grunt-jscs" not found. Is it installed? > Loading "Gruntfile.js" tasks...OK > + custom, default, quick, test, updateManifest > > No tasks specified, running default tasks. > Running tasks: default > > Running "default" task > Creating a widgets file with: storage, uitheme, columns, filter, > stickyHeaders, resizable, saveSort > !js/parsers/*.js > > Running "clean:build" (clean) task > Verifying property clean.build exists in config...OK > Files: [no src] > Options: force=false, no-write=false > >> 0 paths cleaned. > > Running "copy" task > > Running "copy:css" (copy) task > Verifying property copy.css exists in config...OK > Files: css/dragtable.mod.css -> dist/css/dragtable.mod.css > Files: css/filter.formatter.css -> dist/css/filter.formatter.css > Files: css/highlights.css -> dist/css/highlights.css > Files: css/theme.black-ice.css -> dist/css/theme.blackice.css > Files: css/theme.blue.css -> dist/css/theme.blue.css > Files: css/theme.bootstrap_2.css -> dist/css/theme.bootstrap_2.css > Files: css/theme.bootstrap_3.css -> dist/css/theme.bootstrap_3.css > Files: css/theme.bootstrap_4.css -> dist/css/theme.bootstrap_4.css > Files: css/theme.bootstrap.css -> dist/css/theme.bootstrap.css > Files: css/theme.dark.css -> dist/css/theme.dark.css > Files: css/theme.default.css -> dist/css/theme.default.css > Files: css/theme.dropbox.css -> dist/css/theme.dropbox.css > Files: css/theme.green.css -> dist/css/theme.green.css > Files: css/theme.grey.css -> dist/css/theme.grey.css > Files: css/theme.ice.css -> dist/css/theme.ice.css > Files: css/theme.jui.css -> dist/css/theme.jui.css > Files: css/theme.materialize.css -> dist/css/theme.materialize.css > Files: css/theme.metro-dark.css -> dist/css/theme.metro-dark.css > Files: css/widget.grouping.css -> dist/css/widget.grouping.css > Files: addons/pager/jquery.tablesorter.pager.css -> > dist/css/jquery.tablesorter.pager.css > Options: encoding="utf8", processContent=false, processContentExclude=[], > timestamp=false, mode=false
Bug#997641: knews: FTBFS: ar: libdeps specified more than once
Source: knews Version: 1.0b.1-33 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/Widgets' > gcc -Wall -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 > -Wdate-time -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o ArtText.o ArtText.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from ArtText.c:5: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > ArtText.c: In function ‘get_sel_len’: > ArtText.c:885:8: warning: suggest explicit braces to avoid ambiguous ‘else’ > [-Wdangling-else] > 885 | if (start == stop) > |^ > ArtText.c: In function ‘get_sel’: > ArtText.c:940:8: warning: suggest explicit braces to avoid ambiguous ‘else’ > [-Wdangling-else] > 940 | if (start == stop) > |^ > ArtText.c:969:8: warning: suggest explicit braces to avoid ambiguous ‘else’ > [-Wdangling-else] > 969 | if (stop->gen.type == LineTypeString) > |^ > ArtText.c: In function ‘click’: > ArtText.c:1151:31: warning: variable ‘button’ set but not used > [-Wunused-but-set-variable] > 1151 | int x, y, button; > | ^~ > gcc -Wall -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 > -Wdate-time -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o ArtTree.o ArtTree.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from ArtTree.c:5: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > ArtTree.c: In function ‘ArtTreeNodeSetDashed’: > ArtTree.c:1284:8: warning: suggest explicit braces to avoid ambiguous ‘else’ > [-Wdangling-else] > 1284 | if (dashed) > |^ > gcc -Wall -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 > -Wdate-time -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o CloseSh.o CloseSh.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from CloseSh.c:5: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > gcc -Wall -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE
Bug#997640: pybluez: FTBFS: error in PyBluez setup command: use_2to3 is invalid.
Source: pybluez
Version: 0.23-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf PyBluez.egg*
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in PyBluez setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:23: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pybluez_0.23-3_unstable.log
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.
Bug#997639: python-keepalive: FTBFS: error in keepalive setup command: use_2to3 is invalid.
Source: python-keepalive
Version: 0.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in keepalive setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:9: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-keepalive_0.5-2_unstable.log
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.
Bug#997638: nas: FTBFS: ar: libdeps specified more than once
Source: nas Version: 1.9.4-7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/server/dia' > rm -f dispatch.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. > -I../include -I../../include -I../../lib/audio -I../../include-Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -DNASCONFSEARCHPATH=\"/etc/nas/\" > dispatch.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/string.h:26, > from ../include/os.h:124, > from ../include/misc.h:57, > from dispatch.c:52: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f dixutils.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. > -I../include -I../../include -I../../lib/audio -I../../include-Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -DNASCONFSEARCHPATH=\"/etc/nas/\" > dixutils.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/string.h:26, > from ../include/os.h:124, > from ../include/misc.h:57, > from dixutils.c:52: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f events.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. > -I../include -I../../include -I../../lib/audio -I../../include-Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -DNASCONFSEARCHPATH=\"/etc/nas/\" > events.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/string.h:26, > from ../include/os.h:124, > from ../include/misc.h:57, > from events.c:52: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f globals.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. > -I../include -I../../include -I../../lib/audio -I../../include-Dlinux > -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -DNASCONFSEARCHPATH=\"/etc/nas/\" > globals.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, >
Bug#997637: python-oauth: FTBFS: error in oauth setup command: use_2to3 is invalid.
Source: python-oauth
Version: 1.0.1-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean
> error in oauth setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:5: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-oauth_1.0.1-6_unstable.log
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.
Bug#997636: koules: FTBFS: ar: libdeps specified more than once
Source: koules Version: 1.4-27 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > make[3]: warning: -j4 forced in submake: resetting jobserver mode. > gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM > -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6 -ffast-math -I. > -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\" > -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\" -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o init.o init.c > gcc -Wdate-time -D_FORTIFY_SOURCE=2 -c -o mem.o mem.S > gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM > -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6 -ffast-math -I. > -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\" > -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\" -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o interface.o interface.c > gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM > -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6 -ffast-math -I. > -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\" > -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\" -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o shmbitmap.o shmbitmap.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from init.c:18: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdint.h:26, > from /usr/lib/gcc/x86_64-linux-gnu/11/include/stdint.h:9, > from interface.c:17: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdlib.h:25, > from shmbitmap.c:24: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM > -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6 -ffast-math -I. > -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\" > -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\" -Wdate-time
Bug#997635: flask-openid: FTBFS: error in Flask-OpenID setup command: use_2to3 is invalid.
Source: flask-openid
Version: 1.2.5+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with=python3,sphinxdoc --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in Flask-OpenID setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:9: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/flask-openid_1.2.5+dfsg-5_unstable.log
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.
Bug#997634: python-rdflib-jsonld: FTBFS: error in rdflib-jsonld setup command: use_2to3 is invalid.
Source: python-rdflib-jsonld
Version: 0.5.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in rdflib-jsonld setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:11: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-rdflib-jsonld_0.5.0-1_unstable.log
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.
Bug#997632: behave: FTBFS: error in behave setup command: use_2to3 is invalid.
Source: behave
Version: 1.2.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'upload-dir' will not be supported in future versions. Please
> use the underscore name 'upload_dir' instead
> warnings.warn(
> error in behave setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:5: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/behave_1.2.6-3_unstable.log
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.
Bug#997633: python-tempita: FTBFS: error in Tempita setup command: use_2to3 is invalid.
Source: python-tempita
Version: 0.5.2-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in Tempita setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-tempita_0.5.2-6_unstable.log
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.
Bug#997631: pycallgraph: FTBFS: error in pycallgraph2 setup command: use_2to3 is invalid.
Source: pycallgraph
Version: 1.1.3-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean
> error in pycallgraph2 setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pycallgraph_1.1.3-1.2_unstable.log
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.
Bug#997630: pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid.
Source: pygithub
Version: 1.43.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf *.egg-info
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in PyGithub setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pygithub_1.43.7-1_unstable.log
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.
Bug#997629: pyraf: FTBFS: error in setup command: use_2to3 is invalid.
Source: pyraf
Version: 2.1.15-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'author-email' will not be supported in future versions.
> Please use the underscore name 'author_email' instead
> warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'home-page' will not be supported in future versions. Please
> use the underscore name 'home_page' instead
> warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'requires-python' will not be supported in future versions.
> Please use the underscore name 'requires_python' instead
> warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'pre-hook.glob-data-files' will not be supported in future
> versions. Please use the underscore name 'pre_hook.glob_data_files' instead
> warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'pre-hook.pyraf-buildext-hook' will not be supported in future
> versions. Please use the underscore name 'pre_hook.pyraf_buildext_hook'
> instead
> warnings.warn(
> error in setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pyraf_2.1.15-2_unstable.log
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.
Bug#997628: mgp: FTBFS: ar: libdeps specified more than once
Source: mgp Version: 1.13a+upstream20090219-12 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/image' > rm -f imagetypes.o > gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable > -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function > -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L >-D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO-Wdate-time > -D_FORTIFY_SOURCE=2 -DFREETYPEFONTDIR="/usr/share/fonts/truetype" > -D_DEFAULT_SOURCE-D_GNU_SOURCE -DPACKAGE_NAME=\"\" > -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" > -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_FILE_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_STDARG_H=1 > -DHAVE_TERMIOS_H=1 -DHAVE_LOCALE_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void > -DHAVE_POLL=1 -DHAVE_STRSTR=1 -DHAVE_USLEEP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 > -DHAVE_MKSTEMP=1 -DHAVE_SNPRINTF=1 -DHAVE_MEMCMP=1 -DUSE_PNG=1 -DUSE_XFT2=1 > -DHAVE_ICONV=1 -DHAVE_FONTCONFIG_FONTCONFIG_H=1 -DUSE_GIF=1 -DUSE_IMLIB=1 > imagetypes.c > rm -f send.o > gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable > -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function > -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L >-D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO-Wdate-time > -D_FORTIFY_SOURCE=2 -DFREETYPEFONTDIR="/usr/share/fonts/truetype" > -D_DEFAULT_SOURCE-D_GNU_SOURCE -DPACKAGE_NAME=\"\" > -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" > -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_FILE_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_STDARG_H=1 > -DHAVE_TERMIOS_H=1 -DHAVE_LOCALE_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void > -DHAVE_POLL=1 -DHAVE_STRSTR=1 -DHAVE_USLEEP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 > -DHAVE_MKSTEMP=1 -DHAVE_SNPRINTF=1 -DHAVE_MEMCMP=1 -DUSE_PNG=1 -DUSE_XFT2=1 > -DHAVE_ICONV=1 -DHAVE_FONTCONFIG_FONTCONFIG_H=1 -DUSE_GIF=1 -DUSE_IMLIB=1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -DUUDECODE=\"/usr/bin/uudecode\" -DGUNZIP=\"/bin/gunzip\" -DUSE_SETLOCALE > -I/usr/include/libpng16 -I/usr/include send.c > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable > -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function > -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO-Wdate-time > -D_FORTIFY_SOURCE=2 -DFREETYPEFONTDIR="/usr/share/fonts/truetype" > -D_DEFAULT_SOURCE-D_GNU_SOURCE -c -o zio.o zio.c > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable > -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function > -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=19
Bug#997627: pixmap: FTBFS: ar: libdeps specified more than once
Source: pixmap Version: 2.6pl4-20 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/SelFile' > rm -f SelFile.o > gcc -c -g -O2 -fno-strict-aliasing -I. -I.. -I/usr/include/X11 > -I/usr/include/-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -DUSE_ATHENA > -DAPPDEFDIR=\"/etc/X11/app-defaults\" > -DRGBF=\"/etc/X11/rgb.txt\" SelFile.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from SelFile.c:46: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > SelFile.c: In function ‘SFexposeList’: > SelFile.c:153:9: warning: implicit declaration of function ‘SFdrawList’ > [-Wimplicit-function-declaration] > 153 | SFdrawList(n, SF_DO_NOT_SCROLL); > | ^~ > SelFile.c: In function ‘SFcreateWidgets’: > SelFile.c:275:9: warning: implicit declaration of function ‘SFinitFont’ > [-Wimplicit-function-declaration] > 275 | SFinitFont(); > | ^~ > SelFile.c:481:9: warning: implicit declaration of function ‘SFcreateGC’; did > you mean ‘XCreateGC’? [-Wimplicit-function-declaration] > 481 | SFcreateGC(); > | ^~ > | XCreateGC > SelFile.c: In function ‘SFopenFile’: > SelFile.c:568:5: warning: implicit declaration of function ‘SFchdir’; did you > mean ‘fchdir’? [-Wimplicit-function-declaration] > 568 | SFchdir(SFstartDir); > | ^~~ > | fchdir > SelFile.c: At top level: > SelFile.c:594:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 594 | SFtextChanged() > | ^ > SelFile.c: In function ‘SFtextChanged’: > SelFile.c:613:9: warning: implicit declaration of function ‘SFupdatePath’ > [-Wimplicit-function-declaration] > 613 | SFupdatePath(); > | ^~~~ > SelFile.c: At top level: > SelFile.c:624:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 624 | SFprepareToReturn() > | ^ > SelFile.c: In function ‘XsraSelFile’: > SelFile.c:710:33: warning: implicit declaration of function ‘SFsetText’; did > you mean ‘SFgetText’? [-Wimplicit-function-declaration] > 710 | SFsetText(SFcurrentPath); > | ^ > | SFgetText > rm -f Path.o > gcc -c -g -O2 -fno-strict-aliasing -I. -I.. -I/usr/include/X11 > -I/usr/include/-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -DUSE_ATHENA > -DAPPDEFDIR=\"/etc/X11/app-defaults\" > -DRGBF=\"/etc/X11/rgb.txt\" Path.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from Path.c:27: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > Path.c:86:1: warning: return type defaults to ‘int’ [-Wimplicit-int] >86 | SFfree(i) > | ^~ > Path.c:109:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 109 | SFunreadableDir(dir) > | ^~~ > Path.c:169:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 169 | SFreplaceText(dir, str) > | ^ > Path.c: In function ‘SFreplaceText’: > Path.c:183:17: warning: implicit declaration of function ‘SFsetText’ > [-Wimplicit-function-declaration] > 183 | SFsetText(
Bug#997626: django-restricted-resource: FTBFS: TypeError: Abstract models cannot be instantiated.
Source: django-restricted-resource
Version: 2016.8-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> # Run the bundled tests (in-memory database) when building the package
> LC_ALL=C python3 ./django_restricted_resource/test_project/manage.py test
> Creating test database for alias 'default'...
> System check identified some issues:
>
> WARNINGS:
> django_restricted_resource.ExampleRestrictedResource: (models.W042)
> Auto-created primary key used when not defining a primary key type, by
> default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
>
> System check identified 1 issue (0 silenced).
> ....
> ==
> ERROR: test_clean_is_okay_when_just_group_set
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_is_okay_when_just_group_set
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
> File
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
> line 64, in test_clean_is_okay_when_just_group_set
> resource = RestrictedResource(group=group)
> File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413,
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
>
>
> ==
> ERROR: test_clean_is_okay_when_just_user_set
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_is_okay_when_just_user_set
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
> File
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
> line 59, in test_clean_is_okay_when_just_user_set
> resource = RestrictedResource(user=user)
> File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413,
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
>
>
> ==
> ERROR: test_clean_raises_exception_when_both_user_and_group_is_set
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_raises_exception_when_both_user_and_group_is_set
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
> File
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
> line 54, in test_clean_raises_exception_when_both_user_and_group_is_set
> resource = RestrictedResource(user=user, group=group)
> File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413,
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
>
>
> ==
> ERROR: test_clean_raises_exception_when_owner_is_not_set
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_raises_exception_when_owner_is_not_set
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
> File
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
> line 48, in test_clean_raises_exception_when_owner_is_not_set
> resource = RestrictedResource()
> File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413,
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract
Bug#997625: node-jquery: FTBFS: DefaultsError: `ie8` is not a supported option
Source: node-jquery
Version: 3.5.1+dfsg+~3.5.5-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> mkdir -p external
> mkdir -p external/sizzle/dist
> ln -s /usr/share/javascript/sizzle/sizzle.js external/sizzle/dist
> grunt qunit_fixture
> Loading "babel.js" tasks...ERROR
> >> Error: Cannot find module '@babel/core'
> >> Require stack:
> >> - /usr/share/nodejs/grunt-babel/tasks/babel.js
> >> - /usr/share/nodejs/grunt/lib/grunt/task.js
> >> - /usr/share/nodejs/grunt/lib/grunt.js
> >> - /usr/share/nodejs/grunt-cli/bin/grunt
> >> grunt-babel@8 requires Babel 7.x (the package '@babel/core'). If you'd
> >> like to use Babel 6.x ('babel-core'), you should install 'grunt-babel@7'.
>
> Running "qunit_fixture" task
> >> Updated ./test/data/qunit-fixture.js.
>
> Done.
> grunt build:*:* uglify remove_map_comment dist:*
> Loading "babel.js" tasks...ERROR
> >> Error: Cannot find module '@babel/core'
> >> Require stack:
> >> - /usr/share/nodejs/grunt-babel/tasks/babel.js
> >> - /usr/share/nodejs/grunt/lib/grunt/task.js
> >> - /usr/share/nodejs/grunt/lib/grunt.js
> >> - /usr/share/nodejs/grunt-cli/bin/grunt
> >> grunt-babel@8 requires Babel 7.x (the package '@babel/core'). If you'd
> >> like to use Babel 6.x ('babel-core'), you should install 'grunt-babel@7'.
>
> Running "build:all:*" (build) task
> >> File 'dist/jquery.js' created.
>
> Running "uglify:all" (uglify) task
> DefaultsError: `ie8` is not a supported option
> at DefaultsError.get (:69:23)
> at formatError (internal/util/inspect.js:1164:38)
> at formatRaw (internal/util/inspect.js:937:14)
> at formatValue (internal/util/inspect.js:791:10)
> at inspect (internal/util/inspect.js:328:10)
> at formatWithOptions (internal/util/inspect.js:1989:40)
> at console.value (internal/console/constructor.js:308:14)
> at console.log (internal/console/constructor.js:343:61)
> at /usr/share/nodejs/grunt-contrib-uglify/tasks/uglify.js:156:17
> at Array.forEach (:null:null)
> at Object.
> (/usr/share/nodejs/grunt-contrib-uglify/tasks/uglify.js:90:16)
> at Object. (/usr/share/nodejs/grunt/lib/grunt/task.js:253:15)
> at Object.thisTask.fn (/usr/share/nodejs/grunt/lib/grunt/task.js:71:16)
> at Object. (/usr/share/nodejs/grunt/lib/util/task.js:294:30)
> at Task.runTaskFn (/usr/share/nodejs/grunt/lib/util/task.js:244:24)
> at Task. (/usr/share/nodejs/grunt/lib/util/task.js:293:12)
> at /usr/share/nodejs/grunt/lib/util/task.js:220:11
> at processTicksAndRejections (internal/process/task_queues.js:79:11)
> {
> defs: {
> annotations: false,
> ascii_only: false,
> beautify: false,
> braces: false,
> comments: false,
> galio: false,
> ie: false,
> indent_level: 4,
> indent_start: 0,
> inline_script: true,
> keep_quoted_props: false,
> max_line_len: false,
> preamble: null,
> preserve_line: false,
> quote_keys: false,
> quote_style: 0,
> semicolons: true,
> shebang: true,
> source_map: null,
> v8: false,
> webkit: false,
> width: 80,
> wrap_iife: false
> }
> }
> >> Uglifying source dist/jquery.js failed.
> Warning: Uglification failed.
> `ie8` is not a supported option.
> Use --force to continue.
>
> Aborted due to warnings.
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 6
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-jquery_3.5.1+dfsg+~3.5.5-7_unstable.log
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.
Bug#997624: python-defer: FTBFS: error in defer setup command: use_2to3 is invalid.
Source: python-defer
Version: 1.0.6-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with=python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 7 in use)
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'test_requires'
> warnings.warn(msg)
> error in defer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:7: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-defer_1.0.6-2.1_unstable.log
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.
Bug#997623: funcparserlib: FTBFS: error in funcparserlib setup command: use_2to3 is invalid.
Source: funcparserlib
Version: 0.3.6+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in funcparserlib setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:8: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/funcparserlib_0.3.6+dfsg1-1_unstable.log
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.
Bug#997622: kinput2: FTBFS: ar: libdeps specified more than once
Source: kinput2 Version: 3.1-13 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/lib' > rm -f AdoptedShe.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I../include > -Iimlib -I/usr/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO > AdoptedShe.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from AdoptedShe.c:21: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f AuxPanel.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I../include > -Iimlib -I/usr/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTOAuxPanel.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from AuxPanel.c:51: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f CandPanel.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I../include > -Iimlib -I/usr/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTOCandPanel.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrinsic.h:53, > from /usr/include/X11/IntrinsicP.h:51, > from CandPanel.c:21: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > CandPanel.c: In function ‘Notify’: > CandPanel.c:472:24: warning: cast to pointer from integer of different size > [-Wint-to-pointer-cast] > 472 |(XtPointer)cpw->cpanel.current); > |^ > rm -f Canvas.o > gcc -c -g -O2 -fno-strict-aliasing -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I../include > -Iimlib -I/usr/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE > -D_BSD_SOURCE -D_SVID_SOURCE > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTOCanvas.c > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from /usr/include/X11/Xlib.h:38, > from /usr/include/X11/Intrins
Bug#997621: fvwm1: FTBFS: ar: libdeps specified more than once
Source: fvwm1 Version: 1.24r-57 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>/libs' > gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -c -o CatString3.o CatString3.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from CatString3.c:1: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -c -o SendInfo.o SendInfo.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from SendInfo.c:1: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > SendInfo.c: In function ‘SendInfo’: > SendInfo.c:17:7: warning: implicit declaration of function ‘write’; did you > mean ‘fwrite’? [-Wimplicit-function-declaration] >17 | write(fd[0],, sizeof(unsigned long)); > | ^ > | fwrite > gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -c -o SendText.o SendText.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from SendText.c:1: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > SendText.c: In function ‘SendText’: > SendText.c:15:7: warning: implicit declaration of function ‘write’; did you > mean ‘fwrite’? [-Wimplicit-function-declaration] >15 | write(fd[0],, sizeof(unsigned long)); > | ^ > | fwrite > gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO -c -o wild.o wild.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from wild.c:1: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > wild.c: In function ‘matchWildcards’: > wild.c:23:15: warning: implicit declaration of function ‘strcmp’ > [-Wimplicit-function-declaration] >23 | else if(strcmp(pattern,"*")==0) > | ^~ > wild.c:2:1: note: include ‘’ or provide a declaration of ‘strcmp’ > 1 | #include > +++ |+#include > 2 | > gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=1993
Bug#997620: python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid.
Source: python-dexml
Version: 0.5.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in dexml setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-dexml_0.5.1-3_unstable.log
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.
Bug#997618: python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is invalid.
Source: python-jsmin
Version: 2.2.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3 --verbose
>dh_auto_clean -O--buildsystem=pybuild -O--verbose
> pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean
> error in jsmin setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-jsmin_2.2.2-2_unstable.log
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.
Bug#997619: python-mailer: FTBFS: error in mailer setup command: use_2to3 is invalid.
Source: python-mailer
Version: 0.8.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in mailer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-mailer_0.8.1-4_unstable.log
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.
Bug#997617: twofish: FTBFS: ar: libdeps specified more than once
Source: twofish Version: 0.3-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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_testdir > # > gcc -c -o twofish.o -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wextra -O0 twofish.c > twofish.c: In function ‘test_platform’: > twofish.c:498:58: warning: comparison of unsigned expression in ‘< 0’ is > always false [-Wtype-limits] > 498 | if( ((UInt32) ((UInt32)1 << 31) == 0) || ((UInt32)-1 < 0) ) > | ^ > ar clq libtwofish.a twofish.o > ar: libdeps specified more than once > make: *** [debian/rules:30: build-arch-stamp] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/twofish_0.3-5_unstable.log 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.
Bug#997616: python-anyjson: FTBFS: error in anyjson setup command: use_2to3 is invalid.
Source: python-anyjson
Version: 0.3.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 7 in use)
> I: pybuild base:232: python3.9 setup.py clean
> error in anyjson setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-anyjson_0.3.3-2_unstable.log
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.
Bug#997615: troffcvt: FTBFS: ar: libdeps specified more than once
Source: troffcvt Version: 1.04-25 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/portlib-1.01' > rm -f ato.o > gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I /<>/lib -I. -I/usr/local/include > -Dlinux -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE > -DX_LOCALE -DHAS_SYSCONF=0 -DHAS_FLOCK=1 -DHAS_FCNTL=0 > -DHAS_SYS_DIR_H=1 -DHAS_DIRENT_H=0-DHAS_BCOPY=1 ato.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from ato.c:13: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f dir.o > gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I /<>/lib -I. -I/usr/local/include > -Dlinux -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE > -DX_LOCALE -DHAS_SYSCONF=0 -DHAS_FLOCK=1 -DHAS_FCNTL=0 > -DHAS_SYS_DIR_H=1 -DHAS_DIRENT_H=0-DHAS_BCOPY=1 dir.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from dir.c:14: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f fd.o > gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I /<>/lib -I. -I/usr/local/include > -Dlinux -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE > -DX_LOCALE -DHAS_SYSCONF=0 -DHAS_FLOCK=1 -DHAS_FCNTL=0 > -DHAS_SYS_DIR_H=1 -DHAS_DIRENT_H=0-DHAS_BCOPY=1 fd.c > fd.c: In function ‘MaxFileDesc’: > fd.c:24:17: warning: implicit declaration of function ‘getdtablesize’ > [-Wimplicit-function-declaration] >24 | return (getdtablesize ()); > | ^ > rm -f lock.o > gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I /<>/lib -I. -I/usr/local/include > -Dlinux -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE > -DX_LOCALE -DHAS_SYSCONF=0 -DHAS_FLOCK=1 -DHAS_FCNTL=0 > -DHAS_SYS_DIR_H=1 -DHAS_DIRENT_H=0-DHAS_BCOPY=1 lock.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from lock.c:14: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f mem.o > gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I /<>/lib -I. -I/usr/local/include > -Dlinux -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE > -DX_LOCALE -DHAS_SYSCONF=0 -DHAS_FLOCK=1 -DHAS_FCNTL=0 > -DHAS_SYS_DIR_H=1 -DHAS_DIRENT_H=0-DHAS_BCOPY=1 mem.c > In file included from /usr/include/strings.h:21, > from mem.c:13: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > rm -f libport.a > ar clq libport.a ato.o dir.o fd.o lock.o mem.o > ar: libdeps specified more than once > make[3]: *** [Makefile:325: libport.a] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/troffcvt_1.04-25_unstable.log 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.
Bug#997614: python-parse-type: FTBFS: error in parse_type setup command: use_2to3 is invalid.
Source: python-parse-type
Version: 0.3.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'upload-dir' will not be supported in future versions. Please
> use the underscore name 'upload_dir' instead
> warnings.warn(
> error in parse_type setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-parse-type_0.3.4-3_unstable.log
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.
Bug#997613: blessings: FTBFS: error in blessings setup command: use_2to3 is invalid.
Source: blessings
Version: 1.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 7 in use)
> I: pybuild base:232: python3.9 setup.py clean
> error in blessings setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/blessings_1.6-3_unstable.log
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.
Bug#997611: wnn6-sdk: FTBFS: ar: libdeps specified more than once
Source: wnn6-sdk Version: 1.0.0-18 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/contrib/im/Xsi/Wnn/jlib' > Makefile:1435: warning: overriding recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/msg.o' > Makefile:1414: warning: ignoring old recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/msg.o' > Makefile:1435: warning: overriding recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/yincoding.o' > Makefile:1417: warning: ignoring old recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/yincoding.o' > Makefile:1435: warning: overriding recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/py_table.o' > Makefile:1420: warning: ignoring old recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/py_table.o' > Makefile:1435: warning: overriding recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/zy_table.o' > Makefile:1423: warning: ignoring old recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/zy_table.o' > Makefile:1435: warning: overriding recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/strings.o' > Makefile:1426: warning: ignoring old recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/strings.o' > Makefile:1435: warning: overriding recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/serverdefs.o' > Makefile:1429: warning: ignoring old recipe for target > '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/serverdefs.o' > rm -f js.o unshared/js.o > gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security > -I/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/include > -I/<>/contrib/im/Xsi/../../../contrib -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -Wdate-time > -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO > -DLIBDIR=\"/usr/local/lib/wnn6\" -DJAPANESE -DCHINESE -DKOREAN -DLATIN > -DWRITE_CHECK-g -O2 -fno-strict-aliasing -g js.c -o unshared/js.o > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from js.c:167: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > In file included from js.c:207: > ../etc/pwd.c: In function ‘new_pwd’: > ../etc/pwd.c:163:9: warning: implicit declaration of function ‘time’ > [-Wimplicit-function-declaration] > 163 | x = time(NULL); > | ^~~~ > js.c: In function ‘cd_open_in’: > js.c:506:14: warning: implicit declaration of function ‘inet_addr’ > [-Wimplicit-function-declaration] > 506 | ia = inet_addr(pserver); > | ^ > js.c: In function ‘_get_server_name’: > js.c:534:30: warning: implicit declaration of function ‘atoi’ > [-Wimplicit-function-declaration] > 534 | if (*(p+1)) offset = atoi(p+1); > | ^~~~ > js.c: In function ‘js_set_henkan_hinsi’: > js.c:1453:17: warning: implicit declaration of function ‘abs’ > [-Wimplicit-function-declaration] > 1453 | for(x = 0; x < abs(nhinsi); x++) put4com(hlist[x], env->js_id); > | ^~~ > js.c:208:1: note: include ‘’ or provide a declaration of ‘abs’ > 207 | #include "../etc/pwd.c" > +++ |+#include > 208 | > js.c: In function ‘js_access_get_info’: > js.c:5099:9: warning: implicit declaration of function ‘free’ > [-Wimplicit-function-declaration] > 5099 | free((char *)save); > | ^~~~ > js.c:5099:9: note: include ‘’ or provide a declaration of ‘free’ > js.c:5099:9: warning: incompatible implicit declaration of built-in function > ‘free’ [-Wbuiltin-declaration-mismatch] > js.c:5099:9: not
Bug#997612: vatnumber: FTBFS: error in vatnumber setup command: use_2to3 is invalid.
Source: vatnumber
Version: 1:1.2-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package vatnumber
> dpkg-buildpackage: info: source version 1:1.2-10
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Mathias Behrle
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> error in vatnumber setup command: use_2to3 is invalid.
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in vatnumber setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:9: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/vatnumber_1.2-10_unstable.log
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.
Bug#997610: suds: FTBFS: error in suds-community setup command: use_2to3 is invalid.
Source: suds
Version: 0.8.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in suds-community setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:9: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/suds_0.8.5-1_unstable.log
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.
Bug#997609: deap: FTBFS: error in deap setup command: use_2to3 is invalid.
Source: deap
Version: 1.3.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in deap setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:32: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/deap_1.3.1-2_unstable.log
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.
Bug#997608: easyprocess: FTBFS: error in EasyProcess setup command: use_2to3 is invalid.
Source: easyprocess
Version: 0.2.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in EasyProcess setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:5: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/easyprocess_0.2.5-2_unstable.log
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.
Bug#997607: python-fudge: FTBFS: error in fudge setup command: use_2to3 is invalid.
Source: python-fudge
Version: 1.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean
> error in fudge setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-fudge_1.1.0-2_unstable.log
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.
Bug#997606: simpleeval: FTBFS: error in simpleeval setup command: use_2to3 is invalid.
Source: simpleeval
Version: 0.9.10-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf .egg-info
> rm -rf PKG-INFO
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in simpleeval setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/simpleeval_0.9.10-1_unstable.log
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.
Bug#997605: pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid.
Source: pprofile
Version: 2.0.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package pprofile
> dpkg-buildpackage: info: source version 2.0.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Josue Ortega
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from pprofile-2.0.5/debian/source/options:
> --extend-diff-ignore=^[^/]*[.]egg-info/
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in pprofile setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:8: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pprofile_2.0.5-1_unstable.log
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.
Bug#997604: x2gobroker: FTBFS: error in x2gobroker setup command: use_2to3 is invalid.
Source: x2gobroker Version: 0.0.4.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 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 '/<>' > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE > -Wl,-z,relro -Wl,-z,now -pie > -DTRUSTED_BINARY=\"/usr/lib/x2go/x2gobroker-agent.pl\" -o > lib/x2gobroker-agent src/x2gobroker-agent.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE > -Wl,-z,relro -Wl,-z,now -pie -DTRUSTED_BINARY=\"/usr/bin/x2gobroker\" -o > bin/x2gobroker-ssh src/x2gobroker-ssh.c > python3 setup.py build > error in x2gobroker setup command: use_2to3 is invalid. > make[1]: *** [Makefile:68: build_pymodule] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/x2gobroker_0.0.4.3-1_unstable.log 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.
