Bug#997126: [Debian-med-packaging] Bug#997126: nipype test issue reported upstream
Hi Étienne On Fri, 5 Nov 2021 at 00:03, Étienne Mollier wrote: > From Andreas Tille's discussion with upstream, this might be > caused by numpy or scipy, possibly Debian specific. This sounds a lot like #994457 which was due to a change in lapack 3.10. Regards Graham
Bug#887834: [Pkg-mpd-maintainers] Bug#887834: Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid
On 2021/11/05 05:55, Florian Schlichting wrote: > However, Max: behind this hides another problem, which is why I asked > Ryan to delete the pid_file configuration: as part of 0.23.3 you added > the "RuntimeDirectory=mpd" directive to both mpd.service units. In the > absence of User and Group directives, this causes /run/mpd to change > ownership from mpd:audio (as created by our > /usr/lib/tmpfiles.d/mpd.conf) to root:root, which means that mpd would > have to be run as root in order to be able to create a socket or a > pidfile (yes, legacy) there. I think that's broken from an upstream > perspective as well, and only works when running mpd as user. True, and the real fix would be to finally cease launching MPD as root, which is an anachronism. > I suppose the best way forward is to specify User=mpd and Group=audio > in the system unit, however this immediately hits a snag when mpd tries > to open its log file /var/log/mpd/mpd.log, which up to now is created as > root. This we could probably work around in Debian, and defaulting to > log to syslog/journal also feels sensible, but I'm not sure if there may > be other things that mpd might want to be root for when starting up as a > system service? The right way to have a writable /var/log/mpd is "LogsDirectory=mpd", but I don't want to do that. Per-daemon log files are an anachronism, too. Just like starting daemons as root, PID files, per-daemon daemonization code and so on ... all the good stuff that systemd can do for us, stuff which in ancient times every daemon had unnecessary duplicate code for. Another thing that MPD could fail if we don't launch MPD as root is binding to "privileged ports" (another anachronism). For example, a httpd streaming output could be bound to a low port. People who do that could add a drop-in with "AmbientCapabilities=CAP_NET_BIND_SERVICE" to give MPD permission for that.
Bug#887834: [Pkg-mpd-maintainers] Bug#887834: Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid
Hi Ryan (and Max please see below):
> and have the following minimal mpd.conf:
>
> --
> music_directory "/var/lib/mpd/music"
> db_file "/var/lib/mpd/tag_cache"
> pid_file "/run/mpd/pid"
> state_file"/var/lib/mpd/state"
> log_level "verbose"
>
> user "mpd"
> bind_to_address "127.0.0.1"
>
> audio_output {
> type "null"
> name "null"
> }
> --
please, for now, delete or comment out the pid_file line
> Attempting to start mpd results in:
>
> --
> rak@zeta:~$ sudo service mpd start
> Job for mpd.service failed because a fatal signal was delivered to the
> control process.
> See "systemctl status mpd.service" and "journalctl -xeu mpd.service" for
> details.
> rak@zeta:~$ sudo systemctl status mpd.service
> × mpd.service - Music Player Daemon
> Loaded: loaded (/usr/lib/systemd/system/mpd.service; enabled; vendor
> preset: enabled)
> Active: failed (Result: signal) since Thu 2021-11-04 13:49:36 EDT; 2s ago
> TriggeredBy: × mpd.socket
>Docs: man:mpd(1)
> man:mpd.conf(5)
> file:///usr/share/doc/mpd/html/user.html
> Process: 474546 ExecStart=/usr/bin/mpd --no-daemon $MPDCONF (code=killed,
> signal=ABRT)
>Main PID: 474546 (code=killed, signal=ABRT)
> CPU: 175ms
>
> Nov 04 13:49:36 zeta mpd[474546]: sndfile: libsndfile-1.0.31
> Nov 04 13:49:36 zeta mpd[474546]: hybrid_dsd: The Hybrid DSD decoder is
> disabled because it was not explicitly enabled
> Nov 04 13:49:36 zeta mpd[474546]: adplug: adplug 2.3.3
> Nov 04 13:49:36 zeta mpd[474546]: exception: Failed to open
> '/var/lib/mpd/tag_cache': No such file or directory
> Nov 04 13:49:36 zeta mpd[474546]: curl: version 7.74.0
> Nov 04 13:49:36 zeta mpd[474546]: curl: with GnuTLS/3.7.2
> Nov 04 13:49:36 zeta mpd[474546]: mpd: ../src/event/Loop.cxx:60:
> EventLoop::~EventLoop(): Assertion `sockets.empty()' failed.
> Nov 04 13:49:36 zeta systemd[1]: mpd.service: Main process exited,
> code=killed, status=6/ABRT
> Nov 04 13:49:36 zeta systemd[1]: mpd.service: Failed with result 'signal'.
> Nov 04 13:49:36 zeta systemd[1]: Failed to start Music Player Daemon.
The tag_cache exception is non-fatal. The problem here is the Assertion
failure, which is #998310 and fixed in mpd 0.23.3-2
However, Max: behind this hides another problem, which is why I asked
Ryan to delete the pid_file configuration: as part of 0.23.3 you added
the "RuntimeDirectory=mpd" directive to both mpd.service units. In the
absence of User and Group directives, this causes /run/mpd to change
ownership from mpd:audio (as created by our
/usr/lib/tmpfiles.d/mpd.conf) to root:root, which means that mpd would
have to be run as root in order to be able to create a socket or a
pidfile (yes, legacy) there. I think that's broken from an upstream
perspective as well, and only works when running mpd as user.
I suppose the best way forward is to specify User=mpd and Group=audio
in the system unit, however this immediately hits a snag when mpd tries
to open its log file /var/log/mpd/mpd.log, which up to now is created as
root. This we could probably work around in Debian, and defaulting to
log to syslog/journal also feels sensible, but I'm not sure if there may
be other things that mpd might want to be root for when starting up as a
system service?
Florian
Bug#997777: marked as done (python-easygui: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 276))
Your message dated Fri, 05 Nov 2021 04:18:50 + with message-id and subject line Bug#99: fixed in python-easygui 0.98.1-2 has caused the Debian Bug report #99, regarding python-easygui: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 276) 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.) -- 99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-easygui Version: 0.98.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/sphinx' > sphinx-build -b man -d _build/doctrees . _build/man > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: invalid syntax (conf.py, > line 276) > > make[2]: *** [Makefile:133: man] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-easygui_0.98.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-easygui Source-Version: 0.98.1-2 Done: Andreas Noteng We believe that the bug you reported is fixed in the latest version of python-easygui, 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. Andreas Noteng (supplier of updated python-easygui 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, 02 Nov 2021 08:20:33 +0100 Source: python-easygui Architecture: source Version: 0.98.1-2 Distribution: unstable Urgency: medium Maintainer: Andreas Noteng Changed-By: Andreas Noteng Closes: 99 Changes: python-easygui (0.98.1-2) unstable; urgency=medium . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Update standards version to 4.5.0, no changes needed. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Andreas Noteng ] * Successfully build with Python3 (Closes: #99) - fix_py3_sphinx_build.patch * Bump Standards-Version to 4.6.0, no change needed * Bump compat-level to 13 Checksums-Sha1: de32d798275e51ff0477ecdab1809417c29f32db 2154 python-easygui_0.98.1-2.dsc 7d15e5688e98b2a0bf7f98ccc109310f2c4431d5 4288 python-easygui_0.98.1-2.debian.tar.xz cad0f5d42c400b01f5bd4f11ce73b56010b880fd 8177 python-easygui_0.98.1-2_amd64.buildinfo Checksums-Sha256: dfece54dff80050e1863059a1d4165ab2341e3d38b447272394ae8c5bb033ac2 2154 python-easygui_0.98.1-2.dsc 32d1b04602cb81808bbe128f6142bb0a1d4735d2dd6a7eaec4bc8387ae18c45c 4288 python-easygui_0.98.1-2.debian.tar.xz 92e92ee3ee72abbcf426baa65f2628f39d57b24acd2d3f85cdb293323a68accd 8177 python-easygui_0.98.1-2_amd64.buildinfo Files: 34129e130aa35418b33d027d0f7e586e 2154 python optional python-easygui_0.98.1-2.dsc 7a6295999666cb17aad9e4144c92b853 4288 python optional python-easygui_0.98.1-2.debian.tar.xz 0d99bb0fc2b08c3183522c0a32be61d8 8177 python optional python-easygui_0.98.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmGErRgPHHN3dEB0ZWNo aWUubmV0AAoJEFPVvGS1I3iiH80QAIVyJY249fpmyzg2QZC994HXBFaZP+1V82mX +PRdJWVNZoH+/VEkAbk4QXES3sDNi1oUE74OUUDWBuGUR5wSPMittALl2hB6FYrP 0smhvbfuJKG6r6Q089QE7ZHR3/rdCXkCT8iR7KppzHCS6JCC+aP4Z8o/0YMLCgLh RZYksUOZM4yRnwo5vHxwkIuH++6vVOLw/AqM4c2nXEKKCgM80pWaWVIUMSNFnjaX
Bug#998610: marked as done (node-cli-truncate: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Fri, 05 Nov 2021 03:18:26 + with message-id and subject line Bug#998610: fixed in node-cli-truncate 2.1.0-3 has caused the Debian Bug report #998610, regarding node-cli-truncate: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-cli-truncate Version: 2.1.0-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): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/cli-truncate > /bin/sh -ex debian/tests/pkg-js/test > + tape test.js > TAP version 13 > # main > /<>/index.js:102 > return sliceAnsi(text, 0, columns - ellipsisWidth) + ellipsis; > ^ > > TypeError: sliceAnsi is not a function > at module.exports (/<>/index.js:102:10) > at Test. (/<>/test.js:5: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) > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/node-cli-truncate_2.1.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-cli-truncate Source-Version: 2.1.0-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-cli-truncate, 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. Yadd (supplier of updated node-cli-truncate 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 03:51:34 +0100 Source: node-cli-truncate Architecture: source Version: 2.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 998610 Changes: node-cli-truncate (2.1.0-3) unstable; urgency=medium . * Team upload * Add fix for node-slice-ansi ≥ 5 (Closes: #998610) Checksums-Sha1: 67daeef61bea0e3f3c19295d2ef8206c3e433af3 2175 node-cli-truncate_2.1.0-3.dsc 50604b7506774f8de0333974dac39f1f51016798 3448 node-cli-truncate_2.1.0-3.debian.tar.xz Checksums-Sha256: c89c0033e119be8780ef00da87e4ac64bfd29ab10f427c6124a6c44fa2781027 2175 node-cli-truncate_2.1.0-3.dsc 719529a17b8ec55b96c347e387e8d96b3e9263c2c858674d13c5ce1d57d0d361 3448 node-cli-truncate_2.1.0-3.debian.tar.xz Files: 16cd5da1c56e043206742f9759f24dac 2175 javascript optional node-cli-truncate_2.1.0-3.dsc 96ee4cc49ee027aa30bd59db9f36fa18 3448 javascript optional node-cli-truncate_2.1.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGEnjEACgkQ9tdMp8mZ 7ul5hBAAjV4YiG4BHVLcWE3E8V9POAtRlzUYYWI64ieZ1wacO51r5J5bKVh4dXvE EptJ6OGIZBrr4duDafykxvnyTPldalQQOcmQY9eNPJxu/dxf4s8Jj5NR5hNvKNP1 oV+Ci
Processed: Bug#998610 marked as pending in node-cli-truncate
Processing control commands: > tag -1 pending Bug #998610 [src:node-cli-truncate] node-cli-truncate: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 998610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998485: gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times
Hi, maybe it's a good chance to change to the new updated version of gjiten at https://github.com/DarkTrick/gjiten The new version might also encounter packaging problems, but it uses more recent technology and updates; It's probably more worthful to spend time there than in the 10 year old package* Regards Chris - DarkTrick * Yes, I'm trying to promote my updates here :) On 2021/11/05 2:38, Lucas Nussbaum wrote: Source: gjiten Version: 2.6-3.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): debian/rules build dh build dh_update_autotools_config dh_autoreconf autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in' aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.in:7: the top level /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.in:8: the top level autom4te: error: /usr/bin/m4 failed with exit status: 1 aclocal: error: /usr/bin/autom4te failed with exit status: 1 autoreconf: error: aclocal failed with exit status: 1 dh_autoreconf: error: autoreconf -f -i returned exit code 1 make: *** [debian/rules:4: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/gjiten_2.6-3.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#998610: marked as pending in node-cli-truncate
Control: tag -1 pending Hello, Bug #998610 in node-cli-truncate 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/js-team/node-cli-truncate/-/commit/c8ad39d091b6c4b2058eb1ff916a640690839928 Add fix for node-slice-ansi ≥ 5 Closes: #998610 (this message was generated automatically) -- Greetings https://bugs.debian.org/998610
Bug#997482: sublime-music: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Upstream version 0.11.14 seems to fix this issue, but the patch seems to create a new bug: https://gitlab.com/sublime-music/sublime-music/-/issues/325 Currently waiting for feedback from upstream. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#996129: marked as done (ruby-axiom-types: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)
Your message dated Fri, 05 Nov 2021 02:45:17 + with message-id and subject line Bug#996129: fixed in ruby-axiom-types 0.1.1-2 has caused the Debian Bug report #996129, regarding ruby-axiom-types: 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.) -- 996129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-axiom-types Version: 0.1.1-1.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-axiom-types 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. > # ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:31:in > `block (4 levels) in ' > # ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:30:in > `initialize' > # ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:30:in > `new' > # ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:30:in > `block (3 levels) in ' > # ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:9:in > `block (2 levels) in ' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- sorted_set > # > ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:31:in `block > (4 levels) in ' > > Top 10 slowest examples (0.03959 seconds, 14.4% of total time): > Axiom::Types::ValueComparable.extended delegates to the ancestor > 0.00941 seconds > ./spec/unit/axiom/types/value_comparable/class_methods/extended_spec.rb:10 > Axiom::Types::Encodable#finalize when an ascii compatible encoding (UTF-8) > is used adds a constraint that returns true for Windows-1252 encoding > 0.0057 seconds ./spec/unit/axiom/types/encodable/finalize_spec.rb:35 > Axiom::Types::Infinity#<=> when other object is a Integer is symmetric > 0.00426 seconds > ./spec/unit/axiom/types/infinity/spaceship_operator_spec.rb:22 > Axiom::Types::Infinity#<=> when other object is a Rational is expected to > equal 1 > 0.00371 seconds > ./spec/unit/axiom/types/infinity/spaceship_operator_spec.rb:20 > Axiom::Types::Hash.infer with Axiom::Types::Hash with an Hash with a nil > key and value primitive key_type is expected to equal Axiom::Types::Object > (BasicObject) > 0.00367 seconds > ./spec/unit/axiom/types/hash/class_methods/infer_spec.rb:95 > Axiom::Types::Collection.infer with a a non-base class when the argument is > an empty SortedSet > 0.00298 seconds > ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:112 > Axiom::Types::Infinity#<=> when the other object is not comparable is > expected to be nil > 0.00273 seconds > ./spec/unit/axiom/types/infinity/spaceship_operator_spec.rb:61 > Axiom::Types::Infinity#<=> when other object is a Integer is expected to > equal 1 > 0.0026 seconds > ./spec/unit/axiom/types/infinity/spaceship_operator_spec.rb:20 > Axiom::Types::Infinity#<=> when other object is a Float is symmetric > 0.00244 seconds > ./spec/unit/axiom/types/infinity/spaceship_operator_spec.rb:22 > Axiom::Types::ValueComparable.extended adds minimum method > 0.00209 seconds > ./spec/unit/axiom/types/value_comparable/class_methods/extended_spec.rb:24 > > Top 10 slowest example groups: > Axiom::Types::ValueComparable.extended > 0.00253 seconds average (0.01263 seconds / 5 examples) > ./spec/unit/axiom/types/value_comparable/class_methods/extended_spec.rb:5 > Axiom::Types::Type.base? > 0.00229 seconds average (0.00457 seconds / 2 examples) > ./spec/unit/axiom/types/type/class_methods/base_predicate_spec.rb:5 > Axiom::Types::Infinity#<=> > 0.00127 seconds average (0.02287 seconds / 18 examples) > ./spec/unit/axiom/types/infinity/spaceship_operator_spec.rb:5 > Axiom::Types::Collection.infer > 0.00112 seconds average (0.02023 seconds / 18 examples) > ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:5 > Axiom::Types::Hash.infer > 0.00081 seconds average (0.03088 seconds / 38 examples) >
Bug#996726: Some other questions
> After 2 weeks, the bug has finally been fixed. But I wonder why the bug > wasn't tested out in the unstable branch and was pushed into the testing Because on unstable everything worked. The bug happens only due to different transition times from unstable to testing. This cannot be tested in unstable before. Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#996726: Some other questions
After 2 weeks, the bug has finally been fixed. But I wonder why the bug wasn't tested out in the unstable branch and was pushed into the testing branch.
Processed: Bug#996129 marked as pending in ruby-axiom-types
Processing control commands: > tag -1 pending Bug #996129 [src:ruby-axiom-types] ruby-axiom-types: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) pending. -- 996129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996129: marked as pending in ruby-axiom-types
Control: tag -1 pending
Hello,
Bug #996129 in ruby-axiom-types 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-axiom-types/-/commit/d95c6a8fcc517cb776936729804f1b4a1fab3af6
Update packaging files
* d/control: Add Rules-Requires-Root and Testsuite fields.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Add ruby-sorted-set (closes: #996129).
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/ruby-tests.rake: Update to use gem2deb.
* d/rules: Use gem installation layout and check dependencies.
* d/watch: Update file to use github.
* d/patches/*.patch: Refresh patches and add DEP-3 headers.
* d/upstream/metadata: Add YAML header and Archive field.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996129
Bug#997129: marked as done (marble: FTBFS: dh_install: error: missing files, aborting)
Your message dated Fri, 05 Nov 2021 01:19:58 + with message-id and subject line Bug#997129: fixed in marble 4:21.08.3-1 has caused the Debian Bug report #997129, regarding marble: FTBFS: dh_install: error: missing files, aborting 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.) -- 997129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: marble Version: 4:21.08.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # remove extra license files > rm -f debian/tmp/usr/share/marble/data/LICENSE.txt > rm -rf debian/tmp/usr/share/marble/data/licenses/ > make[1]: Leaving directory '/<>' >dh_install > dh_install: warning: Cannot find (any matches for) > "usr/share/kservices5/plasma-applet-org.kde.plasma.worldclock.desktop" (tried > in ., debian/tmp) > > dh_install: warning: plasma-marble missing files: > usr/share/kservices5/plasma-applet-org.kde.plasma.worldclock.desktop > dh_install: warning: Cannot find (any matches for) > "usr/share/kservices5/plasma-wallpaper-org.kde.plasma.worldmap.desktop" > (tried in ., debian/tmp) > > dh_install: warning: plasma-marble missing files: > usr/share/kservices5/plasma-wallpaper-org.kde.plasma.worldmap.desktop > dh_install: error: missing files, aborting > make: *** [debian/rules:14: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/marble_21.08.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: marble Source-Version: 4:21.08.3-1 Done: Norbert Preining We believe that the bug you reported is fixed in the latest version of marble, 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. Norbert Preining (supplier of updated marble 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 09:55:02 +0900 Source: marble Architecture: source Version: 4:21.08.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Norbert Preining Closes: 997129 Changes: marble (4:21.08.3-1) unstable; urgency=medium . [ Norbert Preining ] * Drop files not built with newer frameworks (Closes: #997129). * New upstream release (21.08.3). Checksums-Sha1: 786af3824e35171e9700afc2d23ff61ff19a1e36 3384 marble_21.08.3-1.dsc b57f0704d9b6a2f6052a85ff5025d6695c4a6ab8 52421300 marble_21.08.3.orig.tar.xz 01dd00782fa44cea5c339564a8c4c2144a7eec1c 833 marble_21.08.3.orig.tar.xz.asc a772789c17f79f7c7e98487026c04e65299005c1 74104 marble_21.08.3-1.debian.tar.xz 9eed2246a55dffc0d00b331028d92d837cd3e969 27802 marble_21.08.3-1_source.buildinfo Checksums-Sha256: c1ab6d1eef99c46645bdd05f251348fa6c9884365815ff1b4ed986d05136c689 3384 marble_21.08.3-1.dsc 0a285852438ab4cf0205c74fc4082cef742f16ce4b84f68aae30822e6ab5572d 52421300 marble_21.08.3.orig.tar.xz c5e81fa9997c24d82c6503b70bf5c78a1da8058b2d4fe072d62349672ebe9f63 833 marble_21.08.3.orig.tar.xz.asc 9d63adca27c01103f151ce73184a48960adbca5b89ce6bebf8d0f727672e1988 74104 marble_21.08.3-1.debian.tar.xz 549c7c1be34583ee89449f9f50288cf5b3da538d9e0b5a78da8bdfb9fb0d3c57 27802 marble_21.08.3-1_source.buildinfo Files: 768f4d47727ef93252f4e357905ba574 3384 kde optional marble_21.08.3-1.dsc cee3ef415e083ef724d9c8c1ac67a362 52421300 kde optional marble_21.08.3.orig.tar.xz a8397104f92789d95f4cc7fa77fa2fbf 833 kde optional marble_21.08.3.orig.tar.xz.asc 8ff6b084920c20276e3468e885d9e02a 74104 kde optional
Bug#996124: marked as done (ruby-appraiser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: No such file or directory @ rb_sysopen - http://rubygems.org/api/v1/gems/rails.json)
Your message dated Fri, 05 Nov 2021 01:20:19 + with message-id and subject line Bug#996124: fixed in ruby-appraiser 0.2.0-4 has caused the Debian Bug report #996124, regarding ruby-appraiser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: No such file or directory @ rb_sysopen - http://rubygems.org/api/v1/gems/rails.json 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.) -- 996124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-appraiser Version: 0.2.0-3.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-appraiser 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): > No such file or directory @ rb_sysopen - > http://rubygems.org/api/v1/gems/rails.json > # ./lib/rubygems/commands/appraiser_command.rb:73:in `initialize' > # ./lib/rubygems/commands/appraiser_command.rb:73:in `open' > # ./lib/rubygems/commands/appraiser_command.rb:73:in `load_json' > # ./spec/appraiser_spec.rb:122:in `block (4 levels) in ' > > Deprecation Warnings: > > Using `should_receive` from rspec-mocks' old `:should` syntax without > explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or > explicitly enable `:should` instead. Called from > /<>/spec/appraiser_spec.rb:40:in `block (3 levels) in (required)>'. > > > If you need more of the backtrace for any of these deprecations to > identify where to make the necessary changes, you can configure > `config.raise_errors_for_deprecations!`, and it will turn the > deprecation warnings into errors, giving you the full backtrace. > > 1 deprecation warning total > > Finished in 0.0384 seconds (files took 0.48184 seconds to load) > 25 examples, 13 failures > > Failed examples: > > rspec ./spec/appraiser_spec.rb:60 # > Gem::Commands::AppraiserCommand#process(output) response body is not empty > json retrieves :default group dependency json from RubyGems API > rspec ./spec/appraiser_spec.rb:68 # > Gem::Commands::AppraiserCommand#process(output) response body is not empty > json not retrieves :test group dependency json from RubyGems API > rspec ./spec/appraiser_spec.rb:89 # > Gem::Commands::AppraiserCommand#process(output) response body is empty json > not raises exception > rspec ./spec/appraiser_spec.rb:95 # > Gem::Commands::AppraiserCommand#process(output) response body is empty json > puts dependency source > rspec ./spec/appraiser_spec.rb:113 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() raises > OpenURI::HTTPError exception > rspec ./spec/appraiser_spec.rb:114 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() raises > OpenURI::HTTPError exception > rspec ./spec/appraiser_spec.rb:125 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'name' > rspec ./spec/appraiser_spec.rb:130 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'authors' > rspec ./spec/appraiser_spec.rb:135 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'downloads' > rspec ./spec/appraiser_spec.rb:140 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'project_uri' > rspec ./spec/appraiser_spec.rb:145 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'documentation_uri' > rspec ./spec/appraiser_spec.rb:150 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'source_code_uri' > rspec ./spec/appraiser_spec.rb:155 # > Gem::Commands::AppraiserCommand#load_json(gem_name) open() returns JSON > response have key 'info' > > /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-appraiser/ruby-appraiser_0.2.0-3.1+rebuild1633375259_amd64.build.txt signature.asc Description: PGP signature --- End Message --- ---
Bug#998493: marked as done (packit: FTBFS: configure.ac:34: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Fri, 05 Nov 2021 01:04:03 + with message-id and subject line Bug#998493: fixed in packit 1.8-1 has caused the Debian Bug report #998493, regarding packit: FTBFS: configure.ac:34: 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.) -- 998493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: packit Version: 1.7-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): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf > configure.ac:34: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:30: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:34: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:7: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/packit_1.7-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: packit Source-Version: 1.8-1 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of packit, 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. Joao Eriberto Mota Filho (supplier of updated packit 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: Thu, 04 Nov 2021 21:00:17 -0300 Source: packit Architecture: source Version: 1.8-1 Distribution: unstable Urgency: medium Maintainer: Joao Eriberto Mota Filho Changed-By: Joao Eriberto Mota Filho Closes: 998493 Changes: packit (1.8-1) unstable; urgency=medium . * New upstream version 1.8. (Closes: #998493) * debian/control: bumped Standards-Version to 4.6.0.1. * debian/copyright: - Added rights for Sam James . - Changed man/generate-man.sh to man/create-man.sh. - Updated upstream and packaging copyright years. * debian/tests/control: break long lines. Checksums-Sha1: 7e10382aabab9215b96b50449102e803e92d698f 1920 packit_1.8-1.dsc ed16879b9e8c31eff12b4c6f8559c9b6b56a209b 150410 packit_1.8.orig.tar.gz 9567f7ca00ca0a6bef09b9fe7e576590bba72c75 5656 packit_1.8-1.debian.tar.xz d86c5f89e0597607b11845d44c13cd8155df3856 5710 packit_1.8-1_source.buildinfo Checksums-Sha256: 57eb4f232b2e91c1927b830e2a6f6cbba685c65058ee00d38551383ec81ae859 1920 packit_1.8-1.dsc 2093ecc9012792a96200f5f2b531380b0beabf082b6b9dcceca3f23192da6266 150410 packit_1.8.orig.tar.gz 28eb995856e2f228aa3ea5a320b44638cbcaa89e0436f76380c4b107539f39de 5656 packit_1.8-1.debian.tar.xz 45e06a77ef986cf183f638fc8dadd3317b41536e23ad148aeffa685da9e5e658 5710 packit_1.8-1_source.buildinfo Files: 951249d5a207c2a7d8b4572530fe4ae4 1920 net optional packit_1.8-1.dsc bc1fe336199bcad032901895dcc03fae 150410 net optional packit_1.8.orig.tar.gz 44afddc9b6adeebc1f4472801c76892e 5656 net optional packit_1.8-1.debian.tar.xz 9f953fc98c85e58043bb3c29b4699d26 5710 net optional packit_1.8-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmGEfdgACgkQ3mO5xwTr 6e8FjQ//Uftf
Bug#998581: git-imerge: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
On Thu, 2021-11-04 at 20:45 +0100, Lucas Nussbaum wrote: > Source: git-imerge ... > > ERROR: Could not install packages due to an EnvironmentError: > > [Errno 13] Permission denied: '/usr/lib/python3.9/dist-packages' This is apparently caused by a change in dh-python that will be reverted. For now please don't file any more bugs about this. https://salsa.debian.org/python-team/tools/dh-python/-/commit/169bc6ba400d27cfc143dc7f9f6f4b5db471def1 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#996124: marked as pending in ruby-appraiser
Control: tag -1 pending Hello, Bug #996124 in ruby-appraiser 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-appraiser/-/commit/ac827d895489f30a1abd8ff6b881d6ff24c2a7d2 Fix tests with Ruby 3.0 by using URI.open() * d/rules: Disable DH_RUBY_IGNORE_TESTS. * d/patches/996124-ruby-3-fix-open.patch: Add patch. - Use URI.open and fix tests with Ruby 3.0 (closes: #996124). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996124
Processed: Bug#996124 marked as pending in ruby-appraiser
Processing control commands: > tag -1 pending Bug #996124 [src:ruby-appraiser] ruby-appraiser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: No such file or directory @ rb_sysopen - http://rubygems.org/api/v1/gems/rails.json Added tag(s) pending. -- 996124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998590: marked as done (frogr: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "warnlevel")
Your message dated Fri, 05 Nov 2021 00:48:47 + with message-id and subject line Bug#998590: fixed in frogr 1.6-3 has caused the Debian Bug report #998590, regarding frogr: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "warnlevel" 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.) -- 998590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: frogr Version: 1.6-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): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > 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 > --libexecdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "warnlevel" > > 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:21.622250 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlibexecdir=lib/x86_64-linux-gnu -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:1:0: ERROR: Unknown options: "warnlevel" > 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 > --libexecdir=lib/x86_64-linux-gnu returned exit code 1 > make: *** [debian/rules:6: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/frogr_1.6-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: frogr Source-Version: 1.6-3 Done: Alberto Garcia We believe that the bug you reported is fixed in the latest version of frogr, 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. Alberto Garcia (supplier of updated frogr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Nov 2021 01:09:45 +0100 Source: frogr Architecture: source Version: 1.6-3 Distribution: unstable Urgency: medium Maintainer: Alberto Garcia Changed-By: Alberto Garcia Closes: 998590 Changes: frogr (1.6-3) unstable; urgency=medium . [ Alberto Garcia ] * replace-warnlevel.patch: - Replace obsolete 'warnlevel' option in Meson (Closes: #998590). * debian/watch: - Set version to 4 (fixes older-debian-watch-file-standard). . [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on libexif-dev, libglib2.0-dev, libgtk-3-dev, libjson-glib-dev, libsoup2.4-dev and libxml2-dev. + frogr-data: Drop versioned constraint on frogr in Replaces. + f
Bug#998422: marked as done (ArgumentError: wrong number of arguments (given 2, expected 3) caused by lib/active_support/cache.rb:330)
Your message dated Fri, 05 Nov 2021 00:04:19 + with message-id and subject line Bug#998422: fixed in rails 2:6.0.3.7+dfsg-3 has caused the Debian Bug report #998422, regarding ArgumentError: wrong number of arguments (given 2, expected 3) caused by lib/active_support/cache.rb:330 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.) -- 998422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-active-model-serializers Version: 0.10.10-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-active-model-serializers 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 (given 2, expected 3) > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/cache.rb:710:in > `get_entry_value' > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/cache.rb:330:in > `fetch' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/concerns/caching.rb:234:in > `fetch' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/concerns/caching.rb:225:in > `block in fetch_attributes' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/concerns/caching.rb:224:in > `fetch' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/concerns/caching.rb:224:in > `fetch_attributes' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer.rb:404:in > `attributes_hash' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer.rb:371:in > `serializable_hash' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/collection_serializer.rb:27:in > `block in serializable_hash' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/collection_serializer.rb:26:in > `map' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/collection_serializer.rb:26:in > `serializable_hash' > /<>/lib/active_model_serializers/adapter/attributes.rb:14:in > `serializable_hash' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/serializable_resource.rb:10:in > `serializable_hash' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:71:in > `block (3 levels) in notify' > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/callbacks.rb:112:in > `block in run_callbacks' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:24:in > `block (3 levels) in instrument_rendering' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:81:in > `block in notify_render' > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/notifications.rb:180:in > `block in instrument' > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/notifications/instrumenter.rb:24:in > `instrument' > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/notifications.rb:180:in > `instrument' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:80:in > `notify_render' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:23:in > `block (2 levels) in instrument_rendering' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:99:in > `tag_logger' > > /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model_serializers/logging.rb:22:in > `block in instrument_rendering' > > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/callbacks.rb:121:in > `instance_exec' > >
Bug#998422: marked as pending in rails
Control: tag -1 pending Hello, Bug #998422 in rails 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/rails/-/commit/93d189c726263c6494bde60fb8c47b7cd6abcd80 add patch: fix activesupport for ruby3.0 Closes: #998422 (this message was generated automatically) -- Greetings https://bugs.debian.org/998422
Processed: Bug#998422 marked as pending in rails
Processing control commands: > tag -1 pending Bug #998422 [ruby-activesupport] ArgumentError: wrong number of arguments (given 2, expected 3) caused by lib/active_support/cache.rb:330 Added tag(s) pending. -- 998422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998531: marked as done (libscout: FTBFS: Could not resolve commons-io:commons-io:2.6.)
Your message dated Fri, 05 Nov 2021 00:47:36 +0100 with message-id <3441cb1bfa7476720aab6fc23ec5451e57af0b56.ca...@debian.org> and subject line Closing 998531 as fixed in commons-io version 2.11.0-2 has caused the Debian Bug report #998531, regarding libscout: FTBFS: Could not resolve commons-io:commons-io:2.6. 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.) -- 998531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libscout Version: 2.3.2-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): > debian/rules build > dh build --buildsystem=gradle --with javahelper --with bash-completion >dh_update_autotools_config -O--buildsystem=gradle >dh_autoreconf -O--buildsystem=gradle >dh_auto_configure -O--buildsystem=gradle >jh_linkjars -O--buildsystem=gradle >dh_auto_build -O--buildsystem=gradle > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=libscout -Dfile.encoding=UTF-8 --parallel > --max-workers=4 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file not found (/<>/settings.gradle) > Root project name not defined in settings.gradle, defaulting to > 'libscout' instead of the name of the root directory 'libscout-2.3.2' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'libscout'] > Keep-alive timer started > Adding Debian repository to project 'libscout' > Parallel execution is an incubating feature. > Evaluating root project 'libscout' using build file > '/<>/build.gradle'. > Compiling build file '/<>/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/build.gradle' using > BuildScriptTransformer. > Adding Maven pom generation to project 'libscout' > Linking the generated javadoc to the system JDK API documentation > All projects evaluated. > Selected primary task 'jar' from project : > Creating new cache for metadata-2.36/module-metadata, path > /<>/.gradle/caches/modules-2/metadata-2.36/module-metadata.bin, > access org.gradle.cache.internal.DefaultCacheAccess@3cf06a01 > Loading the Maven rules... > Replacing commons-io:commons-io:jar:2.6 -> > commons-io:commons-io:jar:debian > Passing through org.apache.commons:commons-parent:jar:debian
Bug#998537: marked as done (apktool: FTBFS: Could not resolve all files for configuration ':brut.j.util:compileClasspath'.)
Your message dated Fri, 05 Nov 2021 00:47:36 +0100 with message-id <3441cb1bfa7476720aab6fc23ec5451e57af0b56.ca...@debian.org> and subject line Closing 998531 as fixed in commons-io version 2.11.0-2 has caused the Debian Bug report #998531, regarding apktool: FTBFS: Could not resolve all files for configuration ':brut.j.util:compileClasspath'. 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.) -- 998531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apktool Version: 2.5.0+dfsg.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_build -- -Dfile.encoding=UTF-8 assemble > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=apktool -Dfile.encoding=UTF-8 --parallel > --max-workers=4 -Dfile.encoding=UTF-8 assemble > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@f27ea3 > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@f27ea3 > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@1df98368 > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@793d163b > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Compiling settings file '/<>/settings.gradle' using > SubsetScriptTransformer. > Compiling settings file '/<>/settings.gradle' using > BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file found (/<>/settings.gradle), but > rootProject.name isn't defined > Root project name not defined in settings.gradle, defaulting to > 'apktool' instead of the name of the root directory 'apktool-2.5.0+dfsg.1' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'apktool', project ':brut.apktool', project > ':brut.j.common', project ':brut.j.dir', project ':brut.j.util', project > ':brut.apktool:apktool-cli', project ':brut.apktool:apktool-lib'] > Keep-alive timer started > Adding Debian repository to project 'apktool' > Adding Debian repository to project 'brut.apktool' > Adding Debian repository to project 'brut.j.common' > Adding Debian repository to project 'brut.j.dir' > Adding Debian repository to project 'brut.j.util' > Adding Debian repository to project 'apktool-cli' > Adding Debian repository to project 'apktool-lib' > Parallel execution is an incubating feature. > Evaluating root project 'apktool' using build file > '/<>/build.gradle'. > Compiling build file '/<>/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/build.gradle' using > BuildScriptTransformer. > Compiling script '/<>/gradl
Processed: Reassign FTBFS bugs to commons-io
Processing commands for cont...@bugs.debian.org: > reassign 998531 src:commons-io Bug #998531 [src:libscout] libscout: FTBFS: Could not resolve commons-io:commons-io:2.6. Bug reassigned from package 'src:libscout' to 'src:commons-io'. No longer marked as found in versions libscout/2.3.2-3. Ignoring request to alter fixed versions of bug #998531 to the same values previously set > reassign 998537 src:commons-io Bug #998537 [src:apktool] apktool: FTBFS: Could not resolve all files for configuration ':brut.j.util:compileClasspath'. Bug reassigned from package 'src:apktool' to 'src:commons-io'. No longer marked as found in versions apktool/2.5.0+dfsg.1-2. Ignoring request to alter fixed versions of bug #998537 to the same values previously set > forcemerge 998531 998537 Bug #998531 [src:commons-io] libscout: FTBFS: Could not resolve commons-io:commons-io:2.6. Bug #998537 [src:commons-io] apktool: FTBFS: Could not resolve all files for configuration ':brut.j.util:compileClasspath'. Merged 998531 998537 > thanks Stopping processing here. Please contact me if you need assistance. -- 998531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998531 998537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
> bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be installed It looks like bind8 no longer builds the bind9-dev package. It's still present in unstable as a cruft package but is uninstallable due to version constraints, it's completely gone from testing. Bind maintainers: was this a deliberate change? (I can't seem to find any mention of it in the changelog) and if so what should reverse-dependencies do?
Bug#996207: marked as done (ruby-combustion: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require "bundler/setup")
Your message dated Thu, 04 Nov 2021 23:33:45 + with message-id and subject line Bug#996207: fixed in ruby-combustion 1.3.3-1 has caused the Debian Bug report #996207, regarding ruby-combustion: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require "bundler/setup" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-combustion Version: 1.3.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-combustion 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: require "bundler/setup" > > Bundler::GemNotFound: > Could not find rexml-3.2.3.1, racc-1.4.16 in any of the sources > # > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in > `setup' > # ./spec/spec_helper.rb:3:in `' > No examples found. > > > Finished in 0.4 seconds (files took 0.23196 seconds to load) > [31m0 examples, 0 failures, 1 error occurred outside of examples[0m > > /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: Note that rexml was removed from the standard library. ruby-rexml is already packaged in experimental, but you will need an explicit dependency on it. Not sure about racc though. Didn't find any reference to `racc` in the source. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-combustion/ruby-combustion_1.3.0-1+rebuild1633376946_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-combustion Source-Version: 1.3.3-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-combustion, 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-combustion 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: Thu, 04 Nov 2021 23:53:11 +0100 Source: ruby-combustion Architecture: source Version: 1.3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 996207 Changes: ruby-combustion (1.3.3-1) unstable; urgency=medium . * Team upload. * New upstream release. * d/control (Standards-Version): Bump to 4.6.0. (debian/control): Add ruby-rubocop-packaging added as dependency in 1.3.3. * d/copyright (Copyright): Update. * d/ruby-tests.rake: Require 'bundler/setup' (has been removed from spec_helper.rb) and delete Gemfile.lock (closes: #996207). * d/patches/remove_git_from_gemspec.patch: Remove unnecessary patch. * d/patches/series: Adjust. Checksums-Sha1: e3fb494943841b0076f75daf52271c68641eb70f 2198 ruby-combustion_1.3.3-1.dsc d1e1981b10da4a334a3bf725da42f0c08c545882 15954 ruby-combustion_1.3.3.orig.tar.gz 5a235314659ce4f14bcc7ff13d0bc38ff3f6e57a 4800 ruby-combustion_1.3.3-1.debian.tar.xz 723cf2ff6e5e852011e2165e2b20755de83f4394 11709 ruby-combustion_1.3.3-1_amd64.buildinfo Checksums-Sha256: fb4149a9e138c3ec7bdc293c627b0cdda3f41ce57419c2b078463d373a523172 2198 ruby-combustion_1.3.3-1.dsc d52f16570d1935bf408dda88b845035508de2b8174f31928828648f28fbaa058 15954 ruby-combustion_1.3.3.orig.tar.gz 612c25c1a395c7a769c1aefbe087d44fd6012bfbdd24adeeb928e1d49a1fe357 4800 ruby-combustion_1.3.3-1.debian.tar.xz d0231a6313f8a1d8208ac4889114c31d7fa033bd96897eee06db709489dbd996 11709 ruby-combustion_1.3.3-1_amd64.buildinfo Files: 269ff1b09bf15334d368ccc5609b8904 2198 ruby optional
Bug#998616: epson2: "setting focus failed" error on 1640SU after libsane1 upgrade
Package: libsane1 Version: 1.0.32-4 Severity: grave Justification: renders package unusable Dear Maintainer, I've upgraded libsane1 package from 1.0.31-4.1 to 1.0.32-4 and my Epson Perfection 164SU stopped working. I tried to debug the issue with: ~$ SANE_DEBUG_EPSON2=255 scanimage --device=epson2:libusb:006:011 --format=jpeg --output-file=./test.jpg and I discoverd this error: ... [00:15:42.111491] [epson2] setting focus failed scanimage: sane_start: Operation not supported ... I think that this error is related to this changelog of "SANE Backends 1.0.32": epson2: adds autofocus support for devices that support it (!531) Info: https://gitlab.com/sane-project/backends/-/merge_requests/531 https://gitlab.com/sane-project/backends/-/merge_requests/531/diffs Downgrading to libsane1 1.0.31-4.1 solve the issue. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (850, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsane1 depends on: ii acl2.3.1-1 ii adduser3.118 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libc6 2.32-4 ii libcairo2 1.16.0-5 ii libcurl3-gnutls7.74.0-1.3+b1 ii libgcc-s1 11.2.0-10 ii libglib2.0-0 2.70.0-3 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port12 2.5.27-1 ii libieee1284-3 0.2.11-14 ii libjpeg62-turbo1:2.0.6-4 ii libpng16-161.6.37-3 ii libpoppler-glib8 20.09.0-3.1 ii libsane-common 1.0.32-4 ii libsnmp40 5.9.1+dfsg-1 ii libstdc++6 11.2.0-10 ii libtiff5 4.3.0-2 ii libusb-1.0-0 2:1.0.24-3 ii libxml22.9.12+dfsg-5 ii udev 249.5-1 Versions of packages libsane1 recommends: ii ipp-usb 0.9.19-2 ii sane-utils 1.0.32-4 Versions of packages libsane1 suggests: ii avahi-daemon 0.8-5 pn hplip -- no debconf information
Processed: reassign 998422 to ruby-activesupport
Processing commands for cont...@bugs.debian.org: > reassign 998422 ruby-activesupport Bug #998422 [src:ruby-active-model-serializers] ArgumentError: wrong number of arguments (given 2, expected 3) caused by lib/active_support/cache.rb:330 Bug reassigned from package 'src:ruby-active-model-serializers' to 'ruby-activesupport'. No longer marked as found in versions ruby-active-model-serializers/0.10.10-1. Ignoring request to alter fixed versions of bug #998422 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 998422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996207 marked as pending in ruby-combustion
Processing control commands: > tag -1 pending Bug #996207 [src:ruby-combustion] ruby-combustion: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require "bundler/setup" Added tag(s) pending. -- 996207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996207: marked as pending in ruby-combustion
Control: tag -1 pending Hello, Bug #996207 in ruby-combustion 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-combustion/-/commit/e8bafbf418d2e853c3bad7419b5f6c78d9ce18b4 Add missing build-dep and handle Gemfile.lock and tests * d/control (debian/control): Add ruby-rubocop-packaging added as dependency in 1.3.3. * d/ruby-tests.rake: Require 'bundler/setup' (has been removed from spec_helper.rb) and delete Gemfile.lock (closes: #996207). (this message was generated automatically) -- Greetings https://bugs.debian.org/996207
Bug#996156: marked as done (ruby-ahoy-email: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Thu, 04 Nov 2021 23:04:11 + with message-id and subject line Bug#996156: fixed in ruby-ahoy-email 1.1.1-1 has caused the Debian Bug report #996156, regarding ruby-ahoy-email: 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.) -- 996156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-ahoy-email Version: 1.1.0-2 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-ahoy-email 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-ahoy-email/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/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\ \"ahoy_email\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-ahoy-email/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-ahoy-email/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/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/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:496:in > `materialize': Could not find racc-1.4.16 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:1:in `' > from /<>/test/click_test.rb:1:in `require_relative' > from /<>/test/click_test.rb:1: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) > > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-ahoy-email/ruby-ahoy-email_1.1.0-2+rebuild1633375169_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-ahoy-email Source-Version: 1.1.1-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-ahoy-email, which is due to be installed in the Debian FTP archive.
Processed: Bug#996156 marked as pending in ruby-ahoy-email
Processing control commands: > tag -1 pending Bug #996156 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Ignoring request to alter tags of bug #996156 to the same tags previously set -- 996156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996156: marked as pending in ruby-ahoy-email
Control: tag -1 pending Hello, Bug #996156 in ruby-ahoy-email 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-ahoy-email/-/commit/5cdb4ed2c179210fee30ed9dfa8ea002d8a7251a Add patch to remove Gemfile.lock before each test run * d/patches/996156-remove-gemfile-lock.patch: Add patch. - Remove created Gemfile.lock before each test run (closes: #996156). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996156
Bug#998477: marked as done (phyml: FTBFS: configure.ac:13: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Thu, 04 Nov 2021 22:48:43 + with message-id and subject line Bug#998477: fixed in phyml 3:3.3.20200621-3 has caused the Debian Bug report #998477, regarding phyml: FTBFS: configure.ac:13: 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.) -- 998477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phyml Version: 3:3.3.20200621-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_autoreconf --as-needed > configure.ac:13: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:5: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:13: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make[1]: *** [debian/rules:16: override_dh_autoreconf] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/phyml_3.3.20200621-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: phyml Source-Version: 3:3.3.20200621-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of phyml, 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. Étienne Mollier (supplier of updated phyml 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: Thu, 04 Nov 2021 23:15:13 +0100 Source: phyml Architecture: source Version: 3:3.3.20200621-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 998477 Changes: phyml (3:3.3.20200621-3) unstable; urgency=medium . * Team upload. * Add nodup-am-init-automake.patch (Closes: #998477) Checksums-Sha1: d95bc95d079112c99a73bfac469ab2b564a47f10 2098 phyml_3.3.20200621-3.dsc 7087d7dc57a3bdcd07f4ab27c83906893680f8b1 17624 phyml_3.3.20200621-3.debian.tar.xz 0d87e9e5f9490c57c8bb43fe108bc515765f1800 7671 phyml_3.3.20200621-3_amd64.buildinfo Checksums-Sha256: 5a5db1981e8026a6ce44f5c946c213888b3670bb3ec56cf1e3ba94860c1c84e3 2098 phyml_3.3.20200621-3.dsc 6663e40304dc1aaec0d2838642896960d3808086242571468bcb00993767d6a3 17624 phyml_3.3.20200621-3.debian.tar.xz 6d44ec875a62e24c486b80e67ae17262d8e82db29b064391876e98bcb94bf669 7671 phyml_3.3.20200621-3_amd64.buildinfo Files: cf530406ced29e8c40ff4bdda38038f4 2098 science optional phyml_3.3.20200621-3.dsc a4add55c923d7e36b74445341abbfe04 17624 science optional phyml_3.3.20200621-3.debian.tar.xz 0f43fe7395afb8650c3225ce4878acc4 7671 science optional phyml_3.3.20200621-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmGEXgAUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrv0Q/8DCiYJ/474O5QxMGKG8K/8ilvUXp3 dfXzDrCG/DVMZzQ22XEvN+kMZW0Ndxm6PjAC2mH9vxQjgpgh8nf/mKQ1TL/YDvHJ LenGLpwK2erdlCkSgvkn+19eig6W4T0hQADLTjmn1Nu73gCbgQpE3Rd/1uFa4Kf+ D2F5O1POZRddBTK1M/StvuMciCbXk0ADNu3XeZIuq3yJiy8JoCGwbpPYXEIw9DNk HksKOgnFKr1iKDaVxmo+6q5YujlhTVg61q6sr7T3WcHv+Qb+Q3ZhYsCz7HX60tsk KONEKkQOZ61D3kTcoNlmdc
Bug#996156: marked as pending in ruby-ahoy-email
Control: tag -1 pending Hello, Bug #996156 in ruby-ahoy-email 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-ahoy-email/-/commit/2667a25c5fd82e37c313428c32c0aa5844718fd5 Remove Gemfile.lock and files created by tests * d/clean: Remove Gemfile.lock (closes: #996156) and files created by tests. (this message was generated automatically) -- Greetings https://bugs.debian.org/996156
Processed: Bug#996156 marked as pending in ruby-ahoy-email
Processing control commands: > tag -1 pending Bug #996156 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998108: Tracking this bug down
Maybe I am wrong, but, for me, the simplest method to track this bug down is to check the changes between the two versions, 93.0 and 93.0-1+b1. Firefox code has not changed, only one or some libraries it depends on. I thought that the only change is in libvpx version, but, surprisingly, a previous comment mentions that rebuilding firefox with old vpx (libvpx6) still exhibits the bug. I think that libc6 is out of question, because the last package is 19 Sep, too old wrt this bug; the same for gcc-11, the last package being on 21 Oct. Doesn't this (checking the changes) sound like a good approach to find the cause of the problem?
Bug#998108: Additional information: tab freezes first, then browser
Maybe i missed a comment but can someone give a try with the upstream binary? To see if it happens for you too there? Merci Sylvestre Le jeu. 4 nov. 2021 à 23:15, Josh Triplett a écrit : > Some additional information that might help track this down: several > times, I've observed one tab freezing, but the browser itself is still > responsive for a *short* time. I can open a new tab, and close it again, > and the previous tab then renders as a busy symbol. > > I'm wondering if one of the tab processes or helper processes dies, and > then that grinds the browser to a halt but not instantly. > >
Bug#998411: Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
I have fixed gmsh. It will appear in NEW soon. Regards Anton
Bug#996515: marked as done (ruby-tilt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: TypeError: no implicit conversion of Hash into String)
Your message dated Thu, 04 Nov 2021 22:19:25 + with message-id and subject line Bug#996515: fixed in ruby-tilt 2.0.10-2 has caused the Debian Bug report #996515, regarding ruby-tilt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: TypeError: no implicit conversion of Hash into String to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-tilt Version: 2.0.10-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-tilt 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): > TypeError: no implicit conversion of Hash into String > /usr/lib/ruby/3.0.0/csv.rb:1273:in `initialize' > /usr/lib/ruby/3.0.0/csv.rb:1273:in `new' > /usr/lib/ruby/3.0.0/csv.rb:1273:in `generate' > (__TEMPLATE__):in `__tilt_400' > > /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in > `call' > > /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in > `evaluate' > > /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:109:in > `render' > /<>/test/tilt_csv_test.rb:32:in `block in > ' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 237 runs, 433 assertions, 1 failures, 6 errors, 0 skips > 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/tilt_asciidoctor_test.rb" "test/tilt_blueclothtemplate_test.rb" > "test/tilt_buildertemplate_test.rb" "test/tilt_cache_test.rb" > "test/tilt_coffeescripttemplate_test.rb" > "test/tilt_commonmarkertemplate_test.rb" "test/tilt_compilesite_test.rb" > "test/tilt_creoletemplate_test.rb" "test/tilt_csv_test.rb" > "test/tilt_erbtemplate_test.rb" "test/tilt_erubistemplate_test.rb" > "test/tilt_erubitemplate_test.rb" "test/tilt_etannitemplate_test.rb" > "test/tilt_hamltemplate_test.rb" "test/tilt_kramdown_test.rb" > "test/tilt_lesstemplate_test.rb" "test/tilt_liquidtemplate_test.rb" > "test/tilt_livescripttemplate_test.rb" "test/tilt_mapping_test.rb" > "test/tilt_markaby_test.rb" "test/tilt_markdown_test.rb" > "test/tilt_marukutemplate_test.rb" "test/tilt_metadata_test.rb" > "test/tilt_nokogiritemplate_test.rb" "test/tilt_pandoctemplate_test.rb" > "test/tilt_prawntemplate_test.rb" "test/tilt_radiustemplate_test.rb" > "test/tilt_rdiscounttemplate_test.rb" "test/tilt_rdoctemplate_test.rb" > "test/tilt_redcarpettemplate_test.rb" "test/tilt_redclothtemplate_test.rb" > "test/tilt_rstpandoctemplate_test.rb" "test/tilt_sasstemplate_test.rb" > "test/tilt_sigil_test.rb" "test/tilt_stringtemplate_test.rb" > "test/tilt_template_test.rb" "test/tilt_test.rb" > "test/tilt_typescript_test.rb" "test/tilt_wikiclothtemplate_test.rb" > "test/tilt_yajltemplate_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test
Processed: Bug#998477 marked as pending in phyml
Processing control commands: > tag -1 pending Bug #998477 [src:phyml] phyml: FTBFS: configure.ac:13: error: AM_INIT_AUTOMAKE expanded multiple times Added tag(s) pending. -- 998477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998477: marked as pending in phyml
Control: tag -1 pending Hello, Bug #998477 in phyml 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/phyml/-/commit/fcef2527782eb00dc67aa5f148bb62d7f2a435e1 Add nodup-am-init-automake.patch Closes: #998477 (this message was generated automatically) -- Greetings https://bugs.debian.org/998477
Processed: meaningful nipype ftbfs bug title
Processing commands for cont...@bugs.debian.org: > retitle 997126 nipype: ftbfs: nipype.algorithms.tests.test_CompCor failure Bug #997126 [src:nipype] nipype: FTBFS: XXX Changed Bug title to 'nipype: ftbfs: nipype.algorithms.tests.test_CompCor failure' from 'nipype: FTBFS: XXX'. > thank you Stopping processing here. Please contact me if you need assistance. -- 997126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998108: Additional information: tab freezes first, then browser
Some additional information that might help track this down: several times, I've observed one tab freezing, but the browser itself is still responsive for a *short* time. I can open a new tab, and close it again, and the previous tab then renders as a busy symbol. I'm wondering if one of the tab processes or helper processes dies, and then that grinds the browser to a halt but not instantly.
Bug#998539: marked as done (rust-selinux-sys: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev)
Your message dated Thu, 4 Nov 2021 22:04:14 + with message-id and subject line re: rust-selinux-sys: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev has caused the Debian Bug report #998539, regarding rust-selinux-sys: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev 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.) -- 998539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-selinux-sys Version: 0.5.1-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): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 24), cargo, rustc, > libstd-rust-dev, librust-bindgen-0.59+default-dev, librust-cc-1+default-dev, > librust-dunce-1+default-dev, librust-walkdir-2+default-dev (>= 2.3-~~), > libselinux1-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 24), cargo, rustc, > libstd-rust-dev, librust-bindgen-0.59+default-dev, librust-cc-1+default-dev, > librust-dunce-1+default-dev, librust-walkdir-2+default-dev (>= 2.3-~~), > libselinux1-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [463 B] > Get:5 copy:/<>/apt_archive ./ Packages [532 B] > Fetched 1952 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-bindgen+logging-dev : Depends: librust-env-logger-0.7+default-dev > but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/rust-selinux-sys_0.5.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This was fixed by the upload of rust-bindgen 0.59.1-1.1--- End Message ---
Bug#998598: marked as done (distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2)
Your message dated Thu, 04 Nov 2021 22:04:35 + with message-id and subject line Bug#998598: fixed in distro-info 1.1 has caused the Debian Bug report #998598, regarding distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distro-info Version: 1.0 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 '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > testAll > testDevel > testOldstable > py3versions: no X-Python3-Version in control file, using supported versions > cd python && python3.9 setup.py test > testStable > 1..35 > testSupported > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > testLTS > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testELTS > testUnsupported > testTesting > testFullname > testRelease > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > testSeries > running build_ext > testCombinedShortform > testReleaseDate > test_pylint (distro_info_test.test_pylint.PylintTestCase) > Test: Run pylint on Python source code ... Running following command: > /usr/bin/python3.9 -m pylint > --rcfile=/<>/python/distro_info_test/pylint.conf -- > debian-distro-info ubuntu-distro-info distro_info.py setup.py > testHelp > testExactlyOne > testUnrecognizedOption > testUnrecognizedArguments > testMissingArgumentAlias > testMissingArgumentDate > testMissingArgumentSeries > testInvalidAlias > testInvalidDate > testInvalidSeries > testMultipleAlias > testMultipleDates > testMultipleSeries > testUnknownSeries > testDays > > Ran 30 tests. > > OK > ./test-ubuntu-distro-info > testAll > testDevel > testLatest > testLTS > testStable > testSupported > testUnsupported > testFullname > testRelease > testSeries > testCombinedShortform > testReleaseDate > testHelp > testExactlyOne > testUnrecognizedOption > testUnrecognizedArguments > testMissingArgumentDate > testMissingArgumentSeries > testDistributionDataOutdated > testInvalidDate > testInvalidSeries > testMultipleDates > testMultipleSeries > testUnknownSeries > testDays > > Ran 25 tests. > > OK > FAIL > test_all (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: List all known Debian distributions. ... ok > test_codename (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Codename decoding ... ok > test_codename_result > (distro_info_test.test_distro_info.DebianDistroInfoTestCa
Bug#998599: marked as done (jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5.)
Your message dated Thu, 04 Nov 2021 22:03:39 + with message-id and subject line Bug#998536: fixed in commons-io 2.11.0-2 has caused the Debian Bug report #998536, regarding jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5. 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.) -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jengelman-shadow Version: 4.0.3-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_build -- jar -x test > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=jengelman-shadow -Dfile.encoding=UTF-8 > --parallel --max-workers=4 jar -x test > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@162be91c > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@162be91c > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Generating JAR file: > /<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar > Generating JAR file 'gradle-api-4.4.1.jar' > Keep-alive timer started > Adding Debian repository to project 'buildSrc' > Parallel execution is an incubating feature. > Evaluating project ':buildSrc' using build file > '/<>/buildSrc/build.gradle'. > Compiling build file '/<>/buildSrc/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/buildSrc/build.gradle' using > BuildScriptTransformer. > Adding Maven pom generation to project 'buildSrc' > Linking the generated javadoc to the system JDK API documentation > Creating new cache for metadata-2.36/module-metadata, path > /<>/.gradle/caches/modules-2/metadata-2.36/module-metadata.bin, > access org.gradle.cache.internal.DefaultCacheAccess@57515944 > Loading the Maven rules... > Replacing org.codehaus.groovy:groovy-backports-compat23:jar:2.4.15 -> > org.codehaus.groovy:groovy:jar:debian > Replacing org.jdom:jdom2:jar:2.0.6 -> org.jdom:jdom2:jar:debian > Replacing org.ow2.asm:asm:jar:7.0-beta -> > org.ow2.asm:asm-all:jar:debian > Ignoring org.ow2.asm:asm-commons:jar:7.0-beta > Replacing commons-io:commons-io:jar:2.5 -> > commons-io:commons-io:jar:debian > Passing through org.apache.commons:commons-parent:jar:debian > Passing through org.apache:apache:jar:debian > Passing through org.junit:junit-bom:jar:debian > Replacing org.apache.ant:ant:jar:1.9.7 -> > org.apache.ant:ant:jar:debian > Passing through org.apache.ant:ant-parent:jar:debian
Bug#998606: marked as done (gradle: FTBFS: Could not resolve commons-io:commons-io:debian.)
Your message dated Thu, 04 Nov 2021 22:03:39 + with message-id and subject line Bug#998536: fixed in commons-io 2.11.0-2 has caused the Debian Bug report #998536, regarding gradle: FTBFS: Could not resolve commons-io:commons-io:debian. 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.) -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gradle Version: 4.4.1-13 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 '/<>' > sed '/@GENERATED@/,$d' debian/gradle.pod.in > debian/gradle.pod > # process items: `-?`, `-h`, `--help`:: → =item `-?`, `-h`, `--help` > # process bold: `-?` → B<-?> > # remove empty line markers > # drop text from links: https://gradle.com/build-scans[...] > # drop underscores from documentation links > # replace documentation links by UPPERCASE LABELS > # ... but not those where the link is in a middle of a sentence > # ... since otherwise it breaks the sentence structure > # ... so just make it *bold* instead > # move parethesed option "(comments)" outside of the bold parts > # cut off everything after and including the [[daemon_cli]] section > # cut off the introduction > sed \ > -e 's/\(.*\):: *$/\n=item \1\n/' \ > -e 's/`\([^`]*\)`/B<\1>/g' \ > -e 's/^+$//g' \ > -e 's/\(https:[^[]*\)[[][^]]*\]/L<\1>/g' \ > -e '/<]*>>/y/_/ /' \ > -e 's/\([Tt]he\) <]*\)>>/\1 documentation section > B<\U\2\E>/g' \ > -e 's/<]*\)>>/the documentation section B<\U\1\E>/g' \ > -e '/<<[^>]*>>/y/_/ /' \ > -e 's/<<.[^,]*,\([^>]*\)>>/B<\1>/g' \ > -e 's/\([Tt]he\) <<\([^>]*\)>>/\1 documentation section B<\U\2\E>/g' \ > -e 's/<<\([^>]*\)>>/the documentation section B<\U\1\E>/g' \ > -e 's/ (\([^)]*\))>/> (\1)/g' \ > -e '/^\[\[.*]]$/d' \ > -e 's/GRADLE OPTS/GRADLE_OPTS/g' \ > -e 's/^=== \(.*\)$/=back\n\n=head1 \U\1\n\n/g' \ > -e '0,/The command-line options available/d' \ > subprojects/docs/src/docs/userguide/commandLine.adoc >> > debian/gradle.pod > sed '0,/@GENERATED@/d' debian/gradle.pod.in >> debian/gradle.pod > touch -d@1613028759 debian/gradle.pod > pod2man --errors=stderr --utf8 -r "Gradle 4.4.1" -c "Gradle Command Line > Manual" debian/gradle.pod > debian/gradle.1 > debian/gradle.pod around line 196: '=item' outside of any '=over' > debian/gradle.pod around line 229: '=item' outside of any '=over' > debian/gradle.pod around line 244: '=item' outside of any '=over' > Wide character in printf at /usr/share/perl/5.32/Pod/Simple.pm line 573. > debian/gradle.pod around line 250: Non-ASCII character seen before =encoding > in '“B”'. Assuming UTF-8 > rm -f gradle.properties # Some properties here breaks the latest JVM > mkdir --parents buildSrc/src/main/java/tmp # Symlinks are for building Gradle > 4 using Gradle 3 > ln --symbolic --force --target-directory=buildSrc/src/main/java/tmp/ > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/Directory.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/DirectoryProperty.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/FileSystemLocation.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/RegularFile.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/RegularFileProperty.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/NonNullApi.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/provider/Property.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/provider/Provider.java > > ../../../../../subprojects/core/src/main/java/org/gradle/api/internal/file/TaskFileVarFactory.java > gradle assemble startScripts --project-prop finalRelease=true --offline > --stacktrace --gradle-user-home debian/.gradlehome --no-daemon > -Dgradle-debi
Bug#998604: marked as done (wala: FTBFS: Could not resolve commons-io:commons-io:2.4.)
Your message dated Thu, 04 Nov 2021 22:03:39 + with message-id and subject line Bug#998536: fixed in commons-io 2.11.0-2 has caused the Debian Bug report #998536, regarding wala: FTBFS: Could not resolve commons-io:commons-io:2.4. 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.) -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wala Version: 1.5.2-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 '/<>' > dh_auto_build > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=wala -Dfile.encoding=UTF-8 --parallel > --max-workers=4 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Generating JAR file: > /<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar > Generating JAR file 'gradle-api-4.4.1.jar' > Keep-alive timer started > Adding Debian repository to project 'buildSrc' > Parallel execution is an incubating feature. > Evaluating project ':buildSrc' using build file > '/<>/buildSrc/build.gradle'. > Adding Maven pom generation to project 'buildSrc' > Linking the generated javadoc to the system JDK API documentation > Selected primary task 'clean' from project : > Selected primary task 'build' from project : > Creating new cache for annotation-processors, path > /<>/buildSrc/.gradle/4.4.1/fileContent/annotation-processors.bin, > access org.gradle.cache.internal.DefaultCacheAccess@2047adea > Creating new cache for resourceHashesCache, path > /<>/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > Creating new cache for taskHistory, path > /<>/buildSrc/.gradle/4.4.1/taskHistory/taskHistory.bin, access > org.gradle.cache.internal.DefaultCacheAccess@300aa927 > Creating new cache for outputFiles, path > /<>/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin, access > org.gradle.cache.internal.DefaultCacheAccess@6774f264 > Build cache is an incubating feature. > Using local directory build cache for build ':buildSrc' (location = > /<>/.gradle/caches/build-cache-1, targetSize = 5 GB). > :clean (Thread[main,5,main]) started. > :buildSrc:clean > Putting task artifact state for task ':buildSrc:clean' into context took > 0.001 secs. > Caching disabled for task ':buildSrc:clean': Caching has not been enabled for > the task > Up-to-dat
Bug#998549: marked as done (grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duse
Your message dated Thu, 04 Nov 2021 22:03:39 + with message-id and subject line Bug#998536: fixed in commons-io 2.11.0-2 has caused the Debian Bug report #998536, regarding grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel --max-workers=4 test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grengine Version: 3.0.0+dfsg-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): > debian/rules binary > dh binary --buildsystem=gradle --with javahelper,maven_repo_helper >dh_update_autotools_config -O--buildsystem=gradle >dh_autoreconf -O--buildsystem=gradle >dh_auto_configure -O--buildsystem=gradle >jh_linkjars -O--buildsystem=gradle >dh_auto_build -O--buildsystem=gradle > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel > --max-workers=4 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file not found (/<>/settings.gradle) > Root project name not defined in settings.gradle, defaulting to > 'grengine' instead of the name of the root directory 'grengine-3.0.0+dfsg' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'grengine'] > Keep-alive timer started > Adding Debian repository to project 'grengine' > Parallel execution is an incubating feature. > Evaluating root project 'grengine' using build file > '/<>/build.gradle'. > Compiling build file '/<>/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/build.gradle' using > BuildScriptTransformer. > Adding Maven pom generation to project 'grengine' > Linking the generated javadoc to the system JDK API documentation > All projects evaluated. > Selected primary task 'jar' from project : > Creating new cache for annotation-processors, path > /<>/.gradle/4.4.1/fileContent/annotation-processors.bin, access > org.gradle.cache.internal.DefaultCacheAccess@6dcee890 > Tasks to be executed: [task ':compileJava', task ':processR
Bug#998536: marked as done (commons-io: Missing dependency on junit5 for junit-bom)
Your message dated Thu, 04 Nov 2021 22:03:39 + with message-id and subject line Bug#998536: fixed in commons-io 2.11.0-2 has caused the Debian Bug report #998536, regarding commons-io: Missing dependency on junit5 for junit-bom 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.) -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: osmosis Version: 0.48.3-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 '/<>' > dh_auto_build -- --project-prop osmosisBuildType=RELEASE assemble > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=osmosis -Dfile.encoding=UTF-8 --parallel > --max-workers=4 --project-prop osmosisBuildType=RELEASE assemble > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Compiling settings file '/<>/settings.gradle' using > SubsetScriptTransformer. > Compiling settings file '/<>/settings.gradle' using > BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file found (/<>/settings.gradle), but > rootProject.name isn't defined > Root project name not defined in settings.gradle, defaulting to > 'osmosis' instead of the name of the root directory 'osmosis-0.48.3' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'osmosis', project ':build-support', project > ':osmosis-apidb', project ':osmosis-areafilter', project ':osmosis-core', > project ':osmosis-dataset', project ':osmosis-extract', project > ':osmosis-hstore-jdbc', project ':osmosis-osm-binary', project > ':osmosis-pbf', project ':osmosis-pbf2', project ':osmosis-pgsimple', project > ':osmosis-pgsnapshot', project ':osmosis-replication', project > ':osmosis-set', project ':osmosis-tagfilter', project > ':osmosis-tagtransform', project ':osmosis-testutil', project ':osmosis-xml', > project ':package'] > Keep-alive timer started > Adding Debian repository to project 'osmosis' > Adding Debian repository to project 'build-support' > Adding Debian repository to project 'osmosis-apidb' > Adding Debian repository to project 'osmosis-areafilter' > Adding Debian repository to project 'osmosis-core' > Adding Debian repository to project 'osmosis-dataset' > Adding Debian repository to project 'osmosis-extract' > Adding Debian re
Processed: nipype test issue reported upstream
Processing control commands: > tags -1 confirmed Bug #997126 [src:nipype] nipype: FTBFS: XXX Added tag(s) confirmed. > forwarded -1 https://github.com/nipy/nipype/issues/3382 Bug #997126 [src:nipype] nipype: FTBFS: XXX Set Bug forwarded-to-address to 'https://github.com/nipy/nipype/issues/3382'. -- 997126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 996621
Processing commands for cont...@bugs.debian.org:
> close 996621 2.0.7+dfsg-2
Bug #996621 [src:ruby-enumerable-statistics] ruby-enumerable-statistics: FTBFS
on i386: ERROR: Test "ruby2.7" failed: Failure/Error: it { is_expected.to
eq(x) }
Marked as fixed in versions ruby-enumerable-statistics/2.0.7+dfsg-2.
Bug #996621 [src:ruby-enumerable-statistics] ruby-enumerable-statistics: FTBFS
on i386: ERROR: Test "ruby2.7" failed: Failure/Error: it { is_expected.to
eq(x) }
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996621: closing 996621
close 996621 2.0.7+dfsg-2 thanks
Processed: Bug#996515 marked as pending in ruby-tilt
Processing control commands: > tag -1 pending Bug #996515 [src:ruby-tilt] ruby-tilt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: TypeError: no implicit conversion of Hash into String Added tag(s) pending. -- 996515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996515: marked as pending in ruby-tilt
Control: tag -1 pending Hello, Bug #996515 in ruby-tilt 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-tilt/-/commit/f521eb0e0efd8d08487a65b4dd95ca48e7985aba Add patch to support ruby3.0 (Closes: #996515) (this message was generated automatically) -- Greetings https://bugs.debian.org/996515
Bug#998538: marked as done (rust-onig: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev)
Your message dated Thu, 4 Nov 2021 21:40:57 + with message-id <0c0ae837-8c70-a327-8ae5-c6e99af53...@p10link.net> and subject line re: rust-onig: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev has caused the Debian Bug report #998538, regarding rust-onig: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev 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.) -- 998538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-onig Version: 6.1.0-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): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-bitflags-1+default-dev, > librust-lazy-static-1+default-dev (>= 1.2-~~), librust-libc-0.2+default-dev, > librust-onig-sys-69-dev (>= 69.5-~~), build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-bitflags-1+default-dev, > librust-lazy-static-1+default-dev (>= 1.2-~~), librust-libc-0.2+default-dev, > librust-onig-sys-69-dev (>= 69.5-~~), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [466 B] > Get:5 copy:/<>/apt_archive ./ Packages [536 B] > Fetched 1959 B in 0s (196 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-bindgen+logging-dev : Depends: librust-env-logger-0.7+default-dev > but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/rust-onig_6.1.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 --- This was fixed by the upload of rust-bindgen 0.59.1-1.1--- End Message ---
Bug#998606: marked as pending in commons-io
Control: tag -1 pending Hello, Bug #998606 in commons-io 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/java-team/commons-io/-/commit/07e727289c916a9e0aa51877f59542367780ad54 Add remove-junit-bom-dependency.patch and do not depend on junit5-bom. Closes: #998606 (this message was generated automatically) -- Greetings https://bugs.debian.org/998606
Processed: Bug#998606 marked as pending in commons-io
Processing control commands: > tag -1 pending Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Bug #998536 [src:commons-io] commons-io: Missing dependency on junit5 for junit-bom Bug #998549 [src:commons-io] grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel --max-workers=4 test returned exit code 1 Bug #998599 [src:commons-io] jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5. Bug #998604 [src:commons-io] wala: FTBFS: Could not resolve commons-io:commons-io:2.4. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 998549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998549 998599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998599 998604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998604 998606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998411: Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
On 2021-11-04 21:41, Sebastian Ramacher wrote: On 2021-11-03 22:33:01 +0100, Drew Parsons wrote: ... The problem that hypre 2.18.1-1 (un-versioned libhypre) intended to solve is that hypre is ABI-ignorant (https://github.com/hypre-space/hypre/issues/56), so each point patch release would have to be a new binary package, and the upstream release rate is faster than the average NEW queue processing rate (the new package for the current transition would be libhypre2.22.1, and already libhypre2.23.0 is released upstream). (So why is this packaged as shared library?) A reasonable question to ask. For my part, it was already being packaged as a shared library when I started working on it, so I just continued it so. I could imagine a clash of hypre symbols if a client programs links against both petsc and sundials (which both use hypre), and uses hypre directly. I guess the symbol table must guard against clashes like that. ... Is it best to revert back to strict Policy 8.1 compliance, which will slow down hypre patch release updates? Yes. Having to wait for binNEW to being processed is not an excuse to violate a must section of the policy. Processing of packages in NEW can take some time. I'm also waiting on some of them for months. The solution to that is however not to abondon well established practices for shared libraries. The problems that are caused by that can be seen with libhypre and its reverse dependencies. Fair enough. I'll make the change, either to libhypre2.22.2 or to libhypre-static. Drew
Bug#998550: marked as done (rust-onig-sys: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev)
Your message dated Thu, 4 Nov 2021 21:37:41 + with message-id <8fd7e7b7-02a2-69a9-03d4-b76f979ff...@p10link.net> and subject line re: rust-onig-sys: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev has caused the Debian Bug report #998550, regarding rust-onig-sys: FTBFS: build-dependency not installable: librust-env-logger-0.7+default-dev 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.) -- 998550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-onig-sys Version: 69.5.1-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): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 24), cargo, rustc, > libstd-rust-dev, librust-bindgen-0.59+default-dev | > librust-bindgen-0.58+default-dev | librust-bindgen-0.57+default-dev | > librust-bindgen-0.56+default-dev | librust-bindgen-0.55+default-dev, > librust-cc-1+default-dev, librust-pkg-config-0.3+default-dev (>= 0.3.16-~~), > build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 24), cargo, rustc, > libstd-rust-dev, librust-bindgen-0.59+default-dev, librust-cc-1+default-dev, > librust-pkg-config-0.3+default-dev (>= 0.3.16-~~), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [960 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [474 B] > Get:5 copy:/<>/apt_archive ./ Packages [525 B] > Fetched 1959 B in 0s (192 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-bindgen+logging-dev : Depends: librust-env-logger-0.7+default-dev > but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/rust-onig-sys_69.5.1-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This was fixed by the upload of rust-bindgen 0.59.1-1.1--- End Message ---
Bug#998605: krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error
Hi, On Thu, Nov 04, 2021 at 08:49:47PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: > > syntax error It looks like a result of recent pyqt5 update — it broke compatibility with SIP 4. This issue was discussed on PyQt mailing list yesterday [1], but the upstream developer said he is not going to rush to fix this. I don't know what this means, but if there is a fix at least in upstream Vcs or snapshots, I will cherry-pick it. [1]: https://www.riverbankcomputing.com/pipermail/pyqt/2021-November/044346.html -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Bug#998598 marked as pending in distro-info
Processing control commands: > tag -1 pending Bug #998598 [src:distro-info] distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Ignoring request to alter tags of bug #998598 to the same tags previously set -- 998598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998598: marked as pending in distro-info
Control: tag -1 pending Hello, Bug #998598 in distro-info 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/distro-info/-/commit/264f057aef043afee194bcae281539234f8f92a5 Update Python module to satisfy pylint 2.11 (Closes: #998598) (this message was generated automatically) -- Greetings https://bugs.debian.org/998598
Bug#997655: marked as done (diodon: FTBFS: autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?)
Your message dated Thu, 04 Nov 2021 21:18:45 + with message-id and subject line Bug#997655: fixed in diodon 1.11.2-1 has caused the Debian Bug report #997655, regarding diodon: FTBFS: autoreconf: error: configure.in: AC_INIT not found; not an autoconf script? 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.) -- 997655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: diodon Version: 1.11.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=meson --with gir >dh_update_autotools_config -O--buildsystem=meson >dh_autoreconf -O--buildsystem=meson > autoreconf: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > autoreconf: error: configure.in: AC_INIT not found; not an autoconf script? > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:8: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/diodon_1.11.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: diodon Source-Version: 1.11.2-1 Done: Oliver Sauder We believe that the bug you reported is fixed in the latest version of diodon, 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. Oliver Sauder (supplier of updated diodon 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: Thu, 04 Nov 2021 22:46:18 +0400 Source: diodon Architecture: source Version: 1.11.2-1 Distribution: unstable Urgency: medium Maintainer: Oliver Sauder Changed-By: Oliver Sauder Closes: 997655 Changes: diodon (1.11.2-1) unstable; urgency=medium . * New upstream release. * Fix custom-library-search-path * Removed invalid configure.in file (Closes: #997655) * Bump Standard-Version to 4.6.0 Checksums-Sha1: a2a6b5f6a593941c801f1904aaada134d0c662c2 2521 diodon_1.11.2-1.dsc ae1efdf694ef4707bb4eccabf9f649a251506a66 92260 diodon_1.11.2.orig.tar.xz 723939448bad1d1fa2675475c19c810862454ea8 833 diodon_1.11.2.orig.tar.xz.asc 5d42dd4a49f23e3ad96257423a82b920cd3aaa1c 6832 diodon_1.11.2-1.debian.tar.xz 98cb43bc8db1b432649f20ae225ed7d729f1c05f 14689 diodon_1.11.2-1_source.buildinfo Checksums-Sha256: bb341a4f24f4ec5ff5113c756b1c6c9d671443329257988145d62c5fe9d3b140 2521 diodon_1.11.2-1.dsc 0e9c0e9831a448dfa3e7ed10719359877ad2041a2418c0b2840aab406dc0136e 92260 diodon_1.11.2.orig.tar.xz 132cbbe2caf2e61e06a7dd8a9601d8237c74ed07cda19c7c2f5e45af6a29b9fb 833 diodon_1.11.2.orig.tar.xz.asc 9b19950eb5e5966d82af30dfb4440aa33e090ef9e55599fb1d313dc274764ffe 6832 diodon_1.11.2-1.debian.tar.xz 26982d1e6a501d9c51b097dc58217627eb85e7d6ab400f904ba375573064ad91 14689 diodon_1.11.2-1_source.buildinfo Files: 24c983e4841d8d0a523515a396b9f3f8 2521 utils optional diodon_1.11.2-1.dsc 5b7e8f676cae8e49383fa3a903e97426 92260 utils optional diodon_1.11.2.orig.tar.xz 6bba871059b30c6becb09a2114477367 833 utils optional diodon_1.11.2.orig.tar.xz.asc b49a7b75aad47ab597634be306011d81 6832 utils optional diodon_1.11.2-1.debian.tar.xz 27b1b7adbd84214a4c6bdd781c586a59 14689 utils optional diodon_1.11.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmGESngACgkQweDZLphv fH7tGA/+LWc5giASAWBgux3DK/Ad0+8IV7eqOq2u7D6Sjy3jQICxzN2y4zCQ85G+ fY0l6QF6thxcmahhnYlRuZjAy4J7kDnuswYPeKF5ANtzXTL8o5uWDq6y18fUD7jy
Bug#998529: rust-cargo: FTBFS: unsatisfiable build-dependencies: librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), librust-im-rc-15+default-dev
The packages that will fix this (rust-cargo-util and rust-im-rc) are in NEW.
Processed: Bug#998598 marked as pending in distro-info
Processing control commands: > tag -1 pending Bug #998598 [src:distro-info] distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Added tag(s) pending. -- 998598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998598: marked as pending in distro-info
Control: tag -1 pending Hello, Bug #998598 in distro-info 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/distro-info/-/commit/26a4819ae429e44b61d8c75b46110d9c14e65694 Update Python module to satisfy pylint 2.11 (Closes: #998598) (this message was generated automatically) -- Greetings https://bugs.debian.org/998598
Processed: Merge commons-io bugs
Processing commands for cont...@bugs.debian.org: > forcemerge 998549 998536 Bug #998549 [src:commons-io] grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel --max-workers=4 test returned exit code 1 Bug #998599 [src:commons-io] jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5. Bug #998604 [src:commons-io] wala: FTBFS: Could not resolve commons-io:commons-io:2.4. Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Bug #998549 [src:commons-io] grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel --max-workers=4 test returned exit code 1 Marked as found in versions commons-io/2.11.0-1. Marked as found in versions commons-io/2.11.0-1. Marked as found in versions commons-io/2.11.0-1. Marked as found in versions commons-io/2.11.0-1. Bug #998536 [src:commons-io] commons-io: Missing dependency on junit5 for junit-bom Removed indication that 998536 affects src:osmosis Bug #998599 [src:commons-io] jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5. Bug #998604 [src:commons-io] wala: FTBFS: Could not resolve commons-io:commons-io:2.4. Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Merged 998536 998549 998599 998604 998606 > thanks Stopping processing here. Please contact me if you need assistance. -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 998549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998549 998599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998599 998604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998604 998606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998520: rust-bstr: FTBFS: unsatisfiable build-dependencies (purely virtual?): librust-memchr-2+std-dev (>= 2.4.0-~~), librust-memchr-2-dev (>= 2.4.0-~~)
The new version of rust-memchr which will fix this is in NEW.
Bug#998568: marked as done (libtime-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Thu, 04 Nov 2021 21:04:04 + with message-id and subject line Bug#998568: fixed in libtime-tiny-perl 1.08-2 has caused the Debian Bug report #998568, regarding libtime-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtime-tiny-perl Version: 1.08-1.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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > # > # Versions for all modules listed in MYMETA.json (including optional ones): > # > # === Configure Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker 6.17 7.44 > # > # === Build Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # > # === Test Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # File::Spec any 3.78 > # Test::More any 1.302175 > # > # === Test Recommends === > # > # Module Want Have > # -- > # CPAN::Meta 2.120900 2.150010 > # > # === Runtime Requires === > # > # Module Want Have > # > # Carp any 1.50 > # overload any 1.31 > # strictany 1.11 > # warnings any 1.47 > # > t/00-report-prereqs.t .. > 1..1 > ok 1 > ok > > # Failed test '->locale ok' > # at t/02_main.t line 67. > # got: 'en-US' > # expected: 'en-US-POSIX' > # Looks like you failed 1 test of 15. > t/02_main.t > 1..15 > ok 1 - An object of class 'Time::Tiny' isa 'Time::Tiny' > ok 2 - ->hour ok > ok 3 - ->minute ok > ok 4 - ->second ok > ok 5 - ->as_string ok > ok 6 - Stringification ok > ok 7 - ->from_string ok > ok 8 - An object of class 'Time::Tiny' isa 'Time::Tiny' > ok 9 - An object of class 'Time::Tiny' isa 'Time::Tiny' > ok 10 - An object of class 'DateTime' isa 'DateTime' > not ok 11 - ->locale ok > ok 12 - ->timezone ok > ok 13 - ->year matches > ok 14 - ->month matches > ok 15 - ->day matches > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/15 subtests > > Test Summary Report > --- > t/02_main.t (Wstat: 256 Tests: 15 Failed: 1) > Failed test: 11 > Non-zero exit status: 1 > Files=2, Tests=16, 0 wallclock secs ( 0.01 usr 0.01 sys + 0.29 cusr 0.02 > csys = 0.33 CPU) > Result: FAIL > Failed 1/2 test programs. 1/16 subtests failed. > make[1]: *** [Makefile:844: test_dynamic] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2021/11/04/libtime-tiny-perl_1.08-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libtime-tiny-perl Source-Version: 1.08-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libtime-tiny-perl, 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 a
Bug#998560: marked as done (libdate-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Thu, 04 Nov 2021 21:03:59 + with message-id and subject line Bug#998560: fixed in libdate-tiny-perl 1.07-2 has caused the Debian Bug report #998560, regarding libdate-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdate-tiny-perl Version: 1.07-1.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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > # > # Versions for all modules listed in MYMETA.json (including optional ones): > # > # === Configure Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker 6.17 7.44 > # > # === Build Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # > # === Test Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # File::Spec any 3.78 > # Test::More any 1.302175 > # > # === Test Recommends === > # > # Module Want Have > # -- > # CPAN::Meta 2.120900 2.150010 > # > # === Runtime Requires === > # > # Module Want Have > # > # Carp any 1.50 > # overload any 1.31 > # strictany 1.11 > # warnings any 1.47 > # > t/00-report-prereqs.t .. > 1..1 > ok 1 > ok > > # Failed test '->locale ok' > # at t/02_main.t line 65. > # got: 'en-US' > # expected: 'en-US-POSIX' > # Looks like you failed 1 test of 19. > t/02_main.t > 1..19 > ok 1 - An object of class 'Date::Tiny' isa 'Date::Tiny' > ok 2 - ->year ok > ok 3 - ->month ok > ok 4 - ->day ok > ok 5 - An object of class 'Date::Tiny' isa 'Date::Tiny' > ok 6 - ->year ok > ok 7 - ->month ok > ok 8 - ->day ok > ok 9 - An object of class 'Date::Tiny' isa 'Date::Tiny' > not ok 10 - ->locale ok > ok 11 - An object of class 'DateTime' isa 'DateTime' > ok 12 - ->timezone ok > ok 13 - ->year matches > ok 14 - ->month matches > ok 15 - ->day matches > ok 16 - An object of class 'Date::Tiny' isa 'Date::Tiny' > ok 17 - ->year ok > ok 18 - ->month ok > ok 19 - ->day ok > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/19 subtests > > Test Summary Report > --- > t/02_main.t (Wstat: 256 Tests: 19 Failed: 1) > Failed test: 10 > Non-zero exit status: 1 > Files=2, Tests=20, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.29 cusr 0.02 > csys = 0.33 CPU) > Result: FAIL > Failed 1/2 test programs. 1/20 subtests failed. > make[1]: *** [Makefile:844: test_dynamic] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2021/11/04/libdate-tiny-perl_1.07-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libdate-tiny-perl Source-Version: 1.07-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libdate-tiny-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous
Processed: Reassign FTBFS bugs to commons-io
Processing commands for cont...@bugs.debian.org: > reassign 998606 src:commons-io Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Ignoring request to reassign bug #998606 to the same package > reassign 998604 src:commons-io Bug #998604 [src:wala] wala: FTBFS: Could not resolve commons-io:commons-io:2.4. Bug reassigned from package 'src:wala' to 'src:commons-io'. No longer marked as found in versions wala/1.5.2-1. Ignoring request to alter fixed versions of bug #998604 to the same values previously set > reassign 998599 src:commons-io Bug #998599 [src:jengelman-shadow] jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5. Bug reassigned from package 'src:jengelman-shadow' to 'src:commons-io'. No longer marked as found in versions jengelman-shadow/4.0.3-2. Ignoring request to alter fixed versions of bug #998599 to the same values previously set > reassign 998549 src:commons-io Bug #998549 [src:grengine] grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel --max-workers=4 test returned exit code 1 Bug reassigned from package 'src:grengine' to 'src:commons-io'. No longer marked as found in versions grengine/3.0.0+dfsg-2. Ignoring request to alter fixed versions of bug #998549 to the same values previously set > forcemerge 998606 998604 998599 998549 Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Bug #998549 [src:commons-io] grengine: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=grengine -Dfile.encoding=UTF-8 --parallel --max-workers=4 test returned exit code 1 Bug #998599 [src:commons-io] jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5. Bug #998604 [src:commons-io] wala: FTBFS: Could not resolve commons-io:commons-io:2.4. Merged 998549 998599 998604 998606 > thanks Stopping processing here. Please contact me if you need assistance. -- 998549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998549 998599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998599 998604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998604 998606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998536: osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6.
reassign 998536 src:commons-io found 998536 commons-io/2.11.0-1 affects 998536 src:osmosis retitle 998536 Missing dependency on junit5 for junit-bom thanks On 11/4/21 20:56, Lucas Nussbaum wrote: Putting task artifact state for task ':osmosis-pbf2:compileJava' into context took 0.0 secs. Replacing com.google.guava:guava:jar:26.0-jre -> com.google.guava:guava:jar:debian Passing through com.google.guava:guava-parent:jar:debian Replacing commons-io:commons-io:jar:2.6 -> commons-io:commons-io:jar:debian Passing through org.junit:junit-bom:jar:debian Passing through org.jsr-305:jsr305:jar:0.x :osmosis-pbf2:compileJava FAILED :osmosis-pbf2:compileJava (Thread[main,5,main]) completed. Took 0.078 secs. Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. :osmosis-apidb:compileJava (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 1.031 secs. :osmosis-osm-binary:javadoc (Thread[Task worker for ':' Thread 3,5,main]) completed. Took 8.04 secs. :osmosis-core:javadoc (Thread[Task worker for ':',5,main]) completed. Took 8.998 secs. FAILURE: Build failed with an exception. * What went wrong: Could not resolve all files for configuration ':osmosis-pbf2:compileClasspath'. Could not resolve commons-io:commons-io:2.6. Required by: project :osmosis-pbf2 > Could not resolve commons-io:commons-io:2.6. > Could not parse POM /usr/share/maven-repo/commons-io/commons-io/debian/commons-io-debian.pom > Could not resolve org.junit:junit-bom:debian. > No cached version of org.junit:junit-bom:debian available for offline mode. > No cached version of commons-io:commons-io:2.6 available for offline mode. org.junit:junit-bom:debian is provided by junit5, but commons-io build depends on junit4, and libcommons-io-java depends on neither. commons-io-debian.pom may need to be patched, or the package dependencies fixed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: closing 998566
Processing commands for cont...@bugs.debian.org: > close 998566 Bug #998566 [src:golang-github-alecthomas-chroma] golang-github-alecthomas-chroma: FTBFS: src/github.com/alecthomas/kong-hcl/loader.go:90:18: invalid operation: node.Group != "" (mismatched types *kong.Group and untyped string) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 998566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 4 errors): Reassign FTBFS bugs to commons-io
Processing commands for cont...@bugs.debian.org: > reassign 998606 src:commons-io Bug #998606 [src:gradle] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Bug reassigned from package 'src:gradle' to 'src:commons-io'. No longer marked as found in versions gradle/4.4.1-13. Ignoring request to alter fixed versions of bug #998606 to the same values previously set > reassing 998604 src:commons-io Unknown command or malformed arguments to command. > reassing 998599 src:commons-io Unknown command or malformed arguments to command. > reassing 998549 src:commons-io Unknown command or malformed arguments to command. > forcemerge 998606 998604 998599 998549 Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve commons-io:commons-io:debian. Unable to merge bugs because: package of #998549 is 'src:grengine' not 'src:commons-io' package of #998599 is 'src:jengelman-shadow' not 'src:commons-io' package of #998604 is 'src:wala' not 'src:commons-io' Failed to forcibly merge 998606: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 998549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998549 998599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998599 998604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998604 998606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 998536 to commons-io: Missing dependency on junit5 for junit-bom
Processing commands for cont...@bugs.debian.org: > retitle 998536 commons-io: Missing dependency on junit5 for junit-bom Bug #998536 [src:commons-io] Missing dependency on junit5 for junit-bom Changed Bug title to 'commons-io: Missing dependency on junit5 for junit-bom' from 'Missing dependency on junit5 for junit-bom'. > thanks Stopping processing here. Please contact me if you need assistance. -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#998536: osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6.
Processing commands for cont...@bugs.debian.org: > reassign 998536 src:commons-io Bug #998536 [src:osmosis] osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6. Bug reassigned from package 'src:osmosis' to 'src:commons-io'. No longer marked as found in versions osmosis/0.48.3-1. Ignoring request to alter fixed versions of bug #998536 to the same values previously set > found 998536 commons-io/2.11.0-1 Bug #998536 [src:commons-io] osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6. Marked as found in versions commons-io/2.11.0-1. > affects 998536 src:osmosis Bug #998536 [src:commons-io] osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6. Added indication that 998536 affects src:osmosis > retitle 998536 Missing dependency on junit5 for junit-bom Bug #998536 [src:commons-io] osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6. Changed Bug title to 'Missing dependency on junit5 for junit-bom' from 'osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6.'. > thanks Stopping processing here. Please contact me if you need assistance. -- 998536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998596: marked as done (python-pyproj: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Thu, 04 Nov 2021 20:49:25 +
with message-id
and subject line Bug#998596: fixed in python-pyproj 3.2.1-2
has caused the Debian Bug report #998596,
regarding python-pyproj: FTBFS: dh_auto_test: error: pybuild --test -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.)
--
998596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyproj
Version: 3.2.1-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 '/<>'
> dh_auto_test
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_pyproj/build;
> python3.9 -m pytest -v -m "not network and not cli and not grid"
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 --
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> plugins: cov-3.0.0
> collecting ... collected 816 items / 59 deselected / 757 selected
>
> test/test_aoi.py::test_backwards_compatible_import_paths PASSED [
> 0%]
> test/test_aoi.py::test_contains PASSED [
> 0%]
> test/test_aoi.py::test_not_contains PASSED [
> 0%]
> test/test_aoi.py::test_intersects PASSED [
> 0%]
> test/test_aoi.py::test_not_intersects PASSED [
> 0%]
> test/test_aoi.py::test_null_input[input0-AreaOfInterest] PASSED [
> 0%]
> test/test_aoi.py::test_null_input[input0-BBox] PASSED[
> 0%]
> test/test_aoi.py::test_null_input[input1-AreaOfInterest] PASSED [
> 1%]
> test/test_aoi.py::test_null_input[input1-BBox] PASSED[
> 1%]
> test/test_aoi.py::test_null_input[input2-AreaOfInterest] PASSED [
> 1%]
> test/test_aoi.py::test_null_input[input2-BBox] PASSED[
> 1%]
> test/test_aoi.py::test_null_input[input3-AreaOfInterest] PASSED [
> 1%]
> test/test_aoi.py::test_null_input[input3-BBox] PASSED[
> 1%]
> test/test_aoi.py::test_null_input[input4-AreaOfInterest] PASSED [
> 1%]
> test/test_aoi.py::test_null_input[input4-BBox] PASSED[
> 1%]
> test/test_aoi.py::test_null_input[input5-AreaOfInterest] PASSED [
> 2%]
> test/test_aoi.py::test_null_input[input5-BBox] PASSED[
> 2%]
> test/test_aoi.py::test_null_input[input6-AreaOfInterest] PASSED [
> 2%]
> test/test_aoi.py::test_null_input[input6-BBox] PASSED[
> 2%]
> test/test_aoi.py::test_null_input[input7-AreaOfInterest] PASSED [
> 2%]
> test/test_aoi.py::test_null_input[input7-BBox] PASSED[
> 2%]
> test/test_aoi.py::test_null_input[input8-AreaOfInterest] PASSED [
> 2%]
> test/test_aoi.py::test_null_input[input8-BBox] PASSED[
> 3%]
> test/test_aoi.py::test_null_input[input9-AreaOfInterest] PASSED [
> 3%]
> test/test_aoi.py::test_null_input[input9-BBox] PASSED[
> 3%]
> test/test_awips221.py::test_awips221 PASSED [
> 3%]
> test/test_database.py::test_backwards_compatible_import_paths PASSED [
> 3%]
> test/test_database.py::test_units_map__default PASSED[
> 3%]
> test/test_database.py::test_units_map__category[linear] PASSED [
> 3%]
> test/test_database.py::test_units_map__category[linear_per_time] PASSED [
> 3%]
> test/test_database.py::test_units_map__category[angular] PASSED [
> 4%]
> test/test_database.py::test_units_map__category[angular_per_time] PASSED [
> 4%]
> test/test_database.py::test_units_map__category[scale] PASSED[
> 4%]
> test/test_database.py::test_units_map__category[scale_per_time] PASSED [
> 4%]
> test/test_database.py::test_units_map__category[time] PASSED [
> 4%]
> test/test_database.py::test_units_map__auth_name[EPSG]
Processed: Bug#998560 marked as pending in libdate-tiny-perl
Processing control commands: > tag -1 pending Bug #998560 [src:libdate-tiny-perl] libdate-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 998560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998560: marked as pending in libdate-tiny-perl
Control: tag -1 pending Hello, Bug #998560 in libdate-tiny-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libdate-tiny-perl/-/commit/478a15f0bfb58a9fe120f1bda216e678c6a3bf6e Add patch to adjust test to DateTime::Locale 1.33. Thanks: Lucas Nussbaum for the bug report. Closes: #998560 (this message was generated automatically) -- Greetings https://bugs.debian.org/998560
Bug#984090: marked as done (libbpp-raa: ftbfs with GCC-11)
Your message dated Thu, 04 Nov 2021 20:49:19 + with message-id and subject line Bug#984090: fixed in libbpp-raa 2.4.1-6 has caused the Debian Bug report #984090, regarding libbpp-raa: 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.) -- 984090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-raa Version: 2.4.1-4 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/libbpp-raa_2.4.1-4_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. [...] --movedev debian/tmp/usr/include/* usr/include \ --movedev debian/tmp/usr/lib/*/cmake usr/lib/x86_64-linux-gnu \ debian/tmp/usr/lib/*/*.so Library package automatic movement utility --> libbpp-core-dev package exists. --> libbpp-seq-dev package exists. --> zlib1g-dev package exists. set -e install -d -m 755 debian/libbpp-raa-dev/usr/lib/x86_64-linux-gnu install -d -m 755 debian/libbpp-raa4/usr/lib/x86_64-linux-gnu mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-raa.a debian/libbpp-raa-dev/usr/lib/x86_64-linux-gnu mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-raa.so debian/libbpp-raa-dev/usr/lib/x86_64-linux-gnu mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-raa.so.4 debian/libbpp-raa4/usr/lib/x86_64-linux-gnu mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-raa.so.4.0.0 debian/libbpp-raa4/usr/lib/x86_64-linux-gnu PKGDEV=libbpp-raa-dev PKGSHL=libbpp-raa4 install -d -m 755 debian/libbpp-raa-dev/usr/include mv debian/tmp/usr/include/Bpp debian/libbpp-raa-dev/usr/include install -d -m 755 debian/libbpp-raa-dev/usr/lib/x86_64-linux-gnu mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake debian/libbpp-raa-dev/usr/lib/x86_64-linux-gnu make[1]: Leaving directory '/<>' dh_installdocs dh_installchangelogs dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a dh_makeshlibs -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libbpp-raa4/DEBIAN/symbols doesn't match completely debian/libbpp-raa4.symbols.amd64 --- debian/libbpp-raa4.symbols.amd64 (libbpp-raa4_2.4.1-4_amd64) +++ dpkg-gensymbolsYzL713 2021-03-01 21:10:54.111892382 + @@ -17,7 +17,7 @@ _ZN3bpp17AlphabetExceptionD0Ev@Base 2.4.1 _ZN3bpp17AlphabetExceptionD1Ev@Base 2.4.1 _ZN3bpp17AlphabetExceptionD2Ev@Base 2.4.1 - _ZN3bpp20AbstractCoreSequence11setCommentsERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1 +#MISSING: 2.4.1-4# _ZN3bpp20AbstractCoreSequence11setCommentsERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1 _ZN3bpp3RAA10deleteListEPNS_7RaaListE@Base 2.4.1 _ZN3bpp3RAA10getSeqFragERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiiRS6_@Base 2.4.1 _ZN3bpp3RAA10getSeqFragEiiiRNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 @@ -74,15 +74,17 @@
Bug#998606: gradle: FTBFS: Could not resolve commons-io:commons-io:debian.
Am Donnerstag, dem 04.11.2021 um 20:54 +0100 schrieb Lucas Nussbaum: > Source: gradle > Version: 4.4.1-13 > 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. This looks like the same issue as with syncany. I guess I just remove the (superfluous?) dependency on junit-bom in commons-io and we are done with it. signature.asc Description: This is a digitally signed message part
Bug#998411: Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
On 2021-11-03 22:33:01 +0100, Drew Parsons wrote: > On 2021-11-03 20:57, Sebastian Ramacher wrote: > > Source: hypre > > Severity: serious > ... > > The real blocker is hypre, specifically: > > > > hypre (2.18.1-1) experimental; urgency=medium > > . > >* Team upload. > >* New upstream release. > >* Standards-Version: 4.4.1 > >* Provide library binary package as libhypre without the soname > > version embedded in the package name. Enforce version dependency > > through strict shlibs dependency. This is to workaround lack of > > ABI backwards compatibility and keep minor version updates being > > delayed in the NEW queue. See README.Debian. > > > > > > As a consequence, hypre breaks co-installability of all its reverse > > dependencies, therefore breaking smooth updates of the packages involved > > in the transition. And yes, in the end, deal.ii currently keeps the > > whole stack from migrating as it renders deal.ii's binaries > > uninstallable in testing. > > > The problem that hypre 2.18.1-1 (un-versioned libhypre) intended to solve is > that hypre is ABI-ignorant (https://github.com/hypre-space/hypre/issues/56), > so each point patch release would have to be a new binary package, and the > upstream release rate is faster than the average NEW queue processing rate > (the new package for the current transition would be libhypre2.22.1, and > already libhypre2.23.0 is released upstream). (So why is this packaged as shared library?) > hypre has only 2 direct reverse dependencies, petsc and sundials, which we > can keep up-to-date easily. The current problem is that deal.ii depends on > the old petsc3.14, so it can't be installed with the new petsc3.15. That's why the second sentence of 8.1 reads: "This allows several versions of the shared library to be installed at the same time, allowing installation of the new version of the shared library without immediately breaking binaries that depend on the old version." The problem is not deal.ii. > It > wouldn't be a problem in practice, if deal.ii hadn't started FTBFS > (Bug#996277) preventing it rebuilding against petsc 3.15. We could say it > was tactical error running the hypre and petsc ABI updates at the same time > (I wasn't anticipating deal.ii Bug#996277) deal.ii doesn't FTBFS. deal.ii cannot currently be rebuilt in unsable because of another broken shared library (#995424 in gmsh). Once deal.ii is rebuilt (in testing), #996277 will disappear. > If we revert back to version-named hypre library packages then the cost is > that we won't be able to provide timely patch updates for hypre (each one > will be a new library package needing to pass NEW, since hypre does not > provide ABI compatibility). > > The alternative for this transition is to remove deal.ii from testing, which > is happening anyway due to Bug#996277 It won't be removed. > So the use of un-versioned libhypre was intended as a specific exception to > Policy 8.1, for the purpose of facilitating faster hypre patch updates. The > irregularity is due to a lack of ABI-awareness in hypre itself. > > Is it best to revert back to strict Policy 8.1 compliance, which will slow > down hypre patch release updates? Yes. Having to wait for binNEW to being processed is not an excuse to violate a must section of the policy. Processing of packages in NEW can take some time. I'm also waiting on some of them for months. The solution to that is however not to abondon well established practices for shared libraries. The problems that are caused by that can be seen with libhypre and its reverse dependencies. Cheers -- Sebastian Ramacher
Bug#998568: marked as pending in libtime-tiny-perl
Control: tag -1 pending Hello, Bug #998568 in libtime-tiny-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libtime-tiny-perl/-/commit/e696aff88fe81df52c972a6a510fcfbc7a410a03 Add patch to adjust test to DateTime::Locale 1.33. Thanks: Lucas Nussbaum for the bug report. Closes: #998568 (this message was generated automatically) -- Greetings https://bugs.debian.org/998568
Processed: Bug#998568 marked as pending in libtime-tiny-perl
Processing control commands: > tag -1 pending Bug #998568 [src:libtime-tiny-perl] libtime-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 998568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996237: marked as done (ruby-gsl: FTBFS with ruby3.0: include/rb_gsl_common.h:29:1: error: unknown type name ‘EXTERN’)
Your message dated Thu, 04 Nov 2021 20:36:23 + with message-id and subject line Bug#996237: fixed in ruby-gsl 2.1.0.3+dfsg1-4 has caused the Debian Bug report #996237, regarding ruby-gsl: FTBFS with ruby3.0: include/rb_gsl_common.h:29:1: error: unknown type name ‘EXTERN’ 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.) -- 996237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-gsl Version: 2.1.0.3+dfsg1-3 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-gsl 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): > gcc -fdebug-prefix-map=/<>=. -I. > -I/usr/include/x86_64-linux-gnu/ruby-3.0.0 > -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I. > -DGSL_VERSION=2.7 -DGSL_1_15_LATER -DGSL_1_15_LATER -DGSL_1_16_LATER > -DGSL_2_0_LATER -DGSL_2_1_LATER -DHAVE_ROUND -DHAVE_GSL_EIGEN_FRANCIS > -DHAVE_GNU_GRAPH -DHAVE_TAMU_ANOVA_TAMU_ANOVA_H -DHAVE_GSL_SF_MATHIEU_A_E > -DHAVE_GSL_SF_MATHIEU_B_E -DHAVE_GSL_SF_MATHIEU_CE_E > -DHAVE_GSL_SF_MATHIEU_SE_E -DHAVE_GSL_SF_MATHIEU_MC_E > -DHAVE_GSL_SF_MATHIEU_MS_E -I/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0 > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 > -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall > -Iinclude -I/usr/include -o array.o -c array.c > In file included from array.c:12: > include/rb_gsl_common.h:29:1: error: unknown type name ‘EXTERN’ >29 | EXTERN ID rb_gsl_id_beg, rb_gsl_id_end, rb_gsl_id_excl, > rb_gsl_id_to_a; > | ^~ > include/rb_gsl_common.h:29:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘rb_gsl_id_beg’ >29 | EXTERN ID rb_gsl_id_beg, rb_gsl_id_end, rb_gsl_id_excl, > rb_gsl_id_to_a; > | ^ > In file included from array.c:12: > include/rb_gsl_common.h:352:1: error: unknown type name ‘EXTERN’ > 352 | EXTERN VALUE cGSL_Object; > | ^~ > include/rb_gsl_common.h:352:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cGSL_Object’ > 352 | EXTERN VALUE cGSL_Object; > | ^~~ > In file included from array.c:13: > include/rb_gsl_array.h:39:1: error: unknown type name ‘EXTERN’ >39 | EXTERN VALUE cgsl_block, cgsl_block_int; > | ^~ > include/rb_gsl_array.h:39:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cgsl_block’ >39 | EXTERN VALUE cgsl_block, cgsl_block_int; > | ^~ > include/rb_gsl_array.h:40:1: error: unknown type name ‘EXTERN’ >40 | EXTERN VALUE cgsl_block_uchar; > | ^~ > include/rb_gsl_array.h:40:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cgsl_block_uchar’ >40 | EXTERN VALUE cgsl_block_uchar; > | ^~~~ > include/rb_gsl_array.h:41:1: error: unknown type name ‘EXTERN’ >41 | EXTERN VALUE cgsl_block_complex; > | ^~ > include/rb_gsl_array.h:41:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cgsl_block_complex’ >41 | EXTERN VALUE cgsl_block_complex; > | ^~ > include/rb_gsl_array.h:42:1: error: unknown type name ‘EXTERN’ >42 | EXTERN VALUE cgsl_vector, cgsl_vector_complex; > | ^~ > include/rb_gsl_array.h:42:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cgsl_vector’ >42 | EXTERN VALUE cgsl_vector, cgsl_vector_complex; > | ^~~ > include/rb_gsl_array.h:43:1: error: unknown type name ‘EXTERN’ >43 | EXTERN VALUE cgsl_vector_col; > | ^~ > include/rb_gsl_array.h:43:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cgsl_vector_col’ >43 | EXTERN VALUE cgsl_vector_col; > | ^~~ > include/rb_gsl_array.h:44:1: error: unknown type name ‘EXTERN’ >44 | EXTERN VALUE cgsl_vector_col_view; > | ^~ > include/rb_gsl_array.h:44:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or > ‘__attribute__’ before ‘cgsl_vector_col_view’ >44 | EXTERN VALUE cgsl_vector_col_view; > | ^~~~ > include/rb_gsl_array.h:45:1: error: unknown type name ‘EXTERN’ >45 | EXTERN
Processed: bug 998568 is forwarded to https://github.com/dagolden/Time-Tiny/issues/4, tagging 998568
Processing commands for cont...@bugs.debian.org: > forwarded 998568 https://github.com/dagolden/Time-Tiny/issues/4 Bug #998568 [src:libtime-tiny-perl] libtime-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/dagolden/Time-Tiny/issues/4'. > tags 998568 + upstream confirmed Bug #998568 [src:libtime-tiny-perl] libtime-tiny-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) upstream and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 998568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 998601
Processing commands for cont...@bugs.debian.org: > tags 998601 + confirmed Bug #998601 [src:libconfig-model-itself-perl] libconfig-model-itself-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 2 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 998601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 998541 in 4.7~beta2-1
Processing commands for cont...@bugs.debian.org: > fixed 998541 4.7~beta2-1 Bug #998541 [src:dynare] dynare: FTBFS: TypeError: 'DynareLexer' object is not callable Marked as fixed in versions dynare/4.7~beta2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 998541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998613: retro-gtk: FTBFS: ../retro-gtk/meson.build:188:4: ERROR: Got unknown keyword arguments "export_packages", "namespace"
Source: retro-gtk Version: 1.0.2-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 -- -Ddemos=false > 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 -Ddemos=false > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: retro-gtk > Project version: 1.0.2 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency epoxy found: YES 1.5.9 > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gio-unix-2.0 found: YES 2.70.0 > Run-time dependency glib-2.0 found: YES 2.70.0 > Run-time dependency gmodule-2.0 found: YES 2.70.0 > Run-time dependency gobject-2.0 found: YES 2.70.0 > Run-time dependency gtk+-3.0 found: YES 3.24.30 > Run-time dependency libpulse-simple found: YES 15.0 > Library m found: YES > Run-time dependency samplerate found: YES 0.2.2 > Configuring retro-gtk-config.h using configuration > Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Program make-ipc-runner-private.sh found: YES > (/<>/shared/make-ipc-runner-private.sh) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Configuring retro-gtk-version.h using configuration > Run-time dependency gobject-introspection-1.0 found: YES 1.70.0 > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program vapigen found: YES (/usr/bin/vapigen) > > ../retro-gtk/meson.build:188:4: ERROR: Got unknown keyword arguments > "export_packages", "namespace" > > 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:41.618732 > Main binary: /usr/bin/python3 > Build Options: -Ddemos=false -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -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 > Project name: retro-gtk > Project version: 1.0.2 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the build machine: cc ld.bfd 2.37 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 > Pkg-confi
Bug#998612: libisocodes: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: libisocodes
Version: 1.2.4-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[3]: Entering directory '/<>/po'
> make[3]: Nothing to be done for 'check'.
> make[3]: Leaving directory '/<>/po'
> make[3]: Verzeichnis „/<>“ wird betreten
> make check-local
> make[4]: Verzeichnis „/<>“ wird betreten
> /usr/bin/valac --pkg libxml-2.0 --pkg gee-0.8 --vapidir=./vapi --pkg config
> -X -I. -X -DGETTEXT_PACKAGE=\"libisocodes\" -X
> -DLOCALEDIR=\"/usr/share/locale\" -X -DTESTDIR=\"./tests/data\"
> --output=codetest tests/codetest.vala tests/test_iso_3166.vala
> tests/test_iso_3166_2.vala tests/test_iso_639.vala tests/test_iso_639_3.vala
> tests/test_iso_639_5.vala tests/test_iso_4217.vala tests/test_iso_15924.vala
> src/isocodes.vala src/iso_3166.vala src/iso_3166_item.vala
> src/iso_3166_2.vala src/iso_3166_2_item.vala src/iso_639.vala
> src/iso_639_item.vala src/iso_639_3.vala src/iso_639_3_item.vala
> src/iso_639_5.vala src/iso_639_5_item.vala src/iso_4217.vala
> src/iso_4217_item.vala src/iso_15924.vala src/iso_15924_item.vala
> src/exceptions.vala
> config.vapi:19.2-19.6: warning: Argument `prefix' never used
> [CCode (prefix = "", lower_case_cprefix = "", cheader_filename = "config.h")]
> ^
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:28,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /<>/tests/test_iso_3166.vala.c:22:
> /<>/tests/test_iso_3166.vala.c: In function
> ‘libisocodes_test_iso_3166_get_type’:
> /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
> ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
> 113 | __atomic_load (gapg_temp_atomic, _temp_newval,
> __ATOMIC_SEQ_CST); \
> | ^
> /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
> ‘g_atomic_pointer_get’
> 260 | (!g_atomic_pointer_get (location) && \
> | ^~~~
> /<>/tests/test_iso_3166.vala.c:1913:13: note: in expansion of
> macro ‘g_once_init_enter’
> 1913 | if (g_once_init_enter
> (_test_iso_3166_type_id__volatile)) {
> | ^
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:28,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /<>/tests/test_iso_3166_2.vala.c:22:
> /<>/tests/test_iso_3166_2.vala.c: In function
> ‘libisocodes_test_iso_3166_2_get_type’:
> /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
> ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
> 113 | __atomic_load (gapg_temp_atomic, _temp_newval,
> __ATOMIC_SEQ_CST); \
> | ^
> /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
> ‘g_atomic_pointer_get’
> 260 | (!g_atomic_pointer_get (location) && \
> | ^~~~
> /<>/tests/test_iso_3166_2.vala.c:1191:13: note: in expansion of
> macro ‘g_once_init_enter’
> 1191 | if (g_once_init_enter
> (_test_iso_3166_2_type_id__volatile)) {
> | ^
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:28,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /<>/tests/test_iso_639.vala.c:22:
> /<>/tests/test_iso_639.vala.c: In function
> ‘libisocodes_test_iso_639_get_type’:
> /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
> ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
> 113 | __atomic_load (gapg_temp_atomic, _temp_newval,
> __ATOMIC_SEQ_CST); \
> | ^
> /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
> ‘g_atomic_pointer_get’
>
Bug#998611: rust-tokio-executor: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.19-~~)
Source: rust-tokio-executor Version: 0.1.8-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): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-crossbeam-utils-0.7+default-dev, > librust-futures-0.1+default-dev (>= 0.1.19-~~), build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-crossbeam-utils-0.7+default-dev, > librust-futures-0.1+default-dev (>= 0.1.19-~~), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [449 B] > Get:5 copy:/<>/apt_archive ./ Packages [521 B] > Fetched 1927 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-futures-0.1+default-dev > (>= 0.1.19-~~) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/rust-tokio-executor_0.1.8-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#998608: canl-java: FTBFS: [ERROR] /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17]
Source: canl-java Version: 2.7.0-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): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_autoreconf -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibcanl-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The project eu.eu-emi.security:canl:jar:2.7.0 uses prerequisites > which is only intended for maven-plugin projects but not for non maven-plugin > projects. For such purposes you should use the maven-enforcer-plugin. See > https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html > [INFO] > [INFO] --< eu.eu-emi.security:canl > >--- > [INFO] Building canl 2.7.0 > [INFO] [ jar > ]- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ canl > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ canl --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 167 source files to /<>/target/classes > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/RFC3280CertPathUtilitiesCanl.java: > Some input files use or override a deprecated API. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/RFC3280CertPathUtilitiesCanl.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/PKIXPolicyNode.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/PKIXPolicyNode.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17] > eu.emi.security.authn.x509.helpers.trust.OpensslTruststoreHelper$1> is not > abstract and does not override abstract method > accept(java.nio.file.Path,java.nio.file.attribute.BasicFileAttributes) in > org.apache.commons.io.file.PathFilter > [INFO] 1 error > [INFO] - > [INFO] > [INFO] > > [INFO] Skipping canl > [INFO] This project has been banned from the build due to previous failures. > [INFO] > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.558 s > [INFO] Finished at: 2021-11-04T09:29:19Z > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > (default-compile) on project canl: Compilation failure > [ERROR] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17] > eu.emi.security.authn.x509.helpers.trust.OpensslTruststoreHelper$1> is not > abstract and does not override abstract method > accept(java.nio.file.Path,java.nio.file.attribute.BasicFileAttributes) in > org.apache.commons.io.file.PathFilter > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [
Bug#998610: node-cli-truncate: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Source: node-cli-truncate Version: 2.1.0-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): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/cli-truncate > /bin/sh -ex debian/tests/pkg-js/test > + tape test.js > TAP version 13 > # main > /<>/index.js:102 > return sliceAnsi(text, 0, columns - ellipsisWidth) + ellipsis; > ^ > > TypeError: sliceAnsi is not a function > at module.exports (/<>/index.js:102:10) > at Test. (/<>/test.js:5: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) > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/node-cli-truncate_2.1.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#998609: appstream-glib: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "firmware, ostree"
Source: appstream-glib Version: 0.7.18-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 '/<>' > dh_auto_configure -- -Dbuilder=false -Drpm=false -Dostree=false -Ddep11=true > -Dfirmware=true -Dgtk-doc=true > 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 -Dbuilder=false > -Drpm=false -Dostree=false -Ddep11=true -Dfirmware=true -Dgtk-doc=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "firmware, ostree" > > 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:48:43.587741 > Main binary: /usr/bin/python3 > Build Options: -Dbuilder=false -Drpm=false -Dostree=false -Ddep11=true > -Dfirmware=true -Dgtk-doc=true -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -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:1:0: ERROR: Unknown options: "firmware, ostree" > 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 -Dbuilder=false > -Drpm=false -Dostree=false -Ddep11=true -Dfirmware=true -Dgtk-doc=true > returned exit code 1 > make[1]: *** [debian/rules:23: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/appstream-glib_0.7.18-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#998607: gnome-logs: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "tests"
Source: gnome-logs Version: 3.36.0-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 -- -Dman=true -Dtests=true > 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 -Dman=true -Dtests=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "tests" > > 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:33:47.509593 > Main binary: /usr/bin/python3 > Build Options: -Dman=true -Dtests=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -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:1:0: ERROR: Unknown options: "tests" > 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 -Dman=true -Dtests=true > 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/gnome-logs_3.36.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
