Bug#1059835: marked as done (cython: autopkgtest regression with Python 3.12 on 32-bit)
Your message dated Thu, 18 Apr 2024 05:34:34 + with message-id and subject line Bug#1059835: fixed in cython 3.0.10+dfsg-1 has caused the Debian Bug report #1059835, regarding cython: autopkgtest regression with Python 3.12 on 32-bit 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.) -- 1059835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cython Version: 3.0.7-2 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer cython's autopkgtests fail with Python 3.12 on 32-bit architectures [1][2][3]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/c/cython/testing/armel/ [2] https://ci.debian.net/packages/c/cython/testing/armhf/ [3] https://ci.debian.net/packages/c/cython/testing/i386/ 8361s == 8361s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError) 8361s -- 8361s Traceback (most recent call last): 8361s File "tests/run/test_unicode.pyx", line 2355, in test_unicode.UnicodeTest.test_raiseMemError (test_unicode.c:144223) 8361s self.assertRaises(MemoryError, alloc) 8361s AssertionError: MemoryError not raised by lambda 8361s 8361s == 8361s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError) 8361s -- 8361s Traceback (most recent call last): 8361s File "tests/run/test_unicode.pyx", line 2355, in test_unicode.UnicodeTest.test_raiseMemError (test_unicode.cpp:144235) 8361s self.assertRaises(MemoryError, alloc) 8361s AssertionError: MemoryError not raised by lambda 8361s 8361s -- 8361s Ran 7570 tests in 8252.568s 8361s 8361s FAILED (failures=2, skipped=16) --- End Message --- --- Begin Message --- Source: cython Source-Version: 3.0.10+dfsg-1 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of cython, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated cython 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: Wed, 17 Apr 2024 22:17:50 +0100 Source: cython Architecture: source Version: 3.0.10+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julian Gilbey Closes: 1059835 Changes: cython (3.0.10+dfsg-1) unstable; urgency=medium . * Team upload * New upstream version (closes: #1059835) * Install cythonize command-line script * Update to debhelper compat level 13 * Update Standards-Version to 4.7.0 (no changes required) * Build with sphinxdoc to avoid embedded JavaScript code, and move documentation to /usr/share/doc/cython3 * Add help2man-generated manpages for cythonize and cygdb * Update d/copyright and exclude demo files with unclear licensing conditions * Add doc-base file to cython-doc Checksums-Sha1: 6cae02de67c6c2dc1bb98bcd0a76fa3141da07da 3015 cython_3.0.10+dfsg-1.dsc 6fe38e577a418fdd5dd25e299343342bfd68f735 2166496 cython_3.0.10+dfsg.orig.tar.xz d58ee4900b619ed22f4d57baf446679cc21f400b 27620 cython_3.0.10+dfsg-1.debian.tar.xz 05c50447b6ff005c4fe9991f03cf0d968bbe13bb 10365 cython_3.0.10+dfsg-1_amd64.buildinfo Checksums-Sha256: 6826c2cafbdc0cb71ddd15a72e269149b2106b96c2caced38e34378441e62995 3015 cython_3.0.10+dfsg-1.dsc 723478a4ae8a0f28673ade89735f05009741222c880e28da78671ec56528c059 2166496 cython_3.0.10+dfsg.orig.tar.xz d4805574a084b198030aaa810a7951d2a2a0292d5c1f2c506c04c92bfa9a8449 27620 cython_3.0.10+dfsg-1.debian.tar.xz 32a342b57c110df265af6eb30941a21ab4e08ff1ef9a9b9ca8411bcc4da12b50 10365 cython_3.0.10+dfsg-1_amd64.buildinfo Files: 5ae3f4ba6c271fdd7781725c79adb50b 3015 python optional cython_3.0.10+dfsg-1.dsc
Processed: Re: Bug#1059838: cython: autopkgtest regression with Python 3.12 on ppc64el
Processing commands for cont...@bugs.debian.org: > severity 1059838 normal Bug #1059838 [src:cython] cython: autopkgtest regression with Python 3.12 on ppc64el Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059838: cython: autopkgtest regression with Python 3.12 on ppc64el
severity 1059838 normal thanks On Tue, Jan 02, 2024 at 11:59:09AM +0200, Graham Inggs wrote: > Source: cython > Version: 3.0.7-2 > Severity: serious > User: debian-pyt...@lists.debian.org > Usertags: python3.12 > > Hi Maintainer > > cython's autopkgtests fail with Python 3.12 on ppc64el[1]. I've > copied what I hope is the relevant part of the log below. > > Regards > Graham This has been forwarded upstream and they have suggested it might be a limited-memory issue; there has been no further work on it. The test has been disabled for now, so downgrading the severity to normal. Best wishes, Julian
Processed: Re: Bug#1064629: libamd-comgr2: segfault in rocfft
Processing commands for cont...@bugs.debian.org: > severity 1064629 important Bug #1064629 [libamd-comgr2] libamd-comgr2: segfault in rocfft Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1064629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069216: rust-futures-rustls: Fails to build from source
Source: rust-futures-rustls Version: 0.24.0-3 Severity: serious Tags: ftbfs rust-futures-rustls fails to build: https://buildd.debian.org/status/package.php?p=rust-futures-rustls Thank you, Jeremy Bícha
Bug#1066438:
This fixes the build: --- a/configure.ac +++ b/configure.ac @@ -852,6 +852,7 @@ fi AC_CACHE_CHECK([if gettimeofday takes tz argument],rsync_cv_HAVE_GETTIMEOFDAY_TZ,[ AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include +#include #include ]], [[struct timeval tv; exit(gettimeofday(, NULL));]])],[rsync_cv_HAVE_GETTIMEOFDAY_TZ=yes],[rsync_cv_HAVE_GETTIMEOFDAY_TZ=no])]) if test x"$rsync_cv_HAVE_GETTIMEOFDAY_TZ" != x"no"; then AC_DEFINE(HAVE_GETTIMEOFDAY_TZ, 1, [Define to 1 if gettimeofday() takes a time-zone arg])
Bug#1061782: marked as done (ansible-core fails its autopkg tests with Python 3.12)
Your message dated Wed, 17 Apr 2024 22:49:50 + with message-id and subject line Bug#1061782: fixed in ansible-core 2.16.5-1 has caused the Debian Bug report #1061782, regarding ansible-core fails its autopkg tests with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ansible-core Version: 2.14.13-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails its autopkg tests: [...] 231s autopkgtest [13:33:12]: test unit: [--- 231s This version of ansible-test cannot be executed with Python version 3.12.1. Supported Python versions are: 3.9, 3.10, 3.11 231s autopkgtest [13:33:12]: test unit: ---] 231s autopkgtest [13:33:12]: test unit: - - - - - - - - - - results - - - - - - - - - - 231s unit FAIL non-zero exit status 1 232s autopkgtest [13:33:13]: test unit: - - - - - - - - - - stderr - - - - - - - - - - 232s This version of ansible-test cannot be executed with Python version 3.12.1. Supported Python versions are: 3.9, 3.10, 3.11 232s autopkgtest [13:33:13]: summary 232s unit FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: ansible-core Source-Version: 2.16.5-1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of ansible-core, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated ansible-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 23:47:08 +0200 Source: ansible-core Architecture: source Version: 2.16.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Lee Garrett Closes: 1057640 1061156 1061781 1061782 1065826 Changes: ansible-core (2.16.5-1) unstable; urgency=medium . * New upstream release (Closes: #1057640) - ansible-test supports python 3.12 now (Closes: #1061782, #1061781) - fixes CVE-2024-0690 (Closes: #1061156) * Drop dependency on python3-distutils (Closes: #1065826) * Drop patches applied upstream * Refreshen patches Checksums-Sha1: 0fc5f2020b1101c0a5cabe1f94e4e5a859840916 3138 ansible-core_2.16.5-1.dsc 55152eb03e2a6088c046fa64b7518765989b033c 3171617 ansible-core_2.16.5.orig.tar.gz 188ebe7d2736bfabbb14dc6dd4ca47a724118718 18688 ansible-core_2.16.5-1.debian.tar.xz 240ee4393d648d55c55b98b073d379cdd552e86a 8177 ansible-core_2.16.5-1_amd64.buildinfo Checksums-Sha256: a1eec601c2a83f3a4e7741b5bb8e1ddac3b2d64e6dc2ff5ba97a5d46c4020bd2 3138 ansible-core_2.16.5-1.dsc cdd29b0ec3f20c35657355a2f6a9c1d0cf1131da99cc9a4a3401801b0ab36d6d 3171617 ansible-core_2.16.5.orig.tar.gz 648c9bca96fef98167180c80fe217990d7f6e02f0738e59b2fed67ad168c4f1e 18688 ansible-core_2.16.5-1.debian.tar.xz c8c5128201ed97ae757f577e6fa5e1c9a2c3588b80ea97416c0baa1bee490439 8177 ansible-core_2.16.5-1_amd64.buildinfo Files: 62bea43ad15987b89cd840d9ea32297a 3138 admin optional ansible-core_2.16.5-1.dsc 1d72404132b54f3caee3f12aa9bbe3b7 3171617 admin optional ansible-core_2.16.5.orig.tar.gz f7e796202b3d8a0eef69065b3a52c019 18688 admin optional ansible-core_2.16.5-1.debian.tar.xz 74ccaf59fad73614f2c698e58110a4a9 8177 admin optional ansible-core_2.16.5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQQzBAEBCgAdFiEE2EfGJRCpwv8kLOAs1gShxII+4PgFAmYgTk4ACgkQ1gShxII+ 4Pgc0h//RmdNXEwpMH5A1OsiYwvFXHOuFcurh5pk2jwbKOJVW2FXX2npy876Sfzm Txmp3oUULcV+94TADdG/A/DiLh58qVhIEOcJ14RBE3MHbInFuBvDizz2w+bJwmfD 5NEPtaCa4k4GHHeCLFFp6S3zjnwYyGHf4oqPYICYJNgwfE6S088WIYGTFGLpl9RU mFbRP5CEJBg3Tof5NyqcICnH5KHGSGYddI7Mzrw0Atr1Q/1EHoLeBo8XwdJaHWao zjizlrqteZ6juhvYKGUwSe1T3ttV35OcLhW4V0kxBSaxMtmsjLpIAIXwLgYTvFZi NB0VGbt1Y4dyC89DDeNOhjqd079bNXeY14R1krpS2/Bx4lrjQtuVFhPvkfguU1D4 67xq0HiMrxX+RJt2uqYHutDLa5M2t30FW0fc+EiMx58uz514PKv2ydfU/EDv3UwZ
Bug#1061781: marked as done (ansible fails autopkg tests with Python 3.12 as the default)
Your message dated Wed, 17 Apr 2024 22:49:50 + with message-id and subject line Bug#1061781: fixed in ansible-core 2.16.5-1 has caused the Debian Bug report #1061781, regarding ansible fails autopkg tests with Python 3.12 as the default 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.) -- 1061781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ansible Version: 7.7.0+dfsg-3 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails its autopkg tests: [...] 297s 297s 297s Running tests in ansible_collections/amazon/aws 297s 297s 297s This version of ansible-test cannot be executed with Python version 3.12.1. Supported Python versions are: 3.9, 3.10, 3.11 297s autopkgtest [13:34:20]: test unit-tests-stable: ---] 298s unit-tests-stableFAIL non-zero exit status 1 298s autopkgtest [13:34:21]: test unit-tests-stable: - - - - - - - - - - results - - - - - - - - - - 298s autopkgtest [13:34:21]: test unit-tests-stable: - - - - - - - - - - stderr - - - - - - - - - - 298s This version of ansible-test cannot be executed with Python version 3.12.1. Supported Python versions are: 3.9, 3.10, 3.11 298s autopkgtest [13:34:21]: summary --- End Message --- --- Begin Message --- Source: ansible-core Source-Version: 2.16.5-1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of ansible-core, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated ansible-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 23:47:08 +0200 Source: ansible-core Architecture: source Version: 2.16.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Lee Garrett Closes: 1057640 1061156 1061781 1061782 1065826 Changes: ansible-core (2.16.5-1) unstable; urgency=medium . * New upstream release (Closes: #1057640) - ansible-test supports python 3.12 now (Closes: #1061782, #1061781) - fixes CVE-2024-0690 (Closes: #1061156) * Drop dependency on python3-distutils (Closes: #1065826) * Drop patches applied upstream * Refreshen patches Checksums-Sha1: 0fc5f2020b1101c0a5cabe1f94e4e5a859840916 3138 ansible-core_2.16.5-1.dsc 55152eb03e2a6088c046fa64b7518765989b033c 3171617 ansible-core_2.16.5.orig.tar.gz 188ebe7d2736bfabbb14dc6dd4ca47a724118718 18688 ansible-core_2.16.5-1.debian.tar.xz 240ee4393d648d55c55b98b073d379cdd552e86a 8177 ansible-core_2.16.5-1_amd64.buildinfo Checksums-Sha256: a1eec601c2a83f3a4e7741b5bb8e1ddac3b2d64e6dc2ff5ba97a5d46c4020bd2 3138 ansible-core_2.16.5-1.dsc cdd29b0ec3f20c35657355a2f6a9c1d0cf1131da99cc9a4a3401801b0ab36d6d 3171617 ansible-core_2.16.5.orig.tar.gz 648c9bca96fef98167180c80fe217990d7f6e02f0738e59b2fed67ad168c4f1e 18688 ansible-core_2.16.5-1.debian.tar.xz c8c5128201ed97ae757f577e6fa5e1c9a2c3588b80ea97416c0baa1bee490439 8177 ansible-core_2.16.5-1_amd64.buildinfo Files: 62bea43ad15987b89cd840d9ea32297a 3138 admin optional ansible-core_2.16.5-1.dsc 1d72404132b54f3caee3f12aa9bbe3b7 3171617 admin optional ansible-core_2.16.5.orig.tar.gz f7e796202b3d8a0eef69065b3a52c019 18688 admin optional ansible-core_2.16.5-1.debian.tar.xz 74ccaf59fad73614f2c698e58110a4a9 8177 admin optional ansible-core_2.16.5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQQzBAEBCgAdFiEE2EfGJRCpwv8kLOAs1gShxII+4PgFAmYgTk4ACgkQ1gShxII+ 4Pgc0h//RmdNXEwpMH5A1OsiYwvFXHOuFcurh5pk2jwbKOJVW2FXX2npy876Sfzm Txmp3oUULcV+94TADdG/A/DiLh58qVhIEOcJ14RBE3MHbInFuBvDizz2w+bJwmfD 5NEPtaCa4k4GHHeCLFFp6S3zjnwYyGHf4oqPYICYJNgwfE6S088WIYGTFGLpl9RU
Bug#1067372: marked as done (starlette: FTBFS: with pytest.raises(RuntimeError):)
Your message dated Wed, 17 Apr 2024 22:38:24 +
with message-id
and subject line Bug#1067372: fixed in starlette 0.37.2-1
has caused the Debian Bug report #1067372,
regarding starlette: FTBFS: with pytest.raises(RuntimeError):
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starlette
Version: 0.31.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> tests/test_websockets.py:459:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> starlette/testclient.py:402: in __init__
> super().__init__(
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self =
>
> def __init__(
> self,
> *,
> auth: AuthTypes | None = None,
> params: QueryParamTypes | None = None,
> headers: HeaderTypes | None = None,
> cookies: CookieTypes | None = None,
> verify: VerifyTypes = True,
> cert: CertTypes | None = None,
> http1: bool = True,
> http2: bool = False,
> proxy: ProxyTypes | None = None,
> proxies: ProxiesTypes | None = None,
> mounts: None | (typing.Mapping[str, BaseTransport | None]) = None,
> timeout: TimeoutTypes = DEFAULT_TIMEOUT_CONFIG,
> follow_redirects: bool = False,
> limits: Limits = DEFAULT_LIMITS,
> max_redirects: int = DEFAULT_MAX_REDIRECTS,
> event_hooks: None | (typing.Mapping[str, list[EventHook]]) = None,
> base_url: URLTypes = "",
> transport: BaseTransport | None = None,
> app: typing.Callable[..., typing.Any] | None = None,
> trust_env: bool = True,
> default_encoding: str | typing.Callable[[bytes], str] = "utf-8",
> ) -> None:
> super().__init__(
> auth=auth,
> params=params,
> headers=headers,
> cookies=cookies,
> timeout=timeout,
> follow_redirects=follow_redirects,
> max_redirects=max_redirects,
> event_hooks=event_hooks,
> base_url=base_url,
> trust_env=trust_env,
> default_encoding=default_encoding,
> )
>
> if http2:
> try:
> import h2 # noqa
> except ImportError: # pragma: no cover
> raise ImportError(
> "Using http2=True, but the 'h2' package is not installed.
> "
> "Make sure to install httpx using `pip install
> httpx[http2]`."
> ) from None
>
> if proxies:
> message = (
> "The 'proxies' argument is now deprecated."
> " Use 'proxy' or 'mounts' instead."
> )
> warnings.warn(message, DeprecationWarning)
> if proxy:
> raise RuntimeError("Use either `proxy` or 'proxies', not
> both.")
>
> if app:
> message = (
> "The 'app' shortcut is now deprecated."
> " Use the explicit style 'transport=WSGITransport(app=...)'
> instead."
> )
> > warnings.warn(message, DeprecationWarning)
> E DeprecationWarning: The 'app' shortcut is now deprecated. Use the
> explicit style 'transport=WSGITransport(app=...)' instead.
>
> /usr/lib/python3/dist-packages/httpx/_client.py:680: DeprecationWarning
> ___ test_receive_wrong_message_type[asyncio]
> ___
>
> test_client_factory = functools.partial( 'starlette.testclient.TestClient'>, backend='asyncio', backend_options={})
>
> def test_receive_wrong_message_type(test_client_factory):
> async def app(scope, receive, send):
> websocket = WebSocket(scope, receive=receive, send=send)
> await websocket.accept()
> await websocket.receive()
>
> > client = test_client_factory(app)
>
> tests/test_websockets.py:471:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> starlette/testclient.py:402: in __init__
> super().__init__(
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self =
>
> def __init__(
> self,
> *,
Bug#1066313: fixed upstream
Hi, Le 11/04/2024 à 22:23, micah anderson a écrit : These issues are fixed upstream in main, but there is not a release. The fix is in commit 1171bf2fd4e7a0cab02cf5fca59090b65af9cd29. Clément would you pull that fix into the package to resolve this FTBFS? Thanks for the heads up! I'll try to upload a new version this week or early next week. I did include the fix, but there are a few lintian/policy issues I'd like to fix before an upload. Cheers, -- nodens
Bug#1069202: gpg-sq: gpg-from-sq diverts /usr/bin/gpg but doesn't place a symlink pointing to gpg-sq
Package: gpg-from-sq Version: 0.8.0-1 Severity: grave X-Debbugs-Cc: Daniel Kahn Gillmor I did: apt install gpg-from-sq and i expected to run `gpg --version` and see the resultant info from the chameleon. Instead, i see: bash: gpg: command not found I'm seeing the same issue with gpg-from-sq version 0.8.0-1 --dkg -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gpg-sq depends on: ii libbz2-1.0 1.0.8-5.1 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libgmp102:6.3.0+dfsg-2+b1 ii libhogweed6t64 3.9.1-2.2 ii libnettle8t64 3.9.1-2.2 ii libsqlite3-03.45.1-1 ii libssl3t64 3.2.1-3 Versions of packages gpg-sq recommends: ii sq 0.33.0-3 gpg-sq suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1069201: src:rust-sequoia-chameleon-gnupg: gpg-sq and gpgv-sq from 0.8.0 conflict with sequoia-chameleon-gnupg 0.5.1
Source: rust-sequoia-chameleon-gnupg Version: 0.8.0-1 Severity: grave X-Debbugs-Cc: Daniel Kahn Gillmor trying to upgrade from sequoia-chameleon-gnupg 0.5.1-1 to sequoia-chameleon-gnupg 0.8.0-1, i see this: ``` Selecting previously unselected package gpg-sq. Preparing to unpack .../gpg-sq_0.8.0-1_amd64.deb ... Unpacking gpg-sq (0.8.0-1) ... dpkg: error processing archive /var/cache/apt/archives/gpg-sq_0.8.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/gpg-sq', which is also in package sequoia-chameleon-gnupg 0.5.1-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package gpgv-sq. Preparing to unpack .../gpgv-sq_0.8.0-1_amd64.deb ... Unpacking gpgv-sq (0.8.0-1) ... dpkg: error processing archive /var/cache/apt/archives/gpgv-sq_0.8.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/gpgv-sq', which is also in package sequoia-chameleon-gnupg 0.5.1-2 Preparing to unpack .../sequoia-chameleon-gnupg_0.8.0-1_all.deb ... Unpacking sequoia-chameleon-gnupg (0.8.0-1) over (0.5.1-2) ... Errors were encountered while processing: /var/cache/apt/archives/gpg-sq_0.8.0-1_amd64.deb /var/cache/apt/archives/gpgv-sq_0.8.0-1_amd64.deb ``` I think this is just missing some Replaces/Breaks annotations, as per: https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-in-other-packages This is probably worth fixing before it migrates into testing. --dkg -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature
Bug#1067372: starlette: FTBFS: with pytest.raises(RuntimeError):
Hi, The new upstream version fixed this issue. Cheers!
Bug#1067694: marked as done (Update Build-Depends for the time64 library renames)
Your message dated Wed, 17 Apr 2024 21:37:07 + with message-id and subject line Bug#1067694: fixed in glogg 1.1.4-1.2 has caused the Debian Bug report #1067694, regarding Update Build-Depends for the time64 library renames 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.) -- 1067694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glogg Version: 1.1.4-1.1 Severity: serious The package explicitly Build-Depends: libqt5dbus5, this needs to be changed to libqt5dbus5t64 if it's needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: glogg Source-Version: 1.1.4-1.2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of glogg, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated glogg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 23:11:25 +0200 Source: glogg Architecture: source Version: 1.1.4-1.2 Distribution: unstable Urgency: medium Maintainer: Nicolas Bonnefon Changed-By: Sebastian Ramacher Closes: 1067694 Changes: glogg (1.1.4-1.2) unstable; urgency=medium . * Non-maintainer upload. * debian/control: Remove hard-coded build dependency on libqt5dbus5 (Closes: #1067694) Checksums-Sha1: 8c3a324dfe3ea56394dd9742831e6a533b087792 1383 glogg_1.1.4-1.2.dsc 3290cd33955c2423048da152cef6f1c4f141e73b 5204 glogg_1.1.4-1.2.debian.tar.xz dac8458a19b50a7b7fb0ff18d11cc89244d39b34 10661 glogg_1.1.4-1.2_amd64.buildinfo Checksums-Sha256: fd7e7a7e407b9e8444082b9a5a640a754932cb0b20b2c453ce359874cb441d27 1383 glogg_1.1.4-1.2.dsc 2766f1cdc620ac1c20b1f50182556318edde0343d1bedb747ac15c0bb0d31a6e 5204 glogg_1.1.4-1.2.debian.tar.xz fbdcbcdaba85e7be578d4d34ab7a5c3b8b334ff6ea17b6715caacc2b6fa5ba0f 10661 glogg_1.1.4-1.2_amd64.buildinfo Files: 228e29e479044e7caa94cb2805e986dd 1383 utils optional glogg_1.1.4-1.2.dsc 15d411519246cecc4263291f1cc0772f 5204 utils optional glogg_1.1.4-1.2.debian.tar.xz 932a8fc099d1a14c2a07fcc8018ab6fe 10661 utils optional glogg_1.1.4-1.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZiA73QAKCRAhk2s2YA/N idbCAP4oyQlb6DHlS5vjNPGMu+QRlHEEgzozSsSN1EuEzcFgigD/YtPafT0Yr79k AbDpdfFb2qMT636WJka+0v65ls+ZhAo= =QLnj -END PGP SIGNATURE- pgpBWj2jFTrxz.pgp Description: PGP signature --- End Message ---
Processed: tagging 1066313
Processing commands for cont...@bugs.debian.org: > tags 1066313 + fixed-upstream Bug #1066313 [src:torsocks] torsocks: FTBFS: config-file.c:184:23: error: implicit declaration of function ‘conf_file_set_enable_ipv6’ [-Werror=implicit-function-declaration] Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1066313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067694: glogg: diff for NMU version 1.1.4-1.2
Control: tags 1067694 + patch Dear maintainer, I've prepared an NMU for glogg (versioned as 1.1.4-1.2). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru glogg-1.1.4/debian/changelog glogg-1.1.4/debian/changelog --- glogg-1.1.4/debian/changelog 2018-08-05 18:33:01.0 +0200 +++ glogg-1.1.4/debian/changelog 2024-04-17 23:11:25.0 +0200 @@ -1,3 +1,11 @@ +glogg (1.1.4-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: Remove hard-coded build dependency on libqt5dbus5 (Closes: +#1067694) + + -- Sebastian Ramacher Wed, 17 Apr 2024 23:11:25 +0200 + glogg (1.1.4-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru glogg-1.1.4/debian/control glogg-1.1.4/debian/control --- glogg-1.1.4/debian/control 2017-08-11 20:24:53.0 +0200 +++ glogg-1.1.4/debian/control 2024-04-17 23:10:49.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Nicolas Bonnefon Build-Depends: debhelper (>= 10), cdbs (>= 0.4.120), pkg-config, qt5-qmake (>= 5.2.1), qtbase5-dev (>= 5.2.1), qtchooser, -qtbase5-dev-tools (>= 5.2.1), libqt5dbus5 (>= 5.2.1), +qtbase5-dev-tools (>= 5.2.1), libboost-program-options-dev, markdown, docbook-to-man Standards-Version: 4.0.0 Homepage: http://glogg.bonnefon.org/
Processed: glogg: diff for NMU version 1.1.4-1.2
Processing control commands: > tags 1067694 + patch Bug #1067694 [src:glogg] Update Build-Depends for the time64 library renames Added tag(s) patch. -- 1067694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069199: kamailio: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."
Source: kamailio Version: 5.7.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kamailio=amd64=5.7.4-1%2Bb4=1712538903=0 g++ -std=c++11 -fPIC -DPIC -funroll-loops -Wcast-align -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DVERSION_NODATE -Wno-write-strings -Wno-deprecated -Wno-unused-function -Wno-sign-compare -Wno-strict-aliasing -fPIC -DPIC -funroll-loops -Wcast-align -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DVERSION_NODATE -DNAME='"kamailio"' -DVERSION='"5.7.4"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 13.2.0"' -D__CPU_x86_64 -D__OS_linux -DVERSIONVAL=5007004 -DCFG_DIR='"/etc/kamailio/"' -DSHARE_DIR='"/usr/share/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLOCKLIST -DUSE_NAPTR -DWITH_XAVP -DMEM_JOIN_FREE -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN -DUSE_RAW_SOCKS -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKAROUND -DUSE_FUTEX -DHAVE_SELECT -I/usr/local/include -DMOD_NAME='"phonenum"' -c cphonenumber.cpp -o cphonenumber.o cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ In file included from /usr/include/absl/base/config.h:86, from /usr/include/absl/base/const_init.h:25, from /usr/include/absl/synchronization/mutex.h:67, from /usr/include/phonenumbers/geocoding/phonenumber_offline_geocoder.h:24, from cphonenumber.cpp:24: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported." 79 | #error "C++ versions less than C++14 are not supported." | ^ Cheers -- Sebastian Ramacher
Bug#1066440: marked as done (librep: FTBFS with -Werror=implicit-function-declaration)
Your message dated Wed, 17 Apr 2024 21:07:05 + with message-id and subject line Bug#1066440: fixed in librep 0.92.5-3.2 has caused the Debian Bug report #1066440, regarding librep: FTBFS with -Werror=implicit-function-declaration 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.) -- 1066440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librep Version: 0.92.5-3.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccO0t9oT.o: in function `main': > ././conftest.c:48:(.text.startup+0xb): undefined reference to `mpz_init' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/librep_0.92.5-3.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: librep Source-Version: 0.92.5-3.2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of librep, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated librep package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 22:48:53 +0200 Source: librep Architecture: source Version: 0.92.5-3.2 Distribution: unstable Urgency: medium Maintainer: Jose M Calhariz Changed-By: Sebastian Ramacher Closes: 1066440 Changes: librep (0.92.5-3.2) unstable; urgency=medium . * Non-maintainer upload. * debian/patches: Fix build with -Werror=implict-function-declaration (Closes: #1066440) * debian/control: Drop -dbg package in favor of -dbgsym packages Checksums-Sha1: e5687194ac6fb5d2450b887c00129f5dbabde68f 1503 librep_0.92.5-3.2.dsc 50f1e5b8cade6104e1cab5352681f759c6f2f429 18564 librep_0.92.5-3.2.debian.tar.xz a8cdc18dfdc03453687b44df4b59ac46c4804a49 7997 librep_0.92.5-3.2_amd64.buildinfo Checksums-Sha256: 29acab55733135df6643ab0a5b918e95270f294b62a383408d57e7d62227af22 1503 librep_0.92.5-3.2.dsc 879708924867332fdb09b8a5f9da5bc13c5c7aa5ac7417f307bc6cf49b1d5440 18564 librep_0.92.5-3.2.debian.tar.xz 02d63ef13b04d81502268701fc5be8680feab2048e72838fba0ddd491ca4d2bb 7997 librep_0.92.5-3.2_amd64.buildinfo Files: d8515a92c38248c4fcb1a40786377144 1503 lisp optional librep_0.92.5-3.2.dsc a1cf53c8aea7f2ed1c008242837329ac 18564 lisp optional librep_0.92.5-3.2.debian.tar.xz 4e07cdb3cf8cf9c99b503129fa14de4c 7997 lisp optional librep_0.92.5-3.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZiA2XgAKCRAhk2s2YA/N idqvAQCRewNx5GPqA/35A7o6hL/qTCUj/eS2IsfyeYtbGkf87QD/XATzGHpav9FL ui7n1Q2s548NHpWegiT/YisF/H8XOgY= =2Lh8 -END PGP SIGNATURE- pgp_kEnIAXGqQ.pgp Description: PGP signature --- End Message ---
Bug#1066440: librep: diff for NMU version 0.92.5-3.2
Control: tags 1066440 + patch
Dear maintainer,
I've prepared an NMU for librep (versioned as 0.92.5-3.2). The diff
is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru librep-0.92.5/debian/changelog librep-0.92.5/debian/changelog
--- librep-0.92.5/debian/changelog 2022-06-14 14:08:21.0 +0200
+++ librep-0.92.5/debian/changelog 2024-04-17 22:48:53.0 +0200
@@ -1,3 +1,12 @@
+librep (0.92.5-3.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Fix build with -Werror=implict-function-declaration
+(Closes: #1066440)
+ * debian/control: Drop -dbg package in favor of -dbgsym packages
+
+ -- Sebastian Ramacher Wed, 17 Apr 2024 22:48:53 +0200
+
librep (0.92.5-3.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru librep-0.92.5/debian/control librep-0.92.5/debian/control
--- librep-0.92.5/debian/control 2016-03-19 18:39:50.0 +0100
+++ librep-0.92.5/debian/control 2024-04-17 22:48:16.0 +0200
@@ -74,26 +74,6 @@
This package contains the files needed to embed the rep interpreter in an
application.
-Package: librep-dbg
-Section: debug
-Priority: extra
-Architecture: any
-Multi-Arch: same
-Depends: librep16 (>= ${source:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Recommends: rep (>= ${source:Version})
-Suggests: libncurses5-dbg,
- libreadline5-dbg,
- librep-dev,
- rep-doc
-Description: debug symbols for librep
- rep is a dialect of Lisp, designed to be used both as an extension
- language for applications and as a general purpose programming language.
- .
- This package contains the debug symbols for the interpreter and the embedded
- library. They are only required for debugging.
-
Package: rep-doc
Section: doc
Architecture: all
diff -Nru librep-0.92.5/debian/patches/build-fix-Wimplicit-int-Wimplicit-function-declaration.patch librep-0.92.5/debian/patches/build-fix-Wimplicit-int-Wimplicit-function-declaration.patch
--- librep-0.92.5/debian/patches/build-fix-Wimplicit-int-Wimplicit-function-declaration.patch 1970-01-01 01:00:00.0 +0100
+++ librep-0.92.5/debian/patches/build-fix-Wimplicit-int-Wimplicit-function-declaration.patch 2024-04-17 22:43:40.0 +0200
@@ -0,0 +1,62 @@
+From: Sam James
+Date: Sat, 5 Nov 2022 06:04:27 +
+Subject: build: fix -Wimplicit-int, -Wimplicit-function-declaration
+
+Clang 16 will make -Wimplicit-int and -Wimplicit-function-declaration
+errors by default.
+
+In this case, it manifests as:
+```
+checking for data type to store Lisp values... configure: error: cannot find Lisp value type; set --with-value-type (see README)
+```
+
+For more information, see LWN.net [0] or LLVM's Discourse [1], or the
+(new) c-std-porting mailing list [2].
+
+[0] https://lwn.net/Articles/913505/
+[1] https://discourse.llvm.org/t/configure-script-breakage-with-the-new-werror-implicit-function-declaration/65213
+[2] hosted at lists.linux.dev.
+
+Signed-off-by: Sam James
+Bug-Ubuntu: https://launchpad.net/bugs/2060791
+Origin: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a935681a6fcabf47524c72420050b6a9030f555d
+---
+ configure.in | 12
+ 1 file changed, 8 insertions(+), 4 deletions(-)
+
+diff --git a/configure.in b/configure.in
+index 1d959f4..4448c45 100644
+--- a/configure.in
b/configure.in
+@@ -432,15 +432,18 @@ AC_ARG_WITH(value-type,
+ as a pointer. [TYPE=] (see README)], [],
+ [with_value_type="undef"])
+ if test "${with_value_type}" = "undef"; then
+- AC_TRY_RUN([main () { exit (!(sizeof (int) >= sizeof (void *)));}],
++ AC_TRY_RUN([#include
++ int main () { exit (!(sizeof (int) >= sizeof (void *)));}],
+ [with_value_type=int])
+ fi
+ if test "${with_value_type}" = "undef"; then
+- AC_TRY_RUN([main () { exit (!(sizeof (long int) >= sizeof (void *)));}],
++ AC_TRY_RUN([#include
++ int main () { exit (!(sizeof (long int) >= sizeof (void *)));}],
+ [with_value_type="long int"])
+ fi
+ if test "${with_value_type}" = "undef"; then
+- AC_TRY_RUN([main () { exit (!(sizeof (long long int) >= sizeof (void *)));}],
++ AC_TRY_RUN([#include
++ int main () { exit (!(sizeof (long long int) >= sizeof (void *)));}],
+ [with_value_type="long long int"])
+ fi
+ if test "${with_value_type}" = "undef"; then
+@@ -457,7 +460,8 @@ AC_ARG_WITH(value-sizeof,
+ if test "${with_value_sizeof}" = "undef"; then
+ dnl the following fragment is inspired by AC_CHECK_SIZEOF
+ AC_TRY_RUN([#include
+- main () {
++ #include
++ int main () {
+ FILE *f = fopen ("conftestval", "w");
+ if (!f) exit (1);
+ fprintf (f, "%d\n", sizeof (${with_value_type}));
diff -Nru librep-0.92.5/debian/patches/series librep-0.92.5/debian/patches/series
--- librep-0.92.5/debian/patches/series 2016-03-20 16:40:28.0 +0100
+++ librep-0.92.5/debian/patches/series 2024-04-17 22:43:40.0 +0200
@@ -1,3 +1,4 @@
Processed: librep: diff for NMU version 0.92.5-3.2
Processing control commands: > tags 1066440 + patch Bug #1066440 [src:librep] librep: FTBFS with -Werror=implicit-function-declaration Added tag(s) patch. -- 1066440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069197: udisks: FTBFS on s390x: ./doc/udisks2-scan.c:204:(.text.startup.main+0x216): undefined reference to `udisks_linux_drive_lsm_get_type'
Source: udisks2 Version: 2.10.1-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=udisks2=s390x=2.10.1-6=1710323220=0 /usr/bin/ld: .libs/udisks2-scan.o: in function `get_object_types': ./doc/udisks2-scan.c:204:(.text.startup.main+0x216): undefined reference to `udisks_linux_drive_lsm_get_type' /usr/bin/ld: ./doc/udisks2-scan.c:205:(.text.startup.main+0x222): undefined reference to `udisks_linux_drive_lsm_local_get_type' /usr/bin/ld: ./doc/udisks2-scan.c:210:(.text.startup.main+0x25e): undefined reference to `udisks_linux_iscsi_session_get_type' /usr/bin/ld: ./doc/udisks2-scan.c:211:(.text.startup.main+0x26a): undefined reference to `udisks_linux_iscsi_session_object_get_type' /usr/bin/ld: ./doc/udisks2-scan.c:217:(.text.startup.main+0x2b2): undefined reference to `udisks_linux_manager_iscsi_initiator_get_type' /usr/bin/ld: ./doc/udisks2-scan.c:223:(.text.startup.main+0x2fa): undefined reference to `udisks_linux_module_iscsi_get_type' /usr/bin/ld: ./doc/udisks2-scan.c:224:(.text.startup.main+0x306): undefined reference to `udisks_linux_module_lsm_get_type' collect2: error: ld returned 1 exit status Cheers -- Sebastian Ramacher
Bug#1069196: eulisp: FTBFS on arm{el,hf}: unixcall.c:90:15: error: conflicting types for ‘timezone’; have ‘time_t’ {aka ‘long long int’}
Source: euslisp
Version: 9.29+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=euslisp=armel=9.29%2Bdfsg-1=1713198693=0
cc -c -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-Darmv8l -DLinux -D_REENTRANT -DVERSION=\"9.29\" -DLIB6 -falign-functions=4
-fsigned-char -fno-stack-protector -DTHREADED -DPTHREAD -DX_V11R6_1 -DGCC
-DGCC3 -I/usr/include -I/usr/X11R6/include -I/<>/include -DARM
-fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -Darmv8l -DLinux -D_REENTRANT -DVERSION=\"9.29\" -DLIB6
-falign-functions=4 -fsigned-char -fno-stack-protector -DTHREADED -DPTHREAD
-DX_V11R6_1 -DGCC -DGCC3 -I/usr/include -I/usr/X11R6/include
-I/<>/include -DARM -fPIC -o
/<>/LinuxARM/obj/unixcall.o -O2 unixcall.c)
unixcall.c:90:15: error: conflicting types for ‘timezone’; have ‘time_t’ {aka
‘long long int’}
90 | extern time_t timezone, altzone;/*long*/
| ^~~~
In file included from /usr/include/pthread.h:23,
from eus_thr.h:25,
from eus.h:577,
from unixcall.c:21:
/usr/include/time.h:233:17: note: previous declaration of ‘timezone’ with type
‘long int’
233 | extern long int timezone;
| ^~~~
make[3]: *** [Makefile.generic2:297: /<>/LinuxARM/obj/unixcall.o]
Error 1
Cheers
--
Sebastian Ramacher
Processed: block 1069193 with 1069195
Processing commands for cont...@bugs.debian.org: > block 1069193 with 1069195 Bug #1069193 [src:rust-zstd] rust-zstd: please update to v0.12.3 1069193 was not blocked by any bugs. 1069193 was not blocking any bugs. Added blocking bug(s) of 1069193: 1069195 > thanks Stopping processing here. Please contact me if you need assistance. -- 1069193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067362: marked as done (hylafax: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1)
Your message dated Wed, 17 Apr 2024 21:38:24 +0200
with message-id <10cccdc97134fc78b2f3628b3ba0cfafb3212ca3.ca...@debian.org>
and subject line Bug#1067362: hylafax: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_configure] Error 1
has caused the Debian Bug report #1067362,
regarding hylafax: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_configure] Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hylafax
Version: 3:6.0.7-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp -p /usr/share/misc/config.* .
> yes | /bin/bash ./configure \
> --with-HTML=yes \
> --with-REGEX=no \
> --with-LIBREGEX='' \
> --with-REGEXINC='' \
> --with-UTMP=auto \
> --with-DIR_BIN="/usr/bin" \
> --with-DIR_LIBDATA="/etc/hylafax" \
> --with-DIR_LIB="/usr/lib/hylafax" \
> --with-DIR_LIBEXEC="/usr/sbin" \
> --with-DIR_MAN="/usr/share/man" \
> --with-DIR_SBIN="/usr/sbin" \
> --with-DIR_LOCKS="/var/lock" \
> --with-PATH_AFM="/usr/share/fonts/type1/gsfonts" \
> --with-FONTMAP="/usr/share/ghostscript/9.19/lib" \
> --with-MANSCHEME="bsd-source-gzip-strip" \
> --with-DIR_HTML="/usr/share/doc/hylafax" \
> --with-DIR_CGI="/usr/lib/cgi-bin" \
> --with-HTMLPATH="/doc/hylafax" \
> --with-SYSGID="root" \
> --with-SYSUID="root" \
> --with-PATH_GETTY="/etc/hylafax/getty-link" \
> --with-PATH_VGETTY="/etc/hylafax/vgetty-link" \
> --with-PATH_EGETTY="/etc/hylafax/egetty-link" \
> --with-CONFIG_MAXGID="65534" \
> --with-CMP="/usr/bin/cmp" \
> --with-COL="/usr/bin/col" \
> --with-MKFIFO="/usr/bin/mkfifo" \
> --with-SORT="/usr/bin/sort" \
> --with-OPTIMIZER="-g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2" \
> --with-MANDIR="/usr/share/man" \
> --with-PATH_DPSRIP="" \
> --with-PATH_IMPRIP="/usr/bin/psrip" \
> --with-AWK="/usr/bin/awk"
>
> Configuring HylaFAX (tm) (aka FlexFAX) 6.0.7.
>
> If configure does the wrong thing, check the file config.log for
> information that may help you understand what went wrong.
>
> Reading site-wide parameters from ./config.site.
> Here we are again, this time on a x86_64-pc-linux-gnu system.
> Using /bin/gcc for a C compiler (set CC to override).
> Looks like /bin/gcc supports the -g option.
> ... but not together with the -O option, not using it.
> Looks like /bin/gcc has an ANSI C preprocessor.
> ... but __ANSI_CPP__ is not automatically defined, will compensate.
> Looks like /bin/gcc supports the -M option for generating make dependencies.
> Using /bin/g++ for a C++ compiler (set CXX to override).
> Looks like /bin/g++ supports the -g option.
> Using " -g" for C++ compiler options.
> Looks like /bin/g++ has an ANSI C preprocessor.
> ... but __ANSI_CPP__ is not automatically defined, will compensate.
> Using /bin/make to configure the software.
> Using "include file" syntax for Makefiles.
> Looks like make supports "sinclude" for conditional includes.
> Using /bin/bash to process command scripts.
> Looks like the system has a CXX runtime
> Checking for PAM (Pluggable Authentication Module) support
> ... not found. Disabling PAM support
> Checking for JBIG library support
> ... not found. Disabling JBIG support
> Checking for NLS (gettext) library support
> Couldn't find anything to link for gettext
> Missing INTL Library.
>
> Compilation of the following test program failed:
>
> --
> int t() { gettext(""); return 0; }
> int main(){ t(); return 0; }
> --
>
> LIBINTL=
>
> Verify that you have the LIBINTL configuration parameters
> set correctly for your system (see above) and that any environment
> variables are setup that are needed to locate a libtiff DSO at runtime
> (e.g. LD_LIBRARY_PATH). Also be sure that any relative pathnames are
> made relative to the top of the build area.
>
> If you don't want NLS support, you can disable it with --disable-nls
>
>
Bug#1069195: librust-prost-build-dev: FTBFS
Package: librust-prost-build-dev Version: 0.11.9-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Unsatisfiable build-dependency on librust-heck-0.5+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYgJKgACgkQLHwxRsGg ASGRAw/7B4pWiR2c4LDM2ca6emb9CAHkEAVYVDUK4KKzUQ7uvs9oSTE5ZKqRKNT5 r6tcWEp1IitiB5bt7dimQbzkIGODLFT2MdrXnZqrYglUlMBOXfNnvfevGhWuI+FI PWDE1oEvxf2ZvTOsMkEc+ywXbfxJKjw4TeoFA+L9g979U18wmTYRB0RCz2nwVOI5 cFhueAR6+IKEPxUk6zYieyJtCddxwsYKR+7uWrktMpRA4hOFK8hyqhZ17wlJs4+y DD00q2uiUFEK4F3vsj+wCYpbVFRPIkD1p6/rLNZgHDN/EAD5wdDUyH+V9kGGIc6P uqPaheyLiRlRU1kydwH+mnXcW6+w9YzSnqA8X/e+7qmU76KFn1SpXpDF1rk7EBRN ujKY+ji6M53WbmnkedF0AT6dPqkUp7+sJZpd4jyxmb+4fWlxl/MBhr5eXjaIj/rI CFUgIsFuNaHE/GeSeXYfZZh12PXWYUDn+q9KPUIM386fnrhOPeQOIJZuXYzjiE3a zcSjSyXnDdMtGuZRBMTdJMhmAFgic42k7y082v7SO5XovptInLP1tG5lzePCc52f F+KPqxptX95WY/8Y6Y79cFcgJaef3Zp5Bzv3vd64ewOwdfes3oUic9a2EL8da+YR nHuEO6+s2+6WNE8lEelgR29bYXLO78nzSxkIf9rtlgvWc+r41mc= =V4jZ -END PGP SIGNATURE-
Processed: found 1068457 in 1.6.9-1
Processing commands for cont...@bugs.debian.org:
> found 1068457 1.6.9-1
Bug #1068457 {Done: Thomas Goirand } [src:azure-uamqp-python]
azure-uamqp-python: CVE-2024-29195
Marked as found in versions azure-uamqp-python/1.6.9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066751: marked as done (python-formencode: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest returned exit code 13)
Your message dated Wed, 17 Apr 2024 19:04:30 +
with message-id
and subject line Bug#1066751: fixed in python-formencode 2.1.0-1
has caused the Debian Bug report #1066751,
regarding python-formencode: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" --test-pytest 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.)
--
1066751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-formencode
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # network is required for the
> http://this.domain.does.not.exist.example.org/test.html test
> LC_ALL=C.UTF-8 LANGUAGE=C.UTF-8 http_proxy='' dh_auto_test
> --buildsystem=pybuild -- --test-pytest
> I: pybuild pybuild:308: cp
> /<>/formencode/tests/non_empty.txt
> /<>/.pybuild/cpython3_3.12_formencode/build/formencode/tests/
> cp -r /<>/formencode/tests/htmlfill_data
> /<>/.pybuild/cpython3_3.12_formencode/build/formencode/tests/
> cp -r /<>/formencode/i18n
> /<>/.pybuild/cpython3_3.12_formencode/build/formencode/
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_formencode/build; python3.12 -m
> pytest
> = test session starts
> ==
> platform linux -- Python 3.12.2, pytest-8.0.2, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.12_formencode/build
> configfile: pytest.ini
> collected 266 items
>
> formencode/tests/test_cc.py .. [
> 0%]
> formencode/tests/test_compound.py . [
> 7%]
> formencode/tests/test_context.py ... [
> 8%]
> formencode/tests/test_declarative.py [
> 9%]
> formencode/tests/test_doctest_xml_compare.py . [
> 10%]
> formencode/tests/test_doctests.py . [
> 13%]
> formencode/tests/test_email.py ..[
> 14%]
> formencode/tests/test_htmlfill.py .. [
> 28%]
> [
> 31%]
> formencode/tests/test_htmlfill_control.py ...[
> 34%]
> formencode/tests/test_htmlgen.py ... [
> 36%]
> formencode/tests/test_htmlrename.py .[
> 37%]
> formencode/tests/test_i18n.py [
> 46%]
> formencode/tests/test_schema.py .EE [
> 54%]
> formencode/tests/test_subclassing.py ... [
> 60%]
> formencode/tests/test_subclassing_old.py [
> 66%]
> formencode/tests/test_validators.py [
> 80%]
> .. [
> 95%]
> formencode/tests/test_variabledecode.py ...
> [100%]
>
> ERRORS
>
> _ ERROR at setup of
> TestAtLeastOneCheckboxIsChecked.test_Schema_with_input_present _
>
> cls =
> func = . at 0x7fb3e66ba7a0>
> when = 'setup'
> reraise = (, )
>
> @classmethod
> def from_call(
> cls,
> func: Callable[[], TResult],
> when: Literal["collect", "setup", "call", "teardown"],
> reraise: Optional[
> Union[Type[BaseException], Tuple[Type[BaseException], ...]]
> ] = None,
> ) -> "CallInfo[TResult]":
> """Call func, wrapping the result in a CallInfo.
>
> :param func:
> The function to call. Called without arguments.
> :param when:
> The phase in which the function is called.
> :param reraise:
> Exception or exceptions that shall propagate if raised by the
> function, instead of being wrapped in the CallInfo.
> """
> excinfo = None
> start = timing.time()
> precise_start = timing.perf_counter()
> try:
> > result: Optional[TResult] = func()
>
> /usr/lib/python3/dist-packages/_pytest/runner.py:342:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _
Bug#1069192: Autopkgtest failure: missing dependency on python3-pytz
Source: lektor Version: 3.3.7-2 Severity: serious X-Debbugs-Cc: jer...@riseup.net Hi, lektor fails its autopkgtests with babel in unstable with: 67s autopkgtest [16:15:09]: test upstream: [--- 67s /usr/lib/python3/dist-packages/_pytest/config/__init__.py:331: PluggyTeardownRaisedWarning: A plugin raised an exception during an old-style hookwrapper teardown. 67s Plugin: helpconfig, Hook: pytest_cmdline_parse 67s ConftestImportFailure: ModuleNotFoundError: No module named 'pytz' (from /tmp/autopkgtest-lxc.jih8d3_e/downtmp/autopkgtest_tmp/tests/conftest.py) 67s For more information see https://pluggy.readthedocs.io/en/stable/api_reference.html#pluggy.PluggyTeardownRaisedWarning 67s config = pluginmanager.hook.pytest_cmdline_parse( 67s ImportError while loading conftest '/tmp/autopkgtest-lxc.jih8d3_e/downtmp/autopkgtest_tmp/tests/conftest.py'. 67s tests/conftest.py:11: in 67s from lektor.builder import Builder 67s /usr/lib/python3/dist-packages/lektor/builder.py:15: in 67s from lektor.build_programs import builtin_build_programs 67s /usr/lib/python3/dist-packages/lektor/build_programs.py:8: in 67s from lektor.db import Attachment 67s /usr/lib/python3/dist-packages/lektor/db.py:28: in 67s from lektor.datamodel import load_datamodels 67s /usr/lib/python3/dist-packages/lektor/datamodel.py:13: in 67s from lektor.types import builtin_types 67s /usr/lib/python3/dist-packages/lektor/types/__init__.py:13: in 67s from lektor.types.primitives import BooleanType 67s /usr/lib/python3/dist-packages/lektor/types/primitives.py:6: in 67s from pytz import FixedOffset 67s E ModuleNotFoundError: No module named 'pytz' 68s autopkgtest [16:15:10]: test upstream: ---] https://ci.debian.net/packages/l/lektor/testing/amd64/45501555/ It seems to use pytz in lektor/types/primitives.py:from pytz import FixedOffset and thus should have a dep on pytz regardless. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/8 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), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: Bug#1061421: Fails to start after an upgrade
Processing commands for cont...@bugs.debian.org: > tags 1061421 +moreinfo Bug #1061421 [wlgreet] Fails to start after an upgrade Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067701: marked as done (FTBFS: _TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64)
Your message dated Wed, 17 Apr 2024 18:50:52 + with message-id and subject line Bug#1067701: fixed in erlang 1:26.2.4+dfsg-1 has caused the Debian Bug report #1067701, regarding FTBFS: _TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64 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.) -- 1067701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: erlang Version: 1:25.3.2.10+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=erlang=armhf=1%3A25.3.2.10%2Bdfsg-1=1711383511=0 arm-linux-gnueabihf-gcc -Werror=undef -Werror=implicit -Werror=return-type -fno-strict-aliasing -fno-common -g -O2 -fno-strict-aliasing -I/<>/erts/arm-unknown-linux-gnueabihf -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_CONFIG_H -Wall -Wstrict- prototypes -Wpointer-arith -Wmissing-prototypes -Wdeclaration-after-statement -DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT -DPOSIX_THREADS -D_POSIX_THREAD_SAFE_FUNCTIONS -Iarm-unknown-linux-gnueabihf/opt/emu -Ibeam -Isys/unix -Isys/common -Iarm-unknown-linux-gnueabihf -Ipcre -Iryu -Iopenssl/include -I../include -I../include/arm-unknown-linux-gnueabihf -I../include/internal -I../include/internal/arm-unknown-linux-gnueabihf -c sys/unix/sys_time.c -o obj/arm-unknown-linux-gnueabihf/opt/emu/sys_time.o In file included from /usr/include/features.h:393, from /usr/include/arm-linux-gnueabihf/bits/libc-header- start.h:33, from /usr/include/stdlib.h:26, from sys/unix/sys_time.c:35: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: erlang Source-Version: 1:26.2.4+dfsg-1 Done: Sergei Golovan We believe that the bug you reported is fixed in the latest version of erlang, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergei Golovan (supplier of updated erlang 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: Wed, 17 Apr 2024 21:01:49 +0300 Source: erlang Architecture: source Version: 1:26.2.4+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Erlang Packagers Changed-By: Sergei Golovan Closes: 1067701 Changes: erlang (1:26.2.4+dfsg-1) experimental; urgency=medium . * New upstream release. * Upload to experimental. * Fix bug with _TIME_BITS=64 for Erlang 26 (closes: #1067701). Checksums-Sha1: 08583f3b23426096fbbd1fed0156a0f007eaa7d3 5009 erlang_26.2.4+dfsg-1.dsc 827d13e630ba5f5de9faf9d28b996026a810bf86 48344536 erlang_26.2.4+dfsg.orig.tar.xz fd7dff438ea07b48e754157274015fec5154e700 60380 erlang_26.2.4+dfsg-1.debian.tar.xz fd6561dd44f96742f77cec1deada5a061d2af49f 30732 erlang_26.2.4+dfsg-1_amd64.buildinfo Checksums-Sha256: f732fc90f5f5c7381c790fdfe24a469ff8977724980fb6f635fff5f960a87c7f 5009 erlang_26.2.4+dfsg-1.dsc 7d3d15d92cfe60c9661830ca2242488ff6b4d8b8a6942686a8a2a5f5e485b78c 48344536 erlang_26.2.4+dfsg.orig.tar.xz b6ade2c7766c2fe8dfa65f4b9b29151b323009a7ec06015aba9823c962a32b29 60380 erlang_26.2.4+dfsg-1.debian.tar.xz 6082182b6f138719982d7db50ed7734bf21f4489c2519401cc1562c0b3869aa3 30732 erlang_26.2.4+dfsg-1_amd64.buildinfo Files: 829eba7172c84b484c52f723a17cacbf 5009 interpreters optional erlang_26.2.4+dfsg-1.dsc
Bug#1061421: Fails to start after an upgrade
Control: tags +moreinfo Please verify whether wlgreet is working for you now. Thank you, Jeremy Bícha
Processed: tagging 1066761
Processing commands for cont...@bugs.debian.org:
> tags 1066761 + upstream fixed-upstream
Bug #1066761 [src:requests] requests: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067707: marked as done (FTBFS: env: ‘-Wdate-time’: No such file or directory)
Your message dated Wed, 17 Apr 2024 18:19:37 +
with message-id
and subject line Bug#1067707: fixed in gdb-avr 13.2-4
has caused the Debian Bug report #1067707,
regarding FTBFS: env: ‘-Wdate-time’: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdb-avr
Version: 13.2-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=gdb-
avr=armhf=13.2-3%2Bb1=1710754002=0
cd build && env CC="gcc" CFLAGS="-v -Wno-error=unused-but-set-variable -Wno-
error=unused-but-set-parameter" CPPFLAGS=-D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
../src/configure --host=arm-linux-gnueabihf --build=arm-linux-gnueabihf
--prefix=/usr --mandir='\${prefix}/share/man' --infodir='\${prefix}/share/info'
--target=avr --with-expat --disable-texinfo --with-system-zlib --with-
python=python3 ASFLAGS="" ASFLAGS_FOR_BUILD="" CFLAGS="-g -O2 -Werror=implicit-
function-declaration -ffile-prefix-map=/<>=. -fstack-protector-
strong -fstack-clash-protection -Wformat -Werror=format-security"
CFLAGS_FOR_BUILD="-g -O2" CPPFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2" CPPFLAGS_FOR_BUILD=""
CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security"
CXXFLAGS_FOR_BUILD="-g -O2" DFLAGS="-frelease" DFLAGS_FOR_BUILD="-frelease"
FCFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection" FCFLAGS_FOR_BUILD="-g -O2" FFLAGS="-g -O2 -ffile-
prefix-map=/<>=. -fstack-protector-strong -fstack-clash-
protection" FFLAGS_FOR_BUILD="-g -O2" LDFLAGS="-Wl,-z,relro"
LDFLAGS_FOR_BUILD="" OBJCFLAGS="-g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-
security" OBJCFLAGS_FOR_BUILD="-g -O2" OBJCXXFLAGS="-g -O2 -ffile-prefix-
map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security" OBJCXXFLAGS_FOR_BUILD="-g -O2"
env: ‘-Wdate-time’: No such file or directory
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: gdb-avr
Source-Version: 13.2-4
Done: Steve Meliza
We believe that the bug you reported is fixed in the latest version of
gdb-avr, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve Meliza (supplier of updated gdb-avr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 08 Apr 2024 19:33:34 -0700
Source: gdb-avr
Architecture: source
Version: 13.2-4
Distribution: unstable
Urgency: high
Maintainer: Steve Meliza
Changed-By: Steve Meliza
Closes: 1067707
Changes:
gdb-avr (13.2-4) unstable; urgency=high
.
[ Michael Hudson-Doyle ]
* debain/rules: Add quotes to CPPFLAGS (closes: #1067707)
.
[ Steve Langasek ]
* Configure with --disable-werror to fix the ppc64el build.
Checksums-Sha1:
3ccd3990d1166e79857917e9035ff6e133bb99de 2078 gdb-avr_13.2-4.dsc
3ecda71e868df6ee8f0cfdade09a514c43da34ac 9076 gdb-avr_13.2-4.debian.tar.xz
a69105d10f026d78d3f013d89461fe351cbd8f11 10227 gdb-avr_13.2-4_source.buildinfo
Checksums-Sha256:
f7720ed41f6b4d7821139a884ca761f985f7620e6a865842ab9a10dbf57de9e6 2078
gdb-avr_13.2-4.dsc
3aa672fb2b92d6f9159248e6c292f550eb5785a00dfc4a3b9b04d415e3c09534 9076
gdb-avr_13.2-4.debian.tar.xz
Bug#1067393: marked as done (fastdds: CVE-2024-28231)
Your message dated Wed, 17 Apr 2024 18:10:11 + with message-id and subject line Bug#1067393: fixed in fastdds 2.14.0+ds-1 has caused the Debian Bug report #1067393, regarding fastdds: CVE-2024-28231 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.) -- 1067393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fastdds Version: 2.11.2+ds-6 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for fastdds. CVE-2024-28231[0]: | eprosima Fast DDS is a C++ implementation of the Data Distribution | Service standard of the Object Management Group. Prior to versions | 2.14.0, 2.13.4, 2.12.3, 2.10.4, and 2.6.8, manipulated DATA | Submessage can cause a heap overflow error in the Fast-DDS process, | causing the process to be terminated remotely. Additionally, the | payload_size in the DATA Submessage packet is declared as uint32_t. | When a negative number, such as -1, is input into this variable, it | results in an Integer Overflow (for example, -1 gets converted to | 0x). This eventually leads to a heap-buffer-overflow, | causing the program to terminate. Versions 2.14.0, 2.13.4, 2.12.3, | 2.10.4, and 2.6.8 contain a fix for this issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-28231 https://www.cve.org/CVERecord?id=CVE-2024-28231 [1] https://github.com/eProsima/Fast-DDS/security/advisories/GHSA-9m2j-qw67-ph4w Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: fastdds Source-Version: 2.14.0+ds-1 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of fastdds, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated fastdds package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Apr 2024 22:36:40 +0200 Source: fastdds Binary: fastdds-tools fastdds-tools-dbgsym libfastrtps-dev libfastrtps-doc libfastrtps2.14 libfastrtps2.14-dbgsym Built-For-Profiles: nocheck Architecture: source amd64 all Version: 2.14.0+ds-1 Distribution: experimental Urgency: medium Maintainer: Debian Robotics Team Changed-By: Timo Röhling Description: fastdds-tools - eProsima FastDDS Discovery Server and Tools libfastrtps-dev - C++ library for the Real Time Publish Subscribe Protocol - develo libfastrtps-doc - C++ library for the Real Time Publish Subscribe Protocol - docume libfastrtps2.14 - C++ library for the Real Time Publish Subscribe Protocol Closes: 1064515 1066119 1067180 1067393 Changes: fastdds (2.14.0+ds-1) experimental; urgency=medium . * New upstream version 2.14.0+ds - Fix CVE-2023-50257: Denial of service against subscribers (Closes: #1064515) - Fix CVE-2023-50716: Bad-free on invalid DATA_FRAG submessage (Closes: #1066119) - Fix CVE-2024-26369: SIGABRT on HistoryQosPolicy with depth 0 (Closes: #1067180) - Fix CVE-2024-28231: Heap overflow on invalid DATA submessage (Closes: #1067393) * Update d/copyright * Drop snakeoil cert generation * Update d/rules * Bump SONAME to 2.14 * Bump Standards-Version to 4.7.0 * Build-Depend on libfastcdr-dev >= 2.2 * Re-enable test suite Checksums-Sha1: 764cd2ba995efb529ef9277b1d7f1d0ddd39439b 3254 fastdds_2.14.0+ds-1.dsc b5b8842c740b78da0b125c14986398e696862562 3214940 fastdds_2.14.0+ds.orig.tar.xz fbefd6720a995c25b5d44102687edcaa0c48a4fa 16772 fastdds_2.14.0+ds-1.debian.tar.xz ccd6e59cdc8b51843bba4eeb82378e842d50f294 725660 fastdds-tools-dbgsym_2.14.0+ds-1_amd64.deb 76a3f53bdf22443ae799cbb5810673ed3566968e 63660 fastdds-tools_2.14.0+ds-1_amd64.deb 35f8affafbc84834058c0369f26e1ace6b771f75 11206
Bug#1066119: marked as done (fastdds: CVE-2023-50716)
Your message dated Wed, 17 Apr 2024 18:10:11 + with message-id and subject line Bug#1066119: fixed in fastdds 2.14.0+ds-1 has caused the Debian Bug report #1066119, regarding fastdds: CVE-2023-50716 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.) -- 1066119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fastdds Version: 2.11.2+ds-6.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.11.2+ds-6 Hi, The following vulnerability was published for fastdds. CVE-2023-50716[0]: | eProsima Fast DDS (formerly Fast RTPS) is a C++ implementation of | the Data Distribution Service standard of the Object Management | Group. Prior to versions 2.13.0, 2.12.2, 2.11.3, 2.10.3, and 2.6.7, | an invalid DATA_FRAG Submessage causes a bad-free error, and the | Fast-DDS process can be remotely terminated. If an invalid Data_Frag | packet is sent, the `Inline_qos, SerializedPayload` member of object | `ch` will attempt to release memory without initialization, | resulting in a 'bad-free' error. Versions 2.13.0, 2.12.2, 2.11.3, | 2.10.2, and 2.6.7 fix this issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-50716 https://www.cve.org/CVERecord?id=CVE-2023-50716 [1] https://github.com/eProsima/Fast-DDS/security/advisories/GHSA-5m2f-hvj2-cx2h Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: fastdds Source-Version: 2.14.0+ds-1 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of fastdds, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated fastdds package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Apr 2024 22:36:40 +0200 Source: fastdds Binary: fastdds-tools fastdds-tools-dbgsym libfastrtps-dev libfastrtps-doc libfastrtps2.14 libfastrtps2.14-dbgsym Built-For-Profiles: nocheck Architecture: source amd64 all Version: 2.14.0+ds-1 Distribution: experimental Urgency: medium Maintainer: Debian Robotics Team Changed-By: Timo Röhling Description: fastdds-tools - eProsima FastDDS Discovery Server and Tools libfastrtps-dev - C++ library for the Real Time Publish Subscribe Protocol - develo libfastrtps-doc - C++ library for the Real Time Publish Subscribe Protocol - docume libfastrtps2.14 - C++ library for the Real Time Publish Subscribe Protocol Closes: 1064515 1066119 1067180 1067393 Changes: fastdds (2.14.0+ds-1) experimental; urgency=medium . * New upstream version 2.14.0+ds - Fix CVE-2023-50257: Denial of service against subscribers (Closes: #1064515) - Fix CVE-2023-50716: Bad-free on invalid DATA_FRAG submessage (Closes: #1066119) - Fix CVE-2024-26369: SIGABRT on HistoryQosPolicy with depth 0 (Closes: #1067180) - Fix CVE-2024-28231: Heap overflow on invalid DATA submessage (Closes: #1067393) * Update d/copyright * Drop snakeoil cert generation * Update d/rules * Bump SONAME to 2.14 * Bump Standards-Version to 4.7.0 * Build-Depend on libfastcdr-dev >= 2.2 * Re-enable test suite Checksums-Sha1: 764cd2ba995efb529ef9277b1d7f1d0ddd39439b 3254 fastdds_2.14.0+ds-1.dsc b5b8842c740b78da0b125c14986398e696862562 3214940 fastdds_2.14.0+ds.orig.tar.xz fbefd6720a995c25b5d44102687edcaa0c48a4fa 16772 fastdds_2.14.0+ds-1.debian.tar.xz ccd6e59cdc8b51843bba4eeb82378e842d50f294 725660 fastdds-tools-dbgsym_2.14.0+ds-1_amd64.deb 76a3f53bdf22443ae799cbb5810673ed3566968e 63660 fastdds-tools_2.14.0+ds-1_amd64.deb 35f8affafbc84834058c0369f26e1ace6b771f75 11206 fastdds_2.14.0+ds-1_amd64.buildinfo 208d4857721fc58c03109ef2cebc2b84d9987d7e 297692 libfastrtps-dev_2.14.0+ds-1_amd64.deb c36a2b24100ddbce283ac11ae373bc1ca43fc0f1 2347996
Processed: reassign 1061781 to ansible-core
Processing commands for cont...@bugs.debian.org: > reassign 1061781 ansible-core Bug #1061781 [src:ansible] ansible fails autopkg tests with Python 3.12 as the default Bug reassigned from package 'src:ansible' to 'ansible-core'. No longer marked as found in versions ansible/7.7.0+dfsg-3. Ignoring request to alter fixed versions of bug #1061781 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1061781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069189: mysql-8.0: CVE-2024-21102 CVE-2024-21096 CVE-2024-21087 CVE-2024-21069 CVE-2024-21062 CVE-2024-21060 CVE-2024-21054 CVE-2024-21047 CVE-2024-21013 CVE-2024-21009 CVE-2024-21008 CVE-2024-21
Source: mysql-8.0 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for mysql-8.0. CVE-2024-21102[0]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Thread Pooling). Supported versions that are | affected are 8.0.36 and prior and 8.3.0 and prior. Easily | exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete | DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2024-21096[1]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Client: mysqldump). Supported versions that are | affected are 8.0.36 and prior and 8.3.0 and prior. Difficult to | exploit vulnerability allows unauthenticated attacker with logon to | the infrastructure where MySQL Server executes to compromise MySQL | Server. Successful attacks of this vulnerability can result in | unauthorized update, insert or delete access to some of MySQL Server | accessible data as well as unauthorized read access to a subset of | MySQL Server accessible data and unauthorized ability to cause a | partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Confidentiality, Integrity and Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L). CVE-2024-21087[2]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Group Replication Plugin). Supported versions | that are affected are 8.0.36 and prior and 8.3.0 and prior. Easily | exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete | DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2024-21069[3]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: DDL). Supported versions that are affected are | 8.0.36 and prior and 8.3.0 and prior. Easily exploitable | vulnerability allows high privileged attacker with network access | via multiple protocols to compromise MySQL Server. Successful | attacks of this vulnerability can result in unauthorized ability to | cause a hang or frequently repeatable crash (complete DOS) of MySQL | Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS | Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2024-21062[4]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.36 and prior and 8.3.0 and prior. Easily | exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete | DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2024-21060[5]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Data Dictionary). Supported versions that are | affected are 8.0.36 and prior and 8.3.0 and prior. Easily | exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete | DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2024-21054[6]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.36 and prior and 8.3.0 and prior. Easily | exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete | DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2024-21047[7]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: InnoDB). Supported versions that are affected are | 8.0.36 and prior and 8.3.0 and prior. Easily exploitable | vulnerability allows high privileged attacker with network access | via multiple protocols to compromise MySQL
Bug#1069163: marked as done (libkf5kmanagesieve5: sends password as username when authenticating against sieve servers)
Your message dated Wed, 17 Apr 2024 17:04:49 + with message-id and subject line Bug#1069163: fixed in libkf5ksieve 4:22.12.3-2 has caused the Debian Bug report #1069163, regarding libkf5kmanagesieve5: sends password as username when authenticating against sieve servers 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.) -- 1069163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkf5kmanagesieve5 Version: 4:22.12.3-1 Severity: grave Tags: security, patch, upstream Dear Maintainer, kmail, when using managesieve, sends the password as username to servers. This is particularly bad because usernames are commonly logged by servers in plaintext. It thus leaks passwords into server-side plaintext logs e.g. with dovecot. This seems to have been fixed upstream: https://invent.kde.org/pim/libksieve/-/commit/ 6b460ba93ac4ac503ba039d0b788ac7595120db1 Please consider a backport of that patch or updating the package quickly. Thank you. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkf5kmanagesieve5 depends on: ii kio 5.107.0-1+b1 ii libc6 2.37-15 ii libkf5configcore5 5.107.0-1+b1 ii libkf5coreaddons5 5.107.0-1+b1 ii libkf5i18n5 5.107.0-1+b1 ii libkf5kiocore55.107.0-1+b1 ii libkf5kiowidgets5 5.107.0-1+b1 ii libkf5ksieve-data 4:22.12.3-1 ii libkf5widgetsaddons5 5.107.0-1+b1 ii libqt5core5a 5.15.10+dfsg-7 ii libqt5network55.15.10+dfsg-7 ii libqt5widgets55.15.10+dfsg-7 ii libsasl2-22.1.28+dfsg1-4+b1 ii libstdc++614-20240201-3 libkf5kmanagesieve5 recommends no packages. libkf5kmanagesieve5 suggests no packages. -- no debconf information -- Jonas Schäfer Team Lead Cloud Infrastructure Development Cloud Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schae...@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: libkf5ksieve Source-Version: 4:22.12.3-2 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of libkf5ksieve, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated libkf5ksieve package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 18:46:16 +0200 Source: libkf5ksieve Architecture: source Version: 4:22.12.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1069163 Changes: libkf5ksieve (4:22.12.3-2) unstable; urgency=medium . [ Patrick Franz ] * Add patch to prevent leaking passwords into server-side logs (Closes: #1069163). Checksums-Sha1: a6a4de3eb37a1aa539e40867133fcda6dfe5780b 3198 libkf5ksieve_22.12.3-2.dsc 1ca46917b9f7a037d90c715bc64c3c02206de7b1 16520 libkf5ksieve_22.12.3-2.debian.tar.xz ddfd5607baf1004d4f0150b20f00b16e7cadb91c 12827 libkf5ksieve_22.12.3-2_source.buildinfo Checksums-Sha256: 77e152d2a615b0edcdf00ea179fee5c85941d5ffc566e898b05fe4e3776256ad 3198 libkf5ksieve_22.12.3-2.dsc eed925d50add7ac45d02a34095786da0527d32faadd0f5d4e681a5f7b2a1c57b 16520 libkf5ksieve_22.12.3-2.debian.tar.xz b17cdf70f4470d8386f0bb7f529187203cbb0f2f2ea7dad31602b022f132db36
Bug#1067332: marked as done (python-django-storages: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Wed, 17 Apr 2024 16:32:21 +
with message-id
and subject line Bug#1067332: fixed in python-django-storages 1.14.2-2
has caused the Debian Bug report #1067332,
regarding python-django-storages: FTBFS: dh_missing: error: missing files,
aborting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-storages
Version: 1.14.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. python3 -m sphinx -b html -d docs/.build/.doctrees -N docs
> /<>/debian/python-django-storages-doc/usr/share/doc/python-django-storages-doc/html
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 11 source files that are out of date
> updating environment: [new config] 11 added, 0 changed, 0 removed
> [2Kreading sources... [ 9%] backends/amazon-S3
> [2Kreading sources... [ 18%] backends/apache_libcloud
> [2Kreading sources... [ 27%] backends/azure
> [2Kreading sources... [ 36%] backends/backblaze-B2
> [2Kreading sources... [ 45%] backends/digital-ocean-spaces
> [2Kreading sources... [ 55%] backends/dropbox
> [2Kreading sources... [ 64%] backends/ftp
> [2Kreading sources... [ 73%] backends/gcloud
> [2Kreading sources... [ 82%] backends/oracle-cloud
> [2Kreading sources... [ 91%] backends/sftp
> [2Kreading sources... [100%] index
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> [2Kwriting output... [ 9%] backends/amazon-S3
> [2Kwriting output... [ 18%] backends/apache_libcloud
> [2Kwriting output... [ 27%] backends/azure
> [2Kwriting output... [ 36%] backends/backblaze-B2
> [2Kwriting output... [ 45%] backends/digital-ocean-spaces
> [2Kwriting output... [ 55%] backends/dropbox
> [2Kwriting output... [ 64%] backends/ftp
> [2Kwriting output... [ 73%] backends/gcloud
> [2Kwriting output... [ 82%] backends/oracle-cloud
> [2Kwriting output... [ 91%] backends/sftp
> [2Kwriting output... [100%] index
>
> /<>/docs/backends/dropbox.rst:89: WARNING: Lexing literal_block
> '{\n "access_token": "sl.",\n "token_type":
> "bearer",\n "expires_in": 14400,\n "refresh_token":
> "", <-- your REFRESH_TOKEN\n "scope": ,\n
> "uid": "",\n "account_id":
> "dbid:"\n}' as "json" resulted in an error at token:
> '<'. Retrying in relaxed mode.
> generating indices... genindex done
> highlighting module code...
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 1 warning.
>
> The HTML pages are in
> debian/python-django-storages-doc/usr/share/doc/python-django-storages-doc/html.
> dh_sphinxdoc
> make[1]: Leaving directory '/<>'
>dh_installchangelogs -O--buildsystem=pybuild
>dh_python3 -O--buildsystem=pybuild
>dh_installsystemduser -O--buildsystem=pybuild
>dh_perl -O--buildsystem=pybuild
>dh_link -O--buildsystem=pybuild
>dh_strip_nondeterminism -O--buildsystem=pybuild
>dh_compress -O--buildsystem=pybuild
>dh_fixperms -O--buildsystem=pybuild
>dh_missing -O--buildsystem=pybuild
> dh_missing: warning:
> usr/lib/python3.11/dist-packages/.pytest_cache/.gitignore exists in
> debian/tmp but is not installed to anywhere
> dh_missing: warning:
> usr/lib/python3.11/dist-packages/.pytest_cache/CACHEDIR.TAG exists in
> debian/tmp but is not installed to anywhere
> dh_missing: warning: usr/lib/python3.11/dist-packages/.pytest_cache/README.md
> exists in debian/tmp but is not installed to anywhere
> dh_missing: warning:
> usr/lib/python3.11/dist-packages/.pytest_cache/v/cache/nodeids exists in
> debian/tmp but is not installed to anywhere
> dh_missing: warning:
> usr/lib/python3.11/dist-packages/.pytest_cache/v/cache/stepwise exists in
> debian/tmp but is not installed to anywhere
> dh_missing: warning:
> usr/lib/python3.12/dist-packages/.pytest_cache/.gitignore exists in
> debian/tmp but is
Bug#1061741: marked as done (faiss ftbfs with Python 3.12 as default)
Your message dated Wed, 17 Apr 2024 16:19:18 + with message-id and subject line Bug#1061741: fixed in faiss 1.8.0-1 has caused the Debian Bug report #1061741, regarding faiss ftbfs with Python 3.12 as default 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.) -- 1061741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:faiss Version: 1.7.4-3 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails to build: [...] /<>/build/faiss/python/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx: In function ‘PyObject* swig_ptr(PyObject*)’: /<>/build/faiss/python/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx:4939:41: error: ‘SWIGTYPE_p_unsigned_long_long’ was not declared in this scope; did you mean ‘SWIGTYPE_p_unsigned_long’? 4939 | return SWIG_NewPointerObj(data, SWIGTYPE_p_unsigned_long_long, 0); | ^ /<>/build/faiss/python/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx:1136:94: note: in definition of macro ‘SWIG_NewPointerObj’ 1136 | #define SWIG_NewPointerObj(ptr, type, flags) SWIG_Python_NewPointerObj(NULL, ptr, type, flags) | ^~~~ /<>/build/faiss/python/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx:4946:41: error: ‘SWIGTYPE_p_long_long’ was not declared in this scope; did you mean ‘SWIGTYPE_p_long’? 4946 | return SWIG_NewPointerObj(data, SWIGTYPE_p_long_long, 0); | ^~~~ /<>/build/faiss/python/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx:1136:94: note: in definition of macro ‘SWIG_NewPointerObj’ 1136 | #define SWIG_NewPointerObj(ptr, type, flags) SWIG_Python_NewPointerObj(NULL, ptr, type, flags) | --- End Message --- --- Begin Message --- Source: faiss Source-Version: 1.8.0-1 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of faiss, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated faiss package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 18:05:40 +0200 Source: faiss Architecture: source Version: 1.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Deep Learning Team Changed-By: Timo Röhling Closes: 1061741 Changes: faiss (1.8.0-1) unstable; urgency=medium . * Team upload. * New upstream version 1.8.0 * Reformat d/control * Bump Standards-Version to 4.7.0 * Fix FTBFS with swig >= 4.2.0 (Closes: #1061741) * Build for all supported Python versions * Run autopkgtest with all supported Python versions Checksums-Sha1: 5499cd2261ca2aadfa436a676933622a474e11ad 2887 faiss_1.8.0-1.dsc e62e6fba7d496ad5de60ee94de1bfe9bcdebaad8 1015506 faiss_1.8.0.orig.tar.gz 3eebb3ad83ce6067276565042a17127780c15073 6796 faiss_1.8.0-1.debian.tar.xz Checksums-Sha256: 1e0ffcf9b16feec1c2c81c253325d650ad2ce50463285f3cbf717edf25a6182a 2887 faiss_1.8.0-1.dsc 56ece0a419d62eaa11e39022fa27c8ed6d5a9b9eb7416cc5a0fdbeab07ec2f0c 1015506 faiss_1.8.0.orig.tar.gz 36ede1f93e8361fa403d31a2e2be0d6373a6bf8e8d749e45d9c44bd9c221d99b 6796 faiss_1.8.0-1.debian.tar.xz Files: f7619d23c236d2064f938067b65c0723 2887 science optional faiss_1.8.0-1.dsc fc6de8d8fdffca8ed3ff1944c9ec634d 1015506 science optional faiss_1.8.0.orig.tar.gz 507299b7832791d9e8c370931f16cca6 6796 science optional faiss_1.8.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmYf9KkUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQzIxr3RQD9Mru+xAAiY4tZFSYHnoMdzneN5kiV4l/Hqba 8pWEakpssn7P+jrd2aWj5LhKlhD1CLFV/lJkkV+Kh4ifd+eB4IKMQkg3Ai10PJEN 486/kXqX9/Y7p939NFrqrHPF8Uu4exhzd9/8iEtl2c9RNQXGqEOOH18kO5/cG7AI 5UvNIsINSCLOmXVjj3ElAM7yJLtgGwY42OmhP+UE/zHp9gujkuwW/43mnqgRW3LM FDRlCvWzvIOkQ1KhiLhY4kz3+xmtbr5l7gFeblPCpXpU7V8dAqY10mjpmcdq8vQ6 M0hosNkbO5LXS15CFZ39TVguzzAn3e3lmWTKzk/FxNlJqyC81ut6vZBx0XVH9HZx
Processed: Bug#1067332 marked as pending in python-django-storages
Processing control commands: > tag -1 pending Bug #1067332 [src:python-django-storages] python-django-storages: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. -- 1067332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067332: marked as pending in python-django-storages
Control: tag -1 pending Hello, Bug #1067332 in python-django-storages 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-django-storages/-/commit/0a42a4cb660a25ba3e0d1190977b7679791ee270 Clean up .pytest_cache directory after build-time tests (Closes: #1067332). (this message was generated automatically) -- Greetings https://bugs.debian.org/1067332
Bug#1066823: marked as done (plptools: FTBFS on arm{el,hf}: plpdirent.cc:44:35: error: call of overloaded ‘PsiTime(long int)’ is ambiguous)
Your message dated Wed, 17 Apr 2024 15:21:05 +
with message-id
and subject line Bug#1066823: fixed in plptools 1.0.13-3
has caused the Debian Bug report #1066823,
regarding plptools: FTBFS on arm{el,hf}: plpdirent.cc:44:35: error: call of
overloaded ‘PsiTime(long int)’ is ambiguous
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.)
--
1066823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plptools
Version: 1.0.13-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=plptools=armhf=1.0.13-2%2Bb1=1710265542=0
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../intl -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -c plpdirent.cc
-fPIC -DPIC -o .libs/plpdirent.o
plpdirent.cc: In constructor ‘PlpDirent::PlpDirent()’:
plpdirent.cc:44:35: error: call of overloaded ‘PsiTime(long int)’ is ambiguous
44 | : size(0), attr(0), name(""), time(0L), attrstr("") {
| ^~~~
In file included from plpdirent.h:30,
from plpdirent.cc:23:
./psitime.h:179:5: note: candidate: ‘PsiTime::PsiTime(const PsiTime&)’
179 | PsiTime(const PsiTime );
| ^~~
./psitime.h:161:5: note: candidate: ‘PsiTime::PsiTime(psi_timeval*,
psi_timezone*)’
161 | PsiTime(psi_timeval *_ptv, psi_timezone *_ptz = 0L);
| ^~~
./psitime.h:153:5: note: candidate: ‘PsiTime::PsiTime(time_t)’
153 | PsiTime(time_t time);
| ^~~
./psitime.h:146:5: note: candidate: ‘PsiTime::PsiTime(timeval*, timezone*)’
146 | PsiTime(struct timeval *_utv, struct timezone *_utz = 0L);
| ^~~
make[3]: *** [Makefile:579: plpdirent.lo] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: plptools
Source-Version: 1.0.13-3
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
plptools, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated plptools 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: Wed, 17 Apr 2024 16:43:49 +0200
Source: plptools
Architecture: source
Version: 1.0.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1066823
Changes:
plptools (1.0.13-3) unstable; urgency=medium
.
* QA upload.
* Import package history into GIT.
* Set Maintainer to Debian QA Group. (See: #1064669)
* Switch upstream from sourceforge to github.
* Update obsolete (Build-)Depends.
* Declare Rules-Requires-Root: no.
* Update Lintian overrides.
* Resolve ambiguity on 32-bit platforms with 64-bit time_t.
(Closes: #1066823)
Checksums-Sha1:
b5bc782de22c0074a53c496df692ca76bc5304ab 1980 plptools_1.0.13-3.dsc
5fcbb9c8c3c7dee6a6249cfbe5665082597fedcd 27812 plptools_1.0.13-3.debian.tar.xz
522c1468a7df8202346b8005158389cd6e2c8b6e 6194
plptools_1.0.13-3_source.buildinfo
Checksums-Sha256:
e7e836704d2ee309449e6cbf8388cd1439f9eae5e0befc7f5fdb8a4eaa45beb4 1980
plptools_1.0.13-3.dsc
1df3164811f7677ef03c521c2274b2fb4f4bea2502430af10689ff973c3a0fdd 27812
plptools_1.0.13-3.debian.tar.xz
7534ada41e2e766198992732ee2828d61c75110c080d0f726bc9802bd7c075f6 6194
plptools_1.0.13-3_source.buildinfo
Files:
f78e6a2eb52c3d7f615ae40f196f12aa 1980 otherosfs optional plptools_1.0.13-3.dsc
fd3c300e69bf3ab37018486a34ba20bd 27812 otherosfs optional
plptools_1.0.13-3.debian.tar.xz
077ce7175f6e397881c29b8e81788f48 6194 otherosfs optional
plptools_1.0.13-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYf4JMQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCPBbD/4/5SximrzBnHyDBBpmBbrR7SMZCYHTQX18
Bug#1068735: marked as done (Trying to overwrite libpmix.so.2, which is also in package libpmix2t64:armhf)
Your message dated Wed, 17 Apr 2024 14:58:51 + with message-id and subject line Bug#1068735: fixed in openmpi 4.1.6-12 has caused the Debian Bug report #1068735, regarding Trying to overwrite libpmix.so.2, which is also in package libpmix2t64:armhf 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.) -- 1068735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenmpi3t64 Version: 4.1.6-8 Severity: serious X-Debbugs-Cc: maril...@deb-multimedia.org Hi, apt-get error message : Unpacking libopenmpi3t64:armhf (4.1.6-9) over (4.1.6-8) ... dpkg: error processing archive /tmp/apt-dpkg-install-0UNMnK/4-libopenmpi3t64_4.1.6-9_armhf.deb (--unpack): trying to overwrite '/usr/lib/arm-linux-gnueabihf/libpmix.so.2', which is also in package libpmix2t64:armhf 5.0.1-4.1 Christian -- System Information: Debian Release: trixie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 6.1.83 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopenmpi3t64 depends on: ii libc6 2.37-16 ii libevent-core-2.1-7t64 2.1.12-stable-8.1+b3 ii libevent-pthreads-2.1-7t64 2.1.12-stable-8.1+b3 ii libfabric1 1.17.0-3+b1 ii libgcc-s1 14-20240330-1 ii libhwloc-plugins2.10.0-1+b1 ii libhwloc15 2.10.0-1+b1 ii libibverbs1 50.0-2+b1 ii libnl-3-200 3.7.0-0.3 ii libstdc++6 14-20240330-1 ii zlib1g 1:1.3.dfsg-3.1 libopenmpi3t64 recommends no packages. libopenmpi3t64 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 4.1.6-12 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of openmpi, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi 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: Wed, 17 Apr 2024 14:45:23 +0100 Source: openmpi Architecture: source Version: 4.1.6-12 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1068735 Changes: openmpi (4.1.6-12) unstable; urgency=medium . * Use Conflicts/Provides/Replaces libpmix2. Closes: #1068735 * Patch from Adrian Bunk for atomics. Checksums-Sha1: 64b3f9e2c798ae23f558fb6bedaa939bce8a754e 2833 openmpi_4.1.6-12.dsc 7f77e718b7e2f735d45e49af356df8e7aef3ba11 69748 openmpi_4.1.6-12.debian.tar.xz Checksums-Sha256: e9e5a8c54a023b05d58eadacfab14b9d41b23acbd0d4a9fb990aa50c017afca9 2833 openmpi_4.1.6-12.dsc a42b60297476fc25699ea7eac2da5a2f45399a82bbb90fee6abe21217842f113 69748 openmpi_4.1.6-12.debian.tar.xz Files: 717bbe50a185c3ad60b9e5979df77811 2833 net optional openmpi_4.1.6-12.dsc 472df8dc3263a19a3d3c1fa0e18edb6d 69748 net optional openmpi_4.1.6-12.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmYf3IsACgkQy+a7Tl2a 06XsYg/7B6Yfyc/7tzTDN1YsCtvE8OhMhzC3RaEmkIY/IiwQ/+zYKrOKfaBKABYP yt/J01JQOYPhGQaXgT9Qi0y4EOcMHkSdXY7sfoKRilMm1RrtLePKCHCOzSBcTLi7 CvC+uQC2klKGMichlJ/SvzjSQjzMaMV5WUSajch1ngCHyLurpBljgKYOTF5iLmV1 IX7HD+ghprcdpdAUOvNv+HwVcQaA6fh9tlFnnSF2gPAFZROb1XCrjJMsMaommKHP WvwmT1aw6YqBCGsBzfRHhOZjC617n+dQY8iAkszzb/n83bLBQtGpfmFoe7bVp1HJ JgvJ8q14hVGZDc8Y/EBET0fhJ0hi5S89Sh6whPLLWI6y+r6q30wVkxjE0YaqRDZu aYP4myKK4fWros/OG826KWf/s8eplb2ojHq6LHTVDozLOFAM59YYeqOfyy2pdA1U TT6+D+SD0euWBPUmUGuHYDU2DtMf+0UO19jMywlflCo8d+SiAKd5QLkC1hE5fZ6s /f6/n4xzob2xRjojsIw6OmxVFJNPuRET8YUeXmaN8QxZRonkI0gAqglVPjZKChAc dxEjRj6dut1TzGflr9zjfOXSuZRziRdkSHPyTxhlsRNcL2f02XvXVVkBV7VUcAZz jddfHTIR27e7idemW4d5bq5KE2eODIw8ObcKQjEu+ZwzKqn2QSg= =ILai -END PGP SIGNATURE- pgpptV5qGRc5F.pgp
Bug#1067532: marked as done (nagios-plugins-contrib: Testsuite fails with openssl 3.2)
Your message dated Wed, 17 Apr 2024 14:49:24 +
with message-id
and subject line Bug#1067532: fixed in nagios-plugins-contrib 46.20240417
has caused the Debian Bug report #1067532,
regarding nagios-plugins-contrib: Testsuite fails with openssl 3.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagios-plugins-contrib
Version: 45.20231212
Severity: important
Tags: sid patch
control: affects -1 src:openssl
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-3.2
The package fails the debci testsuite with OpenSSL 3.2 due to output on
stderr. The patch attached is a backport from upstream which avoids
output on stderr.
Sebastian
From: Matteo Corti
Date: Fri, 24 Nov 2023 13:20:59 +0100
Subject: [PATCH] First fix for the STDIN warning on OpenSSL 3.2.0
Applied-Upstream: https://github.com/matteocorti/check_ssl_cert/commit/2c2795860adc165c35f5948116261cb76a94c954
---
check_ssl_cert/check_ssl_cert_2.75.0/check_ssl_cert | 72 ++--
1 file changed, 36 insertions(+), 36 deletions(-)
--- a/check_ssl_cert/check_ssl_cert_2.75.0/check_ssl_cert
+++ b/check_ssl_cert/check_ssl_cert_2.75.0/check_ssl_cert
@@ -1557,8 +1557,8 @@ extract_cert_attribute() {
# shellcheck disable=SC2086,SC2016
case $1 in
cn)
-if echo "${cert_content}" | "${OPENSSL}" x509 -noout ${OPENSSL_PARAMS} -subject 2>/dev/null | "${GREP_BIN}" -F -q 'CN' >/dev/null; then
-echo "${cert_content}" | "${OPENSSL}" x509 -noout ${OPENSSL_PARAMS} -subject |
+if echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout ${OPENSSL_PARAMS} -subject 2>/dev/null | "${GREP_BIN}" -F -q 'CN' >/dev/null; then
+echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout ${OPENSSL_PARAMS} -subject |
sed -e "s/^.*[[:space:]]*CN[[:space:]]=[[:space:]]//" -e 's/\/[[:alpha:]][[:alpha:]]*=.*$//' -e "s/,.*//"
else
echo 'CN unavailable'
@@ -1567,76 +1567,76 @@ extract_cert_attribute() {
;;
subject)
# the Subject could contain UTF-8 characters
-echo "${cert_content}" | "${OPENSSL}" x509 -noout ${OPENSSL_PARAMS} -subject -nameopt utf8
+echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout ${OPENSSL_PARAMS} -subject -nameopt utf8
;;
serial)
-echo "${cert_content}" | "${OPENSSL}" x509 -noout -serial | sed -e "s/^serial=//"
+echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout -serial | sed -e "s/^serial=//"
;;
fingerprint)
-echo "${cert_content}" | "${OPENSSL}" x509 -noout -fingerprint -sha1 | sed -e "s/^SHA1 Fingerprint=//"
+echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout -fingerprint -sha1 | sed -e "s/^SHA1 Fingerprint=//"
;;
oscp_uri)
-echo "${cert_content}" | "${OPENSSL}" "${OPENSSL_COMMAND}" -noout ${OPENSSL_PARAMS} -ocsp_uri
+echo "${cert_content}" | "${OPENSSL}" "${OPENSSL_COMMAND}" -in /dev/stdin -noout ${OPENSSL_PARAMS} -ocsp_uri
;;
oscp_uri_single)
extract_cert_attribute 'oscp_uri' "${cert_content}" | head -n 1
;;
hash)
-echo "${cert_content}" | "${OPENSSL}" x509 -noout -hash
+echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout -hash
;;
modulus)
-echo "${cert_content}" | "${OPENSSL}" x509 -noout -modulus
+echo "${cert_content}" | "${OPENSSL}" x509 -in /dev/stdin -noout -modulus
;;
issuer)
# see https://unix.stackexchange.com/questions/676776/parse-comma-separated-string-ignoring-commas-between-quotes
-echo "${cert_content}" | "${OPENSSL}" "${OPENSSL_COMMAND}" -noout -nameopt sep_multiline,utf8,esc_ctrl -issuer |
+echo "${cert_content}" | "${OPENSSL}" "${OPENSSL_COMMAND}" -in /dev/stdin -noout -nameopt sep_multiline,utf8,esc_ctrl -issuer |
tail -n +2 |
sed 's/^ *//'
;;
issuer_uri)
-echo "${cert_content}" | "${OPENSSL}" "${OPENSSL_COMMAND}" -noout ${OPENSSL_PARAMS} -text | "${GREP_BIN}" -F "CA Issuers" | "${GREP_BIN}" -F -i "http" | sed -e "s/^.*CA Issuers - URI://" | tr -d '"!|;${}<>`&'
+echo "${cert_content}" | "${OPENSSL}" "${OPENSSL_COMMAND}" -in /dev/stdin -noout ${OPENSSL_PARAMS} -text | "${GREP_BIN}" -F "CA Issuers" | "${GREP_BIN}" -F -i "http" | sed -e "s/^.*CA Issuers - URI://" | tr -d '"!|;${}<>`&'
;;
issuer_uri_single)
Bug#1066576: marked as done (nagios-plugins-contrib: FTBFS: check_memcached.l:339:37: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaratio
Your message dated Wed, 17 Apr 2024 14:49:24 +
with message-id
and subject line Bug#1066576: fixed in nagios-plugins-contrib 46.20240417
has caused the Debian Bug report #1066576,
regarding nagios-plugins-contrib: FTBFS: check_memcached.l:339:37: error:
implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’?
[-Werror=implicit-function-declaration]
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.)
--
1066576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nagios-plugins-contrib
Version: 45.20231212
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>/check_memcached=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -c -o check_memcached.o check_memcached.c
> check_memcached.l:155:1: warning: return type defaults to ‘int’
> [-Wimplicit-int]
> 155 | yywrap() {
> | ^~
> check_memcached.l: In function ‘check_memcached’:
> check_memcached.l:339:37: error: implicit declaration of function ‘asprintf’;
> did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
> 339 | str_bytes =
> asprintf(_service_output,"Could not store updated stats object - %s; ",
> | ^~~~
> | vsprintf
> check_memcached.l: In function ‘usage’:
> check_memcached.l:603:16: warning: format ‘%llu’ expects argument of type
> ‘long long unsigned int’, but argument 2 has type ‘uint64_t’ {aka ‘long
> unsigned int’} [-Wformat=]
> 603 | printf("\t-E ... Generate warning if number of evictions
> exceeds this threshold. 0=disable. (default: %llu)\n",max_evictions);
> |
> ^~~~
> ~
> |
> |
> |
> uint64_t {aka long unsigned
> int}
> cc1: some warnings being treated as errors
> make[3]: *** [: check_memcached.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/nagios-plugins-contrib_45.20231212_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: nagios-plugins-contrib
Source-Version: 46.20240417
Done: Jan Wagner
We believe that the bug you reported is fixed in the latest version of
nagios-plugins-contrib, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jan Wagner (supplier of updated nagios-plugins-contrib
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:
Bug#1064019: marked as done (stdgpu: FTBFS on armel: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Wed, 17 Apr 2024 14:37:11 + with message-id and subject line Bug#1064019: fixed in stdgpu 1.3.0+git20220507.32e0517-6 has caused the Debian Bug report #1064019, regarding stdgpu: FTBFS on armel: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 1064019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stdgpu Version: 1.3.0+git20220507.32e0517-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=stdgpu=armel=1.3.0%2Bgit20220507.32e0517-5%2Bb1=1707543753=0 1: stdgpu::deque::push_front : Object full 1: [ OK ] stdgpu_deque.push_front_too_many (40 ms) 1: [ RUN ] stdgpu_deque.push_front_const_type 1: [ OK ] stdgpu_deque.push_front_const_type (13 ms) 1: [ RUN ] stdgpu_deque.push_front_nondefault_type 1: [ OK ] stdgpu_deque.push_front_nondefault_type (14 ms) 1: [ RUN ] stdgpu_deque.emplace_front_some 1: [ OK ] stdgpu_deque.emplace_front_some (17 ms) 1: [ RUN ] stdgpu_deque.emplace_front_all 1: [ OK ] stdgpu_deque.emplace_front_all (40 ms) 1: [ RUN ] stdgpu_deque.emplace_front_too_many 1: stdgpu::deque::push_front : Object full 1: [ OK ] stdgpu_deque.emplace_front_too_many (41 ms) 1: [ RUN ] stdgpu_deque.emplace_front_const_type 1: [ OK ] stdgpu_deque.emplace_front_const_type (14 ms) 1: [ RUN ] stdgpu_deque.emplace_front_nondefault_type 1: [ OK ] stdgpu_deque.emplace_front_nondefault_type (13 ms) 1: [ RUN ] stdgpu_deque.push_back_circular 1: [ OK ] stdgpu_deque.push_back_circular (32 ms) 1: [ RUN ] stdgpu_deque.push_front_circular 1: [ OK ] stdgpu_deque.push_front_circular (32 ms) 1: [ RUN ] stdgpu_deque.clear 1: [ OK ] stdgpu_deque.clear (14 ms) 1: [ RUN ] stdgpu_deque.clear_full 1: [ OK ] stdgpu_deque.clear_full (14 ms) 1: [ RUN ] stdgpu_deque.clear_circular 1: [ OK ] stdgpu_deque.clear_circular (21 ms) 1: [ RUN ] stdgpu_deque.clear_nondefault_type 1: [ OK ] stdgpu_deque.clear_nondefault_type (13 ms) 1: [ RUN ] stdgpu_deque.clear_nondefault_type_full 1: [ OK ] stdgpu_deque.clear_nondefault_type_full (13 ms) 1: [ RUN ] stdgpu_deque.clear_nondefault_type_circular 1: [ OK ] stdgpu_deque.clear_nondefault_type_circular (20 ms) 1: [ RUN ] stdgpu_deque.simultaneous_push_back_and_pop_back E: Build killed with signal TERM after 150 minutes of inactivity Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: stdgpu Source-Version: 1.3.0+git20220507.32e0517-6 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of stdgpu, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated stdgpu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 16:10:56 +0200 Source: stdgpu Architecture: source Version: 1.3.0+git20220507.32e0517-6 Distribution: unstable Urgency: medium Maintainer: Timo Röhling Changed-By: Timo Röhling Closes: 1064019 Changes: stdgpu (1.3.0+git20220507.32e0517-6) unstable; urgency=medium . * Skip testing on armhf and armel (Closes: #1064019) Checksums-Sha1: 64aa5a9111a4497afa5e5d070d9c990526800b82 2936 stdgpu_1.3.0+git20220507.32e0517-6.dsc d49e7ee14feb682749ccf12357c19ea43cdd98c8 12480 stdgpu_1.3.0+git20220507.32e0517-6.debian.tar.xz Checksums-Sha256: b2237c811287b7d17da0227c0cc7d9f5d2c802f3b18c806f8dde377f0938a511 2936 stdgpu_1.3.0+git20220507.32e0517-6.dsc 76eab36882ba0556c62a2364a28a4c274df71ea21daef04fb90076f71beadefa 12480 stdgpu_1.3.0+git20220507.32e0517-6.debian.tar.xz Files: 5540838a2136ef19954bd04dd478e3cf 2936 libs optional stdgpu_1.3.0+git20220507.32e0517-6.dsc 38f87d97fd00b05bbc787385454438f7 12480 libs optional
Processed: reopen
Processing commands for cont...@bugs.debian.org: > reopen 661818 Bug #661818 [libreoffice] libreoffice: some menu icons are missing in KDE menu (but appear in editor) Bug 661818 is not marked as done; doing nothing. > reopen 669064 Bug #669064 [libreoffice-calc] libreoffice-calc: LibreOffice Calc is not shown in top context menu of xlsx files like for xls files Bug 669064 is not marked as done; doing nothing. > reopen 708533 Bug #708533 [libreoffice] libreoffice: connects to the print server (CUPS) when opening some document Bug 708533 is not marked as done; doing nothing. > reopen 729936 Bug #729936 [libreoffice-writer] libreoffice-writer: autotext and menu inserted fields gives different values Bug 729936 is not marked as done; doing nothing. > reopen 754333 Bug #754333 [libreoffice-common] libreoffice-common: junk output on rmdir in libreoffice-common.postrm.in Bug #883443 [libreoffice-common] rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or directory Bug 754333 is not marked as done; doing nothing. > reopen 772097 Bug #772097 [libreoffice] libreoffice: LibreOffice sees only "Generic Printer" Bug 772097 is not marked as done; doing nothing. > reopen 776950 Bug #776950 [libreoffice] libreoffice: Open LibreOffice Basic crash LibreOffice Bug 776950 is not marked as done; doing nothing. > reopen 804174 Bug #804174 [libreoffice] Keyboard shortcuts (Ctrl-Q etc.) do not work Bug #812081 [libreoffice] Keyboard shortcuts (Ctrl-Q etc.) do not work Bug 804174 is not marked as done; doing nothing. > reopen 808754 Bug #808754 [libreoffice] libreoffice: lightproof-en settings revert after each update Bug 808754 is not marked as done; doing nothing. > reopen 819577 Bug #819577 [libreoffice-calc] libreoffice-calc: Crash after runtime error in LibreOffice Basic after changing Code Bug 819577 is not marked as done; doing nothing. > reopen 820350 Bug #820350 [libreoffice] libreoffice: Packaging LibreOfice Still for stable branch of the Debian Bug #914619 [libreoffice] "LibreOffice Still" should be used by the stable distribution Bug 820350 is not marked as done; doing nothing. > reopen 821401 Bug #821401 [libreoffice-gtk3] libreoffice-gtk3: First [Ctrl+Scroll Down] after changing focus to LO makes LO to zoom in instead of zoom out Bug 821401 is not marked as done; doing nothing. > reopen 825650 Bug #825650 [libreoffice-common] libreoffice-common: prompting due to modified conffiles which were not modified by the user: /etc/libreoffice/sofficerc Bug 825650 is not marked as done; doing nothing. > reopen 827459 Bug #827459 [src:libreoffice] libreoffice changes gnome-workspaces on popup Bug 827459 is not marked as done; doing nothing. > reopen 827535 Bug #827535 [libreoffice] libreoffice: system proxy setting does not stick Bug 827535 is not marked as done; doing nothing. > reopen 827911 Bug #827911 [libreoffice-common] libreoffice-common: please ship LibreOffice-bundled fonts missing from Debian otherwise Bug 827911 is not marked as done; doing nothing. > reopen 829379 Bug #829379 [src:libreoffice] fix initialization of DEB_VENDOR for derivatives Bug 829379 is not marked as done; doing nothing. > reopen 834947 Bug #834947 [libreoffice-base] libreoffice-base: Screen redraw problems: no navigation block and random redraw failures Bug 834947 is not marked as done; doing nothing. > reopen 836935 Bug #836935 [libreoffice-gtk3] libreoffice-gtk3: Setting GDK_SCALE and GDK_DPI_SCALE to values other than 1 screws up rendering Bug 836935 is not marked as done; doing nothing. > reopen 838262 Bug #838262 [libreoffice-calc] libreoffice-calc: Renders wrong characters in sheet after some time Bug 838262 is not marked as done; doing nothing. > reopen 852326 Bug #852326 [libreoffice-common] libreoffice-common: Please add Multi-Arch: foreign Bug 852326 is not marked as done; doing nothing. > reopen 854623 Bug #854623 [libreoffice] libreoffice: Libreoffice form control properties are inaccessible under gnome wayland Bug 854623 is not marked as done; doing nothing. > reopen 857441 Bug #857441 [libreoffice-writer,okular] Okular takes precedence over LibreOffice for ODT files Bug #857443 [libreoffice-writer,okular] Okular takes precedence over LibreOffice for ODT files Bug 857441 is not marked as done; doing nothing. > reopen 867591 Bug #867591 [libreoffice,libreoffice-dmaths] libreoffice-writer: bug or no bug? Libreoffice-dmath inhibits to open gallery in libreoffice-writer Bug #908513 [libreoffice,libreoffice-dmaths] libreoffice - missing gallery when Dmaths is installed Bug 867591 is not marked as done; doing nothing. > reopen 870278 Bug #870278 [libreoffice-writer] libreoffice-writer: Some lines of text are not visible for assistive technologies Bug 870278 is not marked as done; doing nothing. > reopen 870291 Bug #870291 [libreoffice-writer] libreoffice-writer: No accessible caret-moved events in Writer tables Bug 870291 is not marked as done; doing nothing. > reopen 870296 Bug #870296
Processed: reopen bugs closed by dak
Processing commands for cont...@bugs.debian.org:
> reopen 640462
Bug #640462 {Done: Debian FTP Masters }
[libreoffice] libreoffice: default window appears partly off-screen
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 661818
Bug #661818 {Done: Debian FTP Masters }
[libreoffice] libreoffice: some menu icons are missing in KDE menu (but appear
in editor)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 669064
Bug #669064 {Done: Debian FTP Masters }
[libreoffice-calc] libreoffice-calc: LibreOffice Calc is not shown in top
context menu of xlsx files like for xls files
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 708533
Bug #708533 {Done: Debian FTP Masters }
[libreoffice] libreoffice: connects to the print server (CUPS) when opening
some document
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 729936
Bug #729936 {Done: Debian FTP Masters }
[libreoffice-writer] libreoffice-writer: autotext and menu inserted fields
gives different values
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 754333
Bug #754333 {Done: Debian FTP Masters }
[libreoffice-common] libreoffice-common: junk output on rmdir in
libreoffice-common.postrm.in
Bug #883443 {Done: Debian FTP Masters }
[libreoffice-common] rmdir: failed to remove
'/var/lib/libreoffice/share/prereg/': No such file or directory
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 772097
Bug #772097 {Done: Debian FTP Masters }
[libreoffice] libreoffice: LibreOffice sees only "Generic Printer"
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 776950
Bug #776950 {Done: Debian FTP Masters }
[libreoffice] libreoffice: Open LibreOffice Basic crash LibreOffice
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 804174
Bug #804174 {Done: Debian FTP Masters }
[libreoffice] Keyboard shortcuts (Ctrl-Q etc.) do not work
Bug #812081 {Done: Debian FTP Masters }
[libreoffice] Keyboard shortcuts (Ctrl-Q etc.) do not work
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 808754
Bug #808754 {Done: Debian FTP Masters }
[libreoffice] libreoffice: lightproof-en settings revert after each update
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 819577
Bug #819577 {Done: Debian FTP Masters }
[libreoffice-calc] libreoffice-calc: Crash after runtime error in LibreOffice
Basic after changing Code
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 820350
Bug #820350 {Done: Debian FTP Masters }
[libreoffice] libreoffice: Packaging LibreOfice Still for stable branch of the
Debian
Bug #914619 {Done: Debian FTP Masters }
[libreoffice] "LibreOffice Still" should be used by the stable distribution
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 821401
Bug #821401 {Done: Debian FTP Masters }
[libreoffice-gtk3] libreoffice-gtk3: First [Ctrl+Scroll Down] after changing
focus to LO makes LO
Bug#1063631: [Debian-pan-maintainers] Bug#1063631: closing 1063631
I am working on it at the upstream level need a few more days. Cheers Fred
Bug#1066547: fixed in xf86-input-mtrack 0.3.1-1.2
sorry for the noise, sending another final diff with all the NMUs inside.
Found that libmtd1 was also listed as runtime dependency, so I removed it.
G.
diff -Nru xf86-input-mtrack-0.3.1/debian/changelog
xf86-input-mtrack-0.3.1/debian/changelog
--- xf86-input-mtrack-0.3.1/debian/changelog2015-06-02 07:09:33.0
+0200
+++ xf86-input-mtrack-0.3.1/debian/changelog2024-04-17 15:07:26.0
+0200
@@ -1,3 +1,27 @@
+xf86-input-mtrack (0.3.1-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop runtime dependency on old libmtdev1
+
+ -- Gianfranco Costamagna Wed, 17 Apr 2024
15:07:26 +0200
+
+xf86-input-mtrack (0.3.1-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Cherry-pick another patch from Benjamin Drung and
+xf86-input-multitouch 1.0~rc3-2.1 to fix another FTBFS due to time64_t
+(Closes: #1066547)
+
+ -- Gianfranco Costamagna Wed, 17 Apr 2024
08:18:29 +0200
+
+xf86-input-mtrack (0.3.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Add patch to fix implicit-function-declaration build failures
+(Closes: #1066547)
+
+ -- Gianfranco Costamagna Tue, 16 Apr 2024
23:32:48 +0200
+
xf86-input-mtrack (0.3.1-1) unstable; urgency=medium
* Upload to unstable.
diff -Nru xf86-input-mtrack-0.3.1/debian/control
xf86-input-mtrack-0.3.1/debian/control
--- xf86-input-mtrack-0.3.1/debian/control 2015-02-23 00:59:49.0
+0100
+++ xf86-input-mtrack-0.3.1/debian/control 2024-04-17 15:07:24.0
+0200
@@ -16,8 +16,7 @@
Architecture: linux-any
Depends: ${shlibs:Depends},
${misc:Depends},
- ${xinpdriver:Depends},
- libmtdev1 (>= 1.0.10)
+ ${xinpdriver:Depends}
Provides: ${xinpdriver:Provides}
Conflicts: xserver-xorg-input-multitouch
Description: Multitouch X input driver
diff -Nru
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
---
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
1970-01-01 01:00:00.0 +0100
+++
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
2024-04-17 08:18:29.0 +0200
@@ -0,0 +1,28 @@
+Description: Add patch to fix missing includes
+Author: Gianfranco Costamagna
+Last-Update: 2024-04-17
+
+Index: xf86-input-mtrack-0.3.1/src/gestures.c
+===
+--- xf86-input-mtrack-0.3.1.orig/src/gestures.c
xf86-input-mtrack-0.3.1/src/gestures.c
+@@ -28,6 +28,7 @@
+ #include "gestures.h"
+ #include "mtouch.h"
+ #include "trig.h"
++#include
+
+ #define IS_VALID_BUTTON(x) (x >= 0 && x <= 31)
+
+Index: xf86-input-mtrack-0.3.1/tools/mtrack-test.c
+===
+--- xf86-input-mtrack-0.3.1.orig/tools/mtrack-test.c
xf86-input-mtrack-0.3.1/tools/mtrack-test.c
+@@ -23,6 +23,7 @@
+ #include "mtouch.h"
+ #include
+ #include
++#include
+
+ void xf86Msg(int type, const char *format, ...)
+ {
diff -Nru
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
---
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
1970-01-01 01:00:00.0 +0100
+++
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
2024-04-17 15:07:11.0 +0200
@@ -0,0 +1,22 @@
+From: Benjamin Drung
+Date: Mon, 15 Apr 2024 19:56:58 +0200
+Subject: Port usage of struct input_event to input_event_*
+
+---
+ src/hwstate.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: xf86-input-mtrack-0.3.1/src/hwstate.c
+===
+--- xf86-input-mtrack-0.3.1.orig/src/hwstate.c
xf86-input-mtrack-0.3.1/src/hwstate.c
+@@ -42,7 +42,8 @@
+ if (!caps->has_abs[MTDEV_WIDTH_MINOR])
+ s->data[i].width_minor = s->data[i].width_major;
+ }
+- timercp(>evtime, >time);
++ s->evtime.tv_sec = syn->input_event_sec;
++ s->evtime.tv_usec = syn->input_event_usec;
+ }
+
+ static int read_event(struct HWState *s, const struct Capabilities *caps,
diff -Nru xf86-input-mtrack-0.3.1/debian/patches/series
xf86-input-mtrack-0.3.1/debian/patches/series
--- xf86-input-mtrack-0.3.1/debian/patches/series 2012-07-05
09:57:49.0 +0200
+++ xf86-input-mtrack-0.3.1/debian/patches/series 2024-04-17
08:12:31.0 +0200
@@ -1,3 +1,5 @@
#drop-mtrack-test
#aa
upsteam-commit
+missing-includes-implicit-function-declaration-fix.patch
+Port-usage-of-struct-input_event-to-input_event_.patch
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1063631: closing 1063631
Hi Roland, On 2024-03-05 03:15, Roland Mas wrote: > close 1063631 5.0.0.3381-2 The version of hkl currently in unstable, 5.0.0.3381-1, fails to build. Would it be possible to upload 5.0.0.3381-2 to unstable? Emanuele
Bug#1013601: marked as done (python-sshoot: FTBFS: /bin/sh: 1: register-python-argcomplete3: not found)
Your message dated Wed, 17 Apr 2024 12:49:23 + with message-id and subject line Bug#1013601: fixed in python-sshoot 1.4.2-3 has caused the Debian Bug report #1013601, regarding python-sshoot: FTBFS: /bin/sh: 1: register-python-argcomplete3: not found 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.) -- 1013601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-sshoot Version: 1.4.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > dh_auto_build: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > I: pybuild base:239: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/i18n.py -> /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/listing.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/manager.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/autocomplete.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/profile.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/main.py -> /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/config.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/conftest.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > creating /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_manager.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_config.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_listing.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_autocomplete.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_profile.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > running egg_info > creating sshoot.egg-info > writing sshoot.egg-info/PKG-INFO > writing dependency_links to sshoot.egg-info/dependency_links.txt > writing entry points to sshoot.egg-info/entry_points.txt > writing requirements to sshoot.egg-info/requires.txt > writing top-level names to sshoot.egg-info/top_level.txt > writing manifest file 'sshoot.egg-info/SOURCES.txt' > reading manifest file 'sshoot.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE.txt' > writing manifest file 'sshoot.egg-info/SOURCES.txt' > creating /<>/.pybuild/cpython3_3.10/build/sshoot/locale > copying sshoot/locale/argparse.pot -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale > copying sshoot/locale/sshoot.pot -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale > creating /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT > creating > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/argparse.mo -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/argparse.po -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/sshoot.mo -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/sshoot.po -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > register-python-argcomplete3 --shell bash sshoot \ > > debian/bash-completion > /bin/sh: 1: register-python-argcomplete3: not found > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 127 The full build log is available from: http://qa-logs.debian.net/2022/06/24/python-sshoot_1.4.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail
Bug#1068457: marked as done (azure-uamqp-python: CVE-2024-29195)
Your message dated Wed, 17 Apr 2024 12:34:24 + with message-id and subject line Bug#1068457: fixed in azure-uamqp-python 1.6.9-2 has caused the Debian Bug report #1068457, regarding azure-uamqp-python: CVE-2024-29195 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.) -- 1068457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: azure-uamqp-python X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for azure-uamqp-python. CVE-2024-29195[0]: | The azure-c-shared-utility is a C library for AMQP/MQTT | communication to Azure Cloud Services. This library may be used by | the Azure IoT C SDK for communication between IoT Hub and IoT Hub | devices. An attacker can cause an integer wraparound or under- | allocation or heap buffer overflow due to vulnerabilities in | parameter checking mechanism, by exploiting the buffer length | parameter in Azure C SDK, which may lead to remote code execution. | Requirements for RCE are 1. Compromised Azure account allowing | malformed payloads to be sent to the device via IoT Hub service, 2. | By passing IoT hub service max message payload limit of 128KB, and | 3. Ability to overwrite code space with remote code. Fixed in commit | https://github.com/Azure/azure-c-shared- | utility/commit/1129147c38ac02ad974c4c701a1e01b2141b9fe2. https://github.com/Azure/azure-c-shared-utility/security/advisories/GHSA-m8wp-hc7w-x4xg https://github.com/Azure/azure-c-shared-utility/commit/1129147c38ac02ad974c4c701a1e01b2141b9fe2 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-29195 https://www.cve.org/CVERecord?id=CVE-2024-29195 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: azure-uamqp-python Source-Version: 1.6.9-2 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of azure-uamqp-python, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated azure-uamqp-python 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: Wed, 17 Apr 2024 14:08:51 +0200 Source: azure-uamqp-python Architecture: source Version: 1.6.9-2 Distribution: unstable Urgency: high Maintainer: Debian Python Team Changed-By: Thomas Goirand Closes: 1068457 Changes: azure-uamqp-python (1.6.9-2) unstable; urgency=high . * Team upload. * CVE-2024-29195: An attacker can cause an integer wraparound or under- allocation or heap buffer overflow due to vulnerabilities in parameter checking mechanism, by exploiting the buffer length parameter in Azure C SDK, which may lead to remote code execution. Applied upstream patch: CVE-2024-29195_Add-malloc-size-checks.patch (Closes: #1068457). Checksums-Sha1: da0868c3083fdc4eae499788754d3241fa30f678 2316 azure-uamqp-python_1.6.9-2.dsc b70fda15971f4a2ebc0ef8298c1857b886fddbb6 11624 azure-uamqp-python_1.6.9-2.debian.tar.xz 840627ba390b18bef514eaef014f72660a0a173d 9095 azure-uamqp-python_1.6.9-2_amd64.buildinfo Checksums-Sha256: 09039d63c22f81849fbbafe413dc423381ee019b47c68bffa765e6e799cf4a57 2316 azure-uamqp-python_1.6.9-2.dsc b0eddda10d4e1197393603e560db78c5caa27cc58d2d91d8fefeddc4243c5bd5 11624 azure-uamqp-python_1.6.9-2.debian.tar.xz 31fd787e426531456f80a953e83339c36281350bf0073dbaad81dd557db097f6 9095 azure-uamqp-python_1.6.9-2_amd64.buildinfo Files: a19610664fc8fd4d090699f9b03f1062 2316 python optional azure-uamqp-python_1.6.9-2.dsc 5140a3fdbb875f8eb29ae443e471c41b 11624 python optional azure-uamqp-python_1.6.9-2.debian.tar.xz ab7997a1ad2913b7afe38df2fe7582bd 9095 python optional azure-uamqp-python_1.6.9-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmYfvqUACgkQ1BatFaxr
Bug#1064726: reopen, still ftbfs
Hello Matthias, On Sun, 14 Apr 2024 20:45:07 +0200 Matthias Klose wrote: > Control: reopen -1 > > the package still build-depends on python3-distutils, removed in 3.12. > > the package then ftbfs with > > [...] > line 13, in > from six.moves import builtins as __builtin__ I just rebuilt 0ad from a clean & updated sid chroot and had no problem. I then found the problem: Python 3.12 is in experimental and not yet in sid. So the FTBFS occurs only with packages from experimental. I understand it will be a problem SOON. Maybe you should have created a *new* bug instead of reopening this one since that is not the same problem. I will work on the issue. Thanks
Bug#1064726: reopen, still ftbfs
Le 17/04/2024 à 14:17, Ludovic Rousseau a écrit : I will work on the issue. The problem with Python 3.12 is already known upstream in https://trac.wildfiregames.com/ticket/6895 It should be fixed with the next version of 0ad i.e. alpha 27. Bye -- Dr. Ludovic Rousseau
Bug#1066780: Checking in on this bug
Hello, It would probably be good to update our package to 0.42.0, since it contains a fix for CVE-2024-22189. Perhaps that would also contain a fix for this? I don't know how hard this issue is to track down, but it will be leading to several packages being unpatched and removed from testing otherwise. Thanks! - John
Processed: Bug#1068457 marked as pending in azure-uamqp-python
Processing control commands: > tag -1 pending Bug #1068457 [src:azure-uamqp-python] azure-uamqp-python: CVE-2024-29195 Added tag(s) pending. -- 1068457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068457: marked as pending in azure-uamqp-python
Control: tag -1 pending Hello, Bug #1068457 in azure-uamqp-python 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/azure-uamqp-python/-/commit/f4f79087f50551619f9659594ecf7f08f6acb952 * CVE-2024-29195: An attacker can cause an integer wraparound or under- allocation or heap buffer overflow due to vulnerabilities in parameter checking mechanism, by exploiting the buffer length parameter in Azure C SDK, which may lead to remote code execution. Applied upstream patch: CVE-2024-29195_Add-malloc-size-checks.patch (Closes: #1068457). (this message was generated automatically) -- Greetings https://bugs.debian.org/1068457
Bug#948087: marked as done (aufs build depends on the removed linux-kbuild-5.2)
Your message dated Wed, 17 Apr 2024 12:12:13 + with message-id and subject line Bug#1069153: Removed package(s) from unstable has caused the Debian Bug report #948087, regarding aufs build depends on the removed linux-kbuild-5.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aufs Version: 5.2+20190909-1.1 Severity: serious Tags: ftbfs linux-kbuild-5.4 is now in unstable. --- End Message --- --- Begin Message --- Version: 5.2+20190909-1.1+rm Dear submitter, as the package aufs has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069153 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1061369: marked as done (fsprotect: proposal to remove)
Your message dated Wed, 17 Apr 2024 12:11:39 + with message-id and subject line Bug#1069154: Removed package(s) from unstable has caused the Debian Bug report #1061369, regarding fsprotect: proposal to remove 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.) -- 1061369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fsprotect Severity: serious fsprotect hasn't made it into bullseye or bookworm. It depends on the broken aufs package. It hasn't seen a (non-QA) upload since 2017. With this background I propose removal from unstable. If you intend to keep fsprotect in Debian, please start maintaining the package (and aufs!) _now_. Chris --- End Message --- --- Begin Message --- Version: 1.0.7+nmu1+rm Dear submitter, as the package fsprotect has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069154 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#958600: marked as done (xorp: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Wed, 17 Apr 2024 12:10:39 + with message-id and subject line Bug#1069152: Removed package(s) from unstable has caused the Debian Bug report #958600, regarding xorp: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorp Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package xorp declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Version: 1.8.6~wip.20160715-2+rm Dear submitter, as the package xorp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069152 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#981761: marked as done (netopeer2 installs world-writable files)
Your message dated Wed, 17 Apr 2024 12:10:10 + with message-id and subject line Bug#1069151: Removed package(s) from unstable has caused the Debian Bug report #981761, regarding netopeer2 installs world-writable files 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.) -- 981761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netopeer2 Version: 1.1.39-1 Severity: serious https://piuparts.debian.org/sid/fail/netopeer2_1.1.39-1.log ... ERROR: BAD PERMISSIONS drwxrwxrwx 4 root root 100 Feb 1 03:12 /etc/sysrepo drwxrwxrwx 3 root root 500 Feb 1 03:12 /etc/sysrepo/data -rw-rw-rw- 1 root root7 Feb 1 03:12 /etc/sysrepo/data/ietf-datastores.startup -rw-rw-rw- 1 root root7 Feb 1 03:12 /etc/sysrepo/data/ietf-netconf-notifications.startup -rw-rw-rw- 1 root root7 Feb 1 03:12 /etc/sysrepo/data/ietf-netconf-with-defaults.startup -rw-rw-rw- 1 root root7 Feb 1 03:12 /etc/sysrepo/data/ietf-origin.startup -rw-rw-rw- 1 root root7 Feb 1 03:12 /etc/sysrepo/data/ietf-yang-library.startup drwxrwxrwx 2 root root 40 Feb 1 03:12 /etc/sysrepo/data/notif -rw-rw-rw- 1 root root 3372 Feb 1 03:12 /etc/sysrepo/data/sysrepo.startup -rw-rw-rw- 1 root root7 Feb 1 03:12 /etc/sysrepo/data/yang.startup -rw-rw-rw- 1 root root0 Feb 1 03:12 /etc/sysrepo/sr_main_lock drwxrwxrwx 2 root root 560 Feb 1 03:12 /etc/sysrepo/yang ... --- End Message --- --- Begin Message --- Version: 2.0.35-1+rm Dear submitter, as the package netopeer2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069151 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#958587: marked as done (lockdown FTBFS: Build-Depends on deprecated dh-systemd which is no longer available)
Your message dated Wed, 17 Apr 2024 12:09:11 + with message-id and subject line Bug#1069148: Removed package(s) from unstable has caused the Debian Bug report #958587, regarding lockdown FTBFS: Build-Depends on deprecated dh-systemd which is no longer available 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.) -- 958587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lockdown Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package lockdown declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Version: 0.2+nmu1+rm Dear submitter, as the package lockdown has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069148 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#947586: marked as done (FTBFS with scons 3.1.2-1)
Your message dated Wed, 17 Apr 2024 12:10:39 + with message-id and subject line Bug#1069152: Removed package(s) from unstable has caused the Debian Bug report #947586, regarding FTBFS with scons 3.1.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorp Version: 1.8.6~wip.20160715-2 Severity: important Usertags: scons_ftbfs Hello, in the context of the change to Python3 also Scons was revised. With the current version 3.1.2-1 from Experimental the changeover is finished so far. However, an error occurred while building your package. The build log is attached. Please check it and fix the error. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. xorp_1.8.6~wip.20160715-2_amd64.build Description: Binary data signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 1.8.6~wip.20160715-2+rm Dear submitter, as the package xorp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069152 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1035287: marked as done (netopeer2: missing Depends: adduser)
Your message dated Wed, 17 Apr 2024 12:10:10 + with message-id and subject line Bug#1069151: Removed package(s) from unstable has caused the Debian Bug report #1035287, regarding netopeer2: missing Depends: adduser 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.) -- 1035287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netopeer2 Version: 2.0.35-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. >From the attached log (scroll to the bottom...): Setting up netopeer2 (2.0.35-1+b1) ... /var/lib/dpkg/info/netopeer2.postinst: 24: addgroup: not found dpkg: error processing package netopeer2 (--configure): installed netopeer2 package post-installation script subprocess returned error exit status 127 Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: netopeer2 cheers, Andreas netopeer2_2.0.35-1+b1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 2.0.35-1+rm Dear submitter, as the package netopeer2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069151 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1005678: marked as done (cadvisor: FTBFS: src/github.com/google/cadvisor/container/libcontainer/helpers.go:176:24: too many arguments in call to fs2.NewManager)
Your message dated Wed, 17 Apr 2024 12:09:40 + with message-id and subject line Bug#1069149: Removed package(s) from unstable has caused the Debian Bug report #1005678, regarding cadvisor: FTBFS: src/github.com/google/cadvisor/container/libcontainer/helpers.go:176:24: too many arguments in call to fs2.NewManager 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.) -- 1005678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cadvisor Version: 0.38.7+ds1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 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 -- -ldflags '-X > github.com/google/cadvisor/version.Version=0.38.7+ds1 -X > github.com/google/cadvisor/version.Revision=0.38.7+ds1-2' > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 -ldflags "-X > github.com/google/cadvisor/version.Version=0.38.7+ds1 -X > github.com/google/cadvisor/version.Revision=0.38.7+ds1-2" > github.com/google/cadvisor github.com/google/cadvisor/accelerators > github.com/google/cadvisor/cache github.com/google/cadvisor/cache/memory > github.com/google/cadvisor/client github.com/google/cadvisor/client/v2 > github.com/google/cadvisor/cmd github.com/google/cadvisor/cmd/internal/api > github.com/google/cadvisor/cmd/internal/container/install > github.com/google/cadvisor/cmd/internal/container/mesos > github.com/google/cadvisor/cmd/internal/container/mesos/install > github.com/google/cadvisor/cmd/internal/healthz > github.com/google/cadvisor/cmd/internal/http > github.com/google/cadvisor/cmd/internal/http/mux > github.com/google/cadvisor/cmd/internal/storage/bigquery > github.com/google/cadvisor/cmd/internal/storage/bigquery/client > github.com/google/cadvisor/cmd/internal/storage/elasticsearch > github.com/google/cadvisor/cmd/internal/storage/kafka > github.com/google/cadvisor/cmd/internal/storage/redis > github.com/google/cadvisor/cmd/internal/storage/statsd > github.com/google/cadvisor/cmd/internal/storage/statsd/client > github.com/google/cadvisor/cmd/internal/storage/stdout > github.com/google/cadvisor/cmd/internal/storage/test > github.com/google/cadvisor/collector github.com/google/cadvisor/container > github.com/google/cadvisor/container/common > github.com/google/cadvisor/container/containerd > github.com/google/cadvisor/container/containerd/install > github.com/google/cadvisor/container/crio > github.com/google/cadvisor/container/crio/install > github.com/google/cadvisor/container/docker > github.com/google/cadvisor/container/docker/install > github.com/google/cadvisor/container/docker/utils > github.com/google/cadvisor/container/libcontainer > github.com/google/cadvisor/container/raw > github.com/google/cadvisor/container/systemd > github.com/google/cadvisor/container/systemd/install > github.com/google/cadvisor/container/testing > github.com/google/cadvisor/devicemapper > github.com/google/cadvisor/devicemapper/fake > github.com/google/cadvisor/events github.com/google/cadvisor/fs > github.com/google/cadvisor/info/v1 github.com/google/cadvisor/info/v1/test > github.com/google/cadvisor/info/v2 github.com/google/cadvisor/machine > github.com/google/cadvisor/manager github.com/google/cadvisor/metrics > github.com/google/cadvisor/nvm github.com/google/cadvisor/perf > github.com/google/cadvisor/resctrl github.com/google/cadvisor/stats > github.com/google/cadvisor/storage github.com/google/cadvisor/summary > github.com/google/cadvisor/utils github.com/google/cadvisor/utils/cloudinfo > github.com/google/cadvisor/utils/container > github.com/google/cadvisor/utils/cpuload > github.com/google/cadvisor/utils/cpuload/netlink > github.com/google/cadvisor/utils/oomparser > github.com/google/cadvisor/utils/sysfs > github.com/google/cadvisor/utils/sysfs/fakesysfs > github.com/google/cadvisor/utils/sysinfo github.com/google/cadvisor/validate > github.com/google/cadvisor/version github.com/google/cadvisor/watcher > github.com/google/cadvisor/zfs > github.com/google/cadvisor > internal/unsafeheader > internal/abi > internal/cpu > internal/goexperiment > runtime/internal/atomic > runtime/internal/sys > internal/race > runtime/internal/math > sync/atomic > unicode > internal/bytealg > unicode/utf8 > internal/itoa > math/bits > crypto/internal/subtle > crypto/subtle > math > internal/nettrace >
Bug#1058075: marked as done (lockdown: RM for trixie?)
Your message dated Wed, 17 Apr 2024 12:09:11 + with message-id and subject line Bug#1069148: Removed package(s) from unstable has caused the Debian Bug report #1058075, regarding lockdown: RM for trixie? 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.) -- 1058075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lockdown Severity: important Hi, lockdown missed bullseye and bookworm. It has an rc bug open since at least 2020. To me, it appears as if nobody cares about lockdown. Is it worth keeping it around in unstable? I would suggest to file an RM bug in a few weeks. Chris --- End Message --- --- Begin Message --- Version: 0.2+nmu1+rm Dear submitter, as the package lockdown has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069148 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1027994: marked as done (cadvisor fails to gather process metrics on bullseye because of cgroup change)
Your message dated Wed, 17 Apr 2024 12:09:40 + with message-id and subject line Bug#1069149: Removed package(s) from unstable has caused the Debian Bug report #1027994, regarding cadvisor fails to gather process metrics on bullseye because of cgroup change 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.) -- 1027994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cadvisor Version: 0.38.7+ds1-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: ssingh+deb...@wikimedia.org Dear Maintainer, The current version of cadvisor on Debian bullseye fails to gather process metrics because of a bug in the upstream version that results from bullseye defaulting to cgroup v2. This bug was fixed in https://github.com/google/cadvisor/pull/3030 by using the correct unified root path and accounting for the cgroup v2 change. The fix has not been backported but is available in the latest release of cadvisor. The current version of cadvisor in bullseye thus fails to gather metrics and other than a "Cannot detect current cgroup on cgroup v2" warning, there isn't any indication to the user. Backporting the specific patch will not work as the version in Debian is outdated: the latest cadvisor version at the time of writing this is 0.46.0 and was released in November 2022 with the above fix, whereas 0.38.7 was released in January 2021 and these two versions have deviated significantly. The only way to make the current version of cadvisor work is to set systemd.unified_cgroup_hierarchy=0 to enable the hybrid/legacy cgroup mode but that's not desirable, and thus perhaps, a new release of the cadvisor package is warranted. Thank you for your time. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cadvisor depends on: ii libc6 2.36-6 ii libzstd1 1.5.2+dfsg-1 cadvisor recommends no packages. cadvisor suggests no packages. --- End Message --- --- Begin Message --- Version: 0.38.7+ds1-2+rm Dear submitter, as the package cadvisor has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069149 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1001796: marked as done (netopeer2: test_rpc fails on 32bits arches, fails package build)
Your message dated Wed, 17 Apr 2024 12:10:10 + with message-id and subject line Bug#1069151: Removed package(s) from unstable has caused the Debian Bug report #1001796, regarding netopeer2: test_rpc fails on 32bits arches, fails package build 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.) -- 1001796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netopeer2 Version: 2.0.35-1 Dear Maintainer, test_rpc fails on 32 bits architectures (i386 example at https://buildd.debian.org/status/fetch.php?pkg=netopeer2=i386=2.0.35-1=1637934181=0) 2: [ RUN ] test_lock_basic 2: [ OK ] test_lock_basic 2: [ RUN ] test_lock_fail 2: " 2: 2: protocol 2: lock-denied 2: error 2: Access to the requested lock is denied because the lock is currently held by another entity. 2: 2: 1 2: 2: 2: 2: " != " 2: 2: protocol 2: lock-denied 2: error 2: Access to the requested lock is denied because the lock is currently held by another entity. 2: 2: 68 2: 2: 2: 2: " 5: [ RUN ] test_basic_notif 2: [ LINE ] --- ./tests/test_rpc.c:154: error: Failure! 2/15 Test #2: test_rpc .Subprocess aborted***Exception: 5.73 sec I filed an upstream bug about it at https://github.com/CESNET/netopeer2/issues/1106 and they published a commit with the fix at https://github.com/CESNET/netopeer2/commit/f63454b0eb9a8d5077e2ca0a80ae1720f1990e30 --- End Message --- --- Begin Message --- Version: 2.0.35-1+rm Dear submitter, as the package netopeer2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069151 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#993701: marked as done (srslte: FTBFS with libsoapysdr 0.8)
Your message dated Wed, 17 Apr 2024 12:08:42 +
with message-id
and subject line Bug#1069147: Removed package(s) from unstable
has caused the Debian Bug report #993701,
regarding srslte: FTBFS with libsoapysdr 0.8
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.)
--
993701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srslte
Version: 18.06.1+ds.1
Severity: important
Tags: ftbfs
I am building rdeps of libsoapysdr in preparation of the transition to
version 0.8. This version has changed the SoapySDRDevice_setupStream()
function signature to return the SoapySDRStream directly rather than
through a pointer:
* Recommended keys to use in the args dictionary:
*- "WIRE" - format of the samples between device and host
* \endparblock
- * \return 0 for success or error code on failure
+ * \return the stream pointer or nullptr for failure
*/
-SOAPY_SDR_API int SoapySDRDevice_setupStream(SoapySDRDevice *device,
-SoapySDRStream **stream,
+SOAPY_SDR_API SoapySDRStream *SoapySDRDevice_setupStream(SoapySDRDevice
*device,
const int direction,
const char *format,
const size_t *channels,
This change causes a build failure in srslte when building against the
new libsoapysdr. I can see upstream has already fixed that in their
sources. Log of the failed build:
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c: In function
'rf_soapy_open_multi':
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:344:52: warning:
passing argument 2 of 'SoapySDRDevice_setupStream' makes integer from pointer
without a cast [-Wint-conversion]
344 | if(SoapySDRDevice_setupStream(handler->device,
&(handler->rxStream), SOAPY_SDR_RX, SOAPY_SDR_CF32, NULL, 0, NULL) != 0) {
|^~~~
||
|SoapySDRStream **
In file included from
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:37:
/usr/include/SoapySDR/Device.h:307:15: note: expected 'int' but argument is of
type 'SoapySDRStream **'
307 | const int direction,
| ~~^
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:344:74: warning:
passing argument 3 of 'SoapySDRDevice_setupStream' makes pointer from integer
without a cast [-Wint-conversion]
344 | if(SoapySDRDevice_setupStream(handler->device,
&(handler->rxStream), SOAPY_SDR_RX, SOAPY_SDR_CF32, NULL, 0, NULL) != 0) {
|
^~~~
|
|
|
int
In file included from
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:37:
/usr/include/SoapySDR/Device.h:308:17: note: expected 'const char *' but
argument is of type 'int'
308 | const char *format,
| ^~
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:344:88: error: passing
argument 4 of 'SoapySDRDevice_setupStream' from incompatible pointer type
[-Werror=incompatible-pointer-types]
344 | if(SoapySDRDevice_setupStream(handler->device,
&(handler->rxStream), SOAPY_SDR_RX, SOAPY_SDR_CF32, NULL, 0, NULL) != 0) {
|
^~
|
|
|
char *
In file included from
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:37:
/usr/include/SoapySDR/Device.h:309:19: note: expected 'const size_t *' {aka
'const long unsigned int *'} but argument is of type 'char *'
309 | const size_t *channels,
| ~~^~~~
/build/srslte-18.06.1+ds.1/lib/src/phy/rf/rf_soapy_imp.c:344:104: warning:
passing argument 5 of 'SoapySDRDevice_setupStream' makes integer from pointer
without a cast [-Wint-conversion]
344 | if(SoapySDRDevice_setupStream(handler->device,
&(handler->rxStream), SOAPY_SDR_RX, SOAPY_SDR_CF32, NULL, 0, NULL) != 0) {
|
^~~~
|
Bug#982113: marked as done (srslte: AVX2 versions are missing)
Your message dated Wed, 17 Apr 2024 12:08:42 + with message-id and subject line Bug#1069147: Removed package(s) from unstable has caused the Debian Bug report #982113, regarding srslte: AVX2 versions are missing 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.) -- 982113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: srslte Version: 18.06.1+ds.1-1 Severity: serious Control: affects -1 srsue srsenb $ srsue Starting with AVX2 extension /usr/bin/srsue: line 7: /usr/lib/srslte/bin/srsue-avx2: No such file or directory $ srsenb Starting with AVX2 extension /usr/bin/srsenb: line 7: /usr/lib/srslte/bin/srsenb-avx2: No such file or directory $ --- End Message --- --- Begin Message --- Version: 18.06.1+ds.1-1+rm Dear submitter, as the package srslte has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069147 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#943332: marked as done (aufs-tools FTBFS: aufs-util for aufs4.14 20190211, but aufs is 5.2.5+-20190909.)
Your message dated Wed, 17 Apr 2024 12:08:11 + with message-id and subject line Bug#1069146: Removed package(s) from unstable has caused the Debian Bug report #943332, regarding aufs-tools FTBFS: aufs-util for aufs4.14 20190211, but aufs is 5.2.5+-20190909. 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.) -- 943332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aufs-tools Version: 1:4.14+20190211-1 Severity: serious Tags: ftbfs A build in sbuild on unstable ends with: |dh_auto_install | install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools | make -j8 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" | make[1]: Entering directory '/<>' | cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-z,relro -Wl,-z,now ver.c -o ver | ./ver | Wrong version! | aufs-util for aufs4.14 20190211, but aufs is 5.2.5+-20190909. | See README in detail and try git branch -a. | make[1]: *** [Makefile:120: ver_test] Error 255 | rm ver | make[1]: Leaving directory '/<>' | dh_auto_install: make -j8 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" returned exit code 2 | make: *** [debian/rules:15: binary] Error 255 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 This failure is reproduced by crossqa.debian.net: http://crossqa.debian.net/build/aufs-tools_1:4.14+20190211-1_armel_20191018093456.log It also is reproduced by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/aufs-tools_4.14+20190211-1.rbuild.log.gz Helmut --- End Message --- --- Begin Message --- Version: 1:4.14+20190211-1+rm Dear submitter, as the package aufs-tools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069146 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1001527: marked as done (FTBFS with fmtlib 8)
Your message dated Wed, 17 Apr 2024 12:07:41 + with message-id and subject line Bug#1069145: Removed package(s) from unstable has caused the Debian Bug report #1001527, regarding FTBFS with fmtlib 8 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.) -- 1001527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vast Version: 2021.05.27-8 Severity: important X-Debbugs-Cc: z...@debian.org Control: forwarded -1 https://github.com/tenzir/vast/pull/1846 Control: affects -1 src:fmtlib Hi, I have uploaded fmtlib/8 to experimental, and plan to start this transition. You package FTBFS with fmtlib/8, it has been fixed in version 2021.08.26. Please package the new version or backport the relevant commits. Thanks --- End Message --- --- Begin Message --- Version: 2021.05.27-8+rm Dear submitter, as the package vast has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069145 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#935182: marked as done (Concurrent file open on the same host results file deletion)
Your message dated Wed, 17 Apr 2024 11:53:46 + with message-id and subject line Bug#1069123: Removed package(s) from experimental has caused the Debian Bug report #935182, regarding Concurrent file open on the same host results file deletion 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.) -- 935182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-core Version: 1:6.1.5-3+deb10u3 Severity: grave Hello, When two users on the same machine open the same file from a samba share, the second gets a notice about the file to be openned in read-only mode. If the first user saves modification while the second user have the file openned, the first user gets an error saying the file does not exists anymore. And then, the file is actually deleted once the second user closes the file. -- Package-specific info: Experimental features enabled: Installed VCLplugs: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++----= un libreoffice-gtk2 (no description available) un libreoffice-gtk3 (no description available) un libreoffice-kde5 (no description available) -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-core depends on: ii fontconfig2.13.1-2 ii fonts-opensymbol 2:102.11+LibO6.3.0-2~bpo10+1 ii libboost-date-time1.67.0 1.67.0-13 ii libboost-locale1.67.0 1.67.0-13 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups2 2.2.10-6 ii libcurl3-gnutls 7.64.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libdconf1 0.30.1-2 ii libeot0 0.01-5 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.6-2 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig12.13.1-2 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-6 ii libglib2.0-0 2.58.3-2 ii libgpgmepp6 1.12.0-6 ii libgraphite2-31.3.13-7 ii libharfbuzz-icu0 2.3.1-1 ii libharfbuzz0b 2.3.1-1 ii libhunspell-1.7-0 1.7.0-2 ii libhyphen02.8.8-7 ii libice6 2:1.0.9-2 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii libharfbuzz0b 2.3.1-1 ii libhunspell-1.7-0 1.7.0-2 ii libhyphen02.8.8-7 ii libice6 2:1.0.9-2 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii libldap-2.4-2 2.4.47+dfsg-3 ii libmythes-1.2-0 2:1.2.4-3 ii libneon27-gnutls 0.30.2-3 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1 ii libnumbertext-1.0-0 1.0.5-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libpng16-16 1.6.36-6 ii libpoppler82 0.71.0-5 ii librdf0 1.0.17-1.1+b1 ii libreoffice-common1:6.1.5-3+deb10u3 ii librevenge-0.0-0 0.0.4-6 ii libsm62:1.2.3-1 ii libstdc++68.3.0-6 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmlsec11.2.27-2 ii libxmlsec1-nss1.2.27-2 ii libxrandr22:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.11.1.32-2 ii uno-libs3 6.3.0-2~bpo10+1 ii ure 6.3.0-2~bpo10+1 ii zlib1g1:1.2.11.dfsg-1
Bug#1066463: marked as done (gnome-paint: FTBFS: cv_resize.c:368:9: error: implicit declaration of function ‘undo_add_resize’ [-Werror=implicit-function-declaration])
Your message dated Wed, 17 Apr 2024 11:49:33 +
with message-id
and subject line Bug#1066463: fixed in gnome-paint 0.4.0-10
has caused the Debian Bug report #1066463,
regarding gnome-paint: FTBFS: cv_resize.c:368:9: error: implicit declaration of
function ‘undo_add_resize’ [-Werror=implicit-function-declaration]
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.)
--
1066463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-paint
Version: 0.4.0-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\"
> -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\"
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0
> -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -DG_DISABLE_DEPRECATED
> -DG_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_DEPRECATED
> -DGDK_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c -o
> gnome_paint-pixbuf-file-chooser.o `test -f 'pixbuf-file-chooser.c' || echo
> './'`pixbuf-file-chooser.c
> cv_resize.c: In function ‘cv_resize_stop’:
> cv_resize.c:368:9: error: implicit declaration of function ‘undo_add_resize’
> [-Werror=implicit-function-declaration]
> 368 | undo_add_resize ( width, height );
> | ^~~
> toolbar.c: In function ‘get_gtk_image’:
> toolbar.c:505:48: warning: passing argument 1 of
> ‘gdk_pixbuf_new_from_xpm_data’ from incompatible pointer type
> [-Wincompatible-pointer-types]
> 505 | pixbuf = gdk_pixbuf_new_from_xpm_data (xpm);
> |^~~
> ||
> |gchar ** {aka char **}
> In file included from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:34,
> from /usr/include/gtk-2.0/gdk/gdkpixbuf.h:37,
> from /usr/include/gtk-2.0/gdk/gdkcairo.h:28,
> from /usr/include/gtk-2.0/gdk/gdk.h:33,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from toolbar.h:28,
> from toolbar.c:27:
> /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:294:55: note:
> expected ‘const char **’ but argument is of type ‘gchar **’ {aka ‘char **’}
> 294 | GdkPixbuf *gdk_pixbuf_new_from_xpm_data (const char **data);
> | ~^~~~
> color.c: In function ‘on_color_palette_entry_button_press_event’:
> color.c:178:17: error: implicit declaration of function
> ‘notify_brush_of_fg_color_change’ [-Werror=implicit-function-declaration]
> 178 | notify_brush_of_fg_color_change();
> | ^~~
> pixbuf-file-chooser.c: In function ‘pixbuf_file_chooser_class_init’:
> pixbuf-file-chooser.c:91:9: warning: ‘g_type_class_add_private’ is deprecated
> [-Wdeprecated-declarations]
>91 | g_type_class_add_private (object_class, sizeof
> (PixbufFileChooserPrivate));
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
> from /usr/include/glib-2.0/gobject/gbinding.h:31,
> from /usr/include/glib-2.0/glib-object.h:24,
> from /usr/include/glib-2.0/gio/gioenums.h:30,
> from /usr/include/glib-2.0/gio/giotypes.h:30,
> from /usr/include/glib-2.0/gio/gio.h:28,
> from
Bug#1069106: marked as done (openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file)
Your message dated Wed, 17 Apr 2024 11:20:10 + with message-id and subject line Bug#1069106: fixed in openmpi 4.1.6-11 has caused the Debian Bug report #1069106, regarding openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file 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.) -- 1069106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openmpi Version: 4.1.6-9 Severity: serious Justification: ftbfs Control: affects -1 src:fenics-dolfinx src:petsc openmpi 4.1.6-9 is failing its own tests on 32-bit systems, presumeably after they were configuring to use a local copy of pmix instead of libpmix-dev. For instance on i386 https://ci.debian.net/data/autopkgtest/unstable/i386/o/openmpi/45463906/log.gz the error message is 69s autopkgtest [12:19:13]: test compile_run_mpicc: [--- 69s -- 69s Sorry! You were supposed to get help about: 69s pmix_init:startup:internal-failure 69s But I couldn't open the help file: 69s /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! 69s -- 69s [ci-107-5e0ffbcf:02362] PMIX ERROR: NOT-FOUND in file ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at line 237 The same error affects builds and debci testing of client packages on the 32 bit architectures, e.g. petsc, dolfinx --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 4.1.6-11 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of openmpi, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi 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: Wed, 17 Apr 2024 11:15:11 +0100 Source: openmpi Architecture: source Version: 4.1.6-11 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1069106 Changes: openmpi (4.1.6-11) unstable; urgency=medium . * Ship help text files for pmix. Closes: #1069106 Checksums-Sha1: 6ed6a5195dbe83344910162981ecf0524e0cfdeb 2832 openmpi_4.1.6-11.dsc 66e8a528d495cadc5fd508d0a7c937c98a182ff0 69644 openmpi_4.1.6-11.debian.tar.xz Checksums-Sha256: 0d2dc4eabbafc1c6c62a389e47b31de044c7e8890ee3eb4179f30859bcd94f37 2832 openmpi_4.1.6-11.dsc 42750bf2270401369f3b04a1cfe6787a5ed0708950022696661b8211fa539e2b 69644 openmpi_4.1.6-11.debian.tar.xz Files: d9e9ed5d4c89a8834464cbfdc4f1d191 2832 net optional openmpi_4.1.6-11.dsc 0630149a9b9c43be462cd45adc23ba1a 69644 net optional openmpi_4.1.6-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmYfquQACgkQy+a7Tl2a 06WG0Q//XM7b1XOIyll6KfZu5ks2PR83RQ7MSz7HxekyWFMnAcL5yRxXB2E8lbRT iw4KJldxYKeUWG/hoaYs3EQetzgYIIDX2jqQnHs32T8dL3T9/lB7tDoCXJGfb8kN y4IuUoxD1OYdV/e4Bi+4jwaqHInEe16OsyFNIXqhrYk3ZIWZjZqasmFPjq+L8OYm vASyodWh0LcxVwpd07mv+5g/Jjdgq9guKPe3FpxgpKeazPF29UUexvKypArR2m/C fB9ED/OZliTZaJx/r7NS9zOQk5oW9FCNKGqlK/TjJvlnsSFSsaxTUMOscjB2fVyz 37/7fKwYSwPJ9cU3CbgPVmREkIPvpbjXkQIq6NghPLWVb2I6KcBcUL+WUYzW0KhU MD8/UTY5oopNrwnt6AIIUJ1NiqImii4oG+ap61mEgCPt/JHXBN1J5Xj7LJmAiw4I zUMmI8sFyatE0OQjnqH/GiZS4F/TlCvpUZiQqGosMIdrQzXaYMjmqKL2Wstl/E6N FTqMa0qJyOH2RjGM6j8EWwn9YEMMwpV4T6ys7KMpwGRCJ3xJgNZ1FuPDq/+zK4jV R/V+tUDsp26IEldvnVh2WO5781muU94N/AQ2KwUY8w1ILXNTuGrWZ4uYWs2x3PrY mjHq2wygwbnCqky03eJev4S3yyt1KpcYV2xpuRdUmuIDMKCMvXY= =DoUs -END PGP SIGNATURE- pgp7Xz2ojbvrW.pgp Description: PGP signature --- End Message ---
Bug#1063324: possible fix?
Hello, this might be a fix, but I don't really know how to test it...
G.
--- uhd-4.6.0.0+ds1/debian/changelog2024-02-28 21:10:38.0 +0100
+++ uhd-4.6.0.0+ds1/debian/changelog2024-04-17 10:21:59.0 +0200
@@ -1,3 +1,10 @@
+uhd (4.6.0.0+ds1-5.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fixup conflict replaces (Closes: #1063324)
+
+ -- Gianfranco Costamagna Wed, 17 Apr 2024
10:21:59 +0200
+
uhd (4.6.0.0+ds1-5.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru uhd-4.6.0.0+ds1/debian/control uhd-4.6.0.0+ds1/debian/control
--- uhd-4.6.0.0+ds1/debian/control 2024-02-28 21:10:37.0 +0100
+++ uhd-4.6.0.0+ds1/debian/control 2024-04-17 10:21:54.0 +0200
@@ -80,8 +80,8 @@
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}
Suggests: uhd-host
-Conflicts: libuhd4.6.0t64
-Provides: libuhd4.6.0t64
+Conflicts: libuhd4.6.0t64, libuhd4.6.0
+Provides: libuhd4.6.0t64, libuhd4.6.0
Multi-Arch: same
Description: universal hardware driver for Ettus Research products - DPDK
Host library for the Universal Hardware Driver for Ettus Research products.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1066462: marked as done (dot-forward: FTBFS: control.c:65:41: error: implicit declaration of function ‘close’ [-Werror=implicit-function-declaration])
Your message dated Wed, 17 Apr 2024 09:49:19 +
with message-id
and subject line Bug#1066462: fixed in dot-forward 1:0.71-7
has caused the Debian Bug report #1066462,
regarding dot-forward: FTBFS: control.c:65:41: error: implicit declaration of
function ‘close’ [-Werror=implicit-function-declaration]
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.)
--
1066462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dot-forward
Version: 1:0.71-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ( cat warn-auto.sh; \
> echo CC=\'`head -1 conf-cc`\'; \
> echo LD=\'`head -1 conf-ld`\' \
> ) > auto-ccld.sh
> nroff -man dot-forward.1 > dot-forward.0
> cat auto-ccld.sh make-load.sh > make-load
> cat auto-ccld.sh find-systype.sh > find-systype
> cat auto-ccld.sh make-compile.sh > make-compile
> cat auto-ccld.sh make-makelib.sh > make-makelib
> chmod 755 make-load
> chmod 755 find-systype
> chmod 755 make-compile
> chmod 755 make-makelib
> ./find-systype > systype
> ( cat warn-auto.sh; ./make-load "`cat systype`" ) > load
> ( cat warn-auto.sh; ./make-compile "`cat systype`" ) > \
> compile
> ( cat warn-auto.sh; ./make-makelib "`cat systype`" ) > \
> makelib
> chmod 755 load
> chmod 755 makelib
> chmod 755 compile
> ./compile dot-forward.c
> ./compile control.c
> ( ( ./compile tryvfork.c && ./load tryvfork ) >/dev/null \
> 2>&1 \
> && cat fork.h2 || cat fork.h1 ) > fork.h
> ./compile auto-str.c
> ./compile substdio.c
> ./compile substdi.c
> ./compile substdo.c
> ./compile subfderr.c
> control.c: In function ‘control_readline’:
> control.c:65:41: error: implicit declaration of function ‘close’
> [-Werror=implicit-function-declaration]
>65 | if (getln(,sa,,'\n') == -1) { close(fd); return -1; }
> | ^
> dot-forward.c: In function ‘run’:
> dot-forward.c:78:7: error: implicit declaration of function ‘pipe’
> [-Werror=implicit-function-declaration]
>78 | if (pipe(pi) == -1)
> | ^~~~
> dot-forward.c:81:19: error: implicit declaration of function ‘fork’
> [-Werror=implicit-function-declaration]
>81 | switch (child = fork()) {
> | ^~~~
> dot-forward.c:85:7: error: implicit declaration of function ‘close’
> [-Werror=implicit-function-declaration]
>85 | close(pi[1]);
> | ^
> dot-forward.c:86:11: error: implicit declaration of function ‘fd_move’
> [-Werror=implicit-function-declaration]
>86 | if (fd_move(0,pi[0]) == -1)
> | ^~~
> dot-forward.c:89:7: error: implicit declaration of function ‘sig_pipedefault’
> [-Werror=implicit-function-declaration]
>89 | sig_pipedefault();
> | ^~~
> dot-forward.c:90:7: error: implicit declaration of function ‘execv’
> [-Werror=implicit-function-declaration]
>90 | execv(*args,args);
> | ^
> auto-str.c:8:6: warning: conflicting types for built-in function ‘puts’;
> expected ‘int(const char *)’ [-Wbuiltin-declaration-mismatch]
> 8 | void puts(s)
> | ^~~~
> auto-str.c:4:1: note: ‘puts’ is declared in header ‘’
> 3 | #include "exit.h"
> +++ |+#include
> 4 |
> dot-forward.c: In function ‘readcontrols’:
> dot-forward.c:141:7: error: implicit declaration of function ‘chdir’
> [-Werror=implicit-function-declaration]
> 141 | if (chdir(auto_qmail) == -1)
> | ^
> dot-forward.c:160:7: error: implicit declaration of function ‘fchdir’
> [-Werror=implicit-function-declaration]
> 160 | if (fchdir(fddir) == -1)
> | ^~
> dot-forward.c: In function ‘gotaddr’:
> dot-forward.c:189:12: error: implicit declaration of function ‘case_diffb’
> [-Werror=implicit-function-declaration]
> 189 | if (!case_diffb(address.s,address.len,user)) {
> |^~
> dot-forward.c: In function ‘main’:
> dot-forward.c:389:3: error: implicit declaration of function ‘sig_pipeignore’
> [-Werror=implicit-function-declaration]
> 389 | sig_pipeignore();
> | ^~
Bug#1069163: Acknowledgement (libkf5kmanagesieve5: sends password as username when authenticating against sieve servers)
Hello again, It seems that this might affect oldstable, too, given that the problematic code has existed for >8 years upstream: https://invent.kde.org/pim/libksieve/-/commit/ 6572c85975133777c803303331c3bfdcec82eecb Upstream bugs have been open since May 2021 (oldstable was released in August 2021): https://bugs.kde.org/show_bug.cgi?id=437858 kind regards, -- Jonas Schäfer Team Lead Cloud Infrastructure Development Cloud Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schae...@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann signature.asc Description: This is a digitally signed message part.
Bug#1023237: openjdk-11: Keep out of testing and stable
Le 17/04/2024 à 09:54, Timo Röhling a écrit : FastDDSGen currently depends on OpenJDK 11 (or more precisely, any OpenJDK before 15) because it needs the Nashorn JavaScript engine, so could OpenJDK 11 be kept in trixie for the time being? That's a dead end, if OpenJDK 11 is kept there will be no incentive to update softwares to follow the evolution of Java, and the old JDK will just hang there forever. Alternatively, someone could help me package the standalone version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038142 Packaging Nashorn is the way to go in this case. You can post to the debian-java mailing list to get some help with the packaging. Emmanuel Bourg
Bug#1069163: libkf5kmanagesieve5: sends password as username when authenticating against sieve servers
Package: libkf5kmanagesieve5 Version: 4:22.12.3-1 Severity: grave Tags: security, patch, upstream Dear Maintainer, kmail, when using managesieve, sends the password as username to servers. This is particularly bad because usernames are commonly logged by servers in plaintext. It thus leaks passwords into server-side plaintext logs e.g. with dovecot. This seems to have been fixed upstream: https://invent.kde.org/pim/libksieve/-/commit/ 6b460ba93ac4ac503ba039d0b788ac7595120db1 Please consider a backport of that patch or updating the package quickly. Thank you. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkf5kmanagesieve5 depends on: ii kio 5.107.0-1+b1 ii libc6 2.37-15 ii libkf5configcore5 5.107.0-1+b1 ii libkf5coreaddons5 5.107.0-1+b1 ii libkf5i18n5 5.107.0-1+b1 ii libkf5kiocore55.107.0-1+b1 ii libkf5kiowidgets5 5.107.0-1+b1 ii libkf5ksieve-data 4:22.12.3-1 ii libkf5widgetsaddons5 5.107.0-1+b1 ii libqt5core5a 5.15.10+dfsg-7 ii libqt5network55.15.10+dfsg-7 ii libqt5widgets55.15.10+dfsg-7 ii libsasl2-22.1.28+dfsg1-4+b1 ii libstdc++614-20240201-3 libkf5kmanagesieve5 recommends no packages. libkf5kmanagesieve5 suggests no packages. -- no debconf information -- Jonas Schäfer Team Lead Cloud Infrastructure Development Cloud Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schae...@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann signature.asc Description: This is a digitally signed message part.
Bug#1066431: marked as done (dsniff: FTBFS: ./decode_yp.c:18:10: fatal error: rpcsvc/yp_prot.h: No such file or directory)
Your message dated Wed, 17 Apr 2024 08:34:46 + with message-id and subject line Bug#1066431: fixed in dsniff 2.4b1+debian-33 has caused the Debian Bug report #1066431, regarding dsniff: FTBFS: ./decode_yp.c:18:10: fatal error: rpcsvc/yp_prot.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dsniff Version: 2.4b1+debian-32 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -I/usr/include/tirpc/ -D_BSD_SOURCE -D_BSD_SOURCE -D__BSD_SOURCE > -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -DDSNIFF_LIBDIR=\"/usr/share/dsniff/\" > -I/usr/include/tirpc -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I/usr/include > -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I./missing -c > ./mailsnarf.c > ./decode_yp.c:18:10: fatal error: rpcsvc/yp_prot.h: No such file or directory >18 | #include > | ^~ > compilation terminated. > In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, > from ./mailsnarf.c:13: > /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -I/usr/include/tirpc/ -D_BSD_SOURCE -D_BSD_SOURCE -D__BSD_SOURCE > -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -DDSNIFF_LIBDIR=\"/usr/share/dsniff/\" > -I/usr/include/tirpc -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I/usr/include > -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I./missing -c > ./msgsnarf.c > make[1]: *** [Makefile:78: decode_yp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/dsniff_2.4b1+debian-32_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: dsniff Source-Version: 2.4b1+debian-33 Done: Arnaud Rebillout We believe that the bug you reported is fixed in the latest version of dsniff, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Rebillout (supplier of updated dsniff package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2024 14:53:41 +0700 Source: dsniff Architecture: source Version: 2.4b1+debian-33 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Arnaud Rebillout Closes: 1066431 Changes: dsniff (2.4b1+debian-33) unstable; urgency=medium . * Add missing libnsl-dev to Build-Depends (Closes:#1066431). Checksums-Sha1: e5832781b5fd29e352a26ddbc483367cf664aa05 2127 dsniff_2.4b1+debian-33.dsc ec4fe6359605a2a7ea44f7e63edf0a847b59f11d 30960 dsniff_2.4b1+debian-33.debian.tar.xz 489225d93d5a0d25edd8147f0e8c949583e72db6 6506
Bug#1069158: jack-mixer: Missing Depends on python3-gi, gir1.2-gtk-3.0, and python3-cairo
Package: jack-mixer
Version: 17-2+b2
Severity: serious
Justification: Policy 3.5
X-Debbugs-Cc: philipchung1...@yahoo.com
Dear Maintainer,
The jack_mixer binary fails to start if these packages are not installed.
I've reported this against the version currently in bookworm (stable),
but I believe it applies to testing and unstable as well.
Without python3-gi, the following trace appears:
Traceback (most recent call last):
File "/usr/bin/jack_mixer", line 5, in
from jack_mixer.app import main
File "/usr/lib/python3/dist-packages/jack_mixer/app.py", line 21, in
import gi
ModuleNotFoundError: No module named 'gi'
Without gir1.2-gtk-3.0, the trace is:
Traceback (most recent call last):
File "/usr/bin/jack_mixer", line 5, in
from jack_mixer.app import main
File "/usr/lib/python3/dist-packages/jack_mixer/app.py", line 23, in
gi.require_version("Gtk", "3.0")
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available
Without python3-cairo, the trace is:
Traceback (most recent call last):
File "/usr/bin/jack_mixer", line 5, in
from jack_mixer.app import main
File "/usr/lib/python3/dist-packages/jack_mixer/app.py", line 30, in
from .channel import InputChannel, NewInputChannelDialog,
NewOutputChannelDialog, OutputChannel
File "/usr/lib/python3/dist-packages/jack_mixer/channel.py", line 27, in
from . import meter
File "/usr/lib/python3/dist-packages/jack_mixer/meter.py", line 20, in
import cairo
ModuleNotFoundError: No module named 'cairo'
(See also bug #995784 about adding python3-cairo as a Recommends for
python3-gi)
Philip Chung
-- System Information:
Debian Release: 12.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages jack-mixer depends on:
ii jackd21.9.21~dfsg-3
ii libc6 2.36-9+deb12u4
ii libglib2.0-0 2.74.6-2
ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-3
ii python3 3.11.2-1+b1
jack-mixer recommends no packages.
jack-mixer suggests no packages.
-- no debconf information
Processed: Re: openjdk-11: Keep out of testing and stable
Processing control commands: > affects -1 + fastddsgen Bug #1023237 [src:openjdk-11] openjdk-11: Keep out of testing and stable Added indication that 1023237 affects fastddsgen -- 1023237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023237: openjdk-11: Keep out of testing and stable
Control: affects -1 + fastddsgen Hi, On Mon, 31 Oct 2022 21:55:24 +0100 Emmanuel Bourg wrote: openjdk-17 is now the default JDK, but openjdk-11 is still required for bootstrapping JVM-based languages like Kotlin or Scala in unstable. Therefore the package should no longer migrate to testing or stable anymore. FastDDSGen currently depends on OpenJDK 11 (or more precisely, any OpenJDK before 15) because it needs the Nashorn JavaScript engine, so could OpenJDK 11 be kept in trixie for the time being? Alternatively, someone could help me package the standalone version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038142 Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1061519: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551
Le lundi 15 avril 2024, 13:58:19 UTC Steve McIntyre a écrit : > On Mon, Apr 15, 2024 at 11:33:14AM +, Bastien Roucariès wrote: > >Source: shim > >Followup-For: Bug #1061519 > >Control: tags -1 + patch > > > >Dear Maintainer, > > > >Please find a MR here > >https://salsa.debian.org/efi-team/shim/-/merge_requests/13 > > ACK. Thanks for trying to help, but the merge isn't the hard bit here. > > Tthe new upstream is a little problematic and I'm debugging some boot > failures in my local CI already. I have backported here https://salsa.debian.org/efi-team/shim/-/merge_requests/14 Need test > > signature.asc Description: This is a digitally signed message part.
Bug#1066547: marked as done (xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration])
Your message dated Wed, 17 Apr 2024 07:07:25 +
with message-id
and subject line Bug#1066547: fixed in xf86-input-mtrack 0.3.1-1.2
has caused the Debian Bug report #1066547,
regarding xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit
declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’?
[-Werror=implicit-function-declaration]
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.)
--
1066547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xf86-input-mtrack
Version: 0.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I./include/ -I/usr/include/xorg
> -I/usr/include/pixman-1 -I/usr/include/xorg -fvisibility=hidden
> -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -D_FORTIFY_SOURCE=2 -c -o
> src/mtrack_test-gestures.o `test -f 'src/gestures.c' || echo
> './'`src/gestures.c
> src/gestures.c: In function ‘gestures_sleep’:
> src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’;
> did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]
> 763 | if (mtdev_empty(>dev)) {
> | ^~~
> | mtdev_get
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:663: src/mtrack_test-gestures.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/xf86-input-mtrack_0.3.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: xf86-input-mtrack
Source-Version: 0.3.1-1.2
Done: Gianfranco Costamagna
We believe that the bug you reported is fixed in the latest version of
xf86-input-mtrack, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gianfranco Costamagna (supplier of updated
xf86-input-mtrack 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: Wed, 17 Apr 2024 08:18:29 +0200
Source: xf86-input-mtrack
Built-For-Profiles: noudeb
Architecture: source
Version: 0.3.1-1.2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu
Changed-By: Gianfranco Costamagna
Closes: 1066547
Changes:
xf86-input-mtrack (0.3.1-1.2) unstable; urgency=medium
.
* Non-maintainer upload
* Cherry-pick another patch from Benjamin Drung and
xf86-input-multitouch 1.0~rc3-2.1 to fix another FTBFS due to time64_t
(Closes: #1066547)
Checksums-Sha1:
d5f853ba256074736d7673117ac44cc01f424b6d 1941 xf86-input-mtrack_0.3.1-1.2.dsc
a3c4ec64af2aa87ef779fe472c1a1bcfb93184eb 13512
xf86-input-mtrack_0.3.1-1.2.debian.tar.xz
6f489b0a85693f1820da1236a83a89d23f66393d 10369
xf86-input-mtrack_0.3.1-1.2_source.buildinfo
Checksums-Sha256:
2c2bb3cc12e708235bbb0c18b083f7ce43028b337c3aeb0d36bf401a9bfd60e1
Processed: Re: Bug#1066547: fixed in xf86-input-mtrack 0.3.1-1.1
Processing control commands:
> reopen -1
Bug #1066547 {Done: Gianfranco Costamagna }
[src:xf86-input-mtrack] xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error:
implicit declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’?
[-Werror=implicit-function-declaration]
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions xf86-input-mtrack/0.3.1-1.1.
> notfixed -1 0.3.1-1.1
Bug #1066547 [src:xf86-input-mtrack] xf86-input-mtrack: FTBFS:
src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’;
did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]
Ignoring request to alter fixed versions of bug #1066547 to the same values
previously set
> tags 1066547 + patch
Bug #1066547 [src:xf86-input-mtrack] xf86-input-mtrack: FTBFS:
src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’;
did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]
Ignoring request to alter tags of bug #1066547 to the same tags previously set
> tags 1066547 + pending
Bug #1066547 [src:xf86-input-mtrack] xf86-input-mtrack: FTBFS:
src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’;
did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1066547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066547: fixed in xf86-input-mtrack 0.3.1-1.1
control: reopen -1
control: notfixed -1 0.3.1-1.1
Control: tags 1066547 + patch
Control: tags 1066547 + pending
Dear maintainer,
I've prepared an NMU for xf86-input-mtrack (versioned as 0.3.1-1.2) and
uploaded it.
diff -Nru xf86-input-mtrack-0.3.1/debian/changelog
xf86-input-mtrack-0.3.1/debian/changelog
--- xf86-input-mtrack-0.3.1/debian/changelog2024-04-16 23:32:48.0
+0200
+++ xf86-input-mtrack-0.3.1/debian/changelog2024-04-17 08:18:29.0
+0200
@@ -1,3 +1,12 @@
+xf86-input-mtrack (0.3.1-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Cherry-pick another patch from Benjamin Drung and
+xf86-input-multitouch 1.0~rc3-2.1 to fix another FTBFS due to time64_t
+(Closes: #1066547)
+
+ -- Gianfranco Costamagna Wed, 17 Apr 2024
08:18:29 +0200
+
xf86-input-mtrack (0.3.1-1.1) unstable; urgency=medium
* Non-maintainer upload
diff -Nru
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
---
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
2024-04-16 23:32:48.0 +0200
+++
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
2024-04-17 08:18:29.0 +0200
@@ -1,17 +1,21 @@
Description: Add patch to fix missing includes
Author: Gianfranco Costamagna
-Last-Update: 2024-04-16
+Last-Update: 2024-04-17
xf86-input-mtrack-0.3.1.orig/include/common.h
-+++ xf86-input-mtrack-0.3.1/include/common.h
-@@ -33,6 +33,7 @@
- #include
- #include
- #include
+Index: xf86-input-mtrack-0.3.1/src/gestures.c
+===
+--- xf86-input-mtrack-0.3.1.orig/src/gestures.c
xf86-input-mtrack-0.3.1/src/gestures.c
+@@ -28,6 +28,7 @@
+ #include "gestures.h"
+ #include "mtouch.h"
+ #include "trig.h"
+#include
- #include
- #include
-
+
+ #define IS_VALID_BUTTON(x) (x >= 0 && x <= 31)
+
+Index: xf86-input-mtrack-0.3.1/tools/mtrack-test.c
+===
--- xf86-input-mtrack-0.3.1.orig/tools/mtrack-test.c
+++ xf86-input-mtrack-0.3.1/tools/mtrack-test.c
@@ -23,6 +23,7 @@
@@ -19,6 +23,6 @@
#include
#include
+#include
-
+
void xf86Msg(int type, const char *format, ...)
{
diff -Nru
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
---
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
1970-01-01 01:00:00.0 +0100
+++
xf86-input-mtrack-0.3.1/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
2024-04-17 08:18:29.0 +0200
@@ -0,0 +1,41 @@
+From: Benjamin Drung
+Date: Mon, 15 Apr 2024 19:56:58 +0200
+Subject: Port usage of struct input_event to input_event_*
+MIME-Version: 1.0
+Content-Type: text/plain; charset="utf-8"
+Content-Transfer-Encoding: 8bit
+
+It fails to build on armhf:
+
+```
+src/hwstate.c: In function ‘finish_packet’:
+src/hwstate.c:43:24: error: ‘const struct input_event’ has no member named
+‘time’
+ 43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
+ | ^~
+src/hwstate.c:43:49: error: ‘const struct input_event’ has no member named
+‘time’
+ 43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
+ | ^~
+```
+
+Closes: #1067596
+LP: #2061591
+---
+ src/hwstate.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: xf86-input-mtrack-0.3.1/src/hwstate.c
+===
+--- xf86-input-mtrack-0.3.1.orig/src/hwstate.c
xf86-input-mtrack-0.3.1/src/hwstate.c
+@@ -42,7 +42,8 @@
+ if (!caps->has_abs[MTDEV_WIDTH_MINOR])
+ s->data[i].width_minor = s->data[i].width_major;
+ }
+- timercp(>evtime, >time);
++ s->evtime.tv_sec = syn->input_event_sec;
++ s->evtime.tv_usec = syn->input_event_usec;
+ }
+
+ static int read_event(struct HWState *s, const struct Capabilities *caps,
diff -Nru xf86-input-mtrack-0.3.1/debian/patches/series
xf86-input-mtrack-0.3.1/debian/patches/series
--- xf86-input-mtrack-0.3.1/debian/patches/series 2024-04-16
23:32:48.0 +0200
+++ xf86-input-mtrack-0.3.1/debian/patches/series 2024-04-17
08:12:31.0 +0200
@@ -2,3 +2,4 @@
#aa
upsteam-commit
missing-includes-implicit-function-declaration-fix.patch
+Port-usage-of-struct-input_event-to-input_event_.patch
thanks
Gianfranco
On Tue, 16 Apr 2024 21:50:39 + Debian FTP Masters
wrote:
Source: xf86-input-mtrack
Source-Version: 0.3.1-1.1
Done: Gianfranco Costamagna
We believe that the bug you reported is fixed in the latest version of
xf86-input-mtrack, which is due to be installed in the Debian FTP
Bug#1068757: marked as done (python-musicpd: FTBFS: dh_installchangelogs: error: could not find changelog)
Your message dated Wed, 17 Apr 2024 06:49:56 + with message-id and subject line Bug#1068757: fixed in python-musicpd 0.9.0-1 has caused the Debian Bug report #1068757, regarding python-musicpd: FTBFS: dh_installchangelogs: error: could not find changelog 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.) -- 1068757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-musicpd Version: 0.8.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3,sphinxdoc --buildsystem=pybuild --name=musicpd dh_update_autotools_config -O--buildsystem=pybuild -O--name=musicpd dh_autoreconf -O--buildsystem=pybuild -O--name=musicpd dh_auto_configure -O--buildsystem=pybuild -O--name=musicpd I: pybuild base:311: python3.11 setup.py config /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. !! parsed = self.parsers.get(option_name, lambda x: x)(value) running config dh_auto_build -O--buildsystem=pybuild -O--name=musicpd I: pybuild base:311: /usr/bin/python3 setup.py build /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. !! parsed = self.parsers.get(option_name, lambda x: x)(value) running build running build_py copying musicpd.py -> /<>/.pybuild/cpython3_3.11/build dh_auto_test -O--buildsystem=pybuild -O--name=musicpd I: pybuild base:311: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover -v -- Ran 0 tests in 0.000s OK create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild -O--name=musicpd dh_prep -O--buildsystem=pybuild -O--name=musicpd dh_auto_install --destdir=debian/python3-musicpd/ -O--buildsystem=pybuild -O--name=musicpd I: pybuild base:311: /usr/bin/python3 setup.py install --root /<>/debian/python3-musicpd /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. !! parsed = self.parsers.get(option_name, lambda x: x)(value) running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. !! self.initialize_options() running build running build_py running install_lib creating /<>/debian/python3-musicpd/usr creating
Bug#1067089: marked as done (librem5-flash-image: FTBFS: Validation failed: warnings: 1, infos: 2, pedantic: 1)
Your message dated Wed, 17 Apr 2024 06:49:45 + with message-id and subject line Bug#1067089: fixed in librem5-flash-image 0.0.4-2 has caused the Debian Bug report #1067089, regarding librem5-flash-image: FTBFS: Validation failed: warnings: 1, infos: 2, pedantic: 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librem5-flash-image Version: 0.0.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, librem5-flash-image recently started to FTBFS in sid: debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/build/librem5-flash-image-0.0.4' PREFIX=/usr dh_auto_build make -j3 "INSTALL=install --strip-program=true" make[2]: Entering directory '/build/librem5-flash-image-0.0.4' make -C scripts/ make[3]: Entering directory '/build/librem5-flash-image-0.0.4/scripts' flake8 librem5-devkit-flash-image python3 -m doctest librem5_flash_image.py make[3]: Leaving directory '/build/librem5-flash-image-0.0.4/scripts' make -C data/ make[3]: Entering directory '/build/librem5-flash-image-0.0.4/data' appstreamcli validate sm.puri.librem5-flash-image.metainfo.xml W: sm.puri.librem5-flash-image:~: url-homepage-missing I: sm.puri.librem5-flash-image:~: content-rating-missing I: sm.puri.librem5-flash-image:~: developer-info-missing ? Validation failed: warnings: 1, infos: 2, pedantic: 1 make[3]: *** [Makefile:7: check] Error 3 make[3]: Leaving directory '/build/librem5-flash-image-0.0.4/data' make[2]: *** [Makefile:9: check] Error 2 make[2]: Leaving directory '/build/librem5-flash-image-0.0.4' dh_auto_build: error: make -j3 "INSTALL=install --strip-program=true" returned exit code 2 make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25 make[1]: Leaving directory '/build/librem5-flash-image-0.0.4' make: *** [debian/rules:6: binary] Error 2 Andreas --- End Message --- --- Begin Message --- Source: librem5-flash-image Source-Version: 0.0.4-2 Done: Guido Günther We believe that the bug you reported is fixed in the latest version of librem5-flash-image, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guido Günther (supplier of updated librem5-flash-image 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: Wed, 17 Apr 2024 08:25:17 +0200 Source: librem5-flash-image Architecture: source Version: 0.0.4-2 Distribution: unstable Urgency: medium Maintainer: DebianOnMobile Maintainers Changed-By: Guido Günther Closes: 1067089 Changes: librem5-flash-image (0.0.4-2) unstable; urgency=medium . * data: Add missing metainfo fields (Closes: #1067089) * data: Avoid net access when checking metainfo * Fix lintian overrides * Bump standards version to 4.6.2 Checksums-Sha1: 9ab5386831e62da82b1f48605bb02cdf053237ff 2248 librem5-flash-image_0.0.4-2.dsc 424068b32efef606154d7de828bad77af2b7fe12 3676 librem5-flash-image_0.0.4-2.debian.tar.xz 645f1d49b5156d350c28056022bf16adcd77c961 8412 librem5-flash-image_0.0.4-2_amd64.buildinfo Checksums-Sha256: 5f08272cd008be6b18bb7ddc88a0e348d78514f412a81ed9d2e11bdc3e6328bd 2248 librem5-flash-image_0.0.4-2.dsc 3cc7e9878fd54de8aeaf8fa879d17fefde62ad5037d2e17ed4b1ab6d5e0b74fe 3676 librem5-flash-image_0.0.4-2.debian.tar.xz fea36652c061dd188c74201821a4a676a2c5e317dca55a92b726e06ff83071a3 8412 librem5-flash-image_0.0.4-2_amd64.buildinfo Files: 736d822614f9b9527f143a69f49acf4c 2248 contrib/admin optional librem5-flash-image_0.0.4-2.dsc 0f5535ec7adf24532c0eab2a9d40c35c 3676 contrib/admin optional librem5-flash-image_0.0.4-2.debian.tar.xz 8ecd745a70f58a395927c835f7f6f6a5 8412 contrib/admin optional librem5-flash-image_0.0.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAmYfa8YACgkQJb+GUkr8 wePOwA/+PjIKJ65wt4+n+3CU0xzsKpGZHjTKknkmj/QNOdyavf0Py8HuftMCyazk
