Bug#999754: tcsh: character class expansion is badly broken
Please consider applying the following three patches as a minimal fix. 1) To fix the character range comparison bug: https://github.com/tcsh-org/tcsh/commit/4679bde3e1ceca63d6eb4de5ce41c996405e61aa.patch 2) To pass the current more stringent compiler options: https://github.com/tcsh-org/tcsh/commit/6974bc35a5cda6eab748e364bd76a860ca66968b.patch 3) To silence the warnings about _DEFAULT_SOURCE: https://github.com/tcsh-org/tcsh/commit/3a6eadd6a30e40667be14b374a234ddcdeb1e638.patch Kind regards, + Kimmo
Bug#994335: marked as done (pynfft: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Tue, 16 Nov 2021 05:18:49 +
with message-id
and subject line Bug#994335: fixed in pynfft 1.3.2-4
has caused the Debian Bug report #994335,
regarding pynfft: Removal of the python3-*-dbg packages in sid/bookworm
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.)
--
994335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pynfft
Version: 1.3.2-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal
Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
https://lists.debian.org/debian-python/2021/09/msg4.html
Stop building the python3-*-dbg package, but be careful
that all the reverse dependencies are also removed.
Please check for dependencies, build dependencies AND autopkg tests.
If help is needed, please ask on IRC #debian-python,
or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: pynfft
Source-Version: 1.3.2-4
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
pynfft, 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 994...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated pynfft package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 15 Nov 2021 23:51:47 -0500
Source: pynfft
Architecture: source
Version: 1.3.2-4
Distribution: unstable
Urgency: high
Maintainer: Debian Science Maintainers
Changed-By: Boyuan Yang
Closes: 994335
Changes:
pynfft (1.3.2-4) unstable; urgency=high
.
* Team upload.
* debian/control: Bump Standards-Version to 4.6.0.
* Drop -dbg package building. (Closes: #994335)
* debian/control: Bump debhelper compat to v13.
* debian/tests/python3:
+ Fix lintian warning uses-deprecated-adttmp.
* debian/control: Add missing variable substitution:
+ XB-Python3-Version: ${python3:Versions}
+ Provides: ${python3:Provides}
+ Built-Using: ${sphinxdoc:Built-Using}
Checksums-Sha1:
8a94d75895265c4fa7081d586f623972f9b0b8b2 2209 pynfft_1.3.2-4.dsc
fced9c0924568a7fde46bb7c02edaa6ba0c09fc1 180500 pynfft_1.3.2.orig.tar.gz
bddb1a0d6af219f071723632bf6c26d2414cf620 4508 pynfft_1.3.2-4.debian.tar.xz
601d01d8eb111695b9fbe0a7d90dca71d7600572 8610 pynfft_1.3.2-4_amd64.buildinfo
Checksums-Sha256:
6b09e51041afda0d83584a598f754d44212b485705aed2ebb9fe8862bf6561b3 2209
pynfft_1.3.2-4.dsc
ae41e720e569d0d99e3a44c82c36b35a49cfc9ecc23a1cd039fe9e2895aada2c 180500
pynfft_1.3.2.orig.tar.gz
2c50fbe3e5bfe62b8ffcfac61c68ae3a330184a37c0e5eb082c86424c798b3df 4508
pynfft_1.3.2-4.debian.tar.xz
2468a07958fcd8cf47223462c85dfccdd1d9d9fe8b6bdc1f832097853889b518 8610
pynfft_1.3.2-4_amd64.buildinfo
Files:
6c186aab3ca9cfa16d1e68901729cdb1 2209 science optional pynfft_1.3.2-4.dsc
d2457a3f43839a8acce3295c60d5e692 180500 science optional
pynfft_1.3.2.orig.tar.gz
43f5a75b85491bdb382a5df700974c7c 4508 science optional
pynfft_1.3.2-4.debian.tar.xz
f9a9a1a4c1f241e142dcb49105565c59 8610 science optional
pynfft_1.3.2-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmGTOjUACgkQwpPntGGC
Ws6imxAAmrsQ41WfaN4EjYJ35KPHGmFaL7oD9GZqq3eUu/xIrH3DTvNm13n5Jrds
nf5doNaqaWQpiOZ0cwmrYX/3Trc2FMWoej6nd/3R2fy7oaSz1lImcqxIcDMWWQzt
IjSJVhcvjA38aCx6uXPhx3YWUJIUOq6VLqOdsZBB89FCv/l9Yef5vOuOYfgCgALx
GVaKwYWp3/UNUdGnrAo+GWcMl/8sRsCvHfdmMkyRWOikTKizZPCPpXN9NM2dTwQW
GAmVJQTTv1eJV8XJP1m/Y/rqr+Kk1/SUkxB7cbYe/hAQu2Rt+e7i1XiSTFb5h+g+
/+5nCRk/3hAr+iLkUzRS1YOIc2lTXM6Cb7+jjx7ZHIAgS8usMbyR733sERFV2L1f
U6dmjwOmgB9l1PpJ8PP5Ou8U0HYw0nWBR9k/O7gJNqYLJb9CusAeRuHA20wkRfp9
7X8tetiuBF6wUYjBmpDmLOTeXNtZgv4hnW+SSan/lgYnEaVXBAIOr7FBnEtZPeEn
gJKYdVKgGLRZh8TXxJgajQUXcgPRRpEKyHEIlC4CtLutvXcsyAjH7des0PcSowPZ
mZLFXT3yC8Ewn7zqbuoJ0cbrKREqQHd6Ya4BGYs7b4XoBe5KVRCFfruVhngucFSF
cUxsPsWEBKlAsDtpt56SddjZL4KbJyPuUHQmw0Qe+12INcGNiIQ=
=HUZn
-END PGP SIGNATURE End Message ---
Bug#999754: tcsh: character class expansion is badly broken
Package: tcsh Version: 6.21.00-1.1 Severity: grave Tags: newcomer Justification: causes non-serious data loss Dear Maintainer, tcsh does not respect character classes. Minimal example: $ mkdir a $ touch a/a a/B $ echo a/[a-z] a/a a/B I expect the result to simply be 'a/a' since 'B' is not in [a-z]. The behavior generalizes to character classes in wildcards - it is not just about the trivial one-character filename example seen here. This is in locale en_US.UTF-8, but switching to locale "C" has the same behavior. This behavior can result in data loss with e.g. 'rm [a-z]*' removing unexpected files, and can also result in operating on the wrong files, so I have tentatively classified it 'grave'. tcsh as packaged is unusable for my purposes. I have verified that tcsh built from the current upstream (version 6.23.00) with $ git clone g...@github.com:tcsh-org/tcsh.git $ cd tcsh $ configure && make Does NOT suffer this behavior, while tcsh built from the Debian source package with $ apt-get --build source tcsh DOES suffer this behavior. The 6.23.00 built from upstream has the same $version string options as the Debian 6.21.00 except for "nd" (NODOT). I attempted to build from the upstream repository at version 6.21.00 but could not successfully build after 'configure', so I cannot tell if this is a bug introduced by the Debian-specific changes, or a bug in the upstream 6.21.00. The differences between the Debian source package with patches applied vs. upstream 6.21.00 source are smallish and don't obviously implicate character classes but that proves nothing. Suggested resolutionn is to update the buster package to tcsh 6.23.00. I believe this will also result in elimination of a large number of warning messages during the build of form /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" | ^~~ -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/12 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 not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tcsh depends on: ii libc6 2.31-13+deb11u2 ii libcrypt1 1:4.4.18-4 ii libtinfo6 6.2+20201114-2 tcsh recommends no packages. tcsh suggests no packages.
Bug#996208: marked as done (ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)
Your message dated Tue, 16 Nov 2021 02:39:01 + with message-id and subject line Bug#996208: fixed in ruby-commander 4.5.2-2 has caused the Debian Bug report #996208, regarding ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 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.) -- 996208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-commander Version: 4.5.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-commander was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > RuntimeError: >The `SortedSet` class has been extracted from the `set` library.You > must use the `sorted_set` gem or other alternatives. > # ./lib/commander/user_interaction.rb:347:in `const_get' > # ./lib/commander/user_interaction.rb:347:in `block in method_missing' > # ./lib/commander/user_interaction.rb:346:in `map' > # ./lib/commander/user_interaction.rb:346:in `method_missing' > # ./spec/methods_spec.rb:49:in `block (4 levels) in ' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- sorted_set > # ./lib/commander/user_interaction.rb:347:in `const_get' > > Finished in 0.15647 seconds (files took 0.27216 seconds to load) > 134 examples, 1 failure > > Failed examples: > > rspec ./spec/methods_spec.rb:47 # Commander::Methods AskForClass defining > methods implements "ask_for_*" > > Coverage report generated for RSpec to /<>/coverage. 398 / 473 > LOC (84.14%) covered. > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-commander/ruby-commander_4.5.2-1+rebuild1633376972_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-commander Source-Version: 4.5.2-2 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-commander, 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. Daniel Leidert (supplier of updated ruby-commander package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Nov 2021 02:24:36 +0100 Source: ruby-commander Architecture: source Version: 4.5.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 996208 Changes: ruby-commander (4.5.2-2) unstable; urgency=medium . * Team upload. * d/control (Build-Depends): Bump dh to version 13. (Standards-Version): Bump to 4.6.0. (Depends, Build-Depends): Use ruby-sorted-set required by the const_get() method (closes: #996208). * d/copyright (Copyright): Update. * d/upstream/metadata (Bug-Submit, Changelog): Update URLs. Checksums-Sha1: 9d1ae6f9749e32600bc718652172c26925ba17ca 2134 ruby-commander_4.5.2-2.dsc 34b1b712df90afdbb24f2b2b7accc1a5185e2deb 4044 ruby-commander_4.5.2-2.debian.tar.xz e49f3d1cae329a7a6f0555ee2e6615f1a9c70036 9701 ruby-commander_4.5.2-2_amd64.buildinfo Checksums-Sha256: 798d82389d25ea91a35fbc970a9a8843b61668fa49afeb21cb394aa71537068b 2134 ruby-commander_4.5.2-2.dsc 2a234b6ce29b6c5b3b7ccb8908346d4b95ac0b6a109f0de44dc3609d7e16213f 4044 ruby-commander_4.5.2-2.debian.tar.xz 9a031c84ad30d8694d3adf05f2adcc5715001008d2bae0fab6a0c9cf70b5ea45 9701 ruby-commander_4.5.2-2_amd64.buildinfo Files: a23c58aca4e7153f2ae1fb1e555086b7 2134 ruby
Bug#999753: wine-development: unsatisfiable build-dependency on unicode-data (< 14)
Source: wine-development Version: 6.0+repack-1 Severity: serious Usertag: edos-uninstallable Hi, wine-development build-deoends on unicode-data (< 14) but the version in testing and in sid is 14.0.0-1.1. -Ralf.
Bug#998555: marked as done (cinnamon-session: FTBFS: ../meson.build:2:0: ERROR: Unknown options: "frequent-warnings")
Your message dated Tue, 16 Nov 2021 01:49:00 + with message-id and subject line Bug#998555: fixed in cinnamon-session 5.0.1-3 has caused the Debian Bug report #998555, regarding cinnamon-session: FTBFS: ../meson.build:2:0: ERROR: Unknown options: "frequent-warnings" 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.) -- 998555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cinnamon-session Version: 5.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- \ > -Ddocbook=true \ > -Dfrequent-warnings=true \ > -Dgconf=false \ > -Dipv6=true \ > -Dxtrans=true \ > --libexecdir=/usr/lib/x86_64-linux-gnu/cinnamon-session > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Ddocbook=true > -Dfrequent-warnings=true -Dgconf=false -Dipv6=true -Dxtrans=true > --libexecdir=/usr/lib/x86_64-linux-gnu/cinnamon-session > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:2:0: ERROR: Unknown options: "frequent-warnings" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:50:14.850918 > Main binary: /usr/bin/python3 > Build Options: -Ddocbook=true -Dfrequent-warnings=true -Dgconf=false > -Dipv6=true -Dxtrans=true -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlibexecdir=/usr/lib/x86_64-linux-gnu/cinnamon-session -Dlocalstatedir=/var > -Dsysconfdir=/etc -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:2:0: ERROR: Unknown options: "frequent-warnings" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Ddocbook=true > -Dfrequent-warnings=true -Dgconf=false -Dipv6=true -Dxtrans=true > --libexecdir=/usr/lib/x86_64-linux-gnu/cinnamon-session returned exit code 1 > make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/cinnamon-session_5.0.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. --- End Message --- --- Begin Message --- Source: cinnamon-session Source-Version: 5.0.1-3 Done: Fabio Fantoni We believe that the bug you reported is fixed in the latest version of cinnamon-session, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Fantoni (supplier of updated cinnamon-session package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Nov 2021 11:55:33 +0100 Source: cinnamon-session Architecture: source Version: 5.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Cinnamon Team Changed-By: Fabio Fantoni Closes: 998555 Changes: cinnamon-session (5.0.1-3) unstable; urgency=medium . * d/rules: - fix a configure option (Closes: #998555) - hardening from bindnow to all
Bug#997101: marked as done (gimp-texturize: FTBFS: type_traits:44:3: error: template with C linkage)
Your message dated Tue, 16 Nov 2021 01:49:07 +
with message-id
and subject line Bug#997101: fixed in gimp-texturize 2.2-1
has caused the Debian Bug report #997101,
regarding gimp-texturize: 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.)
--
997101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp-texturize
Version: 2.1-11
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):
> g++ -DHAVE_CONFIG_H -I. -I.. -I.. -pthread -I/usr/include/gimp-2.0
> -I/usr/include/gegl-0.4 -I/usr/include/gio-unix-2.0
> -I/usr/include/json-glib-1.0 -I/usr/include/babl-0.1 -I/usr/include/gtk-2.0
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
> -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
> -I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include
> -DLOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/gimp-texturize"\"
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c -o graphcut.o
> graphcut.cpp
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from offset.c:6:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
> deprecated [-Wdeprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
> from /usr/include/glib-2.0/gobject/gbinding.h:29,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /usr/include/glib-2.0/gio/gioenums.h:28,
> from /usr/include/glib-2.0/gio/giotypes.h:28,
> from /usr/include/glib-2.0/gio/gio.h:26,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from offset.c:6:
> /usr/include/glib-2.0/gobject/gtype.h:698:1: note: declared here
> 698 | {
> | ^
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from compter.c:4:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
> deprecated [-Wdeprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
> from /usr/include/glib-2.0/gobject/gbinding.h:29,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /usr/include/glib-2.0/gio/gioenums.h:28,
> from /usr/include/glib-2.0/gio/giotypes.h:28,
> from /usr/include/glib-2.0/gio/gio.h:26,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from compter.c:4:
> /usr/include/glib-2.0/gobject/gtype.h:698:1: note:
Bug#996208: marked as pending in ruby-commander
Control: tag -1 pending Hello, Bug #996208 in ruby-commander 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/ruby-team/ruby-commander/-/commit/c00887d3bebbd0cc947ee0623dc0259665b3f050 Fix FTBFS * d/control (Depends, Build-Depends): Use ruby-sorted-set required by the const_get() method (closes: #996208). https://dev.to/aaronc81/removing-functionality-the-ruby-way-a-look-into-sortedset-on-ruby-3-clf (this message was generated automatically) -- Greetings https://bugs.debian.org/996208
Processed: Bug#996208 marked as pending in ruby-commander
Processing control commands: > tag -1 pending Bug #996208 [src:ruby-commander] ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) pending. -- 996208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995653: django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name'
Control: reassign -1 src:hyperkitty 1.3.4-4 Control: retitle -1 hyperkitty FTBFS with django-mailman3 1.3.7 Control: tags -1 ftbfs bookworm sid On Sun, Oct 03, 2021 at 07:15:18PM +0200, Paul Gevers wrote: >... >passfail > django-mailman3from testing1.3.7-1 > hyperkitty from testing1.3.4-4 > all others from testingfrom testing >... > == > ERROR: test_basic_reply (hyperkitty.tests.lib.test_posting.PostingTestCase) > -- > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py", > line 69, in test_basic_reply > self.user.save() > File > "/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line > 66, in save > super().save(*args, **kwargs) > File "/usr/lib/python3/dist-packages/django/db/models/base.py", line > 743, in save > self.save_base(using=using, force_insert=force_insert, > File "/usr/lib/python3/dist-packages/django/db/models/base.py", line > 791, in save_base > post_save.send( > File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", > line 173, in send > return [ > File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", > line 174, in > (receiver, receiver(signal=self, sender=sender, **named)) > File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line > 101, in create_profile > address.display_name = new_display_name > AttributeError: 'str' object has no attribute 'display_name' >... This is also a FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hyperkitty.html cu Adrian
Processed: Re: Bug#995653: django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name'
Processing control commands: > reassign -1 src:hyperkitty 1.3.4-4 Bug #995653 [src:django-mailman3, src:hyperkitty] django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name' Bug reassigned from package 'src:django-mailman3, src:hyperkitty' to 'src:hyperkitty'. No longer marked as found in versions hyperkitty/1.3.4-4 and django-mailman3/1.3.7-1. Ignoring request to alter fixed versions of bug #995653 to the same values previously set Bug #995653 [src:hyperkitty] django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name' Marked as found in versions hyperkitty/1.3.4-4. > retitle -1 hyperkitty FTBFS with django-mailman3 1.3.7 Bug #995653 [src:hyperkitty] django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name' Changed Bug title to 'hyperkitty FTBFS with django-mailman3 1.3.7' from 'django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name''. > tags -1 ftbfs bookworm sid Bug #995653 [src:hyperkitty] hyperkitty FTBFS with django-mailman3 1.3.7 Added tag(s) ftbfs. -- 995653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 995625
Processing commands for cont...@bugs.debian.org: > tags 995625 + patch Bug #995625 [src:httping] httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 995625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999751: di-netboot-assistant: please drop shellcheck autopkgtest
Source: di-netboot-assistant
Version: 0.71
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, shellch...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:shellcheck
Dear maintainer(s),
With a recent upload of shellcheck the autopkgtest of di-netboot-assistant
fails in testing when that autopkgtest is run with the binary packages
of shellcheck from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
shellcheck from testing0.8.0-2
di-netboot-assistantfrom testing0.71
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of shellcheck to
testing [1]. Of course, shellcheck shouldn't just break your autopkgtest
(or even worse, your package), but in this case shellcheck just evolved.
Static analysis tools are intended to run on source code, while
autopkgtest is intended to run against installed packages, where source
code is in principle not relevant; we want to know whether the binary
packages, as provided in the Debian archive, work correctly. In our
opinion running this type of tools as integration tests in autopkgtest,
or even as build-time tests is Wrong™, and should not be done. (Having
them run in salsaci or equivalent is of course totally great.)
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
[1] https://qa.debian.org/excuses.php?package=shellcheck
https://ci.debian.net/data/autopkgtest/testing/amd64/d/di-netboot-assistant/16684224/log.gz
autopkgtest [03:27:30]: test command1: shellcheck -x
/usr/bin/di-netboot-assistant ; shellcheck -x -s dash
/var/lib/dpkg/info/di-netboot-assistant.post*
/var/lib/dpkg/info/di-netboot-assistant.pre*
autopkgtest [03:27:30]: test command1: [---
In /usr/bin/di-netboot-assistant line 452:
echo -e "MENU BACKGROUND ::${s#$TFTP_ROOT}\n" >> pxelinux.cfg/default
^^ SC2295 (info):
Expansions inside ${..} need to be quoted separately, otherwise they
match as patterns.
Did you mean:
echo -e "MENU BACKGROUND ::${s#"$TFTP_ROOT"}\n" >> pxelinux.cfg/default
For more information:
https://www.shellcheck.net/wiki/SC2295 -- Expansions inside ${..} need to b...
autopkgtest [03:27:32]: test command1: ---]
autopkgtest [03:27:32]: test command1: - - - - - - - - - - results -
- - - - - - - - -
command1 FAIL non-zero exit status 1
I took the liberty to base the body of this email on bugreport
#992798, from Paul Gevers,
--
Samuel Henrique
Processed: di-netboot-assistant: please drop shellcheck autopkgtest
Processing control commands: > affects -1 src:shellcheck Bug #999751 [src:di-netboot-assistant] di-netboot-assistant: please drop shellcheck autopkgtest Added indication that 999751 affects src:shellcheck -- 999751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999750: lix FTBFS with ldc 1.28.0
Source: lix Version: 0.9.29-1.1 Severity: serious Tags: ftbfs The attempts to rebuild lix against ldc 1.28.0 failed, on amd64, i386 and armhf the build failed with. /usr/lib/ldc/x86_64-linux-gnu/include/d/std/algorithm/comparison.d(1531,6): Warning: skipping definition of function `std.algorithm.comparison.max!(int, int).max` due to previous definition for the same mangled name: _D3std9algorithm10comparison__T3maxTiTiZQjFNaNbNiNfiiZi Error: warnings are treated as errors While on arm64 it failed with dub build -f -b releaseXDG --cache=local --compiler=ldc2 make[1]: *** [debian/rules:23: override_dh_auto_build] Segmentation fault
Bug#997531: marked as done (extra-xdg-menus: FTBFS: rmdir: failed to remove '/<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/': No such file or directory)
Your message dated Mon, 15 Nov 2021 22:33:59 + with message-id and subject line Bug#997531: fixed in extra-xdg-menus 1.0-6 has caused the Debian Bug report #997531, regarding extra-xdg-menus: FTBFS: rmdir: failed to remove '/<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/': No such file or directory 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.) -- 997531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: extra-xdg-menus Version: 1.0-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 '/<>' > # Remove un-needed translation files (translations are merged into the > .directory files) > rm -rf /<>/debian/extra-xdg-menus/usr/share/locale/ > rm -rf /<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/locale/ > rmdir /<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/ > rmdir: failed to remove > '/<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/': No such file or > directory > make[1]: *** [debian/rules:14: execute_after_dh_auto_install] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/extra-xdg-menus_1.0-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: extra-xdg-menus Source-Version: 1.0-6 Done: Håvard Flaget Aasen We believe that the bug you reported is fixed in the latest version of extra-xdg-menus, 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. Håvard Flaget Aasen (supplier of updated extra-xdg-menus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Nov 2021 21:03:29 +0100 Source: extra-xdg-menus Architecture: source Version: 1.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard Flaget Aasen Closes: 997531 Changes: extra-xdg-menus (1.0-6) unstable; urgency=medium . * QA upload. * d/rules: Remove lines deleting non existing directory. Closes: #997531 Checksums-Sha1: d6be65ff255f8ad0cd3c2bd830a4428761352dd9 1611 extra-xdg-menus_1.0-6.dsc 9b925707165d01a626c4baecc89d5163344cc321 2720 extra-xdg-menus_1.0-6.debian.tar.xz 388583fde13cff7cf24ea65cc76e3b47a9fe5e5e 6448 extra-xdg-menus_1.0-6_source.buildinfo Checksums-Sha256: 09fa68e47aceca4452eda38b8d45763686706839d29a684e3afbdcb318a395b6 1611 extra-xdg-menus_1.0-6.dsc 90090eab9f4189c0936c4e3a4f1f58e68245634e16840a7ed71a1acc90afe84c 2720 extra-xdg-menus_1.0-6.debian.tar.xz 3cc78aed3a1b08aca1704b8c81c8852575102db2c83d2f09898667399bc11d21 6448 extra-xdg-menus_1.0-6_source.buildinfo Files: 39c77dd44aa90ad5d801be39ca716ef7 1611 misc optional extra-xdg-menus_1.0-6.dsc 56148bda5bbd695db69b585a1401a803 2720 misc optional extra-xdg-menus_1.0-6.debian.tar.xz 44ba137856174c99a7bcc9d1f61bbe78 6448 misc optional extra-xdg-menus_1.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmGS3MAACgkQH1x6i0VW QxQgRgwAs06JeiF0mx5UUivBtacpiGswj6sTy/Z6ThsxZXPOzvNNSEUx1IIQwkY0 Ez2XyG9wh+DfV3Vke2akif6jGX5f/EDDaZawhD/47WBNMypDOLCWJHE/eYnqwyEF xMaR7ddW96AQMdektNMot+KVt5AWYEb+HHXdYGPt/wleBsSjlFp7NvmJTs1paZuo R8VZ66QdnkfydrmTMUMCUFo65XAJuSGJpfdOWk06AMBeKcb7rcpRw2K23O32wycA cRLd9mov+UgM3UGHphe1lYA8uxhamAdvlY2gLzNPsyCwpABGanQTfJ+1pEdm+4jV pDcaz5TsBnKlgOPUYlwYbSfdqbZpQ1p5Ckjb+kmGd7dvHlHDN8w4tb4nl9AHR6AH 0+Hf4jd0I5fTIVcOTybuzew//viRuq3a+fkz+q/APVnWX+tFd283SBRO1NlnKokf QajfDYBmICtU/9CYmRynLOoatu9ft9a7fZvmbM30dGQJBIgTuycwJD9YhRxPWIRQ bl0ntAnr =91Rg
Bug#984301: marked as done (proftmb: ftbfs with GCC-11)
Your message dated Mon, 15 Nov 2021 22:19:14 +
with message-id
and subject line Bug#984301: fixed in proftmb 1.1.12-10
has caused the Debian Bug report #984301,
regarding proftmb: ftbfs with GCC-11
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.)
--
984301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:proftmb
Version: 1.1.12-9
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/proftmb_1.1.12-9_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
HMMOutput.h:24:44: warning: ISO C++ forbids converting a string constant to
‘char*’ [-Wwrite-strings]
24 | void PrintEmit(ostream&,Par&,uint,char* ="");
|^
In file included from proftmb.cpp:20:
Zscore.h:9:49: error: ISO C++17 does not allow dynamic exception specifications
9 | Z_Calibrate(set >&,int,double) throw (string&);
| ^
In file included from proftmb.cpp:22:
Eval.h:48:59: error: ISO C++17 does not allow dynamic exception specifications
48 | float RelativeEntropy(vector& A, vector& B) throw (char
*);
| ^
proftmb.cpp:68:88: error: ISO C++17 does not allow dynamic exception
specifications
68 | const char *, double, Par&,
const char*, bool) throw (string &);
|
^
proftmb.cpp:273:113: error: ISO C++17 does not allow dynamic exception
specifications
273 | const char *datfile, double
cut, Par& m, const char *name, bool multiQ) throw (string &) {
|
^
make[3]: *** [Makefile:537: BaumWelch.o] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from TrainSeq.h:5,
from Eval.h:11,
from Eval.cpp:6:
Seq.h:85:53: error: ISO C++17 does not allow dynamic exception specifications
85 | bool InitLabels(set >&) throw (string&);
| ^
Seq.h:194:67: error: ISO C++17 does not allow dynamic exception specifications
194 | static map > > Read(char*) throw
(string&);
| ^
In file included from TrainSeq.h:6,
from Eval.h:11,
from Eval.cpp:6:
Par.h:34:36: error: ISO C++17 does not allow dynamic exception specifications
34 | static void LoadL2L(char*) throw (string&);
|^
Par.h:35:36: error: ISO C++17 does not allow dynamic exception specifications
35 | static void LoadL2A(char*) throw (string&);
|^
Par.h:36:36: error: ISO C++17 does not allow dynamic exception specifications
36 | static void LoadA2E(char*) throw (string&);
Processed: Bug#984301 marked as pending in proftmb
Processing control commands: > tag -1 pending Bug #984301 [src:proftmb] proftmb: ftbfs with GCC-11 Added tag(s) pending. -- 984301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984301: marked as pending in proftmb
Control: tag -1 pending Hello, Bug #984301 in proftmb 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/med-team/proftmb/-/commit/bf153faa70740ee6b35127c133de2d8affa0de63 Add gcc-11.patch; fix ftbfs Closes: #984301 Fix several problems of conformance with ISO C++17. (this message was generated automatically) -- Greetings https://bugs.debian.org/984301
Bug#994239: marked as done (work around ftbfs with GCC 11)
Your message dated Mon, 15 Nov 2021 21:34:43 + with message-id and subject line Bug#994239: fixed in micropython 1.17+ds-1.1 has caused the Debian Bug report #994239, regarding work around ftbfs with GCC 11 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.) -- 994239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:micropython Version: 1.17+ds-1 Severity: important Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 proposed workaround: --- micropython-1.14+ds/debian/rules2021-02-16 09:52:54.0 + +++ micropython-1.17+ds/debian/rules2021-09-14 11:02:24.0 + @@ -3,8 +3,8 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-format -export DEB_CFLAGS_MAINT_APPEND = -Wformat -Werror=format-security -export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed +export DEB_CFLAGS_MAINT_APPEND = -Wformat -Werror=format-security -Wno-error=maybe-uninitialized +export DEB_LDFLAGS_MAINT_APPEND = export BUILD_VERBOSE = 1 --- End Message --- --- Begin Message --- Source: micropython Source-Version: 1.17+ds-1.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of micropython, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated micropython package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 15:51:19 -0500 Source: micropython Architecture: source Version: 1.17+ds-1.1 Distribution: unstable Urgency: high Maintainer: Yangfl Changed-By: Boyuan Yang Closes: 994239 Changes: micropython (1.17+ds-1.1) unstable; urgency=high . * Non-maintainer upload. * debian/rules: Circumvent FTBFS with gcc 11 using -Wno-error=maybe-uninitialized cflag. (Closes: #994239) Checksums-Sha1: 4a66582bac55bff9303f7e3764f8c7f84c0f45ca 2138 micropython_1.17+ds-1.1.dsc 6af84a9e567ea7377f59d22d84b53ec9d56a8c98 4894356 micropython_1.17+ds.orig.tar.xz b4f58765b0e4244850a3672bf6d2cff81e4e5580 14532 micropython_1.17+ds-1.1.debian.tar.xz cb2c39125ebdfca3b53e2392d42a33426e898aa8 9034 micropython_1.17+ds-1.1_amd64.buildinfo Checksums-Sha256: c52feb622e66091e0de1ea88a85bdbec89dce457db11f7053badb863c66260b9 2138 micropython_1.17+ds-1.1.dsc a5fd06560febf7a8a318c41681e871961fea46f35dad53fbb17262c98b9a57b6 4894356 micropython_1.17+ds.orig.tar.xz 7a32ede9822b1625f5b9708e584aa6cb1e10c16ecc5388b670e53a704d9d5d4a 14532 micropython_1.17+ds-1.1.debian.tar.xz 0683cbcb0aee209950fd048d2eb43a66866165f9c4883d078756f667a8efcb32 9034 micropython_1.17+ds-1.1_amd64.buildinfo Files: 114233f5859c07741c07e1327c992b2b 2138 python optional micropython_1.17+ds-1.1.dsc 54a459435a41a807debbeb7cc404100e 4894356 python optional micropython_1.17+ds.orig.tar.xz 71d872897206bba9b1cbe29f4fd18ad7 14532 python optional micropython_1.17+ds-1.1.debian.tar.xz 0676de51b6cc75538ca9ed86dae76731 9034 python optional micropython_1.17+ds-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmGMMiYACgkQwpPntGGC Ws605RAAwMqq1y44K1A6wuPNKV8CLEJNXZrvJbed8KN4VJ1mMsvf+rIznJotdpCQ w15K9D3BnV7gI+X3CjwO4d4KU+O6A9lBQOl0qOk93NtCPNZLTNsy9/MlzMgcntzz IhHbzf0CB/sF1sWc1E9tpTN5hTDC0U0EoCMzadKJJI3UgNcL4C08NHzUZDcyGi6c g9nBHb476bexXsnmJcvzeOgZk7SzMb1AdWsqAmtN+IYJmx7rEOLIBSrHE/AdjN9S u9gFKPotJqlk8AWQtJHjrO4ufr4PJ2JZ6L9oBlpq0OBr25IBE0W/KHYk7ZuwzeHx GkucAS3Ew/Yu2EEjfxiydAjpxwZVflazy9IV3KgNzRQt2h6jAFsbSXXonx+dDa0y ocPteNMxw82XdZ75EM1uVoZrHTPPRm7pOfOvOhPDO2OdH7LZtkCon4V/1xjYQ62s 4bVKOm915wtbh7pxmn9/hVhnkGsjr3ldp+4zlsdaW6KkinvpXchIFmg8acTHgGBF ByU3kZrWoXfDLzFyunV17zjf4ArRsWqNSRxK7+DcSEWzYgFhSMdOd2ZfRXVJZsRK TbRWjvVOar6bxf5oOQf9Rb70H8Bg3TCNSHNXkbDvMdI7sUPig6h2mixhzqZtFzoT z2qmlc1ggG7vQq4fY86OXHTxOAoZfznWZqXVZUjhZRznIzEo9Yo= =uAx+ -END PGP SIGNATURE End Message ---
Bug#999642: marked as done (muttdown: FTBFS due to missing B-D: python3-six)
Your message dated Mon, 15 Nov 2021 21:22:29 +
with message-id
and subject line Bug#999642: fixed in muttdown 0.3.5-1
has caused the Debian Bug report #999642,
regarding muttdown: FTBFS due to missing B-D: python3-six
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.)
--
999642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: muttdown
Version: 0.3.4-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source
Hi,
muttdown recently started to FTBFS, probably because some B-D dropped
its dependency on python3-six:
dh_auto_test -O--buildsystem=pybuild
pybuild --test --test-pytest -i python{version} -p 3.9
I: pybuild base:237: cd
/build/muttdown-0.3.4/.pybuild/cpython3_3.9_muttdown/build; python3.9 -m pytest
tests
= test session starts ==
platform linux -- Python 3.9.8, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /build/muttdown-0.3.4
plugins: mock-3.6.1
collected 0 items / 2 errors
ERRORS
__ ERROR collecting .pybuild/cpython3_3.9_muttdown/build/tests/test_basic.py ___
ImportError while importing test module
'/build/muttdown-0.3.4/.pybuild/cpython3_3.9_muttdown/build/tests/test_basic.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_basic.py:18: in
from muttdown import main
muttdown/main.py:14: in
import six
E ModuleNotFoundError: No module named 'six'
__ ERROR collecting .pybuild/cpython3_3.9_muttdown/build/tests/test_config.py __
ImportError while importing test module
'/build/muttdown-0.3.4/.pybuild/cpython3_3.9_muttdown/build/tests/test_config.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_config.py:3: in
from muttdown.config import Config
muttdown/config.py:6: in
import six
E ModuleNotFoundError: No module named 'six'
=== warnings summary ===
muttdown/main.py:32
/build/muttdown-0.3.4/.pybuild/cpython3_3.9_muttdown/build/muttdown/main.py:32:
DeprecationWarning: invalid escape sequence \s
text = re.sub('\s*!m\s*', '', text, re.M)
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
ERROR tests/test_basic.py
ERROR tests/test_config.py
!!! Interrupted: 2 errors during collection
= 1 warning, 2 errors in 0.11s =
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=2: cd
/build/muttdown-0.3.4/.pybuild/cpython3_3.9_muttdown/build; python3.9 -m pytest
tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
make: *** [debian/rules:9: build] Error 25
Andreas
muttdown_0.3.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: muttdown
Source-Version: 0.3.5-1
Done: gustavo panizzo
We believe that the bug you reported is fixed in the latest version of
muttdown, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gustavo panizzo (supplier of updated muttdown 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: Mon, 15 Nov 2021 20:31:15 +
Source: muttdown
Architecture: source
Version: 0.3.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: gustavo panizzo
Closes: 999642
Changes:
muttdown (0.3.5-1) unstable; urgency=medium
.
[ Ondřej Nový ]
* Use debhelper-compat instead of debian/compat.
* Bump Standards-Version to 4.4.1.
* d/control: Update Maintainer field with
Processed: Add tag patch
Processing commands for cont...@bugs.debian.org: > tag 984180 + patch Bug #984180 [src:htdig] htdig: ftbfs with GCC-11 Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 984180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998623: marked as done (pysha3: FTBFS with dh-python 5.20211105 due to missing tox.ini)
Your message dated Mon, 15 Nov 2021 20:58:05 +
with message-id
and subject line Bug#998623: fixed in pysha3 1.0.2-4.2
has caused the Debian Bug report #998623,
regarding pysha3: FTBFS with dh-python 5.20211105 due to missing tox.ini
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.)
--
998623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysha3
Version: 1.0.2-4.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
dh-python 5.20211105 fixed tox detection based on Build-Depends, which
causes it to try to run tox tests on pysha3.
As pysha3 doesn't have a tox.ini, this fails:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9_sha3/build; tox
-c /<>/tox.ini --sitepackages -e py39
ERROR: /<>/tox.ini is neither file or directory
ERROR: tox config file (either pyproject.toml, tox.ini, setup.cfg) not found
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.9_sha3/build; tox -c
/<>/tox.ini --sitepackages -e py39
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.9
returned exit code 13
make: *** [debian/rules:20: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Here is a trivial patch to resolve the issue:
diff -Nru pysha3-1.0.2/debian/control pysha3-1.0.2/debian/control
--- pysha3-1.0.2/debian/control 2020-01-19 01:43:49.0 -0800
+++ pysha3-1.0.2/debian/control 2021-11-05 00:54:52.0 -0700
@@ -3,7 +3,6 @@
Section: python
Priority: optional
Build-Depends:
-tox,
python3-flake8,
python3-setuptools,
dh-python,
SR
--- End Message ---
--- Begin Message ---
Source: pysha3
Source-Version: 1.0.2-4.2
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
pysha3, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated pysha3 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 05 Nov 2021 12:14:01 -0700
Source: pysha3
Architecture: source
Version: 1.0.2-4.2
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney
Changed-By: Stefano Rivera
Closes: 998623
Changes:
pysha3 (1.0.2-4.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Drop tox Build-Dep, we're doing build-time tests without it, fixes FTBFS
with dh-python >= 5.20211105 (Closes: #998623).
Checksums-Sha1:
3049f202d78144b2c9549cd886331c883dc825d3 1421 pysha3_1.0.2-4.2.dsc
413ee2be189835d8120a9873f63c407cecb3f05d 9192 pysha3_1.0.2-4.2.debian.tar.xz
07bf7327aa52a8f20971b9535b9b07bde7a00923 5749 pysha3_1.0.2-4.2_source.buildinfo
Checksums-Sha256:
28a04d2f1e06e9c27e5a5058f5c06a1d6528d55d9d2772b37f119d15a9209066 1421
pysha3_1.0.2-4.2.dsc
85e4ac89a2076673d2c4c5487ab9bd1c4a272a3d0e2a11e2bf60215a0d02b2a1 9192
pysha3_1.0.2-4.2.debian.tar.xz
a227ff8d087eb2741ed90185a4c9b91995eddafafc062eb55805556907aedba4 5749
pysha3_1.0.2-4.2_source.buildinfo
Files:
abe911abb2711754d71241fcce28d63c 1421 python optional pysha3_1.0.2-4.2.dsc
dcd138986d76c982245857829090dc7e 9192 python optional
pysha3_1.0.2-4.2.debian.tar.xz
28b7d3c9cb06a59e3a3fc10a03536876 5749 python optional
pysha3_1.0.2-4.2_source.buildinfo
-BEGIN PGP SIGNATURE-
iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYYWC7RQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2NcVAP9iVH0Ba02Yt34v+Bc+HYZ7C8W6aOnT
dnsyuVT2kp6XcQD/aNF1seRMXg7veHMYtWmBf27fXx6pvouX1/qoUY+C/Q4=
=Ft6G
-END PGP SIGNATURE End Message ---
Bug#998510: marked as done (ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails)
Your message dated Mon, 15 Nov 2021 20:54:47 + with message-id and subject line Bug#998497: fixed in gem2deb 1.7 has caused the Debian Bug report #998497, regarding ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails 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.) -- 998497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-premailer-rails Version: 1.10.3-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cannot load such file -- rails > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/spec_helper.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/unit/premailer_rails_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `block in load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `load' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- rails > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > No examples found. > > Finished in 0.7 seconds (files took 1.05 seconds to load) > 0 examples, 0 failures, 8 errors occurred outside of examples > > Coverage report generated for RSpec to /<>/coverage. 12 / 245 > LOC (4.9%) covered. > Stopped processing SimpleCov as a previous error not related to SimpleCov has > been detected > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2021/11/04/ruby-premailer-rails_1.10.3-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. --- End Message --- --- Begin Message --- Source: gem2deb Source-Version: 1.7 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of gem2deb, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated gem2deb 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: Mon, 15 Nov 2021 17:23:21 -0300 Source: gem2deb Architecture: source Version: 1.7 Distribution:
Bug#996141: marked as done (ruby-bootsnap: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Mon, 15 Nov 2021 20:54:47 + with message-id and subject line Bug#998497: fixed in gem2deb 1.7 has caused the Debian Bug report #998497, regarding ruby-bootsnap: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. 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.) -- 998497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-bootsnap Version: 1.4.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-bootsnap was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-bootsnap/usr/share/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"bootsnap\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-bootsnap/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0:/<>/debian/ruby-bootsnap/usr/lib/ruby/vendor_ruby:. > > GEM_PATH=/<>/debian/ruby-bootsnap/usr/share/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/bundler_test.rb" "test/compile_cache_handler_errors_test.rb" > "test/compile_cache_key_format_test.rb" "test/compile_cache_test.rb" > "test/helper_test.rb" "test/load_path_cache/cache_test.rb" > "test/load_path_cache/change_observer_test.rb" > "test/load_path_cache/loaded_features_index_test.rb" > "test/load_path_cache/path_scanner_test.rb" > "test/load_path_cache/path_test.rb" > "test/load_path_cache/realpath_cache_test.rb" > "test/load_path_cache/store_test.rb" -v > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:496:in > `materialize': Could not find rexml-3.2.3.1 in any of the sources > (Bundler::GemNotFound) > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:234:in > `specs_for' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/runtime.rb:18:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:136:in > `with_level' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:88:in > `silence' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in > `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/test_helper.rb:3:in `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/bundler_test.rb:2:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in > `block in ' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `select' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" >
Bug#998497: marked as done (gem2deb-test-runner: Remove Gemfile.lock files before running the tests)
Your message dated Mon, 15 Nov 2021 20:54:47 + with message-id and subject line Bug#998497: fixed in gem2deb 1.7 has caused the Debian Bug report #998497, regarding gem2deb-test-runner: Remove Gemfile.lock files before running the tests 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.) -- 998497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-voight-kampff Version: 1.1.3-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cannot load such file -- combustion > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/spec_helper.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/lib/voight_kampff_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `block in load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `load' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- combustion > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > No examples found. > > Finished in 0.6 seconds (files took 0.68629 seconds to load) > 0 examples, 0 failures, 4 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2021/11/04/ruby-voight-kampff_1.1.3-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. --- End Message --- --- Begin Message --- Source: gem2deb Source-Version: 1.7 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of gem2deb, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated gem2deb 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: Mon, 15 Nov 2021 17:23:21 -0300 Source: gem2deb Architecture: source Version: 1.7 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 998497 Changes: gem2deb (1.7) unstable; urgency=medium . [ Antonio Terceiro ] * debian/changelog:
Bug#984232: status
Upstream has fixed this, and I have a package with the latest upstream sources in progress, happy to accept help to put it over the edge. Ryan OpenPGP_signature Description: OpenPGP digital signature
Bug#984403: warzone2100 version 3.4.0 to 4.2.1 CMake build problem
Hi Russell, is your build problem related to Debian bug #984403 "FTBFS with GCC 11" ? I don't intend to investigate this problem soon. We need a new upstream version too. I presume this will fix the current build failures. Regards, Markus #Am Samstag, dem 13.11.2021 um 15:57 +1100 schrieb Russell Coker: > I've got a build problem with warzone2100 that affects all versions from > 3.4.0 > to 4.2.1. I tried various versions in the hope that I could find out where > the error started, but it turns out that it started when CMake started being > used. > > /usr/bin/ld: src/CMakeFiles/warzone2100.dir/data.cpp.o: in function > `dataAudioCfgLoad(char const*, void**)': > ./debian/build/../../src/data.cpp:605: undefined reference to > `ParseResourceFile(PHYSFS_File*)' > > Above is what seems to be the root cause of the problem, which appears to be > due to lib/gamelib/audp_parser.ypp not being compiled due to CMake stuff I > don't understand. > > I've attached the debian.tar.xz file for 4.2.1 for anyone who would like to > have a go at it. I could also provide a debian.tar.xz file for 3.4.0 if > someone wants to try that (same problem but less disk space and compile > time). > > 4.2.1 takes 4.5 minutes of elapsed time and 17.5 minutes of CPU time to > compile on my workstation (which is moderately fast but a system that is 3* > faster is affordable). 3.4.0 takes 3 minutes of elapsed time and 9.5 minutes > of CPU time. > > Any suggestions would be appreciated. I can provide an account on a VM with > all the dependencies etc installed if that's more convenient (but the VM has > a > single core and will take 9 minutes or 17 minutes to compile). > signature.asc Description: This is a digitally signed message part
Bug#999743: xfsprogs FTBFS: .gitcensus: No such file or directory
Source: xfsprogs Version: 5.14.0-rc1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xfsprogs=5.14.0-rc1-1 ... cat: .gitcensus: No such file or directory /bin/tar: .gitcensus: Cannot stat: No such file or directory /bin/tar: Exiting with failure status due to previous errors gmake[2]: *** [Makefile:187: xfsprogs-5.14.0-rc1.tar.gz] Error 2
Bug#996215: marked as done (ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value)
Your message dated Mon, 15 Nov 2021 18:37:56 + with message-id and subject line Bug#996215: fixed in ruby-dbf 3.0.5-2 has caused the Debian Bug report #996215, regarding ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value 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.) -- 996215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-dbf Version: 3.0.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-dbf was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Failure/Error: @encoding ? > value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value > > TypeError: > no implicit conversion of Hash into String > # ./lib/dbf/column_type.rb:98:in `encode' > # ./lib/dbf/column_type.rb:98:in `type_cast' > # ./lib/dbf/column.rb:49:in `type_cast' > # ./lib/dbf/record.rb:94:in `init_attribute' > # ./lib/dbf/record.rb:71:in `block in attribute_map' > # ./lib/dbf/record.rb:71:in `map' > # ./lib/dbf/record.rb:71:in `attribute_map' > # ./lib/dbf/record.rb:56:in `attributes' > # ./lib/dbf/record.rb:82:in `method_missing' > # ./spec/dbf/record_spec.rb:85:in `block (4 levels) in ' > > Finished in 0.82809 seconds (files took 0.79418 seconds to load) > 181 examples, 10 failures > > Failed examples: > > rspec ./spec/dbf/file_formats_spec.rb:88 # DBF of type 30 (Visual FoxPro) > reads memo data > rspec ./spec/dbf/database_spec.rb:46 # DBF::Database::Foxpro#table_path > returns an absolute path > rspec ./spec/dbf/database_spec.rb:39 # DBF::Database::Foxpro#table when > accessing related tables loads an existing related table with wrong filename > casing > rspec ./spec/dbf/database_spec.rb:35 # DBF::Database::Foxpro#table when > accessing related tables supports a long table field name > rspec ./spec/dbf/database_spec.rb:31 # DBF::Database::Foxpro#table when > accessing related tables loads an existing related table > rspec ./spec/dbf/database_spec.rb:9 # DBF::Database::Foxpro#initialize when > given a path to an existing dbc file does not raise an error > rspec ./spec/dbf/database_spec.rb:21 # DBF::Database::Foxpro#initialize it > loads the example db correctly shows a correct list of tables > rspec ./spec/dbf/column_spec.rb:225 # DBF::Column#type_cast with type M > (memo) casts to string > rspec ./spec/dbf/record_spec.rb:96 # DBF::Record column data for table > overriding specified in dbf encoding should transcode from manually specified > encoding to default system encoding > rspec ./spec/dbf/record_spec.rb:84 # DBF::Record column data for table using > specified in dbf encoding should automatically encodes to default system > encoding > > Randomized with seed 8811 > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-dbf/ruby-dbf_3.0.5-1+rebuild1633377673_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-dbf Source-Version: 3.0.5-2 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-dbf, 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. Daniel Leidert (supplier of updated ruby-dbf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Nov
Bug#996215: marked as pending in ruby-dbf
Control: tag -1 pending Hello, Bug #996215 in ruby-dbf 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/ruby-team/ruby-dbf/-/commit/68debea50349b3f7d8914a21b6327355d73f38aa Fix FTBFS * d/patches/0002-Fix-Ruby-3-compatibility.patch: Add patch. - Fix compatibility with Ruby 3 (closes: #996215). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996215
Processed: Bug#996215 marked as pending in ruby-dbf
Processing control commands: > tag -1 pending Bug #996215 [src:ruby-dbf] ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value Added tag(s) pending. -- 996215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997656: marked as done (xfsprogs: FTBFS: mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied)
Your message dated Mon, 15 Nov 2021 18:25:19 + with message-id and subject line Bug#997656: fixed in xfsprogs 5.14.0-rc1-1 has caused the Debian Bug report #997656, regarding xfsprogs: FTBFS: mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied 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.) -- 997656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. --- End Message --- --- Begin Message --- Source: xfsprogs Source-Version: 5.14.0-rc1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of xfsprogs, 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. Bastian Germann (supplier of updated xfsprogs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Nov 2021 23:18:22 +0100 Source: xfsprogs Architecture: source Version: 5.14.0-rc1-1 Distribution: unstable Urgency: medium Maintainer: XFS Development Team Changed-By: Bastian Germann Closes: 794158 997656 Changes: xfsprogs (5.14.0-rc1-1) unstable; urgency=medium . [ Dave Chinner ] * New build dependency: liburcu-dev . [ Helmut Grohne ] * Fix FTCBFS (Closes: #794158) + Pass --build and --host to configure . [ Boian Bonev ] * Fix FTBFS (Closes: #997656) + Keep custom install-sh after autogen Checksums-Sha1: d3c15cd8386cbeb793838196efa329c31f67b170 2045 xfsprogs_5.14.0-rc1-1.dsc 38f986a3f49a914f81f65cf3a09553f565ac2c0d 1536948 xfsprogs_5.14.0-rc1.orig.tar.gz cca1668fde70c881cb28d1e0d612229150293889 14232 xfsprogs_5.14.0-rc1-1.debian.tar.xz 80932400488c0408da8b03f5ef3df87bea6ddd05 6251 xfsprogs_5.14.0-rc1-1_source.buildinfo Checksums-Sha256: 7ba6ebb4446bfd8257e185ef3b15172a9dec870f25dca875939fc2092792169e 2045 xfsprogs_5.14.0-rc1-1.dsc fccadafbf8c609fec5f6b38f452879b83647dff640a16bca939777ea4e81bc04 1536948 xfsprogs_5.14.0-rc1.orig.tar.gz 7eede3f2cb24fecc5419762b4e2493afc856a850f47adfc0ea4a6b044f768885 14232 xfsprogs_5.14.0-rc1-1.debian.tar.xz 516f6e2eb6e94804e0b7e6849507786b2af7bf5af45795c1daaefd980f250d0e 6251 xfsprogs_5.14.0-rc1-1_source.buildinfo Files: c584f503002c94b4375d63a65eeeda79 2045 admin optional xfsprogs_5.14.0-rc1-1.dsc 5170e9971709bb1847b2b5363d3d2807 1536948 admin optional xfsprogs_5.14.0-rc1.orig.tar.gz d2939ac3e1db87942907ba9b6953b016 14232 admin optional xfsprogs_5.14.0-rc1-1.debian.tar.xz c0a1a12e94c11239a1c696a7df4bb7bb 6251 admin optional xfsprogs_5.14.0-rc1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmGSmlcACgkQH1x6i0VW QxRcagv+JRdcKjx/4J8TDXt6wRS9GY9Qx1AcgsjpaY5auCzCXN/l4AzkBHinlVzO JFUy/icg7c2jQq22rEkyMD/uHkURp/O0Kz7Ld73wghYBbTmLs+czLa66cA9eVPYQ cu0X/biC2DTGASHvp0FuetHgvO4KUQvTYDIINEeDnfVgwSjSHzMkHTIPlHj/X74d
Bug#996210: marked as done (ruby-css-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Mon, 15 Nov 2021 18:24:46 + with message-id and subject line Bug#996210: fixed in ruby-css-parser 1.6.0-2 has caused the Debian Bug report #996210, regarding ruby-css-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. 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.) -- 996210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-css-parser Version: 1.6.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-css-parser was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-css-parser/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"css_parser\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-css-parser/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-css-parser/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_css_parser_basic.rb" "test/test_css_parser_loading.rb" > "test/test_css_parser_media_types.rb" "test/test_css_parser_misc.rb" > "test/test_css_parser_offset_capture.rb" "test/test_css_parser_regexps.rb" > "test/test_helper.rb" "test/test_merging.rb" "test/test_rule_set.rb" > "test/test_rule_set_creating_shorthand.rb" > "test/test_rule_set_expanding_shorthand.rb" -v > > File does not exist: webrick > > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_css_parser_basic.rb" "test/test_css_parser_loading.rb" > "test/test_css_parser_media_types.rb" "test/test_css_parser_misc.rb" > "test/test_css_parser_offset_capture.rb" "test/test_css_parser_regexps.rb" > "test/test_helper.rb" "test/test_merging.rb" "test/test_rule_set.rb" > "test/test_rule_set_creating_shorthand.rb" > "test/test_rule_set_expanding_shorthand.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-css-parser/ruby-css-parser_1.6.0-1+rebuild1633377318_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-css-parser Source-Version: 1.6.0-2 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-css-parser, 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. Daniel Leidert (supplier of updated ruby-css-parser 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
Processed: reassign 996216 to src:ruby-faker, forcibly merging 996224 996216
Processing commands for cont...@bugs.debian.org:
> reassign 996216 src:ruby-faker 1.9.1-2
Bug #996216 [ruby-faker] ruby-devise-two-factor: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: ArgumentError:
Bug reassigned from package 'ruby-faker' to 'src:ruby-faker'.
No longer marked as found in versions ruby-faker/1.9.1-2.
Ignoring request to alter fixed versions of bug #996216 to the same values
previously set
Bug #996216 [src:ruby-faker] ruby-devise-two-factor: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: ArgumentError:
Marked as found in versions ruby-faker/1.9.1-2.
> forcemerge 996224 996216
Bug #996224 {Done: Daniel Leidert } [src:ruby-faker]
ruby-faker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:
test_ch_methods(TestZhLocale): ArgumentError: wrong number of arguments (given
2, expected 0..1)
Bug #996216 [src:ruby-faker] ruby-devise-two-factor: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: ArgumentError:
996157 was blocked by: 996224
996157 was not blocking any bugs.
Added blocking bug(s) of 996157: 996216
Marked Bug as done
Marked as fixed in versions ruby-faker/1.9.1-3.
Merged 996216 996224
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996157
996216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996216
996224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 994569 in 2.0.10-2+deb10u1, fixed 994569 in 2.0.10-2+deb11u1
Processing commands for cont...@bugs.debian.org:
> # DSA 5010-1
> fixed 994569 2.0.10-2+deb10u1
Bug #994569 {Done: Markus Koschany }
[src:libxml-security-java] libxml-security-java: CVE-2021-40690
Marked as fixed in versions libxml-security-java/2.0.10-2+deb10u1.
> fixed 994569 2.0.10-2+deb11u1
Bug #994569 {Done: Markus Koschany }
[src:libxml-security-java] libxml-security-java: CVE-2021-40690
Marked as fixed in versions libxml-security-java/2.0.10-2+deb11u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984332: marked as done (simdjson: ftbfs with GCC-11)
Your message dated Mon, 15 Nov 2021 18:04:41 + with message-id and subject line Bug#984332: fixed in simdjson 1.0.2-1 has caused the Debian Bug report #984332, regarding simdjson: ftbfs with GCC-11 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.) -- 984332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:simdjson Version: 0.7.1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/simdjson_0.7.1-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] Dependee "/<>/obj-x86_64-linux-gnu/src/CMakeFiles/simdjson.dir/DependInfo.cmake" is newer than depender "/<>/obj-x86_64-linux-gnu/src/CMakeFiles/simdjson.dir/depend.internal". Dependee "/<>/obj-x86_64-linux-gnu/src/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/obj-x86_64-linux-gnu/src/CMakeFiles/simdjson.dir/depend.internal". Scanning dependencies of target simdjson make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f src/CMakeFiles/simdjson.dir/build.make src/CMakeFiles/simdjson.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 50%] Building CXX object src/CMakeFiles/simdjson.dir/simdjson.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DSIMDJSON_THREADS_ENABLED=1 -Dsimdjson_EXPORTS -I/<>/include -I/<>/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -pthread -fPIC -Werror -Wall -Wextra -Weffc++ -Wsign-compare -Wshadow -Wwrite-strings -Wpointer-arith -Winit-self -Wconversion -Wno-sign-conversion -std=c++17 -o CMakeFiles/simdjson.dir/simdjson.cpp.o -c /<>/src/simdjson.cpp [100%] Linking CXX shared library ../libsimdjson.so cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/simdjson.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,libsimdjson.so.5 -o ../libsimdjson.so.5.0.0 CMakeFiles/simdjson.dir/simdjson.cpp.o -pthread cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_symlink_library ../libsimdjson.so.5.0.0 ../libsimdjson.so.5 ../libsimdjson.so make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [100%] Built target simdjson make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 0 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' dh_auto_test # don't fail the build when SIGILL make[1]: Leaving directory '/<>' create-stamp debian/debhelper-build-stamp dh_prep -O-Scmake dh_auto_install -O-Scmake cd obj-x86_64-linux-gnu && make -j4 install DESTDIR=/<>/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 make -f
Processed (with 1 error): reassign 996216 to ruby-faker, forcibly merging 996224 996216
Processing commands for cont...@bugs.debian.org:
> reassign 996216 ruby-faker 1.9.1-2
Bug #996216 [src:ruby-devise-two-factor] ruby-devise-two-factor: FTBFS with
ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Bug reassigned from package 'src:ruby-devise-two-factor' to 'ruby-faker'.
No longer marked as found in versions ruby-devise-two-factor/4.0.0-2.
Ignoring request to alter fixed versions of bug #996216 to the same values
previously set
Bug #996216 [ruby-faker] ruby-devise-two-factor: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: ArgumentError:
Marked as found in versions ruby-faker/1.9.1-2.
> forcemerge 996224 996216
Bug #996224 {Done: Daniel Leidert } [src:ruby-faker]
ruby-faker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:
test_ch_methods(TestZhLocale): ArgumentError: wrong number of arguments (given
2, expected 0..1)
Unable to merge bugs because:
package of #996216 is 'ruby-faker' not 'src:ruby-faker'
Failed to forcibly merge 996224: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996216
996224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package gnome-shell-extension-disconnect-wifi
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > gnome-shell-extension-disconnect-wifi > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #996052 (http://bugs.debian.org/996052) > # Bug title: gnome-shell-extension-disconnect-wifi: does not declare > compatibility with GNOME Shell 41 > # * https://github.com/kgshank/gse-disconnect-wifi/issues/34 > # * remote status changed: open -> closed > # * closed upstream > tags 996052 + fixed-upstream Bug #996052 [gnome-shell-extension-disconnect-wifi] gnome-shell-extension-disconnect-wifi: does not declare compatibility with GNOME Shell 41 Added tag(s) fixed-upstream. > usertags 996052 - status-open Usertags were: status-open. There are now no usertags set. > usertags 996052 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 996052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996210 marked as pending in ruby-css-parser
Processing control commands: > tag -1 pending Bug #996210 [src:ruby-css-parser] ruby-css-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996210: marked as pending in ruby-css-parser
Control: tag -1 pending Hello, Bug #996210 in ruby-css-parser 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/ruby-team/ruby-css-parser/-/commit/ade387b157c6884e9315613b1c0747f89f2fe296 Update packaging files and fix FTBFS * d/control: Add Rules-Requires-Root field. (Standards-Version): Bump to 4.6.0. (Build-Depends): Add ruby-webrick (closes: #996210). * d/copyright: Add Upstream-Contact field. * d/rules: Use gem installation layout and install upstream changelog. * d/watch: Update watch file. * d/upstream/metadata: Add Archive and Changelog fields. (this message was generated automatically) -- Greetings https://bugs.debian.org/996210
Processed: reassign 998510 to gem2deb-test-runner, forcibly merging 998497 998510
Processing commands for cont...@bugs.debian.org: > reassign 998510 gem2deb-test-runner 1.6 Bug #998510 [src:ruby-premailer-rails] ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails Bug reassigned from package 'src:ruby-premailer-rails' to 'gem2deb-test-runner'. No longer marked as found in versions ruby-premailer-rails/1.10.3-3. Ignoring request to alter fixed versions of bug #998510 to the same values previously set Bug #998510 [gem2deb-test-runner] ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails Marked as found in versions gem2deb/1.6. > forcemerge 998497 998510 Bug #998497 [gem2deb-test-runner] gem2deb-test-runner: Remove Gemfile.lock files before running the tests Bug #996141 [gem2deb-test-runner] ruby-bootsnap: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Bug #998510 [gem2deb-test-runner] ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails Added tag(s) pending. Bug #996141 [gem2deb-test-runner] ruby-bootsnap: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Merged 996141 998497 998510 > thanks Stopping processing here. Please contact me if you need assistance. -- 996141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996141 998497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998497 998510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package python3-typed-ast
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python3-typed-ast > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #998854 (http://bugs.debian.org/998854) > # Bug title: undefined symbol: _PyUnicode_DecodeUnicodeEscape > # * https://bugs.python.org/issue45778 > # * remote status changed: (?) -> closed > # * remote resolution changed: (?) -> wont-fix > # * closed upstream > # * upstream said bug is wontfix > tags 998854 + fixed-upstream upstream wontfix Bug #998854 [python3-typed-ast] undefined symbol: _PyUnicode_DecodeUnicodeEscape Added tag(s) upstream, fixed-upstream, and wontfix. > usertags 998854 + status-closed resolution-wont-fix There were no usertags set. Usertags are now: status-closed resolution-wont-fix. > thanks Stopping processing here. Please contact me if you need assistance. -- 998854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package gnome-shell-extension-gamemode
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > gnome-shell-extension-gamemode > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #996057 (http://bugs.debian.org/996057) > # Bug title: gnome-shell-extension-gamemode: does not declare compatibility > with GNOME Shell 41 > # * https://github.com/gicmo/gamemode-extension/issues/44 > # * remote status changed: open -> closed > # * closed upstream > tags 996057 + fixed-upstream Bug #996057 [gnome-shell-extension-gamemode] gnome-shell-extension-gamemode: does not declare compatibility with GNOME Shell 41 Added tag(s) fixed-upstream. > usertags 996057 - status-open Usertags were: status-open. There are now no usertags set. > usertags 996057 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 996057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:gammapy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gammapy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #994783 (http://bugs.debian.org/994783) > # Bug title: astropy-regions breaks gammapy autopkgtest: KeyError: '.' > # * https://github.com/gammapy/gammapy/issues/3485 > # * remote status changed: open -> closed > # * closed upstream > tags 994783 + fixed-upstream Bug #994783 [src:gammapy] astropy-regions breaks gammapy autopkgtest: KeyError: '.' Added tag(s) fixed-upstream. > usertags 994783 - status-open Usertags were: status-open. There are now no usertags set. > usertags 994783 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 994783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994833: OpenCL programs abort when intel-opencl-icd is installed
Is there any progress on the FTBS? libigc is now at 1.0.8744-2 which breaks 21.32.20609-1, making the icd uninstallable.
Bug#999494: marked as done (zycore-c: FTBFS on at least mips64el)
Your message dated Mon, 15 Nov 2021 17:00:24 + with message-id and subject line Bug#999494: fixed in zycore-c 1.1.0-1 has caused the Debian Bug report #999494, regarding zycore-c: FTBFS on at least mips64el 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.) -- 999494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zycore-c Version: 1.0.0-2 Severity: serious Hi, The issue that seemed to be addressed by a patch included in the latest revision was not fixed; the package still FTBFS at least on mips64el: /usr/bin/cc -DZYCORE_EXPORTS -DZycore_EXPORTS -D_CRT_SECURE_NO_WARNINGS -D_GNU_SOURCE -I/<>/include -I/<>/obj-mips64el-linux-gnuabi64 -I/<>/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=c99 -MD -MT CMakeFiles/Zycore.dir/src/Format.c.o -MF CMakeFiles/Zycore.dir/src/Format.c.o.d -o CMakeFiles/Zycore.dir/src/Format.c.o -c /<>/src/Format.c In file included from /<>/include/Zycore/Types.h:35, from /<>/include/Zycore/ArgParse.h:35, from /<>/src/ArgParse.c:27: /<>/include/Zycore/Defines.h:137:5: error: #error "Unsupported architecture detected" 137 | # error "Unsupported architecture detected" | ^ In file included from /<>/include/Zycore/Types.h:35, from /<>/include/Zycore/Status.h:39, from /<>/include/Zycore/Allocator.h:36, from /<>/src/Allocator.c:27: /<>/include/Zycore/Defines.h:137:5: error: #error "Unsupported architecture detected" 137 | # error "Unsupported architecture detected" | ^ In file included from /<>/include/Zycore/Types.h:35, from /<>/include/Zycore/Status.h:39, from /<>/include/Zycore/Format.h:36, from /<>/src/Format.c:27: /<>/include/Zycore/Defines.h:137:5: error: #error "Unsupported architecture detected" 137 | # error "Unsupported architecture detected" | ^ In file included from /<>/include/Zycore/Types.h:35, from /<>/include/Zycore/Status.h:39, from /<>/include/Zycore/Allocator.h:36, from /<>/include/Zycore/Bitset.h:36, from /<>/src/Bitset.c:27: /<>/include/Zycore/Defines.h:137:5: error: #error "Unsupported architecture detected" 137 | # error "Unsupported architecture detected" | ^ make[3]: *** [CMakeFiles/Zycore.dir/build.make:79: CMakeFiles/Zycore.dir/src/Allocator.c.o] Error 1 make[3]: *** Waiting for unfinished jobs /<>/src/Format.c: In function ‘ZyanStringAppendDecU’: /<>/src/Format.c:434:12: warning: implicit declaration of function ‘ZyanStringAppendDecU32’; did you mean ‘ZyanStringAppendDecU64’? [-Wimplicit-function-declaration] 434 | return ZyanStringAppendDecU32(string, (ZyanU32)value, padding_length); |^~ |ZyanStringAppendDecU64 /<>/src/Format.c: In function ‘ZyanStringAppendHexU’: /<>/src/Format.c:475:12: warning: implicit declaration of function ‘ZyanStringAppendHexU32’; did you mean ‘ZyanStringAppendHexU64’? [-Wimplicit-function-declaration] 475 | return ZyanStringAppendHexU32(string, (ZyanU32)value, padding_length, uppercase); |^~ |ZyanStringAppendHexU64 make[3]: *** [CMakeFiles/Zycore.dir/build.make:93: CMakeFiles/Zycore.dir/src/ArgParse.c.o] Error 1 --- End Message --- --- Begin Message --- Source: zycore-c Source-Version: 1.1.0-1 Done: Andrea Pappacoda We believe that the bug you reported is fixed in the latest version of zycore-c, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrea Pappacoda (supplier of updated zycore-c package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Nov 2021 13:15:38 +0100 Source: zycore-c Binary: libzycore-dev libzycore1.1 libzycore1.1-dbgsym Architecture: source i386 Version: 1.1.0-1 Distribution:
Bug#998142: marked as done (opencv: ABI breakage causes autopkgtest failures)
Your message dated Mon, 15 Nov 2021 17:00:17 + with message-id and subject line Bug#998141: fixed in opencv 4.5.4+dfsg-2 has caused the Debian Bug report #998141, regarding opencv: ABI breakage causes autopkgtest failures 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.) -- 998141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencv, node-opencv Control: found -1 opencv/4.5.4+dfsg-1 Control: found -1 node-opencv/7.0.0+git20200310.6c13234-3 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of opencv the autopkgtest of node-opencv fails in testing when that autopkgtest is run with the binary packages of opencv from unstable. It passes when run with only packages from testing. In tabular form: passfail opencv from testing4.5.4+dfsg-1 node-opencvfrom testing7.0.0+git20200310.6c13234-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of opencv to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=opencv https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-opencv/16302655/log.gz dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation) TAP version 13 # Smoke tests / Can Import ok 1 imported fine ok 2 version is there:4.5 ok 3 point is there ok 4 matrix is there # importing library multiple times is ok ok 5 null ok 6 null # Point ok 7 should be truthy ok 8 cannot call without new ok 9 should be strictly equal ok 10 should be strictly equal ok 11 should be strictly equal ok 12 should be strictly equal ok 13 Points are immutable ok 14 Points are immutable ok 15 should be truthy ok 16 should be strictly equal # Matrix constructor ok 17 should be truthy ok 18 should be truthy ok 19 should be truthy ok 20 should be truthy ok 21 should be truthy # Matrix accessors ok 22 should be deeply equivalent ok 23 should be strictly equal ok 24 should be strictly equal ok 25 should be strictly equal ok 26 should be strictly equal ok 27 should be deeply equivalent ok 28 should be strictly equal /tmp/autopkgtest-lxc.9lc6u5xq/downtmp/autopkgtest_tmp/unittest0svMmN/test/unit.js:83 mat.resize(8,9); ^ Error: c++ Exception processing resize at Test. (/tmp/autopkgtest-lxc.9lc6u5xq/downtmp/autopkgtest_tmp/unittest0svMmN/test/unit.js:83:7) at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:96:32) at Test.run (/usr/share/nodejs/tape/lib/test.js:114:31) at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:96:32) at Immediate.next (/usr/share/nodejs/tape/lib/results.js:88:19) at processImmediate (internal/timers.js:461:21) autopkgtest [23:11:08]: test unittest OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: opencv Source-Version: 4.5.4+dfsg-2 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of opencv, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated opencv 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, 13 Nov 2021 12:49:30 +0100 Source: opencv Binary: libopencv-calib3d-dev libopencv-calib3d4.5d libopencv-calib3d4.5d-dbgsym libopencv-contrib-dev libopencv-contrib4.5d libopencv-contrib4.5d-dbgsym libopencv-core-dev libopencv-core4.5d libopencv-core4.5d-dbgsym libopencv-dev libopencv-dev-dbgsym libopencv-dnn-dev
Bug#998141: marked as done (opencv: ABI breakage causes autopkgtest failures)
Your message dated Mon, 15 Nov 2021 17:00:17 + with message-id and subject line Bug#998141: fixed in opencv 4.5.4+dfsg-2 has caused the Debian Bug report #998141, regarding opencv: ABI breakage causes autopkgtest failures 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.) -- 998141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencv, auto-multiple-choice Control: found -1 opencv/4.5.4+dfsg-1 Control: found -1 auto-multiple-choice/1.5.1-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of opencv the autopkgtest of auto-multiple-choice fails in testing when that autopkgtest is run with the binary packages of opencv from unstable. It passes when run with only packages from testing. In tabular form: passfail opencv from testing4.5.4+dfsg-1 auto-multiple-choice from testing1.5.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of opencv to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=opencv https://ci.debian.net/data/autopkgtest/testing/amd64/a/auto-multiple-choice/16302653/log.gz [>] Installed in /tmp/Sva1UUZmVK [I] Provided scans: 1 [*] auto-multiple-choice prepare --filter --with pdflatex --mode s[sc] --epoch 946684800 --n-copies 1 --prefix /tmp/Sva1UUZmVK/ /tmp/Sva1UUZmVK/source.tex --data /tmp/Sva1UUZmVK/data --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice meptex --src /tmp/Sva1UUZmVK/calage.xy --data /tmp/Sva1UUZmVK/data --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice prepare --filter --with pdflatex --mode b --n-copies 1 --data /tmp/Sva1UUZmVK/data /tmp/Sva1UUZmVK/source.tex --debug /tmp/Sva1UUZmVK/debug.log [T] No layout defects [*] auto-multiple-choice prepare --filter --with pdflatex --mode k --epoch 946684800 --n-copies 1 --prefix /tmp/Sva1UUZmVK/ /tmp/Sva1UUZmVK/source.tex --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice imprime --sujet /tmp/Sva1UUZmVK/corrige.pdf --methode file --output /tmp/Sva1UUZmVK/xx-copie-%e.pdf --fich-numeros /tmp/Sva1UUZmVK/num --data /tmp/Sva1UUZmVK/data --extract-with qpdf --password --password-key password --students-list /tmp/Sva1UUZmVK/names.csv --list-key id --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice read-pdfform --list /tmp/Sva1UUZmVK/scans-list.txt --data /tmp/Sva1UUZmVK/data --password --no-multiple --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice getimages --list /tmp/Sva1UUZmVK/scans-list.txt --copy-to /tmp/Sva1UUZmVK/scans --orientation portrait --password --no-force-convert --no-use-pdftk --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice analyse --no-multiple --bw-threshold 0.6 --pre-allocate 0 --tol-marque 0.4 --no-ignore-red --projet /tmp/Sva1UUZmVK --data /tmp/Sva1UUZmVK/data --debug-image-dir /tmp/Sva1UUZmVK/cr --liste-fichiers /tmp/Sva1UUZmVK/scans-list.txt --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice analyse --no-multiple --bw-threshold 0.6 --pre-allocate 0 --tol-marque 0.4 --no-ignore-red --debug-pixels --projet /tmp/Sva1UUZmVK --data /tmp/Sva1UUZmVK/data --liste-fichiers /tmp/Sva1UUZmVK/scans-list.txt --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice note --data /tmp/Sva1UUZmVK/data --seuil 0.5 --seuil-up 1 --grain 0.01 --arrondi i --notemax 20 --postcorrect-student --postcorrect-copy --debug /tmp/Sva1UUZmVK/debug.log [*] auto-multiple-choice association-auto --liste /tmp/Sva1UUZmVK/names.csv --liste-key id --pre-association --data /tmp/Sva1UUZmVK/data --debug /tmp/Sva1UUZmVK/debug.log [I] Marks: [T] Perfect copies test: [T] Association test: 2 [E] Uncorrect association: 2 autopkgtest [23:14:10]: test simple OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: opencv Source-Version: 4.5.4+dfsg-2 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of opencv, which is due to be installed in the Debian FTP archive. A summary of the changes
Bug#997745: marked as done (rdkit: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Mon, 15 Nov 2021 17:00:21 +
with message-id
and subject line Bug#997745: fixed in rdkit 202103.5-1
has caused the Debian Bug report #997745,
regarding rdkit: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
997745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdkit
Version: 202009.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
> pg_buildext checkcontrol
> --- debian/control2021-09-28 12:56:39.0 +
> +++ debian/control.DuaHuU 2021-10-23 06:32:01.031892836 +
> @@ -164,10 +164,10 @@
> .
> This package contains the header files.
>
> -Package: postgresql-13-rdkit
> +Package: postgresql-14-rdkit
> Architecture: any
> Section: database
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Suggests:
> Description: Cheminformatics and machine-learning software (PostgreSQL
> Cartridge)
> RDKit is a Python/C++ based cheminformatics and machine-learning software
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/rdkit_202009.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.
--- End Message ---
--- Begin Message ---
Source: rdkit
Source-Version: 202103.5-1
Done: Michael Banck
We believe that the bug you reported is fixed in the latest version of
rdkit, 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.
Michael Banck (supplier of updated rdkit 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: Thu, 11 Nov 2021 18:22:40 +0100
Source: rdkit
Binary: librdkit-dev librdkit1 librdkit1-dbgsym postgresql-14-rdkit
postgresql-14-rdkit-dbgsym python3-rdkit python3-rdkit-dbgsym rdkit-data
rdkit-doc
Architecture: source amd64 all
Version: 202103.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team
Changed-By: Michael Banck
Description:
librdkit-dev - Collection of cheminformatics and machine-learning software
(deve
librdkit1 - Collection of cheminformatics and machine-learning software (shar
postgresql-14-rdkit - Cheminformatics and machine-learning software
(PostgreSQL Cartrid
python3-rdkit - Collection of cheminformatics and machine-learning software
rdkit-data - Collection of cheminformatics and machine-learning software (data
rdkit-doc - Collection of cheminformatics and machine-learning software (docu
Closes: 997745
Changes:
rdkit (202103.5-1) unstable; urgency=medium
.
* New upstream release.
* debian/patches/sphinx_compile_fixes.patch: Refreshed.
* debian/control (postgresql-PGVERSION-rdkit): Bump PostgreSQL version to 14
(Closes: #997745).
Checksums-Sha1:
8837f4f7b80e5783ba45baf4270920a2b9314d01 2831 rdkit_202103.5-1.dsc
44d4831b3b202d7bb6c0ff8e14fe83910931197a 60507464 rdkit_202103.5.orig.tar.xz
6750ae1a7a01c0438ab056e287ad59f1280acbf9 100148 rdkit_202103.5-1.debian.tar.xz
a5681b9e06cce24d7934e397c8ab0a0d151aef39 362672
librdkit-dev_202103.5-1_amd64.deb
Bug#999730: mtr: Fix FTBFS with glib2.0 >= 2.70 and deprecated GTimeVal of gtk+2.0
Package: mtr Version: 0.94-2 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Hi Robert, mtr fails to build from source, if compiled against glib2.0 >= v2.70, due to usage of deprecated GTimeVal in gtk+2.0 headers (that's a dependency of mtr). In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS with glib >= 2.70 & deprecated definitions of GTimeVal in gtk+2.0 Thanks for considering the patch. Cheers, Lukas Build log: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/s390x-linux-gnu -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-pointer-sign -c -o ui/mtr-gtk.o `test -f 'ui/gtk.c' || echo '../'`ui/gtk.c ../ui/curses.c: In function ‘mtr_curses_hosts’: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security] 435 | printw(fmt_ipinfo(ctl, addr)); | ^~ ../ui/curses.c:488:21: error: format not a string literal and no format arguments [-Werror=format-security] 488 | printw(fmt_ipinfo(ctl, addrs)); | ^~ ../ui/curses.c: In function ‘mtr_curses_graph’: ../ui/curses.c:653:17: error: format not a string literal and no format arguments [-Werror=format-security] 653 | printw(fmt_ipinfo(ctl, addr)); | ^~ ../ui/curses.c: In function ‘mtr_curses_redraw’: ../ui/curses.c:703:5: error: format not a string literal and no format arguments [-Werror=format-security] 703 | mvprintw(1, maxx - 25, iso_time()); | ^~~~ ../ui/curses.c:763:42: error: format not a string literal and no format arguments [-Werror=format-security] 763 | mvprintw(rowstat - 1, startstat, msg); | ^~~ gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/packet.o ../packet/packet.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/cmdparse.o ../packet/cmdparse.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/command.o ../packet/command.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/probe.o ../packet/probe.c In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, from /usr/include/gtk-2.0/gtk/gtkbin.h:35, from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:33, from ../ui/gtk.c:31: /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is deprecated [-Wdeprecated-declarations] 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); | ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:22, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from ../ui/gtk.c:31:
Bug#998482: marked as done (e2guardian: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Mon, 15 Nov 2021 16:19:40 + with message-id and subject line Bug#998482: fixed in e2guardian 5.3.5-2 has caused the Debian Bug report #998482, regarding e2guardian: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 998482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: e2guardian Version: 5.3.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > NOCONFIGURE=1 ./autogen.sh > + cp README.md README > + aclocal -I m4 > configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:9: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:12: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: autom4te failed with exit status: 1 > make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/e2guardian_5.3.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. --- End Message --- --- Begin Message --- Source: e2guardian Source-Version: 5.3.5-2 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of e2guardian, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated e2guardian 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: Mon, 15 Nov 2021 16:24:16 +0100 Source: e2guardian Architecture: source Version: 5.3.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Edu Packaging Team Changed-By: Mike Gabriel Closes: 998430 998482 Changes: e2guardian (5.3.5-2) unstable; urgency=medium . * debian/patches: + Add 1002_fix-maxcontentramcachescansize.patch. Make sure values of maxcontentfiltersize and maxcontentramcachesize obey to the requirements in the inline documentation. (Closes: #998430). + Add 1003_AM_INIT_AUTOMAKE-expanded-multiple-times.patch. Avoid expanding AM_INIT_AUTOMAKE multiple times. (Closes: #998482). * debian/source/lintian-overrides: + Adjust for lintian in Debian bookworm. Checksums-Sha1: 63aec76f3287eb8ed657de8f83e8824601439aef 2152 e2guardian_5.3.5-2.dsc 3baa417c4aa16d44a7aad92da72ca2df982de068 15600 e2guardian_5.3.5-2.debian.tar.xz 4eee23ded7b9042b8cad46629b70195675961554 6417 e2guardian_5.3.5-2_source.buildinfo Checksums-Sha256: afd0ca9a7618b9667feb0c48c5e22f7790b973985153cc6feac55fd42cf4610e 2152 e2guardian_5.3.5-2.dsc b319d8eb16d23df81d18f3e872940490e1ab725054739a9c685201ad6d4abc6e 15600 e2guardian_5.3.5-2.debian.tar.xz e67ee6c2e851a1b498342041ad21e98b60704f08a63edc1b9220ad1353fb39f8 6417 e2guardian_5.3.5-2_source.buildinfo Files: ae8c7e640a96ef1fe25db8d2185fa8ef 2152 web optional e2guardian_5.3.5-2.dsc 8e1259c3f40d02f5479c241caa590b2a 15600 web optional e2guardian_5.3.5-2.debian.tar.xz 4430f601b9e9c9b637a5a17d08e83c7f 6417 web optional e2guardian_5.3.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmGSgeYVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxZPUP/Rn1ZjL+OQb1JPSftLh9fTK4A4v1 fv+/ORDJ4SSo8fUM/Mxld9vGyM+UELA2F2LP3JqGpJoPydcaJbSVIL2844yZPfBT
Processed: Bug#998482 marked as pending in e2guardian
Processing control commands: > tag -1 pending Bug #998482 [src:e2guardian] e2guardian: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times Added tag(s) pending. -- 998482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998482: marked as pending in e2guardian
Control: tag -1 pending Hello, Bug #998482 in e2guardian 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/debian-edu-pkg-team/e2guardian/-/commit/910419c624b5ca478f90ea96a62e37c496f61867 debian/patches: Add 1003_AM_INIT_AUTOMAKE-expanded-multiple-times.patch. Avoid expanding AM_INIT_AUTOMAKE multiple times. (Closes: #998482). (this message was generated automatically) -- Greetings https://bugs.debian.org/998482
Bug#997490: marked as done (python-twilio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Mon, 15 Nov 2021 15:19:58 +
with message-id
and subject line Bug#997490: fixed in python-twilio 7.1.0+ds-1
has caused the Debian Bug report #997490,
regarding python-twilio: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-twilio
Version: 6.51.0+ds-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):
> === short test summary info
>
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_chat_grant
> FAILED
> tests/unit/jwt/test_access_token.py::AccessTokenTest::test_conversations_grant
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_empty_grants
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_empty_region
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_grants -
> tw...
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_headers -
> t...
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_identity -
> ...
> FAILED
> tests/unit/jwt/test_access_token.py::AccessTokenTest::test_ip_messaging_grant
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_nbf -
> twili...
> FAILED
> tests/unit/jwt/test_access_token.py::AccessTokenTest::test_pass_grants_in_constructor
> FAILED
> tests/unit/jwt/test_access_token.py::AccessTokenTest::test_programmable_voice_grant
> FAILED
> tests/unit/jwt/test_access_token.py::AccessTokenTest::test_programmable_voice_grant_incoming
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_region -
> tw...
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_sync_grant
> FAILED
> tests/unit/jwt/test_access_token.py::AccessTokenTest::test_task_router_grant
> FAILED tests/unit/jwt/test_access_token.py::AccessTokenTest::test_video_grant
> FAILED tests/unit/jwt/test_client.py::ClientCapabilityTokenTest::test_decode
> FAILED
> tests/unit/jwt/test_client.py::ClientCapabilityTokenTest::test_pass_scopes_in_constructor
> FAILED
> tests/unit/jwt/test_client_validation.py::ClientValidationJwtTest::test_jwt_signing
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_basic_encode -
> jwt.exception...
> FAILED
> tests/unit/jwt/test_jwt.py::JwtTest::test_decode_allows_skip_verification
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_decode_modified_jwt_fails -
> ...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_decodes_valid_jwt -
> twilio.j...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_custom_algorithm -
> jw...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_custom_nbf -
> jwt.exce...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_custom_ttl -
> jwt.exce...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_decode -
> twilio.jwt.J...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_override_algorithm -
> ...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_override_ttl -
> jwt.ex...
> FAILED
> tests/unit/jwt/test_jwt.py::JwtTest::test_encode_ttl_added_to_current_time
> FAILED
> tests/unit/jwt/test_jwt.py::JwtTest::test_encode_valid_until_overrides_ttl
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_with_headers -
> jwt.ex...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_with_payload -
> jwt.ex...
> FAILED
> tests/unit/jwt/test_jwt.py::JwtTest::test_encode_with_payload_and_headers
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_with_subject -
> jwt.ex...
> FAILED tests/unit/jwt/test_jwt.py::JwtTest::test_encode_without_nbf -
> jwt.exc...
> FAILED
> tests/unit/jwt/test_task_router.py::TaskQueueCapabilityTokenTest::test_allow_fetch_subresources
> FAILED
> tests/unit/jwt/test_task_router.py::TaskQueueCapabilityTokenTest::test_allow_updates_subresources
> FAILED
> tests/unit/jwt/test_task_router.py::TaskQueueCapabilityTokenTest::test_default
> FAILED
> tests/unit/jwt/test_task_router.py::TaskQueueCapabilityTokenTest::test_generate_token
> FAILED
> tests/unit/jwt/test_task_router.py::TaskQueueCapabilityTokenTest::test_generate_token_with_custom_ttl
> FAILED
>
Bug#997604: marked as done (x2gobroker: FTBFS: error in x2gobroker setup command: use_2to3 is invalid.)
Your message dated Mon, 15 Nov 2021 15:20:05 + with message-id and subject line Bug#997604: fixed in x2gobroker 0.0.4.3-2 has caused the Debian Bug report #997604, regarding x2gobroker: FTBFS: error in x2gobroker 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.) -- 997604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. --- End Message --- --- Begin Message --- Source: x2gobroker Source-Version: 0.0.4.3-2 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of x2gobroker, 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. Mike Gabriel (supplier of updated x2gobroker 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: Mon, 15 Nov 2021 15:17:01 +0100 Source: x2gobroker Architecture: source Version: 0.0.4.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Remote Maintainers Changed-By: Mike Gabriel Closes: 997604 Changes: x2gobroker (0.0.4.3-2) unstable; urgency=medium . * debian/control: + Bump Standards-Version: to 4.6.0. No changes needed. * debian/patches: + Add 2001_no_2to3_supported_any_more.patch. Don't run setup.py with use_2to3 anymore. Support for it has been dropped. (Closes: #997604). + Forward patches 1003 and 2001. + Add 0001_man-man1-x2gobroker.1-Fix-apostrophe-usage-drop-prec.patch. Thanks, lintian. Checksums-Sha1: 5d8e8751fe9383cd0235ac946a13cb95ea4ef189 3064 x2gobroker_0.0.4.3-2.dsc caa4900ca462b5c37ab3cc3993eeb7ec0f5b7851 38880 x2gobroker_0.0.4.3-2.debian.tar.xz 4a683f3154be802d660b0cf8645ba6878c1eb40d 9133 x2gobroker_0.0.4.3-2_source.buildinfo Checksums-Sha256: 72bd0f21442c26eb45e661a47e9c64bbfb531ed3b90f553c91aa0b7cf22387fb 3064 x2gobroker_0.0.4.3-2.dsc 7e61df868949494f28985f234cc1cfe972c742e7e3ae16f6d5b84ab6900b636e 38880 x2gobroker_0.0.4.3-2.debian.tar.xz da2162ffb89fe9b75ab183fc4407d080d4593eff7eb0611c77b18edb6b4d8552 9133 x2gobroker_0.0.4.3-2_source.buildinfo Files: bc4c4da4863987be12302038086ebf7e 3064 misc optional x2gobroker_0.0.4.3-2.dsc c2f1c5de0660e6fabe6489a2f1528a23 38880 misc optional x2gobroker_0.0.4.3-2.debian.tar.xz 3fccfd71b6d57d1d60f794beeb2eee9c 9133 misc optional x2gobroker_0.0.4.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmGScUAVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxj04P/1rh8sGaqiWqkb0N5qd8YohUdreo
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
Hi, On 15/11/2021 14:34, Ondřej Surý wrote: This appears when built with 10.39, but the runtime version is less than that. My guess is that this needs manual debian/libpcre2-8.shlibs override. (Or just mangle the symbols file, so it always generates correct versioned dependency.) I've had a look at the Changelog from 10.36 (previous packaged version), and there's nothing obvious there. Is it possible to work out what is happening lower down the stack to cause this error message? I don't feel I have something I can even refer to upstream yet... Thanks, Matthew
Bug#997225: marked as done (crun: FTBFS: ./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined reference to `gen_runtime_spec_schema_config_zos')
Your message dated Mon, 15 Nov 2021 14:55:48 + with message-id and subject line Bug#997225: fixed in crun 0.17+dfsg-1.1 has caused the Debian Bug report #997225, regarding crun: FTBFS: ./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined reference to `gen_runtime_spec_schema_config_zos' 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.) -- 997225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crun Version: 0.17+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): > /usr/bin/ld: ./.libs/libocispec.a(runtime_spec_schema_config_schema.o): in > function `gen_runtime_spec_schema_config_schema': > ./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined > reference to `gen_runtime_spec_schema_config_zos' > /usr/bin/ld: ./libocispec/src/runtime_spec_schema_config_schema.c:2661: > undefined reference to `gen_runtime_spec_schema_config_zos' > /usr/bin/ld: collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/10/23/crun_0.17+dfsg-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: crun Source-Version: 0.17+dfsg-1.1 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of crun, 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. Reinhard Tartler (supplier of updated crun package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 09:17:23 -0500 Source: crun Architecture: source Version: 0.17+dfsg-1.1 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Reinhard Tartler Closes: 997225 Changes: crun (0.17+dfsg-1.1) unstable; urgency=medium . * Non-maintainer upload. * Bug fix: "FTBFS: undefined reference to `gen_runtime_spec_schema_config_zos", thanks to Lucas Nussbaum (Closes: #997225). Checksums-Sha1: 2b9743c5fc64a806b82afac4cb126bf37125ed0c 2066 crun_0.17+dfsg-1.1.dsc be347bbbe7151dadee78c67c12a4773b60ff1fc0 15240 crun_0.17+dfsg-1.1.debian.tar.xz Checksums-Sha256: f9453407b3a75a18f5e54922f2ad7b7ac0d0008707da704af87e0f016c11001b 2066 crun_0.17+dfsg-1.1.dsc c2e5087dc45ab984f392350e55c4c2483a55ece7cdc3b9f512a63f9724474c77 15240 crun_0.17+dfsg-1.1.debian.tar.xz Files: b27d556590a11394d2dcb7e061db3cf3 2066 admin optional crun_0.17+dfsg-1.1.dsc e02572b2b36daee557d756b3b65929fc 15240 admin optional crun_0.17+dfsg-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmGSY50UHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJssxYA/8CNVe5QFIK2JfmF+xuiNzOQjVAT+J WE9TDppjjSI7hC40FwsKZV6DRe+LLXAoatNN6HMn+ZK35LWxDzyKe3z1zl9QEVLq 6lHD6yswlggL+2YG0syRfd43njYJaMTSIDGQDvA3OsvzOCnfEK87zsCOaqmAyiHx jhhVT74WmGN7ryjvXmeGqj0QIY07Pic/FzgE6yG8BMtHGBoMnaXbQO7LjXs+XrYV FNCKX6YhHK/0/fA6V8QG9QkVUa9G8zjFmLbwdwu9lPY2ewRUxTVRlQHD6584q8zh qz7hmRL0eVI1BsYq0PcAP54UgWZWuF1qY1/5/qoL7hrHREj/I2NyRX4uRqSgk4Xw 5MYMeqwKNywDnTX+FkGlfYzkJTzjUCzrKOYphTDYCWJuYmUkUscuqmrsS8pmg9CY kWHxy2X3KfgMuXM1Qtrc3wV7x8CRYK/BJCi02VWZgIyAoP+e9tyVKBhWDBoosCbj MFCUwQlGLN42XtA8NK4ZsGTUoTjzrFB5rWOHeWFc3H4zVe85uJAJeSsaw+znRR6S Sd6RITkaCZhmOjZJhzVa/AA/8qcR4kojduT32/uZqfAqveRfEmYCk2ij1Fa3YN84 HD3+PJ9wzaUGqofeETFJmWgiSolmFIT+xbFBHvm2JdmQbihqKv8BNWEJ6pNZOyKY 08FtSrID+6HTLrk= =9Gid -END PGP SIGNATURE End Message ---
Processed: Bug#997490 marked as pending in python-twilio
Processing control commands:
> tag -1 pending
Bug #997490 [src:python-twilio] python-twilio: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
997490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997490: marked as pending in python-twilio
Control: tag -1 pending Hello, Bug #997490 in python-twilio reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-twilio/-/commit/b106a239e61543c5b3f9d26aa3cef096e61a1d57 New upstream release. (Closes: #997490) (this message was generated automatically) -- Greetings https://bugs.debian.org/997490
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
This appears when built with 10.39, but the runtime version is less than that. My guess is that this needs manual debian/libpcre2-8.shlibs override. (Or just mangle the symbols file, so it always generates correct versioned dependency.) We can also as upstream, perhaps this is something that should be solved there? Ondřej -- Ondřej Surý (He/Him) > On 15. 11. 2021, at 15:17, Matthew Vernon wrote: > > Hi, > >> On 15/11/2021 14:03, Ondřej Surý wrote: >> It’s still a bug, but I think it might be a bug in pcre2. The other Matthew >> (in CC) might need to bump the shlibs on the shared lib to >= 10.39 > > I'm slightly confused - this appears to be an issue in a php function that > went away after an upgrade? Or, at least, I'm not sure what you are > suggesting needs changing... > > [the .symbols files are automatically checked during build] > > Regards, > > Matthew
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
Hi, On 15/11/2021 14:03, Ondřej Surý wrote: It’s still a bug, but I think it might be a bug in pcre2. The other Matthew (in CC) might need to bump the shlibs on the shared lib to >= 10.39 I'm slightly confused - this appears to be an issue in a php function that went away after an upgrade? Or, at least, I'm not sure what you are suggesting needs changing... [the .symbols files are automatically checked during build] Regards, Matthew
Bug#998565: Errors due to changes in iso-codes data
Hi Scott & Tobias On Monday, 15 November 2021 21:13:09 AEDT Dr. Tobias Quathamer wrote: > On Sun, 14 Nov 2021 20:30:06 -0500 Scott Kitterman > > wrote: > > I looked at this a bit today and it looks like the test failures are due > > to > > updates in the iso-codes data used by the tests, not any real failures. I > > think disabling the failing tests for now would be a reasonable way to > > keep > > this in testing (I'm interested to avoid transitive removal of xml2rfc). > > > > Unless there's some objection to this, I will probably NMU later in the > > week. > > > > Scott K > > Hi Scott, > > iso-codes maintainer here -- I've just seen this bug and your mail. Your > analysis is correct, from my point of view, you should go ahead with the > NMU. The tests look easy enough to fix, so it's worth trying to do that. (and it's in the Debian group on salsa to make that easy :) I'm a bit surprised by some of the data changes though -- apparently England is no longer a part of the UK. Yes, that's quite complicated, but the ISO-3166-2 info does still list ENG and EAW. As the pycountry tests highlight, those divisions disappeared from iso_3166-2.json with the switch over to a different data harvester. https://www.iso.org/obp/ui/#iso:code:3166:GB Is that correct and intended? cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
It’s still a bug, but I think it might be a bug in pcre2. The other Matthew (in
CC) might need to bump the shlibs on the shared lib to >= 10.39
--
Ondřej Surý (He/Him)
> On 15. 11. 2021, at 14:54, Matthew Krauss wrote:
>
> After running apt upgrade, it works fine. I honestly thought I had upgraded
> everything earlier, but had somehow missed doing that one machine. Very
> embarrassing, sorry for the waste of time!
>
> Sent from Yahoo Mail on Android
>
> On Mon, Nov 15, 2021 at 2:04 AM, Ondřej Surý
> wrote:
> Hi,
>
> is your system fully upgraded?
>
> What’s libpcre2 version?
>
> Ondřej
> --
> Ondřej Surý (He/Him)
>
> > On 15. 11. 2021, at 2:51, Matthew Krauss wrote:
> >
> > Package: php8.1-common
> > Version: 8.1.0~rc5-1
> > Severity: grave
> > Justification: renders package unusable
> > X-Debbugs-Cc: zeros0and1o...@yahoo.com
> >
> > Dear Maintainer,
> >
> > After installing php8.1 on testing, I found that most PHP packages are
> > failing. For instance, composer, whether installed directly from
> > getcomposer.org, or through the Debian package, is broken by this bug,
> > as well as likely the vast majority of PHP based software.
> >
> > The problem seems to be in an underlying regexp library, I *think*,
> > and seems to break most of the built in php regexp functions.
> >
> > Simple demonstration, with both php7.4 and php8.1 installed:
> >
> > $ php7.4 -r 'var_export(preg_replace("/foo/", "bar", "some foo here"));
> > echo "\ndone\n";'
> > 'some bar here'
> > done
> >
> > $ php8.1 -r 'var_export(preg_replace("/foo/", "bar", "some foo here"));
> > echo "\ndone\n";'
> > PHP Warning: preg_replace(): Compilation failed: unrecognised compile-time
> > option bit(s) at offset 0 in Command line code on line 1
> > NULL
> > done
> >
> > The php7.4 command runs correctly and is what I would expect. The php8.1
> > command generates a warning, as well as incorrect output.
> >
> >
> > -- System Information:
> > Debian Release: bookworm/sid
> > APT prefers testing
> > APT policy: (500, 'testing')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU threads)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
> > not set
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages php8.1 depends on:
> > ii libapache2-mod-php8.1 8.1.0~rc5-1
> > ii php8.1-common 8.1.0~rc5-1
> >
> > php8.1 recommends no packages.
> >
> > php8.1 suggests no packages.
> >
> > Versions of packages php8.1-common depends on:
> > ii libc6 2.31-17
> > ii libffi83.4.2-3
> > ii libssl1.1 1.1.1l-1
> > ii php-common 2:76
> > ii ucf3.0043
> >
> > -- no debconf information
> >
>
Bug#999726: ruby-omniauth-shibboleth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: Failure/Error: expect(last_response.status).to eq(302)
Source: ruby-omniauth-shibboleth Version: 1.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-shibboleth was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > Failure/Error: expect(last_response.status).to eq(302) > >expected: 302 > got: 200 > >(compared using ==) > # ./spec/omniauth/strategies/shibboleth_spec.rb:42:in `block (3 levels) > in ' > > Finished in 0.06473 seconds (files took 0.14061 seconds to load) > 16 examples, 1 failure > > Failed examples: > > rspec ./spec/omniauth/strategies/shibboleth_spec.rb:41 # > OmniAuth::Strategies::Shibboleth request phase is expected to redirect to > callback_url > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-shibboleth.log signature.asc Description: PGP signature
Bug#999725: ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co
Source: ruby-omniauth-saml Version: 1.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-saml was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.3, >= 1.3.2) among > 77 total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all/specifications/omniauth-saml-1.10.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.3, >= 1.3.2) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > macaddr (1.7.1) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby-saml (1.13.0) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > simplecov (0.19.1) > simplecov-html (0.12.3) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > systemu (2.6.5) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > uuid (2.3.9) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0)
Bug#999724: ruby-omniauth-salesforce: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencie
Source: ruby-omniauth-salesforce Version: 1.0.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-salesforce was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 85 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all/specifications/omniauth-salesforce-1.0.5.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > etc (default: 1.1.0) > faraday (1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth2 (1.4.4) > observer (default: 0.1.0) > omniauth (2.0.4) > omniauth-oauth2 (1.7.1) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby2_keywords (0.0.2) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > simplecov (0.19.1) > simplecov-html (0.12.3) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default:
Bug#999723: ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependenci
Source: ruby-omniauth-remote-user Version: 0.1.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-remote-user was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 68 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all/specifications/omniauth-remote-user-0.1.3.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at
Bug#999714: ruby-omniauth-crowd: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': C
Source: ruby-omniauth-crowd Version: 2.4.0-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-crowd was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 84 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all/specifications/omniauth_crowd-2.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > activesupport (6.0.3.7) > addressable (2.8.0) > atomic (1.1.16) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > concurrent-ruby (1.1.6) > concurrent-ruby-edge (0.6.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > i18n (1.8.11) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > thread_safe (0.3.6) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > tzinfo (1.2.6) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) >
Bug#999722: ruby-omniauth-openid: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies':
Source: ruby-omniauth-openid Version: 1.0.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 77 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all/specifications/omniauth-openid-1.0.1.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-openid (1.4.2) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby-hmac (0.4.0) > ruby-openid (2.9.2) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) >
Bug#999713: ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co
Source: ruby-omniauth-cas3 Version: 1.1.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-cas3 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.2) among 77 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all/specifications/omniauth-cas3-1.1.4.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.2) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > awesome_print (1.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at
Bug#999721: ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_depende
Source: ruby-omniauth-openid-connect Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid-connect was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.9) among 106 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all/specifications/gitlab-omniauth-openid-connect-0.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.9) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > activemodel (6.0.3.7) > activesupport (6.0.3.7) > addressable (2.8.0) > aes_key_wrap (1.0.1) > atomic (1.1.16) > attr_required (1.0.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bindata (2.4.8) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > concurrent-ruby (1.1.6) > concurrent-ruby-edge (0.6.0) > coveralls (0.8.23) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > docile (1.1.5) > domain_name (0.5.20190701) > etc (default: 1.1.0) > faker (1.9.1) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > http-accept (1.7.0) > http-cookie (1.0.3) > httpclient (2.8.3) > i18n (1.8.11) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > json-jwt (1.11.0) > logger (default: 1.4.2) > mail (2.7.1) > matrix (default: 0.2.0) > metaclass (0.0.4) > mime-types (3.3.1) > mime-types-data (3.2015.1120) > mini_mime (1.1.1) > minitest (5.13.0) > mocha (1.7.0) > multi_json (1.14.1) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > netrc (0.11.0) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openid_connect (1.2.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-oauth2 (1.16.0) >
Bug#999720: ruby-omniauth-oauth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': C
Source: ruby-omniauth-oauth Version: 1.1.0-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-oauth was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all/specifications/omniauth-oauth-1.1.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth (0.5.4) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > simplecov (0.19.1) > simplecov-html (0.12.3) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml
Bug#999719: ruby-omniauth-multipassword: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:
Source: ruby-omniauth-multipassword Version: 0.4.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-multipassword was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > NoMethodError: >undefined method `[]' for nil:NilClass > # ./spec/omniauth/strategy/multi_password_spec.rb:32:in `block (4 > levels) in ' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in > `call!' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in > `call' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/test/phony_session.rb:11:in > `call' > # ./spec/omniauth/strategy/multi_password_spec.rb:37:in `block (2 > levels) in ' > > Finished in 0.03768 seconds (files took 0.14531 seconds to load) > 11 examples, 2 failures > > Failed examples: > > rspec ./spec/omniauth/multipassword/base_spec.rb:61 # > OmniAuth::MultiPassword::Base single strategy shows login FORM > rspec ./spec/omniauth/strategy/multi_password_spec.rb:36 # > OmniAuth::Strategies::MultiPassword shows login FORM > > Randomized with seed 13795 > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-multipassword.log signature.asc Description: PGP signature
Bug#999718: ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co
Source: ruby-omniauth-ldap Version: 2.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-ldap was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.3) among 71 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all/specifications/gitlab_omniauth-ldap-2.1.1.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.3) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-ldap (0.16.3) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > pyu-ruby-sasl (0.0.3.3) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > rubyntlm (0.6.3) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-ldap.log signature.asc Description: PGP
Bug#999712: ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependenc
Source: ruby-omniauth-azure-oauth2 Version: 0.0.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-azure-oauth2 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all/specifications/omniauth-azure-oauth2-0.0.10.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > faraday (1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mustermann (1.1.1) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth2 (1.4.4) > observer (default: 0.1.0) > omniauth (2.0.4) > omniauth-oauth2 (1.7.1) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby2_keywords (0.0.2) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > sinatra (2.0.8.1) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > tilt (2.0.10) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR:
Bug#999717: ruby-omniauth-jwt: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Cou
Source: ruby-omniauth-jwt Version: 0.0.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-jwt was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.1) among 68 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all/specifications/omniauth-jwt-0.0.2.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.1) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-jwt.log signature.asc Description: PGP signature
Bug#999716: ruby-omniauth-google-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:
Source: ruby-omniauth-google-oauth2 Version: 0.6.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-google-oauth2 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: >undefined method `[]' for nil:NilClass > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:501:in > `script_name' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:450:in > `callback_path' > # ./spec/omniauth/strategies/google_oauth2_spec.rb:293:in `block (3 > levels) in ' > > Finished in 0.09861 seconds (files took 0.22631 seconds to load) > 102 examples, 1 failure > > Failed examples: > > rspec ./spec/omniauth/strategies/google_oauth2_spec.rb:292 # > OmniAuth::Strategies::GoogleOauth2#callback_path has the correct default > callback path > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-google-oauth2.log signature.asc Description: PGP signature
Bug#999715: ruby-omniauth-github: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies':
Source: ruby-omniauth-github Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-github was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.5) among 82 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-github/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-github/usr/share/rubygems-integration/all/specifications/omniauth-github-1.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.5) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-github/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > faraday (1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth2 (1.4.4) > observer (default: 0.1.0) > omniauth (2.0.4) > omniauth-oauth2 (1.7.1) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby2_keywords (0.0.2) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml
Processed: Re: Bug#984087: libayatana-appindicator: ftbfs with GCC-11
Processing control commands:
> close -1
Bug #984087 [src:libayatana-appindicator] libayatana-appindicator: ftbfs with
GCC-11
Marked Bug as done
> fixed -1 0.5.5-3
Bug #984087 {Done: Mike Gabriel }
[src:libayatana-appindicator] libayatana-appindicator: ftbfs with GCC-11
Marked as fixed in versions libayatana-appindicator/0.5.5-3.
--
984087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998867: debootstrap: --no-merged-usr became a no-op
There are multiple issues reported in a single bug. > This means that I cannot create a Debian chroot from Debian unstable from 10 > years ago from snapshot.debian.org without merged-/usr and thus my chroot > will behave differently as it did back then. > Please re-enable --no-merged-usr so that I can re-create old chroots from > snapshot.d.o again. I don't think debootstrap has such goals, or requirement to be able to bootstrap rolling release without a changing codename like unstable/sid. debootstrap already sets options that may not be supported or lead to incorrect chroots if debootstrap & scripts are used from too far away time window for a rolling release. If you desire to re-create a debootstrap of unstable as it looked 10 years ago, it is best to do it using 10 years old debootstrap from the said snapshot archive too. Note that stable/testing are not affected as much, because the rolling alias is resolved to a codename, and hence doing debootstrap from an old snapshot of "stable" will do what the codename "lenny" wants, although there is no guarantee that current debootstrap will resolve things the same way as the 10 year old debootstrap did. Allowing --no-merged-usr option unguarded may lead to users creating incorrect installations and chroots for the future releases, especially since packages can assume merged-usr in the upcoming releases. I wonder if I can do some further checks, I.e. if unstable, and the InRelease / Release Date is old, do split-usr. I.e. anything before 2022. Effectively implement a time guard "old-sid" vs "new-sid", since the codename for sid has not changed. Thus allowing to bootstrap old sid snapshots in a manner closer to what old debootstrap from said snapshot would do. But still wIthout any guarantees that it will be identical. > Also, build chroots must still be created without merged-usr for > sid/bookworm, until something's been done to migrate user systems. But Julien, you said that buildds run stable, meaning they are unaffected by this debootstrap change in sid/bookworm. > Please point out what you plan to do about this change in debootstrap so that > I can adapt the mmdebstrap autopkgtest accordingly. I did notice the mmdebstrap autopkgtest regression. I also noticed that mmdebstrap does not support --merged-usr flag, and instead offers three ways of creating chroots that are merged-usr. To match the current debootstrap behaviour in sid, as currently implemented in debootstrap in sid, it seems to me that mmdebstrap should auto-enable `--setup-hook=/usr/share/mmdebstrap/hooks/merged-usr/setup00.sh` for sid/bookworm, but somehow continue to honor user supplied --setup-hooks (append? override?) I was going to file a bug report about that after using mmdebstrap, as I have not used it yet and not sure how that would fit into UX and user expectations. -- Regards, Dimitri.
Bug#999711: netselect-apt: ERROR: The certificate of 'www.debian.org' is not trusted.
Package: netselect-apt Severity: serious netselect-apt doesn't work in a minimal environment: # netselect-apt /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. Using distribution stable. Retrieving the list of mirrors from www.debian.org... --2021-11-15 12:49:13-- http://www.debian.org/mirror/mirrors_full Resolving www.debian.org (www.debian.org)... 128.31.0.62, 149.20.4.15, 2603:400a::bb8::801f:3e, ... Connecting to www.debian.org (www.debian.org)|128.31.0.62|:80... connected. HTTP request sent, awaiting response... 302 Found Location: https://www.debian.org/mirror/mirrors_full [following] --2021-11-15 12:49:13-- https://www.debian.org/mirror/mirrors_full Connecting to www.debian.org (www.debian.org)|128.31.0.62|:443... connected. ERROR: The certificate of 'www.debian.org' is not trusted. ERROR: The certificate of 'www.debian.org' doesn't have a known issuer. /usr/bin/netselect-apt: wget failed to retrieve http://www.debian.org/mirror/mirrors_full. Please try to correct the problem by reading the wget messages printed above. Installing ca-certificates fixes this. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Versions of packages netselect-apt depends on: ii curl 7.79.1-2 ii netselect 0.3.ds1-29 ii wget 1.21.2-2 -- Jakub Wilk
Bug#996529: marked as done (vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)
Your message dated Mon, 15 Nov 2021 12:48:51 +
with message-id
and subject line Bug#996529: fixed in vagrant 2.2.19+dfsg-1
has caused the Debian Bug report #996529,
regarding vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError:
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.)
--
996529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vagrant
Version: 2.2.14+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, vagrant was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> RuntimeError:
>class variable access from toplevel
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:10:in
> `block (3 levels) in '
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `initialize'
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `new'
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `block (2 levels) in '
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:34:in
> `block (4 levels) in '
>
> Finished in 14 minutes 32 seconds (files took 5.03 seconds to load)
> 2824 examples, 7 failures, 9 pending
>
> Failed examples:
>
> rspec
> /<>/test/unit/plugins/commands/cloud/provider/upload_test.rb:88
> #
> VagrantPlugins::CloudCommand::ProviderCommand::Command::Upload#upload_provider
> with direct option should use direct upload
> rspec /<>/test/unit/plugins/commands/cloud/search_test.rb:59 #
> VagrantPlugins::CloudCommand::Command::Search#search with valid options
> should use options when performing search
> rspec /<>/test/unit/plugins/commands/cloud/search_test.rb:72 #
> VagrantPlugins::CloudCommand::Command::Search#search with valid options with
> invalid options should only pass supported options to search
> rspec /<>/test/unit/plugins/kernel_v2/config/disk_test.rb:120 #
> VagrantPlugins::Kernel_V2::VagrantConfigDisk#add_provider_config normalizes
> provider config
> rspec
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:21
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with no
> override should split options into individual options
> rspec
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:28
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with
> overrides should merge all options
> rspec
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:33
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with
> overrides should override options defined in base
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern test/unit/\{plugins\}/\*\*/\*_test.rb --exclude-pattern
> \{test/unit/vagrant/action/builtin/box_add_test.rb,test/unit/plugins/communicators/winrm/\*_test.rb,test/unit/plugins/pushes/ftp/\*_test.rb\}
> -I/<>/debian/lib failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/vagrant/vagrant_2.2.14+dfsg-1+rebuild1633400150_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.2.19+dfsg-1
Done: Antonio Terceiro
We believe that the bug you reported is fixed in the latest version of
vagrant, 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.
Antonio Terceiro (supplier of updated vagrant 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: Mon, 15
Bug#996225: marked as done (ruby-fakeredis: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Mon, 15 Nov 2021 12:48:43 + with message-id and subject line Bug#996225: fixed in ruby-fakeredis 0.8.0-5 has caused the Debian Bug report #996225, regarding ruby-fakeredis: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-fakeredis Version: 0.8.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-fakeredis was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments > # > /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:1604:in > `block in zadd' > # > /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:69:in > `block in synchronize' > # /usr/lib/ruby/3.0.0/monitor.rb:202:in `synchronize' > # /usr/lib/ruby/3.0.0/monitor.rb:202:in `mon_synchronize' > # > /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:69:in > `synchronize' > # > /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:1596:in > `zadd' > # ./spec/sorted_sets_spec.rb:767:in `block (4 levels) in > ' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:257:in > `instance_exec' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:257:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:503:in > `block in with_around_and_singleton_context_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:460:in > `block in with_around_example_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/hooks.rb:481:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/hooks.rb:619:in > `run_around_example_hooks_for' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/hooks.rb:481:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:460:in > `with_around_example_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:503:in > `with_around_and_singleton_context_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:254:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:644:in > `block in run_examples' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:640:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:640:in > `run_examples' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:606:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:607:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:607:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:607:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:607:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:607:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:607:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:121:in > `block (3 levels) in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:121:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:121:in > `block (2 levels) in run_specs' > # >
Bug#995281: marked as done (lomiri-download-manager: FTBFS due to symbols changes)
Your message dated Mon, 15 Nov 2021 12:36:35 + with message-id and subject line Bug#995281: fixed in lomiri-download-manager 0.1.0-9 has caused the Debian Bug report #995281, regarding lomiri-download-manager: FTBFS due to symbols changes 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.) -- 995281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri-download-manager Version: 0.1.0-8 Severity: serious Hi Mike, The lomiri-download-manager package fails to build in unstable, because of some symbols file mismatches: [...] dpkg-gensymbols: warning: debian/liblomiri-download-manager-common0/DEBIAN/symbols doesn't match completely debian/liblomiri-download-manager-common0.symbols --- debian/liblomiri-download-manager-common0.symbols (liblomiri-download-manager-common0_0.1.0-8_amd64) +++ dpkg-gensymbolsKFBfk1 2021-09-29 04:28:53.866805288 + @@ -34,8 +34,8 @@ _ZN6Lomiri15DownloadManager19GroupDownloadStructC2ERK7QStringS4_S4_@Base 0.1.0 _ZN6Lomiri15DownloadManager19GroupDownloadStructC2ERKS1_@Base 0.1.0 _ZN6Lomiri15DownloadManager19GroupDownloadStructC2Ev@Base 0.1.0 - (arch=armel armhf)_ZN6Lomiri15DownloadManager19GroupDownloadStructD1Ev@Base 0.1.0 - (arch=armel armhf)_ZN6Lomiri15DownloadManager19GroupDownloadStructD2Ev@Base 0.1.0 + _ZN6Lomiri15DownloadManager19GroupDownloadStructD1Ev@Base 0.1.0 + _ZN6Lomiri15DownloadManager19GroupDownloadStructD2Ev@Base 0.1.0 _ZN6Lomiri15DownloadManager19GroupDownloadStructaSERKS1_@Base 0.1.0 _ZN6Lomiri15DownloadManagerlsER13QDBusArgumentRKNS0_14DownloadStructE@Base 0.1.0 _ZN6Lomiri15DownloadManagerlsER13QDBusArgumentRKNS0_19DownloadStateStructE@Base 0.1.0 dpkg-gensymbols: warning: debian/liblomiri-download-manager-client0/DEBIAN/symbols doesn't match completely debian/liblomiri-download-manager-client0.symbols --- debian/liblomiri-download-manager-client0.symbols (liblomiri-download-manager-client0_0.1.0-8_amd64) +++ dpkg-gensymbolsUJ6Ro5 2021-09-29 04:28:53.982805242 + @@ -131,14 +131,14 @@ _ZNK6Lomiri15DownloadManager9DBusError10metaObjectEv@Base 0.1.0 _ZNK6Lomiri15DownloadManager9HashError10metaObjectEv@Base 0.1.0 _ZNK6Lomiri15DownloadManager9HttpError10metaObjectEv@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC1ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC2ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC1ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC2ERKS5_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS8_@Base 0.1.0 -#MISSING: 0.1.0# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS8_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC1ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager13GroupDownloadEEEC2ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC1ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvPN6Lomiri15DownloadManager8DownloadEEEC2ERKS5_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC1ERKS8_@Base 0.1.0 +#MISSING: 0.1.0-8# (optional=templinst|arch=amd64)_ZNSt8functionIFvRK7QStringS2_PN6Lomiri15DownloadManager13DownloadsListEEEC2ERKS8_@Base 0.1.0 _ZTIN6Lomiri15DownloadManager12NetworkErrorE@Base 0.1.0 _ZTIN6Lomiri15DownloadManager12ProcessErrorE@Base 0.1.0
Processed: Bug#996225 marked as pending in ruby-fakeredis
Processing control commands: > tag -1 pending Bug #996225 [src:ruby-fakeredis] ruby-fakeredis: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996225: marked as pending in ruby-fakeredis
Control: tag -1 pending Hello, Bug #996225 in ruby-fakeredis 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/ruby-team/ruby-fakeredis/-/commit/bd0f9fbcaee35603cc1b705f6ad436b67006a9e2 * Team upload. * Add Fix_tests_for_Ruby_2.7+_compatibility.patch (Closes: #996225). (this message was generated automatically) -- Greetings https://bugs.debian.org/996225
Bug#998587: marked as done (isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Mon, 15 Nov 2021 11:48:46 + with message-id and subject line Bug#998587: fixed in isoquery 3.2.6-1 has caused the Debian Bug report #998587, regarding isoquery: FTBFS: dh_auto_test: error: make -j4 check 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.) -- 998587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: isoquery Version: 3.2.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 /<>/debian/tmpdir/locale > localedef -i de_DE -f UTF-8 /<>/debian/tmpdir/locale/de_DE.UTF-8 > LOCPATH=/<>/debian/tmpdir/locale LANG=de LC_ALL=de_DE.UTF-8 > dh_auto_test > make -j4 check VERBOSE=1 > make[2]: Verzeichnis „/<>“ wird betreten > Making check in po > make[3]: Verzeichnis „/<>/po“ wird betreten > make[3]: Für das Ziel „check“ ist nichts zu tun. > make[3]: Verzeichnis „/<>/po“ wird verlassen > Making check in src > make[3]: Verzeichnis „/<>/src“ wird betreten > make[3]: Für das Ziel „check“ ist nichts zu tun. > make[3]: Verzeichnis „/<>/src“ wird verlassen > Making check in tests > make[3]: Verzeichnis „/<>/tests“ wird betreten > make check-am > make[4]: Verzeichnis „/<>/tests“ wird betreten > make options integration\ > > make[5]: Verzeichnis „/<>/tests“ wird betreten > gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" > -DPACKAGE_VERSION=\"3.2.5\" -DPACKAGE_STRING=\"isoquery\ 3.2.5\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" > -DVERSION=\"3.2.5\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DGETTEXT_PACKAGE=\"isoquery\" -I. -I../src -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -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 > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o options.o > options.c > gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" > -DPACKAGE_VERSION=\"3.2.5\" -DPACKAGE_STRING=\"isoquery\ 3.2.5\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" > -DVERSION=\"3.2.5\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DGETTEXT_PACKAGE=\"isoquery\" -I. -DTESTDIR=\".\" -I../src > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -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 > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > integration-integration.o `test -f 'integration.c' || echo './'`integration.c > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o integration > integration-integration.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 > -lglib-2.0 ../src/options.o > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o options > options.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 > ../src/options.o > make[5]: Verzeichnis „/<>/tests“ wird verlassen > make check-TESTS > make[5]: Verzeichnis „/<>/tests“ wird betreten > make[6]: Verzeichnis „/<>/tests“ wird betreten > PASS: options 1 /options/standard_default > PASS: options 2 /options/standard_provided > PASS: options 3 /options/standard_deprecated_639 > PASS: options 4 /options/standard_deprecated_3166 > PASS: options 5 /options/standard_invalid > PASS: options 6 /options/pathname_default > PASS: options 7 /options/pathname_provided > PASS: options 8 /options/pathname_provided_with_dir_separator > PASS: options 9 /options/pathname_from_standard > PASS: options 10 /options/name_default > PASS: options 11 /options/name_name > PASS: options 12 /options/name_official_name > PASS: options 13 /options/name_common_name > PASS: options 14 /options/null_separator > PASS: options 15 /options/invalid_option > PASS: integration 1 /integration/iso_639-2/all_localized > PASS: integration 2 /integration/iso_639-2/all_null_separator > PASS: integration 3
Bug#998565: Errors due to changes in iso-codes data
On Sun, 14 Nov 2021 20:30:06 -0500 Scott Kitterman wrote: I looked at this a bit today and it looks like the test failures are due to updates in the iso-codes data used by the tests, not any real failures. I think disabling the failing tests for now would be a reasonable way to keep this in testing (I'm interested to avoid transitive removal of xml2rfc). Unless there's some objection to this, I will probably NMU later in the week. Scott K Hi Scott, iso-codes maintainer here -- I've just seen this bug and your mail. Your analysis is correct, from my point of view, you should go ahead with the NMU. Regards, Tobias OpenPGP_signature Description: OpenPGP digital signature
Bug#995281: marked as pending in lomiri-download-manager
Control: tag -1 pending Hello, Bug #995281 in lomiri-download-manager 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/ubports-team/lomiri-download-manager/-/commit/b72a0eb519c31f8d313a4d5c02bd768b4027c24e debian/rules: Comment out DPKG_GENSYMBOLS_CHECK_LEVEL, lets use default (closes: #995281) (this message was generated automatically) -- Greetings https://bugs.debian.org/995281
Processed: Bug#995281 marked as pending in lomiri-download-manager
Processing control commands: > tag -1 pending Bug #995281 [src:lomiri-download-manager] lomiri-download-manager: FTBFS due to symbols changes Added tag(s) pending. -- 995281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996951: marked as done (linux-image-5.14.0-3-amd64: iouring looses requests)
Your message dated Mon, 15 Nov 2021 10:00:20 +
with message-id
and subject line Bug#996951: fixed in linux 5.15.2-1~exp1
has caused the Debian Bug report #996951,
regarding linux-image-5.14.0-3-amd64: iouring looses requests
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.)
--
996951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.14.12-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
MariaDB has been investigating a 10.6+ related problem for a while
https://jira.mariadb.org/browse/MDEV-26674
https://jira.mariadb.org/browse/MDEV-26555
The result of this investigation is that between 5.11 and fixed in 5.15
is a uring kernel related fault that results in a write request getting
lost.
The result of this is that MariaDB-10.6 users, and perhaps other
applications using the iouring kernel interface will loose either
availablity or data.
The good news is I've validated that the linux mainline 5.14.14 build
from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.14/ has
actually fixed this problem.
As such this affects bullseye-backports, bookworm and side currently.
This can be validated by installing mariadb-test-10.6 from MariaDB's
repo.
https://mariadb.org/download/#mariadb-repositories
To test run:
cd /usr/share/mysql/mysql-test
./mtr --vardir=/tmp/var --parallel=4 encryption.innochecksum{,}
./mtr --vardir=/tmp/var --parallel=4 stress.ddl_innodb stress.ddl_innodb
stress.ddl_innodb stress.ddl_innodb
A test failure (after a large timeout 10 mins I think) results in the
mariadb error:
2021-10-21 9:08:43 0 [ERROR] [FATAL] InnoDB:
innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please
refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
Marko (MariaDB innodb maintainer) in
https://jira.mariadb.org/browse/MDEV-26674?focusedCommentId=202674=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-202674
already validated the problem on sid.
This is reported on an ubuntu impish machine with the Debian kernel
installed to eliminate any other userspace effects that may have caused
this.
-- Package-specific info:
** Version:
Linux version 5.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian
10.3.0-11) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian
5.14.12-1 (2021-10-14)
** Command line:
BOOT_IMAGE=/vmlinuz-5.14.0-3-amd64 root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
** Not tainted
** Kernel log:
[1.866883] ata4: SATA link down (SStatus 0 SControl 300)
[1.869434] scsi 0:0:0:0: CD-ROMQEMU QEMU DVD-ROM 2.5+
PQ: 0 ANSI: 5
[1.878673] ata6: SATA link down (SStatus 0 SControl 300)
[1.880335] ata5: SATA link down (SStatus 0 SControl 300)
[1.915393] sr 0:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[1.916496] cdrom: Uniform CD-ROM driver Revision: 3.20
[1.958195] sr 0:0:0:0: Attached scsi CD-ROM sr0
[2.217095] input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/serio1/input/input3
[2.225457] pcieport :00:02.6: pciehp: Slot(0-6): No device found
[2.525250] raid6: avx2x4 gen() 29809 MB/s
[2.593249] raid6: avx2x4 xor() 13304 MB/s
[2.661249] raid6: avx2x2 gen() 34952 MB/s
[2.729248] raid6: avx2x2 xor() 20847 MB/s
[2.797248] raid6: avx2x1 gen() 29982 MB/s
[2.865248] raid6: avx2x1 xor() 16322 MB/s
[2.933259] raid6: sse2x4 gen() 14256 MB/s
[3.001247] raid6: sse2x4 xor() 8371 MB/s
[3.069248] raid6: sse2x2 gen() 14546 MB/s
[3.137248] raid6: sse2x2 xor() 8631 MB/s
[3.205249] raid6: sse2x1 gen() 12159 MB/s
[3.273248] raid6: sse2x1 xor() 6207 MB/s
[3.273649] raid6: using algorithm avx2x2 gen() 34952 MB/s
[3.274147] raid6: xor() 20847 MB/s, rmw enabled
[3.274552] raid6: using avx2x2 recovery algorithm
[3.278389] xor: automatically using best checksumming function avx
[3.282251] async_tx: api initialized (async)
[3.433164] Btrfs loaded, crc32c=crc32c-intel, zoned=yes
[3.667862] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts:
(null). Quota mode: none.
[3.759716] Not activating Mandatory Access Control as /sbin/tomoyo-init
does not exist.
[3.853765] systemd[1]: Inserted module 'autofs4'
[3.893289] systemd[1]: systemd 248.3-1ubuntu8 running in system mode. (+PAM
+AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT
