Bug#1011863: marked as pending in guix

[Vagrant Cascadian]

Control: tag -1 pending

Hello,

Bug #1011863 in guix 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/guix/-/commit/6b1c4a4ff194a9e225c0629a87e7d3a218a8b2ce


debian/patches: Remove expiration dates on openpgp keys used in test suite.
(Closes: #1011863)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011863

Processed: Bug#1011863 marked as pending in guix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011863 [src:guix] guix: FTBFS in bullseye because of expired certificates 
used in tests
Added tag(s) pending.

-- 
1011863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026816: marked as done (speedcrunch: FTBFS: KeyError: 'extra-doc-strings')

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2022 01:45:24 +
with message-id 
and subject line Bug#1026816: fixed in speedcrunch 0.12.0-6
has caused the Debian Bug report #1026816,
regarding speedcrunch: FTBFS: KeyError: 'extra-doc-strings'
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.)


-- 
1026816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: speedcrunch
Version: 0.12.0-5.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221221 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[4]: Entering directory '/<>/build-docs'
> [100%] Generating manual.qrc
> Running Sphinx v5.3.0
> WARNING: Invalid configuration value found: 'language = None'. Update your 
> configuration to a valid language code. Falling back to 'en' (English).
> loading translations [en_US]... not available for built-in messages
> 
> Exception occurred:
>   File "/<>/doc/src/extensions/translations.py", line 29, in _
> return locale.translators[_CATALOG].gettext(message)
> KeyError: 'extra-doc-strings'
> The full traceback has been saved in /tmp/sphinx-err-avr0b5ds.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> Building docs for en_US...
> Traceback (most recent call last):
>   File "/<>/doc/src/doc-tool.py", line 208, in 
> main(sys.argv)
>   File "/<>/doc/src/doc-tool.py", line 202, in main
> args.func(tools, args)
>   File "/<>/doc/src/doc-tool.py", line 135, in build_bundled_docs
> build_docs(tools, args.source_dir, args.build_dir, lang,
>   File "/<>/doc/src/doc-tool.py", line 77, in build_docs
> return tools.sphinx_build(*args)
>   File "/<>/doc/src/doc-tool.py", line 52, in 
> return lambda *args: self.run_tool(name, *args)
>   File "/<>/doc/src/doc-tool.py", line 49, in run_tool
> return subprocess.check_call(cmd)
>   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/sphinx-build', 
> '/<>/doc/src', '/<>/build-docs/en_US', '-b', 
> 'qthelp2', '-D', 'qthelp_basename=manual-en_US', '-D', 'language=en_US', 
> '-t', 'sc_bundled_docs']' returned non-zero exit status 2.
> make[4]: *** [CMakeFiles/manual.dir/build.make:102: manual.qrc] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/21/speedcrunch_0.12.0-5.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221221;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221221=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: speedcrunch
Source-Version: 0.12.0-6
Done: Felix Krull 

We believe that the bug you reported is fixed in the latest version of
speedcrunch, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felix Krull  (supplier of updated speedcrunch 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, 23 Dec 2022 19:24:30 +0100
Source: speedcrunch
Architecture: source
Version: 0.12.0-6
Distribution: unstable
Urgency: medium
Maintainer: Felix Krull 
Changed-By: Felix Krull 
Closes: 1026816
Changes:
 speedcrunch (0.12.0-6) unstable; urgency=medium

Bug#1026472: marked as done (python-blessed: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2022 00:39:09 +
with message-id 
and subject line Bug#1026472: fixed in python-blessed 1.19.1-1
has caused the Debian Bug report #1026472,
regarding python-blessed: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.11 3.10" 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.)


-- 
1026472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-blessed
Version: 1.19.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x -rs" 
> dh_auto_test
> I: pybuild base:240: python3.11 -m pytest -v -x -rs
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/_pytest/main.py", line 
> 266, in wrap_session
> INTERNALERROR> config._do_configure()
> INTERNALERROR>   File 
> "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1037, in 
> _do_configure
> INTERNALERROR> 
> self.hook.pytest_configure.call_historic(kwargs=dict(config=self))
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 
> 277, in call_historic
> INTERNALERROR> res = self._hookexec(self.name, self.get_hookimpls(), 
> kwargs, False)
> INTERNALERROR>   
> ^^
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_manager.py", 
> line 80, in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, 
> firstresult)
> INTERNALERROR>
> ^
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", 
> line 60, in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR>
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_result.py", 
> line 60, in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", 
> line 39, in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR>   ^
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/xdist/plugin.py", line 
> 220, in pytest_configure
> INTERNALERROR> config.issue_config_time_warning(warning, 2)
> INTERNALERROR>   File 
> "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1394, in 
> issue_config_time_warning
> INTERNALERROR> warnings.warn(warning, stacklevel=stacklevel)
> INTERNALERROR> DeprecationWarning: The --looponfail command line argument and 
> looponfailroots config variable are deprecated.
> INTERNALERROR> The loop-on-fail feature will be removed in pytest-xdist 4.0.
> E: pybuild pybuild:386: test: plugin custom failed with: exit code=3: 
> python3.11 -m pytest -v -x -rs
> I: pybuild base:240: python3.10 -m pytest -v -x -rs
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/_pytest/main.py", line 
> 266, in wrap_session
> INTERNALERROR> config._do_configure()
> INTERNALERROR>   File 
> "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1037, in 
> _do_configure
> INTERNALERROR> 
> self.hook.pytest_configure.call_historic(kwargs=dict(config=self))
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 
> 277, in call_historic
> INTERNALERROR> res = self._hookexec(self.name, self.get_hookimpls(), 
> kwargs, False)
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_manager.py", 
> line 80, in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, 
> firstresult)
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", 
> line 60, in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_result.py", 
> line 60, in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/_callers.py", 
> line 39, in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR>   File 

Bug#1026855: marked as done (libgoogle-auto-service-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2022 00:34:44 +
with message-id 
and subject line Bug#1026855: fixed in google-auto-service-java 1.0.1-1
has caused the Debian Bug report #1026855,
regarding libgoogle-auto-service-java: ships 
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
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.)


-- 
1026855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgoogle-auto-service-java
Version: 1.0~rc7-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

libgoogle-auto-service-java ships two dubious files that should probably
not be in the package at all:

  
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
  /usr/share/maven-repo/build-only/build-only/debian/build-only-debian.pom

This now started to cause a file conflict with another package doing
the same mistake.

No other package in the archive ships anything "useful" in
/usr/share/maven-repo/build-only/


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: google-auto-service-java
Source-Version: 1.0.1-1
Done: Olek Wojnar 

We believe that the bug you reported is fixed in the latest version of
google-auto-service-java, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated google-auto-service-java 
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, 23 Dec 2022 18:13:55 -0500
Source: google-auto-service-java
Architecture: source
Version: 1.0.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Olek Wojnar 
Closes: 1026855
Changes:
 google-auto-service-java (1.0.1-1) unstable; urgency=high
 .
   * New upstream release
   * Use xz compression for source package
   * Don't install build-only artifacts (Closes: #1026855)
   * Standardize upstream "rc" version string to prevent dependency problems
Checksums-Sha1:
 bdfd2f8fd0e11fbdb6e480becb52532378daf857 2197 
google-auto-service-java_1.0.1-1.dsc
 1a82a91d857a65babad504b35a432fc27d25c5ee 279616 
google-auto-service-java_1.0.1.orig.tar.xz
 c45f7fa15fd0a170ab14c3265a344d1beb329b02 3088 
google-auto-service-java_1.0.1-1.debian.tar.xz
 87d876ad79d7974a172ff195f881b0abede9568d 13858 
google-auto-service-java_1.0.1-1_amd64.buildinfo
Checksums-Sha256:
 1fe5e93207678658ff2f71c5cecaa4d50afa4636eab22d73a0e73809937e450d 2197 
google-auto-service-java_1.0.1-1.dsc
 842d33e2e0876aed8d03e3c1d6463913fc5951ffd25ef247094ce85456125c26 279616 
google-auto-service-java_1.0.1.orig.tar.xz
 7d70f81713c3b599b8a91d2ba08d958957bbf31da3fee956607953d8093af411 3088 
google-auto-service-java_1.0.1-1.debian.tar.xz
 3364048665564312d3d243a7b220925cd1e9c47926d0eee512feafb5d220bafe 13858 
google-auto-service-java_1.0.1-1_amd64.buildinfo
Files:
 c2864ff678cf9968080c680b59dc2690 2197 java optional 
google-auto-service-java_1.0.1-1.dsc
 309c29e8f03e041dfd0bd4ba667965e7 279616 java optional 
google-auto-service-java_1.0.1.orig.tar.xz
 e897ee67fa98fa8a1d9c83ebb052c0fc 3088 java optional 
google-auto-service-java_1.0.1-1.debian.tar.xz
 39e5bad9a6de2c260d0ca66976ee8376 13858 java optional 
google-auto-service-java_1.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmOmRQEACgkQfYPUBqCd
weSCxBAAi/bjm+cdMppt59ZRs3z+S8WW/oxprR1dSL5SiU7L4kPTv4ywiagh+N5x
dAF3JKYmHQb6dyBF/jpa3Kz4A5oxGnN1r/vrPvUWcGOx175vJ7OAV/HdUpsFC3XE
6QB2WRjG0EYqEzKEoB9UrFXOR6OV00dqmB7rY5jm9NL4f4DSvVnMrz2Isjthbo/7
cxMx5ncwmfOw6DfH7ktWlHVvEo1Mpb0Jr3pv4afnG263ve9+rkCzyXgTg8dvYxYu
7gLQH0mdgmwyxwN21umLktyDsaXZXX1wEtYhfWrA+yuu2DN2mtvru2srhR8ynAqT
YVwITjF19jsMJNGmp6qfbh/lQCVOqza0Bt6S8O+ycTqopshM0/uLe1u4gMrdRENJ
11tem/cFeLIl4b2ovjeZeCGOFwOtAPuOxyTMP5uc+DIYdMkplCO3ZjOzCJQMHREw
ymWq0nFjXBhLS2wlXxuCYkXGssVNTgMz/6xaVfYmu+abK4rvsbVXT1xRKSmoWWxa
i1rVjXAsmzQrhX/6aE5c7XTU+zy4m28KOxqFb8k5ZQDk4/M6Ojwbnhg1vBXkTD1B
3D+YH7ogypK6ipw1SNpBuuWLg/fVDnZSrdNu4I8fRG9V0BIpCtlPuAdofWVYeV0S
6MjXiVkG5DCteOnx+w7/NQ4GKKKTyxRrpQj9/s9enls2R4uaGOI=

Processed: Bug#1026472 marked as pending in python-blessed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026472 [src:python-blessed] python-blessed: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit 
code 13
Added tag(s) pending.

-- 
1026472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026472: marked as pending in python-blessed

[Pierre-Elliott Bécue]

Control: tag -1 pending

Hello,

Bug #1026472 in python-blessed reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-blessed/-/commit/0386f33f025e6d33470a51731930914ad11c5cbd


d/p/0002: Remove a deprecated flag on tox.ini

Closes: #1026472


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026472

Bug#1026726: apache-directory-api: FTBFS: [ERROR] /<>/ldap/client/api/src/main/java/org/apache/directory/ldap/client/api/LdapNetworkConnection.java:[4018,22] cannot find symbol

[tony mancill]

On Tue, Dec 20, 2022 at 06:32:07PM +0100, Lucas Nussbaum wrote:
> Source: apache-directory-api
> Version: 1.0.0-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm

The FTBFS is due to the recent upload of mina2 [1] that updates the
library from 2.1.x.  When addressing this bug, also see #1026713.

[1] 
https://tracker.debian.org/news/1399061/accepted-mina2-221-1-source-into-unstable/
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026713

Bug#1026854: marked as done (libgoogle-auto-common-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 23:05:10 +
with message-id 
and subject line Bug#1026854: fixed in google-auto-common-java 1.1.2-1
has caused the Debian Bug report #1026854,
regarding libgoogle-auto-common-java: ships 
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
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.)


-- 
1026854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgoogle-auto-common-java
Version: 1.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

libgoogle-auto-common-java ships two dubious files that should probably
not be in the package at all:

  
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
  /usr/share/maven-repo/build-only/build-only/debian/build-only-debian.pom

This now started to cause a file conflict with another package doing
the same mistake.

No other package in the archive ships anything "useful" in
/usr/share/maven-repo/build-only/


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: google-auto-common-java
Source-Version: 1.1.2-1
Done: Olek Wojnar 

We believe that the bug you reported is fixed in the latest version of
google-auto-common-java, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated google-auto-common-java 
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, 23 Dec 2022 17:48:57 -0500
Source: google-auto-common-java
Architecture: source
Version: 1.1.2-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Olek Wojnar 
Closes: 1021630 1026854
Changes:
 google-auto-common-java (1.1.2-1) unstable; urgency=high
 .
   * New upstream release (Closes: #1021630)
   * Add build-dependency on libchecker-framework-java
   * Don't install build-only artifacts (Closes: #1026854)
Checksums-Sha1:
 67ea59b6e4dae0b81c660dc7fbf2d4b5464dc7d0 2202 
google-auto-common-java_1.1.2-1.dsc
 4f3f0a1f3be39cfb1b5f1a48fff9d70891cd7b88 276356 
google-auto-common-java_1.1.2.orig.tar.xz
 8642faff7e033bd2a87a8d4f1173a01152894803 3712 
google-auto-common-java_1.1.2-1.debian.tar.xz
 68f18127676e98cbe3801288830d2ed2e0cec2ee 13886 
google-auto-common-java_1.1.2-1_amd64.buildinfo
Checksums-Sha256:
 dac5c8bb97f4f46c8cd6ed279af564d1ea37b1cb5ca3ec81c5b9440732768be5 2202 
google-auto-common-java_1.1.2-1.dsc
 081c28b77d57e10927ac09116fb4361e030518a92117167532ba49813bcaeff8 276356 
google-auto-common-java_1.1.2.orig.tar.xz
 80756790101d96f354774b5b995719c10d2c8bb01ea37e1f1af34d43d4e03da1 3712 
google-auto-common-java_1.1.2-1.debian.tar.xz
 97acc78d4d712580e112dc40b793679846fd4ab75be31084de7900b9b517865b 13886 
google-auto-common-java_1.1.2-1_amd64.buildinfo
Files:
 a144fe846f090b9f72cf9783a6acd52a 2202 java optional 
google-auto-common-java_1.1.2-1.dsc
 ee0fc3a992d9cfb129dca7a18c6d4952 276356 java optional 
google-auto-common-java_1.1.2.orig.tar.xz
 0322c7237c4804d9dfa026c97b2087af 3712 java optional 
google-auto-common-java_1.1.2-1.debian.tar.xz
 15e07266c6f27ff014984811d6f02150 13886 java optional 
google-auto-common-java_1.1.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmOmMSEACgkQfYPUBqCd
weQLkg//aql4BRRaxLsXhYGpDMMUkJAO+wayCRmyhW0Oh/pUL/nRbd1hZkglA4+v
m1VXfSUjXy7Jo4Ws6aZHkP6QZXRYi6prC9jF0hR/usoJQ+1oPuLeJLPjpAbmcVG+
MVwnlkzSEQDQKJCpPkrnERt037h9XssLDDyclzaIP5BWhRGmbj8hNpco3ls71U4W
YZ7TdQUaq6Lg/JDCdVVO4aAi+tN7pe1/QE0FGri8eppZfVNKvNIKdfIroqhRXsrk
BPL/r048H3dERkU/3b1vCpwUn0QPT9H/2++31jk7sXNyszNLLvWdkn9WXJpLHTQK
tslPDO5KWnFRCxlz05cISR56IDbMw4pfpty70X0mnrfA2RigMWe85qcm0NV3/g1C
r9eA7PuOPOJB1sCDZM2eR0mX6BrRoK+FBxI2dlM2VZ7lVAzgcSQmJftgk3ceKRwl
jg4DoUczxKt1Et9cmJsQUEn1xXUM1nMHIviy19QH1t/d0a00ibx5TVdUW/2ZrtXH
5r//mrv9axcSij3UEl6wHmSC5IsdfgScvtGOe+RaD5n213qDFRTmwulJQvT7EVTy
6RessXsOCMJb7PlLr0ybunB6WHAl63ywKwLXnWggFJ07PWr7cJfv4Dx+0WR162ob
iJ/gGp0wU9cC0DoB3oxio7LahdQ59i3w2WVcSCuIpg4xgLU0PtM=
=wg+D
-END PGP SIGNATURE End Message ---

Bug#1026659: marked as done (aeonbits-owner: FTBFS: make: *** [debian/rules:6: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 22:34:11 +
with message-id 
and subject line Bug#1026659: fixed in aeonbits-owner 1.0.12+ds-3
has caused the Debian Bug report #1026659,
regarding aeonbits-owner: FTBFS: make: *** [debian/rules:6: binary] Error 25
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.)


-- 
1026659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aeonbits-owner
Version: 1.0.12+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 --with javahelper
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibaeonbits-owner-java --debian-build --keep-pom-version 
> --maven-repo=/<>/aeonbits-owner-1.0.12\+ds/debian/maven-repo
>jh_linkjars
>dh_auto_build
>   /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=/<>/aeonbits-owner-1.0.12\+ds 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/aeonbits-owner-1.0.12\+ds/debian 
> -Dmaven.repo.local=/<>/aeonbits-owner-1.0.12\+ds/debian/maven-repo 
> --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] OWNER :: Parent
> [pom]
> [INFO] OWNER :: Core  
> [jar]
> [INFO] OWNER :: Extras
> [jar]
> [INFO] 
> [INFO] --< org.aeonbits.owner:owner-parent 
> >---
> [INFO] Building OWNER :: Parent 1.0.12
> [1/3]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --< org.aeonbits.owner:owner 
> >--
> [INFO] Building OWNER :: Core 1.0.12  
> [2/3]
> [INFO] [ jar 
> ]-
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The artifact org.hamcrest:hamcrest-all:jar:debian has been 
> relocated to org.hamcrest:hamcrest:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ owner 
> ---
> [INFO] skip non existing resourceDirectory 
> /<>/owner/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ owner ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 52 source files to /<>/owner/target/classes
> Use of release 6 is no longer supported, switching to 7
> [INFO] 
> /<>/owner/src/main/java/org/aeonbits/owner/util/Collections.java:
>  
> /<>/owner/src/main/java/org/aeonbits/owner/util/Collections.java 
> uses unchecked or unsafe operations.
> [INFO] 
> /<>/owner/src/main/java/org/aeonbits/owner/util/Collections.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:testResources (default-testResources) 
> @ owner ---
> [INFO] Copying 18 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ 
> owner ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 91 source files to /<>/owner/target/test-classes
> Use of release 6 is no longer supported, switching to 7
> [INFO] 
> /<>/owner/src/test/java/org/aeonbits/owner/typeconversion/arrays/ArraySupportTest.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/owner/src/test/java/org/aeonbits/owner/typeconversion/arrays/ArraySupportTest.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ owner ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-jar-plugin:3.3.0:jar 

Bug#1026110: marked as done (xournal: FTBFS: Makefile:263: *** missing separator. Stop.)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 23:04:39 +0100
with message-id 
and subject line Re: xournal: FTBFS: Makefile:263: *** missing separator.  Stop.
has caused the Debian Bug report #1026110,
regarding xournal: FTBFS: Makefile:263: *** missing separator.  Stop.
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.)


-- 
1026110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xournal
Version: 1:0.4.8.2016-7+b1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer(s),

Your package fails to build with:

|dh_auto_build
|   make -j8
| make[1]: Entering directory '/build/1st/xournal-0.4.8.2016'
| Makefile:263: *** missing separator.  Stop.
| make[1]: Leaving directory '/build/1st/xournal-0.4.8.2016'
| dh_auto_build: error: make -j8 returned exit code 2
| make: *** [debian/rules:6: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

The full build log is available from:
  
https://buildd.debian.org/status/fetch.php?pkg=xournal=riscv64=1%3A0.4.8.2016-7%2Bb2=1671008048=0
  
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/xournal_0.4.8.2016-7.rbuild.log.gz

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Hi,

On 2022-12-14 22:23, Aurelien Jarno wrote:
> Package: xournal
> Version: 1:0.4.8.2016-7+b1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear maintainer(s),
> 
> Your package fails to build with:
> 
> |dh_auto_build
> | make -j8
> | make[1]: Entering directory '/build/1st/xournal-0.4.8.2016'
> | Makefile:263: *** missing separator.  Stop.
> | make[1]: Leaving directory '/build/1st/xournal-0.4.8.2016'
> | dh_auto_build: error: make -j8 returned exit code 2
> | make: *** [debian/rules:6: binary] Error 25
> | dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
> status 2
> 
> The full build log is available from:
>   
> https://buildd.debian.org/status/fetch.php?pkg=xournal=riscv64=1%3A0.4.8.2016-7%2Bb2=1671008048=0
>   
> https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/xournal_0.4.8.2016-7.rbuild.log.gz
> 

It happens that xournal now builds fine on both riscv64 and reproducible
build. It's not clear to me what got fixed, anyway closing the bug.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---

Processed: forcibly merging 1019634 1026565 1026601 1026544 1026560 1026578 1026564 1026557 1026550 1026589 1026629

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1019634 1026565 1026601 1026544 1026560 1026578 1026564 1026557 
> 1026550 1026589 1026629
Bug #1019634 [src:jekyll] jekyll requires liquid gem v4, whereas the archive 
has 5.4
Bug #1026601 [src:jekyll] ruby-jekyll-feed: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 138 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026601 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026544 [src:jekyll] ruby-jekyll-data: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 139 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026544 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026565 [src:jekyll] ruby-jekyll-seo-tag: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 143 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026565 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026564 [src:jekyll] ruby-jekyll-polyglot: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 136 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026564 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026629 [src:jekyll] ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 134 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026629 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026550 [src:jekyll] ruby-jekyll-last-modified-at: FTBFS: ERROR: Test 
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 'liquid' (~> 4.0) 
among 133 total gem(s) (Gem::MissingSpecError)
Added indication that 1026550 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026560 [src:jekyll] ruby-jekyll-asciidoc: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 133 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026560 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026557 [src:jekyll] ruby-jekyll-toc: FTBFS: ERROR: Test "ruby3.1" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 137 total gem(s) 
(Gem::MissingSpecError)
Added indication that 1026557 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026589 [src:jekyll] jekyll-theme-minima: FTBFS: ERROR: Test "ruby3.1" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 128 
total gem(s) (Gem::MissingSpecError)
Added indication that 1026589 affects 
ruby-jekyll-include-cache,ruby-jekyll-data,ruby-jekyll-polyglot,ruby-jekyll-remote-theme,ruby-jekyll-toc,ruby-jekyll-last-modified-at,ruby-jekyll-seo-tag,ruby-jekyll-asciidoc,ruby-jekyll-feed,ruby-jekyll-commonmark
Bug #1026578 [src:jekyll] 

Processed: reassign 1026629 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026629 src:jekyll
Bug #1026629 [src:ruby-jekyll-commonmark] ruby-jekyll-commonmark: FTBFS: ERROR: 
Test "ruby3.1" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 134 total gem(s) 
(Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-commonmark' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-commonmark/1.3.1-6.
Ignoring request to alter fixed versions of bug #1026629 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026589 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026589 src:jekyll
Bug #1026589 [src:jekyll-theme-minima] jekyll-theme-minima: FTBFS: ERROR: Test 
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 'liquid' (~> 4.0) 
among 128 total gem(s) (Gem::MissingSpecError)
Bug reassigned from package 'src:jekyll-theme-minima' to 'src:jekyll'.
No longer marked as found in versions jekyll-theme-minima/2.5.1-2.
Ignoring request to alter fixed versions of bug #1026589 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026550 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026550 src:jekyll
Bug #1026550 [src:ruby-jekyll-last-modified-at] ruby-jekyll-last-modified-at: 
FTBFS: ERROR: Test "ruby3.1" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 133 total gem(s) 
(Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-last-modified-at' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-last-modified-at/1.3.0-1.
Ignoring request to alter fixed versions of bug #1026550 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026578 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026578 src:jekyll
Bug #1026578 [src:ruby-jekyll-include-cache] ruby-jekyll-include-cache: FTBFS: 
ERROR: Test "ruby3.1" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 132 total gem(s) 
(Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-include-cache' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-include-cache/0.2.1-1.
Ignoring request to alter fixed versions of bug #1026578 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026564 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026564 src:jekyll
Bug #1026564 [src:ruby-jekyll-polyglot] ruby-jekyll-polyglot: FTBFS: ERROR: 
Test "ruby3.1" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 136 total gem(s) 
(Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-polyglot' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-polyglot/1.5.0-1.
Ignoring request to alter fixed versions of bug #1026564 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026557 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026557 src:jekyll
Bug #1026557 [src:ruby-jekyll-toc] ruby-jekyll-toc: FTBFS: ERROR: Test 
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 'liquid' (~> 4.0) 
among 137 total gem(s) (Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-toc' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-toc/0.17.1-1.
Ignoring request to alter fixed versions of bug #1026557 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026565 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026565 src:jekyll
Bug #1026565 [src:ruby-jekyll-seo-tag] ruby-jekyll-seo-tag: FTBFS: ERROR: Test 
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 'liquid' (~> 4.0) 
among 143 total gem(s) (Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-seo-tag' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-seo-tag/2.7.1-2.
Ignoring request to alter fixed versions of bug #1026565 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026560 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026560 src:jekyll
Bug #1026560 [src:ruby-jekyll-asciidoc] ruby-jekyll-asciidoc: FTBFS: ERROR: 
Test "ruby3.1" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 133 total gem(s) 
(Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-asciidoc' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-asciidoc/3.0.0-2.
Ignoring request to alter fixed versions of bug #1026560 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026601 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026601 src:jekyll
Bug #1026601 [src:ruby-jekyll-feed] ruby-jekyll-feed: FTBFS: ERROR: Test 
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 'liquid' (~> 4.0) 
among 138 total gem(s) (Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-feed' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-feed/0.15.1-2.
Ignoring request to alter fixed versions of bug #1026601 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1026544 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026544 src:jekyll
Bug #1026544 [src:ruby-jekyll-data] ruby-jekyll-data: FTBFS: ERROR: Test 
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in 
`rescue in block in activate_dependencies': Could not find 'liquid' (~> 4.0) 
among 139 total gem(s) (Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-data' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-data/1.1.1-2.
Ignoring request to alter fixed versions of bug #1026544 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1019634 to src:jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1019634 src:jekyll
Bug #1019634 [jekyll] jekyll requires liquid gem v4, whereas the archive has 5.4
Bug reassigned from package 'jekyll' to 'src:jekyll'.
Ignoring request to alter found versions of bug #1019634 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1019634 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1019673: marked as done (ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require 'ruby-growl')

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 20:55:01 +
with message-id 
and subject line Bug#1019673: fixed in ruby-uniform-notifier 1.16.0-1
has caused the Debian Bug report #1019673,
regarding ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1" 
failed: Failure/Error: require 'ruby-growl'
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.)


-- 
1019673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-uniform-notifier
Version: 1.13.0-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-uniform-notifier with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> Failure/Error: require 'ruby-growl'
> 
> NameError:
>   uninitialized class variable @@schemes in URI
>   Did you mean?  scheme_list
> # 
> /usr/share/rubygems-integration/all/gems/ruby-growl-4.1/lib/uri/x_growl_resource.rb:74:in
>  `'
> # 
> /usr/share/rubygems-integration/all/gems/ruby-growl-4.1/lib/uri/x_growl_resource.rb:73:in
>  `'
> # 
> /usr/share/rubygems-integration/all/gems/ruby-growl-4.1/lib/ruby-growl/gntp.rb:6:in
>  `'
> # 
> /usr/share/rubygems-integration/all/gems/ruby-growl-4.1/lib/ruby-growl.rb:330:in
>  `'
> # ./spec/spec_helper.rb:6:in `'
> # ./spec/uniform_notifier/xmpp_spec.rb:3:in `'
> No examples found.
> 
> Finished in 0.4 seconds (files took 0.22139 seconds to load)
> 0 examples, 0 failures, 15 errors occurred outside of examples
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-uniform-notifier/ruby-uniform-notifier_1.13.0-2+rebuild1663008285_amd64-2022-09-12T18:44:46Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-uniform-notifier
Source-Version: 1.16.0-1
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-uniform-notifier, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated 
ruby-uniform-notifier 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, 23 Dec 2022 21:25:59 +0100
Source: ruby-uniform-notifier
Architecture: source
Version: 1.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1019673
Changes:
 ruby-uniform-notifier (1.16.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.6.0, no changes needed.
 .
   [ Cédric Boutillier ]
   * Add .gitattributes to keep unwanted files out of the source package
   * New upstream version 1.16.0
 + drop support for ruby-growl, deprecated (Closes: #1019673)
   * Fix upstream metadata
   * Update control file
 + Update standards version to 4.6.1, no changes needed.
   * Set homepage to Github repo
Checksums-Sha1:
 

Processed: affects 1019634

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1019634 ruby-jekyll-asciidoc ruby-jekyll-commonmark ruby-jekyll-data 
> ruby-jekyll-feed ruby-jekyll-include-cache ruby-jekyll-last-modified-at 
> ruby-jekyll-polyglot ruby-jekyll-remote-theme ruby-jekyll-seo-tag 
> ruby-jekyll-toc
Bug #1019634 [jekyll] jekyll requires liquid gem v4, whereas the archive has 5.4
Added indication that 1019634 affects ruby-jekyll-asciidoc, 
ruby-jekyll-commonmark, ruby-jekyll-data, ruby-jekyll-feed, 
ruby-jekyll-include-cache, ruby-jekyll-last-modified-at, ruby-jekyll-polyglot, 
ruby-jekyll-remote-theme, ruby-jekyll-seo-tag, and ruby-jekyll-toc
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026914: arcanist client improperly uploading files

[Elliott Mitchell]

Package: arcanist
Version: 0~git20200925-1
Severity: grave

If one has one or more commits in /some/repo one can create a
Phabricator diff by running `arc diff $oldver`.  If there are are
untracked files in the directory the arcanist client gives the message:

8<-8<
You have untracked files in this working copy.

  Working copy: /some/repo

  Untracked changes in working copy:
  (To ignore these 1 change(s), add them to ".git/info/exclude".)
file0
file1
file2

Ignore these 3 untracked file(s) and continue? [y/N]
8<-8<

Suspicious resemblance to what `git status` might give.  If one then goes
to an appropriate version of Phabricator, on the right column between
"Tags" and "Subscribers" will be "Referenced Files".

I have noticed "Referenced Files" appears when untracked files are
present.  Diffs done from repository directories with no untracked files
do not have the "Referenced Files".

As such I reasonably believe arcanist is NOT ignoring these files.  At a
minimum it is uploading metadata about them to Phabricator, at worst it
is uploading them to the server without notification.

Privacy and security violation.  This is visible enough I suspect many
people have already noticed.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Processed (with 1 error): forcibly merging 1019634 1026565 1026601 1026544 1026560 1026578 1026564 1026557 1026550 1026589 1026629

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1019634 1026565 1026601 1026544 1026560 1026578 1026564 1026557 
> 1026550 1026589 1026629
Bug #1019634 [jekyll] jekyll requires liquid gem v4, whereas the archive has 5.4
Unable to merge bugs because:
package of #1026565 is 'src:ruby-jekyll-seo-tag' not 'jekyll'
package of #1026550 is 'src:ruby-jekyll-last-modified-at' not 'jekyll'
package of #1026601 is 'src:ruby-jekyll-feed' not 'jekyll'
package of #1026560 is 'src:ruby-jekyll-asciidoc' not 'jekyll'
package of #1026629 is 'src:ruby-jekyll-commonmark' not 'jekyll'
package of #1026589 is 'src:jekyll-theme-minima' not 'jekyll'
package of #1026557 is 'src:ruby-jekyll-toc' not 'jekyll'
package of #1026544 is 'src:ruby-jekyll-data' not 'jekyll'
package of #1026564 is 'src:ruby-jekyll-polyglot' not 'jekyll'
package of #1026578 is 'src:ruby-jekyll-include-cache' not 'jekyll'
Failed to forcibly merge 1019634: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019634
1026544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026544
1026550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026550
1026557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026557
1026560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026560
1026564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026564
1026565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026565
1026578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026578
1026589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026589
1026601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026601
1026629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1019634 to jekyll

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1019634 jekyll
Bug #1019634 [src:ruby-jekyll-remote-theme] ruby-jekyll-remote-theme: FTBFS: 
ERROR: Test "ruby3.0" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 147 total gem(s) 
(Gem::MissingSpecError)
Bug reassigned from package 'src:ruby-jekyll-remote-theme' to 'jekyll'.
No longer marked as found in versions ruby-jekyll-remote-theme/0.4.3-2.
Ignoring request to alter fixed versions of bug #1019634 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 1019634 to jekyll requires liquid gem v4, whereas the archive has 5.4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1019634 jekyll requires liquid gem v4, whereas the archive has 5.4
Bug #1019634 [jekyll] ruby-jekyll-remote-theme: FTBFS: ERROR: Test "ruby3.0" 
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'liquid' (~> 4.0) among 147 
total gem(s) (Gem::MissingSpecError)
Changed Bug title to 'jekyll requires liquid gem v4, whereas the archive has 
5.4' from 'ruby-jekyll-remote-theme: FTBFS: ERROR: Test "ruby3.0" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in 
activate_dependencies': Could not find 'liquid' (~> 4.0) among 147 total gem(s) 
(Gem::MissingSpecError)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026912: hypre: autopkgtest regularly timeouts on armhf

[Paul Gevers]

Source: hypre
Version: 2.18.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout
Control: found -1 2.25.0-2 2.26.0-2 2.22.1-3

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails regularly on 
armhf. What's worse, it regularly fails because it seems to hang and 
eventually times out due to autopkgtest. Can you please investigate the 
situation and fix it? I copied some of the output at the bottom of this 
report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Also tests that time out (while 
normally running in much less time) are bad for our infrastructure. I 
have added your package to our reject_list and will remove it once this 
bug is closed.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/armhf/h/hypre/29021897/log.gz

Building ij_mv ...
mpicc -o ij_mv ij_mv.o -L/lib -lHYPRE -Wl,-rpath,/lib 
-L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi  -lm
mpicc -I/usr/include/hypre -I/usr/include/superlu 
-I/usr/include/superlu-dist 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -c -o ij_mm.o 
ij_mm.c

Building ij_mm ...
mpicc -o ij_mm ij_mm.o -L/lib -lHYPRE -Wl,-rpath,/lib 
-L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi  -lm
mpicc -I/usr/include/hypre -I/usr/include/superlu 
-I/usr/include/superlu-dist 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi   -c zboxloop.c 
-o zboxloop.obj

Building zboxloop ...
mpicc -o zboxloop zboxloop.obj -L/lib -lHYPRE -Wl,-rpath,/lib 
-L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi  -lm

Running tests for HYPRE
testing began at Mon Dec  5 09:15:39 CST 2022
running TEST_ams ... autopkgtest [12:02:11]: ERROR: timed out on command 
"su -s /bin/bash debci


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1026910: calamares-settings-mobian: file conflicts with calamares-settings-debian

[Andreas Beckmann]

Package: calamares-settings-mobian
Version: 0.2.6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

There are three files in conflict:

  /etc/calamares/modules/mount.conf
  /etc/calamares/modules/unpackfs.conf
  /etc/calamares/settings.conf


>From the attached log (scroll to the bottom...):

  Selecting previously unselected package calamares-settings-mobian.
  Preparing to unpack .../147-calamares-settings-mobian_0.2.6_all.deb ...
  Unpacking calamares-settings-mobian (0.2.6) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-MPIdXZ/147-calamares-settings-mobian_0.2.6_all.deb 
(--unpack):
   trying to overwrite '/etc/calamares/modules/mount.conf', which is also in 
package calamares-settings-debian 12.0.3-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-MPIdXZ/147-calamares-settings-mobian_0.2.6_all.deb


cheers,

Andreas


calamares-settings-debian=12.0.3-1_calamares-settings-mobian=0.2.6.log.gz
Description: application/gzip

Bug#1020042: marked as done (emacs-bind-map: FTBFS: Errors while processing: elpa-evil sbuild-build-depends-main-dummy)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 19:49:50 +
with message-id 
and subject line Bug#1020970: fixed in evil-el 1.14.2-1
has caused the Debian Bug report #1020970,
regarding emacs-bind-map: FTBFS: Errors while processing:  elpa-evil 
sbuild-build-depends-main-dummy
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.)


-- 
1020970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-bind-map
Version: 1.1.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-elpa, elpa-evil, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-elpa, elpa-evil, 
> 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 [382 B]
> Get:5 copy:/<>/apt_archive ./ Packages [463 B]
> Fetched 1802 B in 0s (143 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> The following additional packages will be installed:
>   autoconf automake autopoint autotools-dev bsdextrautils ca-certificates
>   debhelper dh-autoreconf dh-elpa dh-elpa-helper dh-strip-nondeterminism dwz
>   elpa-evil elpa-goto-chg elpa-queue elpa-undo-tree emacs-bin-common
>   emacs-common emacs-el emacs-nox emacsen-common file gettext gettext-base
>   groff-base install-info intltool-debian libapt-pkg-perl libarchive-zip-perl
>   libarray-unique-perl libarray-utils-perl libasound2 libasound2-data
>   libcgi-pm-perl libclass-accessor-perl libconfig-tiny-perl libdbus-1-3
>   libdebhelper-perl libdebian-source-perl libelf1 libencode-locale-perl
>   liberror-perl libexporter-lite-perl libexporter-tiny-perl
>   libfile-find-rule-perl libfile-listing-perl libfile-stripnondeterminism-perl
>   libgccjit0 libgpm2 libhtml-form-perl libhtml-parser-perl libhtml-tagset-perl
>   libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl
>   libhttp-message-perl libhttp-negotiate-perl libicu71 libio-html-perl
>   libio-socket-ssl-perl libio-stringy-perl libjansson4 liblcms2-2
>   liblist-moreutils-perl liblist-moreutils-xs-perl liblwp-mediatypes-perl
>   liblwp-protocol-https-perl libmagic-mgc libmagic1 libnet-http-perl
>   libnet-ssleay-perl libnumber-compare-perl libparse-debcontrol-perl
>   libpipeline1 libregexp-ipv6-perl libsub-install-perl libsub-name-perl
>   libsub-override-perl libtext-glob-perl libtie-ixhash-perl libtimedate-perl
>   libtool libtry-tiny-perl libuchardet0 liburi-perl libwww-mechanize-perl
>   libwww-perl libwww-robotrules-perl libxml2 m4 man-db netbase openssl
>   perl-openssl-defaults po-debconf sensible-utils
> Suggested packages:
>   autoconf-archive gnu-standards autoconf-doc dh-make emacs-common-non-dfsg
>   ncurses-term gettext-doc libasprintf-dev libgettextpo-dev groff
>   libasound2-plugins alsa-utils gpm libdata-dump-perl liblcms2-utils
>   libcrypt-ssleay-perl libtool-doc gfortran | fortran95-compiler gcj-jdk
>   libbusiness-isbn-perl libauthen-ntlm-perl m4-doc apparmor less www-browser
>   libmail-box-perl
> Recommended packages:
>   emacs mailutils curl | wget | lynx alsa-ucm-conf alsa-topology-conf
>   libcgi-fast-perl dbus libarchive-cpio-perl libhtml-format-perl libclone-perl
>   libltdl-dev libdata-dump-perl libhttp-daemon-perl libmailtools-perl
>   libmail-sendmail-perl
> The following NEW packages will be installed:
>   autoconf automake autopoint autotools-dev bsdextrautils ca-certificates
>   debhelper dh-autoreconf dh-elpa dh-elpa-helper dh-strip-nondeterminism dwz
>   elpa-evil elpa-goto-chg elpa-queue elpa-undo-tree emacs-bin-common
>   emacs-common emacs-el emacs-nox emacsen-common file gettext gettext-base
>   

Bug#1017835: marked as done (elpa-evil: emacs 28.1 upgrade fails with byte compiling elpa-evil)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 19:49:50 +
with message-id 
and subject line Bug#1020970: fixed in evil-el 1.14.2-1
has caused the Debian Bug report #1020970,
regarding elpa-evil: emacs 28.1 upgrade fails with byte compiling elpa-evil
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.)


-- 
1020970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-evil
Version: 1.14.0-1
Severity: normal

Dear Maintainer,

Upgrading to emacs-gtk 28.1 fails with byte copiling elpa-evil*

... skipped a lot of successfull byte compiling lines
Install elpa-evil for emacs
install/evil-1.14.0: Handling install of emacsen flavor emacs
install/evil-1.14.0: byte-compiling for emacs
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-command-window.el:36:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-commands.el:29:1: Error: Wrong number of arguments: (3 . 4), 2

In evil-add-to-alist:
evil-common.el:128:18: Warning: ‘evil-add-to-alist’ is an obsolete function
(as of 1.13.1); use ‘evil--add-to-alist’ instead. You may need to
recompile code with evil macros.

In evil-with-view-list:
evil-common.el:3922:11: Warning: docstring wider than 80 characters

In toplevel form:
evil-core.el:181:31: Warning: defcustom for ‘evil-mode’ fails to specify
containing group
evil-core.el:181:31: Warning: defcustom for ‘evil-mode’ fails to specify
containing group

In toplevel form:
evil-ex.el:596:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-integration.el:35:1: Error: Wrong number of arguments: (3 . 4), 2

In toplevel form:
evil-jumps.el:38:1: Warning: custom-declare-variable
`evil-jumps-cross-buffers' docstring wider than 80 characters
evil-jumps.el:58:1: Warning: custom-declare-variable
`evil-jumps-ignored-file-patterns' docstring wider than 80 characters
evil-jumps.el:71:1: Warning: defvar `evil--jumps-buffer-targets' docstring
wider than 80 characters
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-keybindings.el:35:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-maps.el:29:1: Error: Wrong number of arguments: (3 . 4), 2

In evil-repeat-force-abort-p:
evil-repeat.el:242:8: Warning: docstring wider than 80 characters

In evil-repeat-motion:
evil-repeat.el:349:8: Warning: docstring wider than 80 characters
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-search.el:30:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil.el:133:1: Error: Wrong number of arguments: (3 . 4), 2
ERROR: install script from elpa-evil package failed
dpkg: erreur de traitement du paquet emacs-gtk (--configure) :
 installed emacs-gtk package post-installation script subprocess returned error 
exit status 1

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-evil depends on:
ii  dh-elpa-helper 2.0.10
ii  elpa-goto-chg  1.7.3-1
ii  elpa-undo-tree 0.8.1-1
iu  emacs  1:28.1+1-2
ih  emacs-gtk [emacs]  1:28.1+1-2
ii  emacsen-common 3.0.4

Versions of packages elpa-evil recommends:
iu  emacs  1:28.1+1-2
ih  emacs-gtk [emacs]  1:28.1+1-2

elpa-evil suggests no packages.

-- no debconf information
--- End Message ---
--- 

Bug#1020970: marked as done (elpa-evil: fails to install: wrong-number-of-arguments)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 19:49:50 +
with message-id 
and subject line Bug#1020970: fixed in evil-el 1.14.2-1
has caused the Debian Bug report #1020970,
regarding elpa-evil: fails to install: wrong-number-of-arguments
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.)


-- 
1020970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-evil
Version: 1.14.0-1
Severity: grave
Justification: non-installable

Hi!
I'm afraid your package fails to install:

Setting up elpa-evil (1.14.0-1) ...
tsort: -: input contains a loop:
tsort: emacsen-common
tsort: elpa-goto-chg
tsort: -: input contains a loop:
tsort: elpa-undo-tree
tsort: emacsen-common
Install elpa-queue for emacs
install/queue-0.2: Handling install of emacsen flavor emacs
install/queue-0.2: byte-compiling for emacs
Install elpa-undo-tree for emacs
install/undo-tree-0.8.1: Handling install of emacsen flavor emacs
install/undo-tree-0.8.1: byte-compiling for emacs
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install elpa-goto-chg for emacs
install/goto-chg-1.7.3: Handling install of emacsen flavor emacs
install/goto-chg-1.7.3: byte-compiling for emacs
Install elpa-evil for emacs
install/evil-1.14.0: Handling install of emacsen flavor emacs
install/evil-1.14.0: byte-compiling for emacs
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-command-window.el:36:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-commands.el:29:1: Error: Wrong number of arguments: (3 . 4), 2

In evil-add-to-alist:
evil-common.el:128:18: Warning: ‘evil-add-to-alist’ is an obsolete function
(as of 1.13.1); use ‘evil--add-to-alist’ instead. You may need to
recompile code with evil macros.

In evil-with-view-list:
evil-common.el:3922:11: Warning: docstring wider than 80 characters

In toplevel form:
evil-core.el:181:31: Warning: defcustom for ‘evil-mode’ fails to specify
containing group
evil-core.el:181:31: Warning: defcustom for ‘evil-mode’ fails to specify
containing group

In toplevel form:
evil-ex.el:596:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-integration.el:35:1: Error: Wrong number of arguments: (3 . 4), 2

In toplevel form:
evil-jumps.el:38:1: Warning: custom-declare-variable
`evil-jumps-cross-buffers' docstring wider than 80 characters
evil-jumps.el:58:1: Warning: custom-declare-variable
`evil-jumps-ignored-file-patterns' docstring wider than 80 characters
evil-jumps.el:71:1: Warning: defvar `evil--jumps-buffer-targets' docstring
wider than 80 characters
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-keybindings.el:35:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-maps.el:29:1: Error: Wrong number of arguments: (3 . 4), 2

In evil-repeat-force-abort-p:
evil-repeat.el:242:8: Warning: docstring wider than 80 characters

In evil-repeat-motion:
evil-repeat.el:349:8: Warning: docstring wider than 80 characters
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil-search.el:30:1: Error: Wrong number of arguments: (3 . 4), 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
evil.el:133:1: Error: Wrong number of arguments: (3 . 4), 2
ERROR: install script from elpa-evil package failed
dpkg: error processing package elpa-evil (--configure):
 installed elpa-evil package post-installation script subprocess returned error 
exit status 1


Meow!
-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign 

Bug#1004813: marked as done (retroarch: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 19:17:23 +
with message-id 
and subject line Fixed in 1.13.0
has caused the Debian Bug report #1004813,
regarding retroarch: FTBFS with ffmpeg 5.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1004813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: retroarch
Version: 1.7.3+dfsg1-1.1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

retroarch FTBFS with ffmpeg 5.0 in experimental:

MOC ui/drivers/qt/ui_qt_load_core_window.h
CXX obj-unix/release/ui/drivers/moc_ui_qt.cpp
record/drivers/record_ffmpeg.c: In function ‘ffmpeg_init_audio’:
record/drivers/record_ffmpeg.c:321:37: warning: initialization discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  321 |AVCodec *codec = avcodec_find_encoder_by_name(
  | ^~~~
record/drivers/record_ffmpeg.c: In function ‘ffmpeg_init_video’:
record/drivers/record_ffmpeg.c:410:13: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  410 |   codec = avcodec_find_encoder_by_name(params->vcodec);
  | ^
record/drivers/record_ffmpeg.c:415:13: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  415 |   codec = avcodec_find_encoder_by_name("libx264rgb");
  | ^
record/drivers/record_ffmpeg.c:525:11: warning: implicit declaration of 
function ‘avpicture_get_size’ [-Wimplicit-function-declaration]
  525 |size = avpicture_get_size(video->pix_fmt, param->out_width,
  |   ^~
record/drivers/record_ffmpeg.c:530:4: warning: implicit declaration of function 
‘avpicture_fill’ [-Wimplicit-function-declaration]
  530 |avpicture_fill((AVPicture*)video->conv_frame, video->conv_frame_buf,
  |^~
record/drivers/record_ffmpeg.c:530:20: error: ‘AVPicture’ undeclared (first use 
in this function); did you mean ‘AVPictureType’?
  530 |avpicture_fill((AVPicture*)video->conv_frame, video->conv_frame_buf,
  |^
  |AVPictureType
record/drivers/record_ffmpeg.c:530:20: note: each undeclared identifier is 
reported only once for each function it appears in
record/drivers/record_ffmpeg.c:530:30: error: expected expression before ‘)’ 
token
  530 |avpicture_fill((AVPicture*)video->conv_frame, video->conv_frame_buf,
  |  ^
record/drivers/record_ffmpeg.c: In function ‘ffmpeg_init_muxer_pre’:
record/drivers/record_ffmpeg.c:622:18: error: ‘AVFormatContext’ has no member 
named ‘filename’
  622 |av_strlcpy(ctx->filename, handle->params.filename, 
sizeof(ctx->filename));
  |  ^~
record/drivers/record_ffmpeg.c:622:65: error: ‘AVFormatContext’ has no member 
named ‘filename’
  622 |av_strlcpy(ctx->filename, handle->params.filename, 
sizeof(ctx->filename));
  | ^~
record/drivers/record_ffmpeg.c:627:47: error: ‘AVFormatContext’ has no member 
named ‘filename’
  627 |   ctx->oformat = av_guess_format(NULL, ctx->filename, NULL);
  |   ^~
record/drivers/record_ffmpeg.c:632:31: error: ‘AVFormatContext’ has no member 
named ‘filename’
  632 |if (avio_open(>pb, ctx->filename, AVIO_FLAG_WRITE) < 0)
  |   ^~
record/drivers/record_ffmpeg.c: In function ‘ffmpeg_init_muxer_post’:
record/drivers/record_ffmpeg.c:647:10: error: ‘AVStream’ has no member named 
‘codec’
  647 |stream->codec = handle->video.codec;
  |  ^~
record/drivers/record_ffmpeg.c:648:30: error: ‘AVStream’ has no member named 
‘codec’
  648 |stream->time_base = stream->codec->time_base;
  |  ^~
record/drivers/record_ffmpeg.c:657:13: error: ‘AVStream’ has no member named 
‘codec’
  657 |   stream->codec = handle->audio.codec;
  | ^~
record/drivers/record_ffmpeg.c:658:33: error: ‘AVStream’ has no member named 
‘codec’
  658 |   stream->time_base = stream->codec->time_base;
  | ^~
record/drivers/record_ffmpeg.c: In function ‘ffmpeg_new’:
record/drivers/record_ffmpeg.c:790:4: warning: implicit declaration of function 
‘av_register_all’ [-Wimplicit-function-declaration]
  790 |av_register_all();
  |

Processed: Re: fastnetmon: FTBFS with grpc 1.51+

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025490 [src:fastnetmon] fastnetmon: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'

-- 
1025490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: llvm-toolchain-15: FTBFS with grpc 1.51+

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025530 [src:llvm-toolchain-15] llvm-toolchain-15: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'

-- 
1025530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: llvm-toolchain-14: FTBFS with grpc 1.51+

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025529 [src:llvm-toolchain-14] llvm-toolchain-14: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'

-- 
1025529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: open-vm-tools: FTBFS with grpc 1.51+

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025491 [src:open-vm-tools] open-vm-tools: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'

-- 
1025491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026771: misspell-fixer: flaky autopkgtest

[Paul Gevers]

Hi Lajos,

On 23-12-2022 00:58, Lajos Veres wrote:

How can I test my changes on the below infrastructure?


Once your package is uploaded to the archive, the test will be run 
automatically. If you have a salsa account, you can also trigger tests 
yourself.



Does https://mentors.debian.net/ run those tests?


I'm not aware that it does.


Or is this something different?


I don't understand this question. ci.debian.net runs autopkgtest on 
request of humans and of some tools. One of the tools that triggers 
tests is the migration software of the release team. Does that answer 
your question?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:cvise: fails to migrate to testing for too long: FTBFS on mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.6.0-1
Bug #1026909 [src:cvise] src:cvise: fails to migrate to testing for too long: 
FTBFS on mipsel
Marked as fixed in versions cvise/2.6.0-1.
Bug #1026909 [src:cvise] src:cvise: fails to migrate to testing for too long: 
FTBFS on mipsel
Marked Bug as done

-- 
1026909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026909: src:cvise: fails to migrate to testing for too long: FTBFS on mipsel

[Paul Gevers]

Source: cvise
Version: 2.5.0-1
Severity: serious
Control: close -1 2.6.0-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:cvise has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on mipsel, where it successfully built in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=cvise



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1026582: marked as done (python-apsw: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 18:34:56 +
with message-id 
and subject line Bug#1026582: fixed in python-apsw 3.40.0.0-2
has caused the Debian Bug report #1026582,
regarding python-apsw: FTBFS: ModuleNotFoundError: No module named 'setuptools'
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.)


-- 
1026582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-apsw
Version: 3.40.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 18, in 
> from setuptools import setup, Extension, Command
> ModuleNotFoundError: No module named 'setuptools'
> E: pybuild pybuild:386: clean: plugin distutils failed with: exit code=1: 
> python3.11 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.11 3.10" 
> returned exit code 13
> make: *** [debian/rules:12: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/python-apsw_3.40.0.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-apsw
Source-Version: 3.40.0.0-2
Done: Joel Rosdahl 

We believe that the bug you reported is fixed in the latest version of
python-apsw, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joel Rosdahl  (supplier of updated python-apsw 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, 23 Dec 2022 19:19:32 +0100
Source: python-apsw
Architecture: source
Version: 3.40.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Joel Rosdahl 
Changed-By: Joel Rosdahl 
Closes: 1026582
Changes:
 python-apsw (3.40.0.0-2) unstable; urgency=medium
 .
   * Update Standards-Version to 4.6.2 with no changes
   * Add build dependency on python3-setuptools (closes: #1026582)
Checksums-Sha1:
 c939675516ba7653115896cdbfc24b6234f8a3d8 1857 python-apsw_3.40.0.0-2.dsc
 8e5626e44cf7955f88ff57ba03c05d5c26a44057 5040 
python-apsw_3.40.0.0-2.debian.tar.xz
 74bf65a9eb944a2f656336049f048ae5db6b4460 11800 
python-apsw_3.40.0.0-2_amd64.buildinfo
Checksums-Sha256:
 59458c6ced34fcb48c8ce6bd3a9a6af46b48ef33e3d96f6ec2d406e60ffc0776 1857 
python-apsw_3.40.0.0-2.dsc
 f88c9b626189d68171690e0bcccef7041060845aa048951cc4789a1e435de0d4 5040 
python-apsw_3.40.0.0-2.debian.tar.xz
 fe3153020724bdd92053e5b38fe715aa42af868d46ae9f5bf3f7d31af5434c7f 11800 
python-apsw_3.40.0.0-2_amd64.buildinfo
Files:
 e6a8b73b85f82b7016c1b45f4a8fb4c2 1857 python optional 
python-apsw_3.40.0.0-2.dsc
 03178d08c08b77730b28b42680557f8b 5040 python optional 
python-apsw_3.40.0.0-2.debian.tar.xz
 14e9679e1ac32a2d9ac2d07e4f1f9371 11800 python optional 
python-apsw_3.40.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWpOacaRnks9XhmpRmW3aB1WUrbgFAmOl8VkACgkQmW3aB1WU
rbgeZRAAgwdq3Yy0uv3RgdN91HkkzNw2wEz3lPwA+aad4kDnJ/e7t3Bv+dpCHBgM
iBB/lhkV0nlGqWBrY4lcSR1kl3CCsJvlG0OYlN/Ng1qYaVPSv6h9PH7nQawCJeGb
LoWQJZzrg5A4BBSCngsd1odTa9yA8VCmQqbLaziK8n9Up6oDPH1D0TFkYGIJlg1B

Bug#1026897: marked as done (ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 18:22:03 +
with message-id 
and subject line Bug#1026897: fixed in ruby-tilt 2.0.11-2
has caused the Debian Bug report #1026897,
regarding ruby-tilt: FTBFS: ERROR: Test "ruby3.1" 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.)


-- 
1026897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-tilt
Version: 2.0.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

After updating ruby-haml to 6.1.1, ruby-tilt fails to build with a test
failure.

Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-tilt/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"tilt\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-tilt/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/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
> Tilt::AsciidoctorTemplate (disabled)
> Tilt::BlueClothTemplate (disabled)
> Tilt::BuilderTemplate (disabled)
> Tilt::CoffeeScriptTemplate (disabled)
> Tilt::CommonMarkerTemplate (disabled)
> /<>/test/tilt_compilesite_test.rb:40: warning: assigned but 
> unused variable - res
> /usr/share/rubygems-integration/all/gems/creole-0.5.0/lib/creole/parser.rb:255:
>  warning: character class has duplicated range: /\A([:alpha:]|[:digit:])+/
> Tilt::ErubiTemplate (disabled)
> Tilt::KramdownTemplate (disabled)
> Tilt::LessTemplate (disabled)
> Tilt::LiquidTemplate (disabled)
> Tilt::LiveScriptTemplate (disabled)
> /<>/test/tilt_markaby_test.rb:51: warning: assigned but unused 
> variable - eval_scope
> Tilt::MarkabyTemplate (disabled)
> /<>/test/tilt_markdown_test.rb:85: warning: assigned but unused 
> variable - boom
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85:
>  warning: possibly useless use of a variable in void context
> 

Bug#1026869: marked as done (lua-nvim: flaky autopkgtest: times out on ppc64el and s390x)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 18:20:40 +
with message-id 
and subject line Bug#1026869: fixed in lua-nvim 0.2.4-1-1
has caused the Debian Bug report #1026869,
regarding lua-nvim: flaky autopkgtest: times out on ppc64el and s390x
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.)


-- 
1026869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: lua-nvim
Version: 0.2.2-1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky timeout
Control: found -1 0.2.3-1-1

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on s390x and ppc64el due to an autopkgtest 
timeout after 2 hours and 47 minutes, while a successful run only takes 
about a minute.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/l/lua-nvim/testing/ppc64el/
https://ci.debian.net/packages/l/lua-nvim/testing/s390x/
https://ci.debian.net/packages/l/lua-nvim/stable/ppc64el/
https://ci.debian.net/packages/l/lua-nvim/stable/s390x/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/l/lua-nvim/26699552/log.gz
* lua dynamic custom (5.1, autopkgtest) **
[==] Running tests from scanned files.
[--] Global test environment setup.
[--] Running tests from test/session_spec.lua
[ RUN  ] test/session_spec.lua @ 38: Session using ChidProcessStream 
can make requests to nvim
[   OK ] test/session_spec.lua @ 38: Session using ChidProcessStream 
can make requests to nvim (7.88 ms)
[ RUN  ] test/session_spec.lua @ 43: Session using ChidProcessStream 
can get api metadata
autopkgtest [13:07:01]: ERROR: timed out on command "su -s /bin/bash 
debci [...]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: lua-nvim
Source-Version: 0.2.4-1-1
Done: James McCoy 

We believe that the bug you reported is fixed in the latest version of
lua-nvim, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated lua-nvim 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, 23 Dec 2022 12:49:30 -0500
Source: lua-nvim
Architecture: source
Version: 0.2.4-1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: James McCoy 
Closes: 1026869
Changes:
 lua-nvim (0.2.4-1-1) unstable; urgency=medium
 .
   * New upstream release
   * Declare compliance with Policy 4.6.2, no changes needed
   * Use debian/clean to declare required cleanup
   * Annotate neovim Build-Depends as 
   * Remove libkvm-dev Build-Depends now that libuv1-dev has it
   * autopkgtest:
 - Limit autopkgtest runtime to 5 minutes
 - Skip the test if it times out (Closes: #1026869)
Checksums-Sha1:
 59f36e6dd09082cc7c500995aa07611c45a8 2434 lua-nvim_0.2.4-1-1.dsc
 7a3b159ca7cb8e5e591be07fb9b685c0cda064d3 13715 lua-nvim_0.2.4-1.orig.tar.gz
 c9196c35e026a6c09a871ac87f97b2c57816e865 3068 lua-nvim_0.2.4-1-1.debian.tar.xz
Checksums-Sha256:
 20ee39b21b596dc1fe555a4cd16f4981fe122e7e071b2b7df6d86a93c3e29bb2 2434 
lua-nvim_0.2.4-1-1.dsc
 2edf991ca2d8dcaac664e06bab08c9aba4b624e6c09a3b6692fe9e0c64a5616a 13715 
lua-nvim_0.2.4-1.orig.tar.gz
 d1b43c4b3b065c095b122ebe35720d259946ca3e846bd14aeb547ffb342a637c 3068 
lua-nvim_0.2.4-1-1.debian.tar.xz
Files:
 162d1440d762df97f50a2fa0b2ae1423 2434 interpreters optional 
lua-nvim_0.2.4-1-1.dsc
 5fb84cac6d4d9b0223d39bfb9d5f8497 13715 interpreters optional 
lua-nvim_0.2.4-1.orig.tar.gz
 77f1d7ea10c4d0e60f8c089fbafc1c92 3068 interpreters optional 
lua-nvim_0.2.4-1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: Bug#1026897 marked as pending in ruby-tilt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026897 [src:ruby-tilt] ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.
Added tag(s) pending.

-- 
1026897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026897: marked as pending in ruby-tilt

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #1026897 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/4990458cf7b824ae7bc0cb7b9562a7f27ff78017


Add patch to remove warnings with ruby-haml >= 6

Closes: #1026897


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026897

Bug#1020851: marked as done (elpa-ement: fails to install along emacs)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 10:52:01 -0700
with message-id <871qoq9fem@melete.silentflame.com>
and subject line Re: Bug#1020851: elpa-ement: fails to install along emacs
has caused the Debian Bug report #1020851,
regarding elpa-ement: fails to install along emacs
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.)


-- 
1020851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-ement
Version: 0.1.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

This is the failure when installing the package along emacs 27 in bookworm.
(In sid there is currently a different error that is likely caused by
emacs 28 and hides this problem.)

>From the attached log (scroll to the bottom...):

  Setting up elpa-ement (0.1.4-1) ...
  Install elpa-magit-section for emacs
  install/magit-section-3.3.0: Handling install of emacsen flavor emacs
  install/magit-section-3.3.0: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-svg-lib for emacs
  install/svg-lib-0.2.5: Handling install of emacsen flavor emacs
  install/svg-lib-0.2.5: byte-compiling for emacs
  Install elpa-taxy for emacs
  install/taxy-0.10: Handling install of emacsen flavor emacs
  install/taxy-0.10: byte-compiling for emacs
  Install elpa-plz for emacs
  install/plz-0.2: Handling install of emacsen flavor emacs
  install/plz-0.2: byte-compiling for emacs
  Install elpa-taxy-magit-section for emacs
  install/taxy-magit-section-0.9.1: Handling install of emacsen flavor emacs
  install/taxy-magit-section-0.9.1: byte-compiling for emacs
  Install elpa-ement for emacs
  install/ement-0.1.4: Handling install of emacsen flavor emacs
  install/ement-0.1.4: byte-compiling for emacs
  
  In ement--xml-escape-string:
  ement-lib.el:1113:8:Warning: xml-escape-string called with 2 arguments, but
  accepts only 1
  
  In end of data:
  ement-lib.el:1227:1:Warning: the following functions are not known to be
  defined: color-dark-p, button-buttonize
  
  In toplevel form:
  ement-notify.el:34:1:Error: Cannot open load file: No such file or directory, 
transient
  
  In toplevel form:
  ement-room-list.el:48:1:Error: Cannot open load file: No such file or 
directory, transient
  
  In toplevel form:
  ement-room.el:2443:1:Warning: Unused lexical variable `room-buffer'
  ement-room.el:4084:1:Error: Cannot open load file: No such file or directory, 
transient
  
  In toplevel form:
  ement-taxy.el:34:1:Error: Cannot open load file: No such file or directory, 
transient
  
  In toplevel form:
  ement.el:62:1:Error: Cannot open load file: No such file or directory, 
transient
  ERROR: install script from elpa-ement package failed
  dpkg: error processing package elpa-ement (--configure):
   installed elpa-ement package post-installation script subprocess returned 
error exit status 1
  Processing triggers for install-info (6.8-6) ...
  Errors were encountered while processing:
   elpa-ement


cheers,

Andreas


elpa-ement=0.1.4-1_emacs.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.1.4-1

Hello,

On Wed 28 Sep 2022 at 07:55AM -07, Sean Whitton wrote:

> Hello,
>
> On Tue 27 Sep 2022 at 05:09PM +02, Andreas Beckmann wrote:
>
>> Package: elpa-ement
>> Version: 0.1.4-1
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: piuparts
>>
>> Hi,
>>
>> during a test with piuparts I noticed your package failed to install. As
>> per definition of the release team this makes the package too buggy for
>> a release, thus the severity.
>>
>> This is the failure when installing the package along emacs 27 in bookworm.
>> (In sid there is currently a different error that is likely caused by
>> emacs 28 and hides this problem.)
>
> transient is included in Emacs 28 so I'm inclined to leave this to fix
> itself when Emacs 28 migrates.

This is fixed now.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#984274: marked as done (openclonk: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:20:56 +
with message-id 
and subject line Bug#984274: fixed in openclonk 8.1-3
has caused the Debian Bug report #984274,
regarding openclonk: 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.)


-- 
984274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openclonk
Version: 8.1-2
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/openclonk_8.1-2_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.

[...]
/<>/src/script/C4AulCompiler.cpp:1100:31: warning: this statement 
may fall through [-Wimplicit-fallthrough=]
 1100 | AddBCC(n->loc, AB_CFUNCTION, 
reinterpret_cast(v._getFunction()));
  | 
~~^~~~
/<>/src/script/C4AulCompiler.cpp:1101:17: note: here
 1101 | default:
  | ^~~
make[3]: Leaving directory '/<>/build'
[ 15%] Built target c4group
[ 17%] Building CXX object CMakeFiles/libc4script.dir/src/script/C4AulFunc.cpp.o
/usr/bin/c++ -DCOMPILED_AS_C4LIBRARY -DHAVE_CONFIG_H -DNDEBUG 
-DOC_SYSTEM_DATA_DIR=\"/usr/share/games/openclonk\" -I/<>/build 
-I/<> -I/<>/build/libc4script_autogen/include 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/<>/src 
-isystem /usr/include/SDL2 -isystem /<>/thirdparty -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall 
-Wextra -Wredundant-decls -Wendif-labels -Wpointer-arith -Wcast-qual 
-Wcast-align -Wwrite-strings -Winit-self -Wsign-promo -Wno-reorder 
-Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wformat-security 
-std=gnu++14 -o CMakeFiles/libc4script.dir/src/script/C4AulFunc.cpp.o -c 
/<>/src/script/C4AulFunc.cpp
/<>/src/script/C4AulExec.cpp: In member function ‘void 
C4AulProfiler::Show()’:
/<>/src/script/C4AulExec.cpp:1004:36: warning: typedef ‘EntryList’ 
locally defined but not used [-Wunused-local-typedefs]
 1004 | typedef std::vector EntryList;
  |^
[ 17%] Building CXX object CMakeFiles/libc4script.dir/src/script/C4AulLink.cpp.o
/usr/bin/c++ -DCOMPILED_AS_C4LIBRARY -DHAVE_CONFIG_H -DNDEBUG 
-DOC_SYSTEM_DATA_DIR=\"/usr/share/games/openclonk\" -I/<>/build 
-I/<> -I/<>/build/libc4script_autogen/include 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/<>/src 
-isystem /usr/include/SDL2 -isystem /<>/thirdparty -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -Wall 
-Wextra -Wredundant-decls -Wendif-labels -Wpointer-arith -Wcast-qual 
-Wcast-align -Wwrite-strings -Winit-self -Wsign-promo -Wno-reorder 
-Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wformat-security 
-std=gnu++14 -o CMakeFiles/libc4script.dir/src/script/C4AulLink.cpp.o -c 
/<>/src/script/C4AulLink.cpp
[ 17%] Building CXX object 
CMakeFiles/libc4script.dir/src/script/C4AulParse.cpp.o
/usr/bin/c++ -DCOMPILED_AS_C4LIBRARY 

Bug#1026198: marked as done (ruby-webpack-rails: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-webpack-rails: FTBFS in bookworm (missing build-depends on 
tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-webpack-rails
Version: 0.9.11+git-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby

[... snipped ...]


TZInfo::DataSourceNotFound:
  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# /<>/spec/spec_helper.rb:13:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# /<>/spec/manifest_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.

Finished in 0.7 seconds (files took 1.34 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/ruby-webpack-rails-0.9.11\+git/debian/ruby-webpack-rails returned 
exit code 1
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot 

Bug#1026197: marked as done (ruby-webpacker: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-webpacker: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-webpacker
Version: 5.4.3-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-webpacker/ -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from /<>/test/test_app/config/environment.rb:4:in `'
from /<>/test/test_helper.rb:7:in `require_relative'
from /<>/test/test_helper.rb:7:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/command_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/command_test.rb" 
"test/compiler_test.rb" "test/configuration_test.rb" "test/dev_server_test.rb" "test/env_test.rb" "test/helper_test.rb" 
"test/manifest_test.rb" "test/rake_tasks_test.rb" "test/webpacker_test.rb"  -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-webpacker returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

Bug#1026196: marked as done (ruby-voight-kampff: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-voight-kampff: FTBFS in bookworm (missing build-depends on 
tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-voight-kampff
Version: 1.1.3-4
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-voight-kampff/ -i -O--buildsystem=ruby

[... snipped ...]

# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
# ./spec/spec_helper.rb:6:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/lib/voight_kampff_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.

Finished in 0.6 seconds (files took 0.86722 seconds to load)
0 examples, 0 failures, 4 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 

Bug#1026195: marked as done (ruby-sprockets-rails: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-sprockets-rails: FTBFS in bookworm (missing build-depends on 
tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-sprockets-rails
Version: 3.4.1-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-sprockets-rails/ -i 
-O--buildsystem=ruby

[... snipped ...]

TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'

/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
/usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/test/test_quiet_assets.rb:28:in `setup'

rails test <>/test/test_quiet_assets.rb:42


Finished in 7.276513s, 22.5383 runs/s, 92.9016 assertions/s.
164 runs, 676 assertions, 0 failures, 29 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/test_asset_url_processor.rb" "test/test_helper.rb" "test/test_quiet_assets.rb" "test/test_railtie.rb" 
"test/test_sourcemapping_url_processor.rb" "test/test_task.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-sprockets-rails returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 

Bug#1026194: marked as done (ruby-sassc-rails: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-sassc-rails: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-sassc-rails
Version: 2.1.2-6
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-sassc-rails/ -i -O--buildsystem=ruby

[... snipped ...]

railties (6.1.7) lib/rails/railtie.rb:207:in `method_missing'
<>/test/sassc_rails_test.rb:43:in `initialize!'
<>/test/sassc_rails_test.rb:122:in 
`test_sass_imports_work_correctly'
minitest (5.14.2) lib/minitest/test.rb:98:in `block (3 levels) in run'
minitest (5.14.2) lib/minitest/test.rb:195:in `capture_exceptions'
minitest (5.14.2) lib/minitest/test.rb:95:in `block (2 levels) in run'
minitest (5.14.2) lib/minitest.rb:272:in `time_it'
minitest (5.14.2) lib/minitest/test.rb:94:in `block in run'
minitest (5.14.2) lib/minitest.rb:367:in `on_signal'
minitest (5.14.2) lib/minitest/test.rb:211:in `with_info_handler'
minitest (5.14.2) lib/minitest/test.rb:93:in `run'
minitest (5.14.2) lib/minitest.rb:1029:in `run_one_method'
minitest (5.14.2) lib/minitest.rb:341:in `run_one_method'
minitest (5.14.2) lib/minitest.rb:328:in `block (2 levels) in run'
minitest (5.14.2) lib/minitest.rb:327:in `each'
minitest (5.14.2) lib/minitest.rb:327:in `block in run'
minitest (5.14.2) lib/minitest.rb:367:in `on_signal'
minitest (5.14.2) lib/minitest.rb:354:in `with_info_handler'
minitest (5.14.2) lib/minitest.rb:326:in `run'
minitest (5.14.2) lib/minitest.rb:164:in `block in __run'
minitest (5.14.2) lib/minitest.rb:164:in `map'
minitest (5.14.2) lib/minitest.rb:164:in `__run'
minitest (5.14.2) lib/minitest.rb:141:in `run'
minitest (5.14.2) lib/minitest.rb:68:in `block in autorun'

rails test /<>/test/sassc_rails_test.rb:120


Finished in 0.144429s, 138.4761 runs/s, 0. assertions/s.
20 runs, 0 assertions, 0 failures, 18 errors, 2 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/sassc_rails_test.rb" "test/test_helper.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-sassc-rails returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-tzinfo
Source-Version: 2.0.5-1
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-tzinfo, which is due to be installed in the Debian FTP 

Bug#1026193: marked as done (ruby-rails-controller-testing: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-rails-controller-testing: FTBFS in bookworm (missing 
build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-rails-controller-testing
Version: 1.0.5-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-rails-controller-testing/ -i 
-O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from /<>/test/dummy/config/environment.rb:5:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/test_helper.rb:4:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/controllers/assigns_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/controllers/assigns_test.rb" 
"test/controllers/template_assertions_test.rb" "test/helpers/template_assertions_test.rb" 
"test/integration/template_assertions_test.rb" "test/test_helper.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-rails-controller-testing returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

Bug#1026191: marked as done (ruby-omniauth-rails-csrf-protection: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-omniauth-rails-csrf-protection: FTBFS in bookworm (missing 
build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-omniauth-rails-csrf-protection
Version: 1.0.1-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-omniauth-rails-csrf-protection/ -i 
-O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/test_helper.rb:56:in `'
from /<>/test/test_helper.rb:34:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/application_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
Running test against Rails 6.1.7
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/application_test.rb" "test/test_helper.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-omniauth-rails-csrf-protection returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the 

Bug#1026192: marked as done (ruby-pry-rails: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-pry-rails: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-pry-rails
Version: 0.3.9-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-pry-rails/ -i -O--buildsystem=ruby

[... snipped ...]

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/spec/config/environment.rb:23:in `'
:85:in 
`require'
:85:in 
`require'
/<>/debian/ruby-tests.rake:25:in `block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'

Caused by:
TZInfo::DataSources::ZoneinfoDirectoryNotFound: None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `new'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/spec/config/environment.rb:23:in `'
:85:in 
`require'
:85:in 
`require'
/<>/debian/ruby-tests.rake:25:in `block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test => console => development_env
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-pry-rails returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About 

Bug#1026190: marked as done (ruby-joiner: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-joiner: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-joiner
Version: 0.6.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-joiner/ -i -O--buildsystem=ruby

[... snipped ...]

# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
# ./spec/spec_helper.rb:7:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/acceptance/paths_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.


Finished in 0.6 seconds (files took 0.81624 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-joiner 
returned exit 

Bug#1026189: marked as done (ruby-invisible-captcha: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-invisible-captcha: FTBFS in bookworm (missing build-depends on 
tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-invisible-captcha
Version: 1.1.0-5
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-invisible-captcha/ -i 
-O--buildsystem=ruby

[... snipped ...]

An error occurred while loading spec_helper.
Failure/Error: Rails.application.initialize!

TZInfo::DataSourceNotFound:
  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# ./spec/dummy/config/environment.rb:5:in `'
# ./spec/spec_helper.rb:5:in `'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.
No examples found.


Finished in 0.7 seconds (files took 0.90923 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Finished in 0.7 seconds (files took 0.90923 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples


/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-invisible-captcha returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide 

Bug#1026186: marked as done (ruby-factory-bot-rails: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-factory-bot-rails: FTBFS in bookworm (missing build-depends on 
tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-factory-bot-rails
Version: 6.2.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-factory-bot-rails/ -i 
-O--buildsystem=ruby

[... snipped ...]

  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# ./spec/fake_app.rb:12:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/spec_helper.rb:6:in `'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.
No examples found.


Finished in 0.00012 seconds (files took 0.75777 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Finished in 0.00012 seconds (files took 0.75777 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples


/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-factory-bot-rails returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build 

Bug#1026188: marked as done (ruby-haml: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-haml: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-haml
Version: 5.2.2-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
yard && mv doc yardoc
[warn]: @param tag has unknown parameter name: new
in file `lib/haml/parser.rb' near line 215
[warn]: @param tag has unknown parameter name: old

[... snipped ...]

from debian/ruby-tests.rb:7:in `'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize': None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories. (TZInfo::DataSources::ZoneinfoDirectoryNotFound)
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `new'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/test_helper.rb:32:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/attribute_parser_test.rb:3:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from debian/ruby-tests.rb:7:in `block in '
from debian/ruby-tests.rb:7:in `each'
from debian/ruby-tests.rb:7:in `'
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-haml 
returned exit code 1
make[1]: *** [debian/rules:15: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

Bug#1026187: marked as done (ruby-globalid: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-globalid: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-globalid
Version: 0.6.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-globalid/ -i -O--buildsystem=ruby

[... snipped ...]

Error:
RailtieTest#test_GlobalID.app_for_Blog::Application_defaults_to_blog:
TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install
test/cases/railtie_test.rb:22:in `block in '

rails test test/cases/railtie_test.rb:21

E

Error:
RailtieTest#test_SignedGlobalID.verifier_defaults_to_Blog::Application.message_verifier(:signed_global_ids)_when_secret_key_base_is_present:
TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install
test/cases/railtie_test.rb:62:in `block in '

rails test test/cases/railtie_test.rb:61

E

Error:
RailtieTest#test_SignedGlobalID.verifier_can_be_set_with_config.global_id.verifier_=:
TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install
test/cases/railtie_test.rb:82:in `block in '

rails test test/cases/railtie_test.rb:80



Finished in 0.585726s, 230.4834 runs/s, 402.9191 assertions/s.
135 runs, 236 assertions, 0 failures, 8 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/cases/global_id_test.rb" "test/cases/global_identification_test.rb" "test/cases/global_locator_test.rb" 
"test/cases/railtie_test.rb" "test/cases/signed_global_id_test.rb" "test/cases/uri_gid_test.rb" 
"test/cases/verifier_test.rb" ]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-globalid 
returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-tzinfo
Source-Version: 2.0.5-1
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-tzinfo, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution 

Bug#1026182: marked as done (ruby-browser: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-browser: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-browser
Version: 4.2.0-3
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/sample_app.rb:55:in `'
from 
:148:in 
`require'
from 
:148:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
from /<>/test/middleware_test.rb:5:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
Coverage report generated for Unit Tests to /<>/coverage. 768 / 
1256 LOC (61.15%) covered.
rake aborted!
Command failed with status (1): [ruby -w -I"lib:lib:test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/browser_test.rb" 
"test/middleware_test.rb" "test/rails_test.rb" ]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-browser 
returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 

Bug#1026185: marked as done (ruby-enumerize: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-enumerize: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-enumerize
Version: 2.5.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-enumerize/ -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/test_helper.rb:26:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/activemodel_test.rb:3:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/activemodel_test.rb" "test/activerecord_test.rb" 
"test/attribute_map_test.rb" "test/attribute_test.rb" "test/base_test.rb" "test/module_attributes_test.rb" "test/mongo_mapper_test.rb" "test/mongoid_test.rb" 
"test/multiple_test.rb" "test/predicates_test.rb" "test/rails_admin_test.rb" "test/sequel_test.rb" "test/set_test.rb" "test/value_test.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with 

Bug#1026184: marked as done (ruby-combustion: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-combustion: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-combustion
Version: 1.3.7-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-combustion/ -i -O--buildsystem=ruby

[... snipped ...]


An error occurred while loading spec_helper.rb.
Failure/Error: Combustion::Application.initialize!

TZInfo::DataSourceNotFound:
  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# ./lib/combustion.rb:56:in `initialize!'
# ./spec/spec_helper.rb:17:in `block in '
# ./spec/spec_helper.rb:16:in `chdir'
# ./spec/spec_helper.rb:16:in `'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.


Finished in 0.6 seconds (files took 1.82 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib:/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*_spec.rb failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-combustion returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus

Bug#1026183: marked as done (ruby-coffee-rails: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-coffee-rails: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-coffee-rails
Version: 5.0.0-3
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby

[... snipped ...]


/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
/usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/test/assets_test.rb:16:in `setup'

Error:
AssetsTest#test_coffee-script.js_is_included_in_Sprockets_environment:
Errno::ENOENT: No such file or directory @ apply2files - 
/<>/test/tmp/coffee-script.js
/<>/test/assets_test.rb:22:in `delete'
/<>/test/assets_test.rb:22:in `teardown'

rails test test/assets_test.rb:25



Finished in 1.037368s, 4.8199 runs/s, 5.7839 assertions/s.
5 runs, 6 assertions, 0 failures, 2 errors, 0 skips
rake aborted!
Command failed with status (1)
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-coffee-rails returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-tzinfo
Source-Version: 2.0.5-1
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-tzinfo, which is due to be installed in the 

Bug#1026181: marked as done (ruby-arbre: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-arbre: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-arbre
Version: 1.4.0-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-arbre/ -i -O--buildsystem=ruby

[... snipped ...]

# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
# ./spec/rails/rails_spec_helper.rb:4:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/rails/integration/rendering_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'

Finished in 0.7 seconds (files took 1.03 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format 

Bug#1026180: marked as done (ruby-ahoy-email: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-ahoy-email: FTBFS in bookworm (missing build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-ahoy-email
Version: 1.1.1-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-ahoy-email/ -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
from /<>/test/test_helper.rb:10: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/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1)
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-ahoy-email returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

Bug#1026179: marked as done (ruby-active-model-serializers: FTBFS in bookworm (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-active-model-serializers: FTBFS in bookworm (missing 
build-depends on tzdata)
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-active-model-serializers
Version: 0.10.12-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-active-model-serializers/ -i 
-O--buildsystem=ruby

[... snipped ...]

from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/support/isolated_unit.rb:77:in 
`make_basic_app'
from /<>/test/support/rails_app.rb:5:in 
`'
from /<>/test/support/rails_app.rb:4:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
from /<>/test/test_helper.rb:57:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/action_controller/adapter_selector_test.rb:3:in 
`'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/action_controller/adapter_selector_test.rb" "test/action_controller/explicit_serializer_test.rb" "test/action_controller/json/include_test.rb" "test/action_controller/json_api/deserialization_test.rb" "test/action_controller/json_api/errors_test.rb" "test/action_controller/json_api/fields_test.rb" "test/action_controller/json_api/linked_test.rb" "test/action_controller/json_api/transform_test.rb" "test/action_controller/lookup_proc_test.rb" "test/action_controller/namespace_lookup_test.rb" 
"test/action_controller/serialization_scope_name_test.rb" "test/action_controller/serialization_test.rb" "test/active_model_serializers/adapter_for_test.rb" "test/active_model_serializers/json_pointer_test.rb" 

Bug#1026178: marked as done (ruby-tzinfo: missing dependency on tzdata)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id 
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-tzinfo: missing dependency on tzdata
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.)


-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:redmine
Version: 5.0.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --with ruby
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./debian/check-locales
bundle --local --quiet
`/sbuild-nonexistent` is not a directory.
Bundler will use `/tmp/bundler20220525-2469344-bbkpvo2469344' as your home 
directory temporarily.
rm -f Gemfile.lock
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'

[... snipped ...]

/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:391:in
 `initialize!'
/<>/config/environment.rb:16:in `'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `block in require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `require'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:367:in
 `require_environment!'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:533:in
 `block in run_tasks_blocks'

Caused by:
TZInfo::DataSources::ZoneinfoDirectoryNotFound: None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `new'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/railtie.rb:50:in
 `block in '
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:32:in
 `instance_exec'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:391:in
 `initialize!'
/<>/config/environment.rb:16:in `'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `block in require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `require'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:367:in
 `require_environment!'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:533:in
 `block in run_tasks_blocks'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace 

Processed: tagging 1026855

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1026855 + pending
Bug #1026855 [libgoogle-auto-service-java] libgoogle-auto-service-java: ships 
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026510: marked as pending in openjfx

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1026510 in openjfx 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/openjfx/-/commit/e24ba0fd908e63ed6c241f80898e09f0c76894df


Add patch to address javadoc FTBFS (Closes: #1026510)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026510

Processed: Bug#1026510 marked as pending in openjfx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026510 [src:openjfx] openjfx: FTBFS: 
ReadOnlyJavaBeanObjectPropertyBuilder.java:58: error: invalid use of @param
Added tag(s) pending.

-- 
1026510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026854: libgoogle-auto-common-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom

[Olek Wojnar]

Control: tag -1 pending

Hi Andreas and thanks for the report!

On 12/22/22 11:29, Andreas Beckmann wrote:

libgoogle-auto-common-java ships two dubious files that should probably
not be in the package at all:

   
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
   /usr/share/maven-repo/build-only/build-only/debian/build-only-debian.pom


Agreed! I noticed that too right after I uploaded. I made a fixed 
version but haven't had a change to upload it yet. I'll update the 
changelog to close this bug and upload soon.


-Olek


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1026854: libgoogle-auto-common-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026854 [libgoogle-auto-common-java] libgoogle-auto-common-java: ships 
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
Added tag(s) pending.

-- 
1026854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1024795: python-llvmlite

[Diane Trout]

On Fri, 2022-12-23 at 10:56 -0500, M. Zhou wrote:
> Control: tags -1 +moreinfo
> 
> I'm confused. How did you manage to build the package from source
> using c65b3e662b7b08920172b710419d7a06b660be59 on salsa?
> 
> I did not upload it because I can never successfully build it
> from source.
> 


It turns out I was confused and had slipped an additional change into
c37e824380fec443edb24c914b1767dcff496d38.patch and forgotten about it
while I was flailing at numba.

I found the small change and am attaching it 

It adds an #include "llvm/Pass.h" to passmanager.cpp

And I was slow in replying because I was building llvmlite and numba
and making sure the tests run. (Numba's tests can take a couple of
hours to run)

Hope that helps.

Diane

--- a/ffi/passmanagers.cpp
+++ b/ffi/passmanagers.cpp
@@ -22,6 +22,7 @@
 #include "llvm/Transforms/IPO.h"
 #include "llvm/Transforms/Scalar.h"
 
+#include "llvm/Pass.h"
 #include 
 
 using namespace llvm;

Processed: bug 1024219 is forwarded to https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/commit/2765e68dc4650b7306255e0c10056508d5ab44f8

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1024219 
> https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/commit/2765e68dc4650b7306255e0c10056508d5ab44f8
Bug #1024219 [src:cpu-x] cpu-x: FTBFS with libproc2
Set Bug forwarded-to-address to 
'https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/commit/2765e68dc4650b7306255e0c10056508d5ab44f8'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1024219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1026178 marked as pending in ruby-tzinfo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Bug #1026179 [ruby-tzinfo] ruby-active-model-serializers: FTBFS in bookworm 
(missing build-depends on tzdata)
Bug #1026180 [ruby-tzinfo] ruby-ahoy-email: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026181 [ruby-tzinfo] ruby-arbre: FTBFS in bookworm (missing build-depends 
on tzdata)
Bug #1026182 [ruby-tzinfo] ruby-browser: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026183 [ruby-tzinfo] ruby-coffee-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026184 [ruby-tzinfo] ruby-combustion: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026185 [ruby-tzinfo] ruby-enumerize: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026186 [ruby-tzinfo] ruby-factory-bot-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026187 [ruby-tzinfo] ruby-globalid: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026188 [ruby-tzinfo] ruby-haml: FTBFS in bookworm (missing build-depends 
on tzdata)
Bug #1026189 [ruby-tzinfo] ruby-invisible-captcha: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026190 [ruby-tzinfo] ruby-joiner: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026191 [ruby-tzinfo] ruby-omniauth-rails-csrf-protection: FTBFS in 
bookworm (missing build-depends on tzdata)
Bug #1026192 [ruby-tzinfo] ruby-pry-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026193 [ruby-tzinfo] ruby-rails-controller-testing: FTBFS in bookworm 
(missing build-depends on tzdata)
Bug #1026194 [ruby-tzinfo] ruby-sassc-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026195 [ruby-tzinfo] ruby-sprockets-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026196 [ruby-tzinfo] ruby-voight-kampff: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026197 [ruby-tzinfo] ruby-webpacker: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug #1026198 [ruby-tzinfo] ruby-webpack-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
1026179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026179
1026180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026180
1026181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026181
1026182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026182
1026183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026183
1026184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026184
1026185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026185
1026186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026186
1026187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026187
1026188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026188
1026189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026189
1026190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026190
1026191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026191
1026192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026192
1026193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026193
1026194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026194
1026195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026195
1026196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026196
1026197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026197
1026198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026178: marked as pending in ruby-tzinfo

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #1026178 in ruby-tzinfo 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-tzinfo/-/commit/f05c11f0a73409edf49bd1f3555198701561f232


Add dependency on tzdata

Closes: #1026178


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026178

Processed: reassign 1026179 to ruby-tzinfo, reassign 1026180 to ruby-tzinfo, reassign 1026181 to ruby-tzinfo ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1026179 ruby-tzinfo
Bug #1026179 [src:ruby-active-model-serializers] ruby-active-model-serializers: 
FTBFS in bookworm (missing build-depends on tzdata)
Bug reassigned from package 'src:ruby-active-model-serializers' to 
'ruby-tzinfo'.
No longer marked as found in versions ruby-active-model-serializers/0.10.12-1.
Ignoring request to alter fixed versions of bug #1026179 to the same values 
previously set
> reassign 1026180 ruby-tzinfo
Bug #1026180 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-ahoy-email' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-ahoy-email/1.1.1-2.
Ignoring request to alter fixed versions of bug #1026180 to the same values 
previously set
> reassign 1026181 ruby-tzinfo
Bug #1026181 [src:ruby-arbre] ruby-arbre: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-arbre' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-arbre/1.4.0-2.
Ignoring request to alter fixed versions of bug #1026181 to the same values 
previously set
> reassign 1026182 ruby-tzinfo
Bug #1026182 [src:ruby-browser] ruby-browser: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-browser' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-browser/4.2.0-3.
Ignoring request to alter fixed versions of bug #1026182 to the same values 
previously set
> reassign 1026183 ruby-tzinfo
Bug #1026183 [src:ruby-coffee-rails] ruby-coffee-rails: FTBFS in bookworm 
(missing build-depends on tzdata)
Bug reassigned from package 'src:ruby-coffee-rails' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-coffee-rails/5.0.0-3.
Ignoring request to alter fixed versions of bug #1026183 to the same values 
previously set
> reassign 1026184 ruby-tzinfo
Bug #1026184 [src:ruby-combustion] ruby-combustion: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-combustion' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-combustion/1.3.7-1.
Ignoring request to alter fixed versions of bug #1026184 to the same values 
previously set
> reassign 1026185 ruby-tzinfo
Bug #1026185 [src:ruby-enumerize] ruby-enumerize: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-enumerize' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-enumerize/2.5.0-1.
Ignoring request to alter fixed versions of bug #1026185 to the same values 
previously set
> reassign 1026186 ruby-tzinfo
Bug #1026186 [src:ruby-factory-bot-rails] ruby-factory-bot-rails: FTBFS in 
bookworm (missing build-depends on tzdata)
Bug reassigned from package 'src:ruby-factory-bot-rails' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-factory-bot-rails/6.2.0-1.
Ignoring request to alter fixed versions of bug #1026186 to the same values 
previously set
> reassign 1026187 ruby-tzinfo
Bug #1026187 [src:ruby-globalid] ruby-globalid: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-globalid' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-globalid/0.6.0-1.
Ignoring request to alter fixed versions of bug #1026187 to the same values 
previously set
> reassign 1026188 ruby-tzinfo
Bug #1026188 [src:ruby-haml] ruby-haml: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-haml' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-haml/5.2.2-1.
Ignoring request to alter fixed versions of bug #1026188 to the same values 
previously set
> reassign 1026189 ruby-tzinfo
Bug #1026189 [src:ruby-invisible-captcha] ruby-invisible-captcha: FTBFS in 
bookworm (missing build-depends on tzdata)
Bug reassigned from package 'src:ruby-invisible-captcha' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-invisible-captcha/1.1.0-5.
Ignoring request to alter fixed versions of bug #1026189 to the same values 
previously set
> reassign 1026190 ruby-tzinfo
Bug #1026190 [src:ruby-joiner] ruby-joiner: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from package 'src:ruby-joiner' to 'ruby-tzinfo'.
No longer marked as found in versions ruby-joiner/0.6.0-1.
Ignoring request to alter fixed versions of bug #1026190 to the same values 
previously set
> reassign 1026191 ruby-tzinfo
Bug #1026191 [src:ruby-omniauth-rails-csrf-protection] 
ruby-omniauth-rails-csrf-protection: FTBFS in bookworm (missing build-depends 
on tzdata)
Bug reassigned from package 'src:ruby-omniauth-rails-csrf-protection' to 
'ruby-tzinfo'.
No longer marked as found in versions 
ruby-omniauth-rails-csrf-protection/1.0.1-2.
Ignoring request to alter fixed versions of bug #1026191 to the same values 
previously set
> reassign 1026192 ruby-tzinfo
Bug #1026192 [src:ruby-pry-rails] ruby-pry-rails: FTBFS in bookworm (missing 
build-depends on tzdata)
Bug reassigned from 

Processed (with 1 error): forcibly merging 1026178 1026179 1026180 1026181 1026182 1026183 1026184 1026185 1026186 1026187 1026188 1026189 1026190 1026191 1026192 1026193 1026194 1026195 1026196 10261

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1026178 1026179 1026180 1026181 1026182 1026183 1026184 1026185 
> 1026186 1026187 1026188 1026189 1026190 1026191 1026192 1026193 1026194 
> 1026195 1026196 1026197 1026198
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Unable to merge bugs because:
package of #1026197 is 'src:ruby-webpacker' not 'ruby-tzinfo'
package of #1026188 is 'src:ruby-haml' not 'ruby-tzinfo'
package of #1026184 is 'src:ruby-combustion' not 'ruby-tzinfo'
package of #1026190 is 'src:ruby-joiner' not 'ruby-tzinfo'
package of #1026189 is 'src:ruby-invisible-captcha' not 'ruby-tzinfo'
package of #1026182 is 'src:ruby-browser' not 'ruby-tzinfo'
package of #1026183 is 'src:ruby-coffee-rails' not 'ruby-tzinfo'
package of #1026185 is 'src:ruby-enumerize' not 'ruby-tzinfo'
package of #1026191 is 'src:ruby-omniauth-rails-csrf-protection' not 
'ruby-tzinfo'
package of #1026186 is 'src:ruby-factory-bot-rails' not 'ruby-tzinfo'
package of #1026179 is 'src:ruby-active-model-serializers' not 'ruby-tzinfo'
package of #1026192 is 'src:ruby-pry-rails' not 'ruby-tzinfo'
package of #1026187 is 'src:ruby-globalid' not 'ruby-tzinfo'
package of #1026198 is 'src:ruby-webpack-rails' not 'ruby-tzinfo'
package of #1026180 is 'src:ruby-ahoy-email' not 'ruby-tzinfo'
package of #1026194 is 'src:ruby-sassc-rails' not 'ruby-tzinfo'
package of #1026195 is 'src:ruby-sprockets-rails' not 'ruby-tzinfo'
package of #1026181 is 'src:ruby-arbre' not 'ruby-tzinfo'
package of #1026196 is 'src:ruby-voight-kampff' not 'ruby-tzinfo'
package of #1026193 is 'src:ruby-rails-controller-testing' not 'ruby-tzinfo'
Failed to forcibly merge 1026178: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026178
1026179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026179
1026180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026180
1026181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026181
1026182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026182
1026183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026183
1026184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026184
1026185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026185
1026186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026186
1026187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026187
1026188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026188
1026189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026189
1026190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026190
1026191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026191
1026192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026192
1026193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026193
1026194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026194
1026195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026195
1026196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026196
1026197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026197
1026198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 20 errors): all tzadata issues with ruby packages are due to ruby-tzinfo

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1026178 ruby-tzinfo: missing dependency on tzdata
Bug #1026178 [src:redmine] redmine: FTBFS in bookworm (missing build-depends on 
tzdata)
Changed Bug title to 'ruby-tzinfo: missing dependency on tzdata' from 'redmine: 
FTBFS in bookworm (missing build-depends on tzdata)'.
> reassign 1026178 ruby-tzinfo
Bug #1026178 [src:redmine] ruby-tzinfo: missing dependency on tzdata
Bug reassigned from package 'src:redmine' to 'ruby-tzinfo'.
No longer marked as found in versions redmine/5.0.0-1.
Ignoring request to alter fixed versions of bug #1026178 to the same values 
previously set
> affects 1026178 src:redmine
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:redmine
> affects 1026178 src:ruby-active-model-serializers
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-active-model-serializers
> affects 1026178 src:ruby-ahoy-email
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-ahoy-email
> affects 1026178 src:ruby-arbre
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-arbre
> affects 1026178 src:ruby-browser
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-browser
> affects 1026178 src:ruby-coffee-rails
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-coffee-rails
> affects 1026178 src:ruby-combustion
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-combustion
> affects 1026178 src:ruby-enumerize
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-enumerize
> affects 1026178 src:ruby-factory-bot-rails
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-factory-bot-rails
> affects 1026178 src:ruby-globalid
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-globalid
> affects 1026178 src:ruby-haml
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-haml
> affects 1026178 src:ruby-invisible-captcha
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-invisible-captcha
> affects 1026178 src:ruby-joiner
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-joiner
> affects 1026178 src:ruby-omniauth-rails-csrf-protection
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-omniauth-rails-csrf-protection
> affects 1026178 src:ruby-pry-rails
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-pry-rails
> affects 1026178 src:ruby-rails-controller-testing
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-rails-controller-testing
> affects 1026178 src:ruby-sassc-rails
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-sassc-rails
> affects 1026178 src:ruby-sprockets-rails
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-sprockets-rails
> affects 1026178 src:ruby-voight-kampff
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-voight-kampff
> affects 1026178 src:ruby-webpacker
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-webpacker
> affects 1026178 src:ruby-webpack-rails
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Added indication that 1026178 affects src:ruby-webpack-rails
> forcemerge 1026178 1026179
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Unable to merge bugs because:
package of #1026179 is 'src:ruby-active-model-serializers' not 'ruby-tzinfo'
Failed to forcibly merge 1026178: Did not alter merged bugs.

> forcemerge 1026178 1026180
Failed to forcibly merge 1026178: failed to get lock on 
/srv/bugs.debian.org/spool/lock/1026178 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1026178 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1026178 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1026178 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock 

Bug#1026753: libio-compress-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[gregor herrmann]

On Tue, 20 Dec 2022 20:27:02 +0100, gregor herrmann wrote:

> > > # Failed test (t/cz-03zlib-v1.t at line 713)
> > > #  got: 1
> > > # expected: -3
> > > # Looks like you failed 1 test of 471.
> > > t/cz-03zlib-v1.t  
> > > 1..471
> 
> I think this has to do with zlib1g-dev 1:1.2.13.dfsg-1 and
> libcompress-raw-zlib-perl and (a bit)
> https://github.com/pmqs/Compress-Raw-Zlib/issues/20
> 
> If I rebuild libcompress-raw-zlib-perl (against zlib 1.2.13) and then
> rebuild libio-compress-perl, its tests pass.
> 
> 
> PS: This also reminds me that #1024179 in libcompress-raw-zlib-perl
> is still not closed.


And using the same patch as in #1024179 als make this test here pass:

#v+
--- a/t/cz-03zlib-v1.t
+++ b/t/cz-03zlib-v1.t
@@ -14,7 +14,8 @@
 use CompTestUtils;
 use Symbol;
 
-use constant ZLIB_1_2_12_0 => 0x12C0;
+use constant ZLIB_1_2_12_0 => '1.2.12';
+my $Zlib_ver = Compress::Raw::Zlib::zlib_version ;
 
 BEGIN
 {
@@ -704,7 +705,7 @@
 
 # Z_STREAM_END returned by 1.12.2, Z_DATA_ERROR for older zlib
 # always Z_STREAM_ENDin zlib_ng
-if (ZLIB_VERNUM >= ZLIB_1_2_12_0 || Compress::Raw::Zlib::is_zlibng)
+if ($Zlib_ver gt ZLIB_1_2_12_0 || Compress::Raw::Zlib::is_zlibng)
 {
 cmp_ok $status, '==', Z_STREAM_END ;
 }
#v-

Does this make sense?


Cheers,
gregor


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1024795: python-llvmlite

[M. Zhou]

Control: tags -1 +moreinfo

I'm confused. How did you manage to build the package from source
using c65b3e662b7b08920172b710419d7a06b660be59 on salsa?

I did not upload it because I can never successfully build it
from source.

-

passmanagers.cpp: In function ‘void LLVMPY_SetTimePasses(bool)’:
passmanagers.cpp:36:37: error: ‘TimePassesIsEnabled’ was not declared in this 
scope
   36 | LLVMPY_SetTimePasses(bool enable) { TimePassesIsEnabled = enable; }
  | ^~~
passmanagers.cpp: In function ‘void 
LLVMPY_AddDeadCodeEliminationPass(LLVMPassManagerRef)’:
passmanagers.cpp:158:50: error: cannot convert ‘llvm::FunctionPass*’ to 
‘llvm::Pass*’
  158 | unwrap(PM)->add(createDeadCodeEliminationPass());
  | ~^~
  |  |
  |  llvm::FunctionPass*
In file included from passmanagers.cpp:10:
/usr/lib/llvm-14/include/llvm/IR/LegacyPassManager.h:48:26: note:   
initializing argument 1 of ‘virtual void
llvm::legacy::PassManagerBase::add(llvm::Pass*)’
   48 |   virtual void add(Pass *P) = 0;
  |~~^
passmanagers.cpp: In function ‘void LLVMPY_AddSROAPass(LLVMPassManagerRef)’:
passmanagers.cpp:181:75: error: cannot convert ‘llvm::FunctionPass*’ to 
‘llvm::Pass*’
  181 | LLVMPY_AddSROAPass(LLVMPassManagerRef PM) { 
unwrap(PM)->add(createSROAPass()); }
  | 
~~^~
  | 
  |
  | 
  llvm::FunctionPass*
/usr/lib/llvm-14/include/llvm/IR/LegacyPassManager.h:48:26: note:   
initializing argument 1 of ‘virtual void
llvm::legacy::PassManagerBase::add(llvm::Pass*)’
   48 |   virtual void add(Pass *P) = 0;
  |~~^
make[1]: *** [Makefile.linux:22: passmanagers.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>/ffi'
14.0.6

SVML not detected
Traceback (most recent call last):
  File "/<>/ffi/build.py", line 227, in 
main()
  File "/<>/ffi/build.py", line 217, in main
main_posix('linux', '.so')
  File "/<>/ffi/build.py", line 209, in main_posix
subprocess.check_call(['make', '-f', makefile] + makeopts)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make', '-f', 'Makefile.linux', 
'-j8']' returned non-zero exit status 2.
error: command '/usr/bin/python3' failed with exit code 1
E: pybuild pybuild:386: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.10" 
returned exit code 13
make: *** [debian/rules:11: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


On Thu, 2022-12-22 at 18:20 -0500, M. Zhou wrote:
> Sure, I think we can ship a snapshot version as long as it works
> fine with llvm-14. Could you please verify the snapshot hash
> again?
> 
> https://github.com/numba/llvmlite/commit/c65b3e662b7b08920172b710419d7a06b660be59
> 
> The commit seems missing. If it was close to the master branch,
> I can directly pull the master branch and upload the corresponding
> snapshot.
> 
> On Wed, 2022-12-21 at 20:05 -0800, Diane Trout wrote:
> > Hi,
> > 
> > I was trying to update numba, and need the updated version of llvmlite
> > built against llvm-14
> > 
> > The version that's currently in unstable is still built against llvml-
> > 11
> > 
> > https://packages.debian.org/sid/python3-llvmlite
> > 
> > I've checked out out the llvmlite repository and rebuilt it locally
> > using commit c65b3e662b7b08920172b710419d7a06b660be59 against llvm-14
> > 
> > and llvmlite's test cases pass. (And most of numba's passed too. And I
> > think the remaining test failures aren't related to llvmlite)
> > 
> > Is there a chance we could get an updated version released soon?
> > 
> > Thanks
> > Diane Trout
> 

Processed: Re: python-llvmlite

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #1024795 [python3-llvmlite] python3-llvmlite: Depends from non-existing 
packages libllvm11 and llvm-11
Added tag(s) moreinfo.

-- 
1024795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 979610, tagging 1026853, tagging 1026407, tagging 1026803, tagging 981600 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 979610 - bullseye
Bug #979610 {Done: Gregor Jasny } [src:v4l-utils] 
v4l-utils: vendors ancient version of libbpf
Removed tag(s) bullseye.
> tags 1026853 + sid bookworm
Bug #1026853 [rust-svgdom] rust-svgdom: (build-)depends on old version of 
rust-roxmltree
Added tag(s) bookworm and sid.
> tags 1026407 + pending
Bug #1026407 [nvidia-support] nvidia-support: [INTL:pt_BR] Brazilian Portuguese 
debconf templates translation
Added tag(s) pending.
> tags 1026803 + sid bookworm
Bug #1026803 [src:chiaki] chiaki: FTBFS (ModuleNotFoundError: No module named 
'pkg_resources')
Added tag(s) sid and bookworm.
> tags 981600 + sid bookworm
Bug #981600 [src:nghttp2] nghttp2: missing build-depends on tzdata
Added tag(s) bookworm and sid.
> notfound 1026088 33.2-1
Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS
No longer marked as found in versions rdma-core/33.2-1.
> found 1026088 43.0-1
Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS
Marked as found in versions rdma-core/43.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026088
1026407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026407
1026803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026803
1026853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026853
979610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979610
981600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025096: marked as done (nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 15:43:42 +
with message-id 
and subject line Bug#1025096: fixed in nanoc 4.12.14-1
has caused the Debian Bug report #1025096,
regarding nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year
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.)


-- 
1025096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:nanoc
Version: 4.11.23-1
Severity: serious
Tags: ftbfs, patch

Dear maintainer:

During a rebuild of all packages in bullseye I noticed that this package 
does not build from source anymore:


  1) Nanoc::Core has up-to-date version information
 Failure/Error: expect(described_class.version_information).to 
match(/–#{current_year} /)


   expected "Nanoc 4.11.23 © 2007–2021 Denis Defreyne.\nRunning 
ruby 2.7.4 (2021-07-07) on x86_64-linux-gnu with RubyGems 3.2.5.\n" to 
match /–2022 /

   Diff:
   @@ -1,2 +1,3 @@
   -/–2022 /
   +Nanoc 4.11.23 © 2007–2021 Denis Defreyne.
   +Running ruby 2.7.4 (2021-07-07) on x86_64-linux-gnu with 
RubyGems 3.2.5.



This happens because there is a test which expects the current year to 
be equal to 2021, which naturally fails now that we are in 2022, and 
will fail forever from now on.


I include a trivial patch to disable the test in bullseye.

Note also that the current version in testing/unstable also has the bug 
in "latent state", as it will fail from 2023 onwards. To check this, try 
building the package after setting current_year to 2023 as in 
poc.diff.txt and you will see what happens next year.


Thanks.

[ p.s. I'm having a dejavu. Didn't I report something like this a few 
years ago? ]--- a/nanoc-core/spec/nanoc/core_spec.rb
+++ b/nanoc-core/spec/nanoc/core_spec.rb
@@ -3,8 +3,8 @@
 require 'nanoc/version'
 
 describe Nanoc::Core do
-  it 'has up-to-date version information' do
-current_year = Date.today.year
-expect(described_class.version_information).to match(/–#{current_year} /)
-  end
+#  it 'has up-to-date version information' do
+#current_year = Date.today.year
+#expect(described_class.version_information).to match(/–#{current_year} /)
+#  end
 end
--- a/nanoc-core/spec/nanoc/core_spec.rb
+++ b/nanoc-core/spec/nanoc/core_spec.rb
@@ -4,7 +4,7 @@ require 'nanoc/version'
 
 describe Nanoc::Core do
   it 'has up-to-date version information' do
-current_year = Date.today.year
+current_year = 2023
 expect(described_class.version_information).to match(/–#{current_year} /)
   end
 end
--- End Message ---
--- Begin Message ---
Source: nanoc
Source-Version: 4.12.14-1
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
nanoc, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated nanoc 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, 23 Dec 2022 11:24:01 -0300
Source: nanoc
Architecture: source
Version: 4.12.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1025096
Changes:
 nanoc (4.12.14-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Pirate Praveen ]
   * New upstream version 4.12.7 (upstream switched to terser from uglifier)
   * Drop 0016-filesystem_spec-skip-tests-that-fail-on-debian.patch (merged
 upstream) and refresh other patches (remove fuzz).
   * TODO: need psych 4.0
 .
   [ Antonio Terceiro ]
   * New upstream version 4.12.14
   * Refresh patches
   * Bump Build-Depends: on ruby-contracts to (>= 0.17)
   * Drop build dependencies on ruby-coffee-script
   * debian/ruby-tests.rake: run all test tasks even after one fails
   * debian/ruby-tests.rake: don't run coffee-script test
   * Bump build dependency on ruby-haml to (>= 6.0)
   * debian/rules: ignore test failure under ruby3.0
   * Disable test that checks for the current year (Closes: #1025096)
Checksums-Sha1:
 1aeeeca3ad27b70cf8e80ff88671d00315a20573 3321 nanoc_4.12.14-1.dsc
 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 984274 + patch
Bug #984274 [src:openclonk] openclonk: ftbfs with GCC-11
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
984274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026897: ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.

[Antonio Terceiro]

Source: ruby-tilt
Version: 2.0.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

After updating ruby-haml to 6.1.1, ruby-tilt fails to build with a test
failure.

Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-tilt/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"tilt\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-tilt/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/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
> Tilt::AsciidoctorTemplate (disabled)
> Tilt::BlueClothTemplate (disabled)
> Tilt::BuilderTemplate (disabled)
> Tilt::CoffeeScriptTemplate (disabled)
> Tilt::CommonMarkerTemplate (disabled)
> /<>/test/tilt_compilesite_test.rb:40: warning: assigned but 
> unused variable - res
> /usr/share/rubygems-integration/all/gems/creole-0.5.0/lib/creole/parser.rb:255:
>  warning: character class has duplicated range: /\A([:alpha:]|[:digit:])+/
> Tilt::ErubiTemplate (disabled)
> Tilt::KramdownTemplate (disabled)
> Tilt::LessTemplate (disabled)
> Tilt::LiquidTemplate (disabled)
> Tilt::LiveScriptTemplate (disabled)
> /<>/test/tilt_markaby_test.rb:51: warning: assigned but unused 
> variable - eval_scope
> Tilt::MarkabyTemplate (disabled)
> /<>/test/tilt_markdown_test.rb:85: warning: assigned but unused 
> variable - boom
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85:
>  warning: possibly useless use of a variable in void context
> Tilt::MarukuTemplate (disabled)
> Tilt::PandocTemplate (disabled)
> Tilt::PrawnTemplate (disabled)
> Tilt::RadiusTemplate (disabled)
> Tilt::RDiscountTemplate (disabled)
> Tilt::RedcarpetTemplate (disabled)
> Tilt::RedClothTemplate (disabled)
> Tilt::RstPandocTemplate (disabled) [cannot load such file -- pandoc]
> Tilt::SassTemplate (disabled)
> Tilt::SigilTemplate (disabled)
> /<>/test/tilt_template_test.rb:3: warning: setting 
> Encoding.default_external
> /<>/test/test_helper.rb:39: warning: method redefined; 
> discarding old test_template_source_with_locals_of_strings
> /<>/test/tilt_template_test.rb:132: warning: previous definition 
> of test_template_source_with_locals_of_strings was here
> Tilt::TypeScriptTemplate (disabled)
> Tilt::WikiClothTemplate (disabled)
> Run options: -v --seed 27460
> 
> # 

Bug#1026895: ruby-html2haml: FTBFS with ruby-haml 6.1.1: ERROR: Test "ruby3.1" failed: Could not find 'haml' (>= 4.0, < 6) among 102 total gem(s) (Gem::MissingSpecError)

[Antonio Terceiro]

Source: ruby-html2haml
Version: 2.2.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):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'haml' (>= 4.0, < 6) among 102 
> total gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-html2haml/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-html2haml/usr/share/rubygems-integration/all/specifications/html2haml-2.2.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'haml' (>= 4.0, < 6) - did find: [haml-6.1.1] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-html2haml/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (default: 2.3.7)
> cgi (default: 0.3.1)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> did_you_mean (default: 1.6.1)
> digest (default: 3.1.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> erubis (2.7.0)
> etc (default: 1.3.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> haml (6.1.1)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> logger (default: 1.5.0)
> matrix (0.4.2)
> mini_portile2 (2.8.0)
> minitest (5.15.0)
> mutex_m (default: 0.1.1)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.1.1)
> nkf (default: 0.1.1)
> nokogiri (1.13.10)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> pkg-config (1.4.6)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> racc (default: 1.6.0, 1.4.14)
> rake (13.0.6)
> rbs (2.1.0)
> rdoc (default: 6.4.0)
> readline (default: 0.0.3)
> readline-ext (default: 0.1.4)
> reline (default: 0.3.0)
> resolv (default: 0.2.1)
> resolv-replace (default: 0.1.0)
> rexml (3.2.5)
> rinda (default: 0.1.1)
> rss (0.2.9)
> ruby2_keywords (default: 0.0.5)
> ruby_parser (3.15.1)
> rubygems-update (3.3.15)
> sdbm (1.0.0)
> securerandom (default: 0.1.1)
> set (default: 1.0.2)
> sexp_processor (4.15.2)
> shellwords (default: 0.1.0)
> singleton (default: 0.1.1)
> stringio (default: 3.0.1)
> strscan (default: 3.0.1)
> syslog (default: 0.1.0)
> tempfile (default: 0.1.2)
> temple (0.8.2)
> test-unit (3.5.3)
> thor (1.2.1)
> tilt (2.0.11)
> time (default: 0.2.0)
> 

Bug#1026891: marked as done (mpv fails to start: undefined symbol: ass_track_set_feature)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 15:45:59 +0100
with message-id 
and subject line Re: Bug#1026891: mpv fails to start: undefined symbol: 
ass_track_set_feature
has caused the Debian Bug report #1026891,
regarding mpv fails to start: undefined symbol: ass_track_set_feature
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.)


-- 
1026891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpv
Version: 0.35.0-4
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mpv depends on:
ii  libarchive13  3.6.0-1
ii  libasound21.2.8-1
ii  libass9   2:0.14.0-dmo2
ii  libavcodec59  7:5.1.2-1
ii  libavdevice59 7:5.1.2-1
ii  libavfilter8  7:5.1.2-1
ii  libavformat59 7:5.1.2-1
ii  libavutil57   7:5.1.2-1
ii  libbluray22:1.2.0-dmo1
ii  libc6 2.36-6
ii  libcaca0  0.99.beta20-3
ii  libcdio-cdda2 10.2+2.0.1-dmo1
ii  libcdio-paranoia2 10.2+2.0.1-dmo1
ii  libcdio19 1:2.1.0-dmo1
ii  libdrm2   2.4.114-1
ii  libdvdnav46.1.1-1
ii  libegl1   1.5.0-1
ii  libgbm1   22.3.1-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-1
ii  libjpeg62-turbo   1:2.1.2-1+b1
ii  liblcms2-22.13.1-1+b1
ii  liblua5.2-0   5.2.4-3
ii  libmujs2  1.3.2-1
ii  libpipewire-0.3-0 0.3.63-1
ii  libplacebo208 4.208.0-3
ii  libpulse0 16.1+dfsg1-2+b1
ii  librubberband23.1.2+dfsg0-1
ii  libsdl2-2.0-0 2.26.1+dfsg-1
ii  libsixel1 1.10.3-3
ii  libswresample47:5.1.2-1
ii  libswscale6   7:5.1.2-1
ii  libuchardet0  0.0.7-1
ii  libva-drm22.16.0-1
ii  libva-wayland22.16.0-1
ii  libva-x11-2   2.16.0-1
ii  libva22.16.0-1
ii  libvdpau1 1.5-1
ii  libvulkan11.3.231.1-1
ii  libwayland-client01.21.0-1
ii  libwayland-cursor01.21.0-1
ii  libwayland-egl1   1.21.0-1
ii  libx11-6  2:1.8.1-2
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.4.1-1
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libzimg2  1:2.9.3-dmo1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2022.11.11-1

Versions of packages mpv suggests:
pn  libcuda1  

-- no debconf information
--- End Message ---
--- Begin Message ---
On 2022-12-23 14:56:40 +0100, Eric wrote:
> Package: mpv
> Version: 0.35.0-4
> Severity: grave
> Justification: renders package unusable
> 
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages mpv depends on:
> ii  libarchive13  3.6.0-1
> ii  libasound2

Bug#1026577: marked as done (typer: FTBFS: pytest-3: error: unrecognized arguments: --forked)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 14:45:31 +
with message-id 
and subject line Bug#1026577: fixed in typer 0.7.0-1
has caused the Debian Bug report #1026577,
regarding typer: FTBFS: pytest-3: error: unrecognized arguments: --forked
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.)


-- 
1026577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: typer
Version: 0.6.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="pytest-3 --cov=typer --cov=tests --cov=docs_src 
> --cov-report=term-missing -o console_output_style=progress --forked 
> --numprocesses=auto" \
> dh_auto_test
>   pybuild --test --test-pytest -i python{version} -p "3.11 3.10"
> I: pybuild base:240: pytest-3 --cov=typer --cov=tests --cov=docs_src 
> --cov-report=term-missing -o console_output_style=progress --forked 
> --numprocesses=auto
> ERROR: usage: pytest-3 [options] [file_or_dir] [file_or_dir] [...]
> pytest-3: error: unrecognized arguments: --forked
>   inifile: None
>   rootdir: /<>
> 
> E: pybuild pybuild:386: test: plugin custom failed with: exit code=4: 
> pytest-3 --cov=typer --cov=tests --cov=docs_src --cov-report=term-missing -o 
> console_output_style=progress --forked --numprocesses=auto
> I: pybuild base:240: pytest-3 --cov=typer --cov=tests --cov=docs_src 
> --cov-report=term-missing -o console_output_style=progress --forked 
> --numprocesses=auto
> ERROR: usage: pytest-3 [options] [file_or_dir] [file_or_dir] [...]
> pytest-3: error: unrecognized arguments: --forked
>   inifile: None
>   rootdir: /<>
> 
> E: pybuild pybuild:386: test: plugin custom failed with: exit code=4: 
> pytest-3 --cov=typer --cov=tests --cov=docs_src --cov-report=term-missing -o 
> console_output_style=progress --forked --numprocesses=auto
>   rm -fr -- /tmp/dh-xdg-rundir-atO536Xy
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 
> 3.10" returned exit code 13
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/typer_0.6.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: typer
Source-Version: 0.7.0-1
Done: Sergio de Almeida Cipriano Junior 

We believe that the bug you reported is fixed in the latest version of
typer, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergio de Almeida Cipriano Junior  (supplier of updated 
typer 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, 23 Dec 2022 09:19:32 -0300
Source: typer
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sergio de Almeida Cipriano Junior 
Closes: 1026577
Changes:
 typer (0.7.0-1) unstable; urgency=medium
 .
   * New upstream version 0.7.0.
   * Rediff patches.
   * d/tests/run-pytest, d/rules:
 - Remove unrecognized argument --forked from pytest-3 (Closes: 1026577).
Checksums-Sha1:
 5c6dabdbba19eafe4743eb350a92f558a330dd82 2457 typer_0.7.0-1.dsc
 29409e06c8a0414821e496253be4d71b8053ec73 

Bug#1026894: ruby-haml-rails: FTBFS: unsatisfiable build-dependency: ruby-haml (< 6.0) but 6.1.1-1 is to be installed

[Antonio Terceiro]

Source: ruby-haml-rails
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

After updating ruby-haml to 6.1.1, ruby-haml-rails has unsatisfiable
build dependencies.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), gem2deb, rails, rake, 
> ruby-actionpack, ruby-activesupport, ruby-haml (<< 6.0), ruby-haml (>= 
> 4.0.6~), ruby-html2haml (>= 2.0~), ruby-railties, ruby-test-unit, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), gem2deb, rails, rake, 
> ruby-actionpack, ruby-activesupport, ruby-haml (<< 6.0), ruby-haml (>= 
> 4.0.6~), ruby-html2haml (>= 2.0~), ruby-railties, ruby-test-unit, 
> 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 [580 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [776 B]
> Get:5 copy:/<>/apt_archive ./ Packages [808 B]
> Fetched 2164 B in 0s (0 B/s)
> Reading package lists...
> Get:1 file:/<>/resolver-c7QS2B/apt_archive ./ InRelease
> Ign:1 file:/<>/resolver-c7QS2B/apt_archive ./ InRelease
> Get:2 file:/<>/resolver-c7QS2B/apt_archive ./ Release [577 B]
> Get:2 file:/<>/resolver-c7QS2B/apt_archive ./ Release [577 B]
> Get:3 file:/<>/resolver-c7QS2B/apt_archive ./ Release.gpg
> Ign:3 file:/<>/resolver-c7QS2B/apt_archive ./ Release.gpg
> 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: ruby-haml (< 6.0) but 6.1.1-1 is 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


signature.asc
Description: PGP signature

Bug#1026893: ruby-haml-contrib: FTBFS: ERROR: Test "ruby3.1" failed: /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in `': Filters is not a modul

[Antonio Terceiro]

Source: ruby-haml-contrib
Version: 1.0.0.1-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

After updaring ruby-haml to 6.6.1, ruby-haml-contrib fails to build with
a test failure.

Relevant part (hopefully):
> /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in
>  `': Filters is not a module (TypeError)
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/haml-6.1.1/lib/haml/filters/base.rb:5:
>  previous definition of Filters was here
>   from 
> /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:7:in
>  `'
>   from 
> :85:in
>  `require'
>   from 
> :85:in
>  `require'
>   from /<>/test/php_filter_test.rb:2:in `'
>   from 
> :85:in
>  `require'
>   from 
> :85:in
>  `require'
>   from debian/ruby-tests.rb:2:in `block in '
>   from debian/ruby-tests.rb:2:in `each'
>   from debian/ruby-tests.rb:2:in `'
> ERROR: Test "ruby3.1" failed: 

Attached is the full build log.


ruby-haml-contrib.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1026892: asciidoctor: FTBFS with haml 6.1.1: ERROR: Test "ruby3.1" failed.

[Antonio Terceiro]

Source: asciidoctor
Version: 2.0.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

I'm working on updating ruby-haml to the new upstream versinon 6.1.1,
and when trying asciidoctor against that the tests fail.


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-asciidoctor/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"asciidoctor\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-asciidoctor/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-asciidoctor/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"lib:test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/api_test.rb" "test/attribute_list_test.rb" "test/attributes_test.rb" 
> "test/blocks_test.rb" "test/converter_test.rb" "test/document_test.rb" 
> "test/extensions_test.rb" "test/helpers_test.rb" "test/invoker_test.rb" 
> "test/links_test.rb" "test/lists_test.rb" "test/logger_test.rb" 
> "test/manpage_test.rb" "test/options_test.rb" "test/paragraphs_test.rb" 
> "test/parser_test.rb" "test/paths_test.rb" "test/preamble_test.rb" 
> "test/reader_test.rb" "test/sections_test.rb" "test/substitutions_test.rb" 
> "test/syntax_highlighter_test.rb" "test/tables_test.rb" "test/text_test.rb" 
> RUBY_GC_HEAP_FREE_SLOTS=75 (default value: 4096)
> RUBY_GC_HEAP_INIT_SLOTS=75 (default value: 1)
> RUBY_GC_HEAP_GROWTH_FACTOR=2.00 (default value: 1.80)
> RUBY_GC_HEAP_GROWTH_MAX_SLOTS=5 (default value: 0)
> RUBY_GC_MALLOC_LIMIT=12800 (default value: 16777216)
> RUBY_GC_OLDMALLOC_LIMIT=12800 (default value: 16777216)
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85:
>  warning: possibly useless use of a variable in void context
> Run options: --seed 60429
> 
> # Running:
> 
> ...Haml::Engine:
>  Option :attr_wrapper is invalid
> Haml::Engine: Option :attr_wrapper is invalid
> FHaml::Engine: Option :attr_wrapper is invalid
> 

Bug#1026891: mpv fails to start: undefined symbol: ass_track_set_feature

[Eric]

Package: mpv
Version: 0.35.0-4
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mpv depends on:
ii  libarchive13  3.6.0-1
ii  libasound21.2.8-1
ii  libass9   2:0.14.0-dmo2
ii  libavcodec59  7:5.1.2-1
ii  libavdevice59 7:5.1.2-1
ii  libavfilter8  7:5.1.2-1
ii  libavformat59 7:5.1.2-1
ii  libavutil57   7:5.1.2-1
ii  libbluray22:1.2.0-dmo1
ii  libc6 2.36-6
ii  libcaca0  0.99.beta20-3
ii  libcdio-cdda2 10.2+2.0.1-dmo1
ii  libcdio-paranoia2 10.2+2.0.1-dmo1
ii  libcdio19 1:2.1.0-dmo1
ii  libdrm2   2.4.114-1
ii  libdvdnav46.1.1-1
ii  libegl1   1.5.0-1
ii  libgbm1   22.3.1-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-1
ii  libjpeg62-turbo   1:2.1.2-1+b1
ii  liblcms2-22.13.1-1+b1
ii  liblua5.2-0   5.2.4-3
ii  libmujs2  1.3.2-1
ii  libpipewire-0.3-0 0.3.63-1
ii  libplacebo208 4.208.0-3
ii  libpulse0 16.1+dfsg1-2+b1
ii  librubberband23.1.2+dfsg0-1
ii  libsdl2-2.0-0 2.26.1+dfsg-1
ii  libsixel1 1.10.3-3
ii  libswresample47:5.1.2-1
ii  libswscale6   7:5.1.2-1
ii  libuchardet0  0.0.7-1
ii  libva-drm22.16.0-1
ii  libva-wayland22.16.0-1
ii  libva-x11-2   2.16.0-1
ii  libva22.16.0-1
ii  libvdpau1 1.5-1
ii  libvulkan11.3.231.1-1
ii  libwayland-client01.21.0-1
ii  libwayland-cursor01.21.0-1
ii  libwayland-egl1   1.21.0-1
ii  libx11-6  2:1.8.1-2
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.4.1-1
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libzimg2  1:2.9.3-dmo1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2022.11.11-1

Versions of packages mpv suggests:
pn  libcuda1  

-- no debconf information

Bug#1025659: libgl1-mesa-dri: mesa causes xorg segfault; regression against 22.2.0-1

[Fabio Pedretti]

Is this still an issue with 22.3.1-1?

Bug#1007954: [debian-mysql] Bug#1007954: galera-4 FTBFS on IPV6-only buildds

[Michael Prokop]

[Looked briefly into this, since this is a RC bug]

* Otto Kekäläinen [Sat Mar 19, 2022 at 09:04:21AM -0700]:

> Thanks for looking into this. Can you elaborate why you filed this on
> 26.4.8 and not latest 26.4.10?
> 
> Builds are passing. Thus tests indicate that there is no issue. What is the
> broken thing exactly and since tests are passing, how will we verify that
> the broken thing is fixed or still broken?

The problems seems to to present also in version 26.4.11-1+b1:

| Running suite(s): gu::asio
| terminate called after throwing an instance of 'gu::Exception'
|   what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
|  at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
| terminate called after throwing an instance of 'gu::Exception'
|   what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
|  at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
| terminate called after throwing an instance of 'gu::Exception'
|   what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
|  at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
| terminate called after throwing an instance of 'gu::Exception'
|   what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
|  at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
| 94%: Checks: 77, Failures: 0, Errors: 4
| 
./galerautils/tests/gu_asio_test.cpp:1811:E:test_datagram_open:test_datagram_open:0:
 (after this point) Received signal 6 (Aborted)
| 
./galerautils/tests/gu_asio_test.cpp:1820:E:test_datagram_connect:test_datagram_connect:0:
 (after this point) Received signal 6 (Aborted)
| 
./galerautils/tests/gu_asio_test.cpp:1829:E:test_datagram_open_connect:test_datagram_open_connect:0:
 (after this point) Received signal 6 (Aborted)
| 
./galerautils/tests/gu_asio_test.cpp:1894:E:test_datagram_send_to_and_async_read:test_datagram_send_to_and_async_read:0:
 (after this point) Received signal 6 (Aborted)
| Running suite(s): gu::DeqMap
| 100%: Checks: 11, Failures: 0, Errors: 0
| Total tests failed: 4

  -- 
https://buildd.debian.org/status/fetch.php?pkg=galera-4=amd64=26.4.11-1%2Bb1=1652901726=0

Looking at
https://buildd.debian.org/status/logs.php?pkg=galera-4=amd64 it
seems to be failing always at the x86-conova-01 builders, which
means that it seems to be environment specific. AFAICS x86-conova-01
is IPv6 only, and this is also what "FTBFS on IPV6-only buildds" in
the original bug report was about.

Possibly useful for further information/reproducing:

* https://lists.debian.org/debian-devel/2020/07/msg00070.html
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952740

HTH && regards
-mika-


signature.asc
Description: PGP signature

Bug#1026658: marked as done (onioncircuits: FTBFS: make: *** [debian/rules:8: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 13:51:18 +
with message-id 
and subject line Bug#1026658: fixed in onioncircuits 0.7-3
has caused the Debian Bug report #1026658,
regarding onioncircuits: FTBFS: make: *** [debian/rules:8: binary] Error 25
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.)


-- 
1026658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onioncircuits
Version: 0.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> error: Multiple top-level packages discovered in a flat-layout: ['po', 
> 'debian', 'apparmor'].
> 
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
> 
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
> 
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
> 
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:386: configure: plugin distutils failed with: exit code=1: 
> python3.11 setup.py config 
> dh_auto_configure: error: pybuild --configure -i python{version} -p "3.11 
> 3.10" returned exit code 13
> make: *** [debian/rules:8: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/onioncircuits_0.7-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: onioncircuits
Source-Version: 0.7-3
Done: Sascha Steinbiss 

We believe that the bug you reported is fixed in the latest version of
onioncircuits, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated onioncircuits 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, 23 Dec 2022 13:54:47 +0100
Source: onioncircuits
Architecture: source
Version: 0.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Sascha Steinbiss 
Closes: 1026658
Changes:
 onioncircuits (0.7-3) unstable; urgency=medium
 .
   * Fix FTBFS by patching setup.py not to infer package names during build.
 Closes: #1026658
   * Update copyright date for debian/ directory.
   * Add upstream metadata.
Checksums-Sha1:
 d33efa1863205a454dfb3d482d533be514af9657 2303 onioncircuits_0.7-3.dsc
 78c9a825c53a816cf9b8a21538a81db8aa21e6cd 6136 onioncircuits_0.7-3.debian.tar.xz
 b7fad156a98902d005c8a1c7da6f10333c95a73f 11641 
onioncircuits_0.7-3_amd64.buildinfo
Checksums-Sha256:
 b002f489a003e95d3d08ca982b3e05962192988115873cb565f1bccbeba5cd77 2303 
onioncircuits_0.7-3.dsc
 695287516f743217544609dd407ee2c2e78905039df41204ccb4848b732b546e 6136 
onioncircuits_0.7-3.debian.tar.xz
 

Bug#1026500: marked as done (pexpect: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 23 Dec 2022 13:36:52 +
with message-id 
and subject line Bug#1026500: fixed in pexpect 4.8.0-4
has caused the Debian Bug report #1026500,
regarding pexpect: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.11 3.10" 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.)


-- 
1026500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pexpect
Version: 4.8.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> /<>/setup.py:2: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup
> /usr/lib/python3.11/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/ANSI.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/fdpexpect.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/spawnbase.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/popen_spawn.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/screen.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/replwrap.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/_async.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/pxssh.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/run.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/pty_spawn.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/expect.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/utils.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/FSM.py -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> copying pexpect/bashrc.sh -> 
> /<>/.pybuild/cpython3_3.11_pexpect/build/pexpect
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:2: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/ANSI.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/fdpexpect.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/spawnbase.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/popen_spawn.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/screen.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/exceptions.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/replwrap.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/_async.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/pxssh.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/run.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/pty_spawn.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/expect.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/utils.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/FSM.py -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> copying pexpect/bashrc.sh -> 
> /<>/.pybuild/cpython3_3.10_pexpect/build/pexpect
> PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml doc/ 
> build/html
> Running