Bug#1053245: fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it
I had the same problem and it took me quite some time to find that fluidsynth was the root cause of this. Fluidsynth was installed as new dependency from lutris 0.5.14 and blocked my sound device each ~second boot. @Patrick I could check the status with "systemctl --user status fluidsynth" and disable it with "sudo systemctl --global disable fluidsynth.service" Regards, Axel
Bug#1042682: marked as done (mongo-c-driver: FTBFS with Sphinx 7.1, docutils 0.20: make[3]: *** [src/libbson/doc/CMakeFiles/bson-html.dir/build.make:554: src/libbson/doc/html/api.html] Error 2)
Your message dated Thu, 02 Nov 2023 22:04:49 + with message-id and subject line Bug#1042682: fixed in mongo-c-driver 1.25.0-1 has caused the Debian Bug report #1042682, regarding mongo-c-driver: FTBFS with Sphinx 7.1, docutils 0.20: make[3]: *** [src/libbson/doc/CMakeFiles/bson-html.dir/build.make:554: src/libbson/doc/html/api.html] Error 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.) -- 1042682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mongo-c-driver Version: 1.24.2-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, mongo-c-driver fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 12%] Building C object > src/libbson/CMakeFiles/bson_shared.dir/src/bson/bson-md5.c.o > cd /<>/obj-x86_64-linux-gnu/src/libbson && /usr/bin/cc > -DBSON_COMPILATION -DJSONSL_PARSE_NAN -DMCOMMON_NAME_PREFIX=_bson_mcommon > -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -Dbson_shared_EXPORTS > -I/<>/obj-x86_64-linux-gnu/src/libbson/src > -I/<>/obj-x86_64-linux-gnu/src/libbson/src/bson > -I/<>/src/libbson/src -I/<>/src/libbson/src/bson > -I/<>/src/libbson/../../src/common > -I/<>/obj-x86_64-linux-gnu/src/libbson/../../src > -I/<>/obj-x86_64-linux-gnu/src/libbson/../../src/common > -Wuninitialized -Wundef -Wswitch-enum -Wswitch-default -Wstrict-prototypes > -Wshadow -Wredundant-decls -Wno-uninitialized -Wno-strict-aliasing > -Wmissing-include-dirs -Winit-self -Wformat-security -Wformat-nonliteral > -Wformat -Wexpansion-to-defined -Wempty-body -Wall -pedantic -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -fPIC > -Werror=implicit -Werror=return-type -Werror=incompatible-pointer-types > -Werror=int-conversion -Werror=discarded-qualifiers -Werror=uninitialized -MD > -MT src/libbson/CMakeFiles/bson_shared.dir/src/bson/bson-md5.c.o -MF > CMakeFiles/bson_shared.dir/src/bson/bson-md5.c.o.d -o > CMakeFiles/bson_shared.dir/src/bson/bson-md5.c.o -c > /<>/src/libbson/src/bson/bson-md5.c > [ 12%] Building C object > src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mcd-azure.c.o > cd /<>/obj-x86_64-linux-gnu/src/libmongoc && /usr/bin/cc > -DBSON_STATIC -DHAVE_STDARG_H -DHAVE_UNISTD_H -DKMS_MESSAGE_ENABLE_CRYPTO > -DKMS_MESSAGE_ENABLE_CRYPTO_LIBCRYPTO -DKMS_MSG_STATIC > -DMCOMMON_NAME_PREFIX=_mongoc_mcommon -DMONGOC_COMPILATION -DMONGOC_STATIC > -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 > -I/<>/src/libmongoc/../kms-message/src > -I/<>/obj-x86_64-linux-gnu/src/libmongoc/src > -I/<>/obj-x86_64-linux-gnu/src/libmongoc/src/mongoc > -I/<>/src/libmongoc/src > -I/<>/src/libmongoc/src/mongoc > -I/<>/src/libmongoc/../../src/common > -I/<>/obj-x86_64-linux-gnu/src/libmongoc/../../src > -I/<>/obj-x86_64-linux-gnu/src/libmongoc/../../src/common > -I/<>/obj-x86_64-linux-gnu/src/libbson/src > -I/<>/obj-x86_64-linux-gnu/src/libbson/src/bson > -I/<>/src/libbson/src -I/<>/src/libbson/src/bson > -I/<>/src/libbson/../../src/common > -I/<>/obj-x86_64-linux-gnu/src/libbson/../../src > -I/<>/obj-x86_64-linux-gnu/src/libbson/../../src/common > -Wuninitialized -Wundef -Wswitch-enum -Wswitch-default -Wstrict-prototypes > -Wshadow -Wredundant-decls -Wno-uninitialized -Wno-strict-aliasing > -Wmissing-include-dirs -Winit-self -Wformat-security -Wformat-nonliteral > -Wformat -Wexpansion-to-defined -Wempty-body -Wall -pedantic -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 > -Werror=implicit -Werror=return-type -Werror=incompatible-pointer-types > -Werror=int-conversion -Werror=discarded-qualifiers -Werror=uninitialized > -fPIC -MD -MT > src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mcd-azure.c.o -MF > CMakeFiles/mongoc_static.dir/src/mongoc/mcd-azure.c.o.d -o > CMakeFiles/mongoc_static.dir/src/mongoc/mcd-azure.c.o -c > /<>/src/libmongoc/src/mongoc/mcd-azure.c > [ 12%] Building C object > src/libbson/CMakeFiles/bson_shared.dir/src/bson/bson-memory.c.o > cd /<>/obj-x86_64-linux-gnu/src/libbson && /usr/bin/cc > -DBSON_COMPILATION -DJSONSL_PARSE_NAN -DMCOMMON_NAME_PREFIX=_bson_mcommon > -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -Dbson_shared_EXPORTS > -I/<>/obj-x86_64-linux-gnu/src/libbson/src >
Bug#1055256: colmap: Missing build dependency on libcgal-dev
Source: colmap Version: 3.8+git20231101+ds-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=colmap=3.8%2Bgit20231101%2Bds-1 ... CMake Error at cmake/FindDependencies.cmake:62 (find_package): By not providing "FindCGAL.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "CGAL", but CMake did not find one. Could not find a package configuration file provided by "CGAL" with any of the following names: CGALConfig.cmake cgal-config.cmake Add the installation prefix of "CGAL" to CMAKE_PREFIX_PATH or set "CGAL_DIR" to a directory containing one of the above files. If "CGAL" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:86 (include) -- Configuring incomplete, errors occurred!
Bug#1055255: matrix-synapse: CVE-2023-43796
Source: matrix-synapse Version: 1.95.0-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for matrix-synapse. CVE-2023-43796[0]: | Synapse is an open-source Matrix homeserver Prior to versions 1.95.1 | and 1.96.0rc1, cached device information of remote users can be | queried from Synapse. This can be used to enumerate the remote users | known to a homeserver. System administrators are encouraged to | upgrade to Synapse 1.95.1 or 1.96.0rc1 to receive a patch. As a | workaround, the `federation_domain_whitelist` can be used to limit | federation traffic with a homeserver. 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-43796 https://www.cve.org/CVERecord?id=CVE-2023-43796 [1] https://github.com/matrix-org/synapse/security/advisories/GHSA-mp92-3jfm-3575 [2] https://github.com/matrix-org/synapse/commit/daec55e1fe120c564240c5386e77941372bf458f Regards, Salvatore
Bug#1055253: amanda: CVE-2023-30577
Source: amanda Version: 1:3.5.1-11 Severity: grave Tags: security upstream Forwarded: https://github.com/zmanda/amanda/pull/228 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1:3.5.1-7 Hi, The following vulnerability was published for amanda. CVE-2023-30577[0]: | AMANDA (Advanced Maryland Automatic Network Disk Archiver) before | tag-community-3.5.4 mishandles argument checking for runtar.c, a | different vulnerability than CVE-2022-37705. 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-30577 https://www.cve.org/CVERecord?id=CVE-2023-30577 [1] https://github.com/zmanda/amanda/security/advisories/GHSA-crrw-v393-h5q3 [2] https://github.com/zmanda/amanda/pull/228 Regards, Salvatore
Processed: amanda: CVE-2023-30577
Processing control commands: > found -1 1:3.5.1-7 Bug #1055253 [src:amanda] amanda: CVE-2023-30577 Marked as found in versions amanda/1:3.5.1-7. -- 1055253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055252: squid: CVE-2023-46724: SQUID-2023:4 Denial of Service in SSL Certificate validation
Source: squid Version: 6.3-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid. CVE-2023-46724[0]: | Squid is a caching proxy for the Web. Due to an Improper Validation | of Specified Index bug, Squid versions 3.3.0.1 through 5.9 and 6.0 | prior to 6.4 compiled using `--with-openssl` are vulnerable to a | Denial of Service attack against SSL Certificate validation. This | problem allows a remote server to perform Denial of Service against | Squid Proxy by initiating a TLS Handshake with a specially crafted | SSL Certificate in a server certificate chain. This attack is | limited to HTTPS and SSL-Bump. This bug is fixed in Squid version | 6.4. In addition, patches addressing this problem for the stable | releases can be found in Squid's patch archives. Those who you use a | prepackaged version of Squid should refer to the package vendor for | availability information on updated packages. 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-46724 https://www.cve.org/CVERecord?id=CVE-2023-46724 [1] https://github.com/squid-cache/squid/commit/792ef23e6e1c05780fe17f733859eef6eb8c8be3 [2] https://megamansec.github.io/Squid-Security-Audit/ssl-bufferunderread.html [3] https://github.com/squid-cache/squid/security/advisories/GHSA-73m6-jm96-c6r3 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: cloning 1054537 ..., retitle -3 to squid: CVE-2023-46848: SQUID-2023:5 Denial of Service in FTP
Processing commands for cont...@bugs.debian.org: > clone 1054537 -1 -2 -3 Bug #1054537 [squid] Squid 6.3: multiple vulnerabilities, patches available Bug 1054537 cloned as bugs 1055249-1055251 > retitle 1054537 squid: CVE-2023-46846: SQUID-2023:1 Request/Response > smuggling in HTTP/1.1 and ICAP Bug #1054537 [squid] Squid 6.3: multiple vulnerabilities, patches available Changed Bug title to 'squid: CVE-2023-46846: SQUID-2023:1 Request/Response smuggling in HTTP/1.1 and ICAP' from 'Squid 6.3: multiple vulnerabilities, patches available'. > retitle -1 squid: CVE-2023-5824: SQUID-2023:2 Multiple issues in HTTP > response caching Bug #1055249 [squid] Squid 6.3: multiple vulnerabilities, patches available Changed Bug title to 'squid: CVE-2023-5824: SQUID-2023:2 Multiple issues in HTTP response caching' from 'Squid 6.3: multiple vulnerabilities, patches available'. > retitle -2 squid: CVE-2023-46847: SQUID-2023:3 Denial of Service in HTTP > Digest Authentication Bug #1055250 [squid] Squid 6.3: multiple vulnerabilities, patches available Changed Bug title to 'squid: CVE-2023-46847: SQUID-2023:3 Denial of Service in HTTP Digest Authentication' from 'Squid 6.3: multiple vulnerabilities, patches available'. > retitle -3 squid: CVE-2023-46848: SQUID-2023:5 Denial of Service in FTP Bug #1055251 [squid] Squid 6.3: multiple vulnerabilities, patches available Changed Bug title to 'squid: CVE-2023-46848: SQUID-2023:5 Denial of Service in FTP' from 'Squid 6.3: multiple vulnerabilities, patches available'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054537 1055249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055249 1055250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055250 1055251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958692: node-matrix-js-sdk: Remove dependency to node-request
On 2/11/23 10:27 PM, Hubert Chathi wrote: On Sun, 29 Oct 2023 22:43:55 +0530, Praveen Arimbrathodiyil said: On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote: Upstream has deprecated node-request: https://github.com/request/request/issues/3142 It can be replaced by node-got Hi Jonas, Hubert, Are you planning to update matrix-js-sdk? We'd like to remove deprecated node-request from the archive and this package is a blocker. I don't currently have time to update matrix-js-sdk. Feel free to remove it from testing so that it doesn't block anything else. I can always upload a new version later. This is already not in testing for 525 days. We can't remove a package from the archive if any package (build) depends on it.
Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected
Hi, On 02-11-2023 15:13, Andreas Tille wrote: There is probably one remaining problem. As per file R/zzz.R[2] the function checkMatrixPackageVersion verifies that TMB is running always with the Matrix version it was built against. Well, I suggested before to just patch that check out. Is it really doing any good? If the test suite is remotely well done, it should catch the case where rmatrix breaks the package, while enabling running it against any version that works. Do you see some automatic method to approach this which is better than simply waiting for a CI test to fail (which should happen once a r-cran-matrix package of a new Matrix version is uploaded)? Well, if you get the version tightly recorded, the migration software will refuse to migrate r-cran-matrix because it would break the version in testing. No CI is needed for that. But tight version relations are a pain, i.e. they limit apt in finding upgrade orders, so if too many packages do that, it might prevent people from upgrading their system. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#958692: node-matrix-js-sdk: Remove dependency to node-request
On Sun, 29 Oct 2023 22:43:55 +0530, Praveen Arimbrathodiyil said: > On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote: >> Upstream has deprecated node-request: >> https://github.com/request/request/issues/3142 It can be replaced by >> node-got > Hi Jonas, Hubert, > Are you planning to update matrix-js-sdk? We'd like to remove > deprecated node-request from the archive and this package is a > blocker. I don't currently have time to update matrix-js-sdk. Feel free to remove it from testing so that it doesn't block anything else. I can always upload a new version later. -- Hubert Chathi -- https://www.uhoreg.ca/ Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
Bug#1052837: marked as done (pgloader: FTBFS: build-dependency not installable: postgresql-15-ip4r)
Your message dated Thu, 02 Nov 2023 17:34:45 + with message-id and subject line Bug#1052837: fixed in pgloader 3.6.10-1 has caused the Debian Bug report #1052837, regarding pgloader: FTBFS: build-dependency not installable: postgresql-15-ip4r 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.) -- 1052837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgloader Version: 3.6.9-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: buildapp (>= 1.5), cl-abnf, cl-alexandria, cl-asdf (>= > 3.0.3), cl-asdf-finalizers, cl-asdf-system-connections, cl-bordeaux-threads > (>= 0.8.3), cl-cffi (>= 1:0.12.0), cl-command-line-arguments, cl-csv (>= > 20180712), cl-db3 (>= 20200212), cl-drakma, cl-esrap, cl-fad, > cl-flexi-streams, cl-interpol, cl-ixf, cl-local-time, cl-log, cl-lparallel, > cl-markdown, cl-md5, cl-metabang-bind, cl-mssql, cl-mustache, cl-plus-ssl (>= > 20190204), cl-postmodern, cl-ppcre, cl-py-configparser, cl-qmynd, cl-quri, > cl-simple-date, cl-split-sequence, cl-sqlite, cl-trivial-backtrace, > cl-trivial-utf-8, cl-unicode, cl-usocket, cl-utilities, cl-uuid, cl-yason, > cl-zs3, debhelper-compat (= 13), gawk, help2man, libsqlite3-dev, > postgresql-15-ip4r | postgresql-ip4r, python3-sphinx, > python3-sphinx-rtd-theme, sbcl (>= 1.1.13), tzdata, build-essential, fakeroot > Filtered Build-Depends: buildapp (>= 1.5), cl-abnf, cl-alexandria, cl-asdf > (>= 3.0.3), cl-asdf-finalizers, cl-asdf-system-connections, > cl-bordeaux-threads (>= 0.8.3), cl-cffi (>= 1:0.12.0), > cl-command-line-arguments, cl-csv (>= 20180712), cl-db3 (>= 20200212), > cl-drakma, cl-esrap, cl-fad, cl-flexi-streams, cl-interpol, cl-ixf, > cl-local-time, cl-log, cl-lparallel, cl-markdown, cl-md5, cl-metabang-bind, > cl-mssql, cl-mustache, cl-plus-ssl (>= 20190204), cl-postmodern, cl-ppcre, > cl-py-configparser, cl-qmynd, cl-quri, cl-simple-date, cl-split-sequence, > cl-sqlite, cl-trivial-backtrace, cl-trivial-utf-8, cl-unicode, cl-usocket, > cl-utilities, cl-uuid, cl-yason, cl-zs3, debhelper-compat (= 13), gawk, > help2man, libsqlite3-dev, postgresql-15-ip4r, python3-sphinx, > python3-sphinx-rtd-theme, sbcl (>= 1.1.13), tzdata, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1426 B] > Get:5 copy:/<>/apt_archive ./ Packages [1416 B] > Fetched 3457 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: postgresql-15-ip4r but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/09/25/pgloader_3.6.9-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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
Bug#1052809: marked as done (parlatype: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1)
Your message dated Thu, 02 Nov 2023 17:19:30 + with message-id and subject line Bug#1052809: fixed in parlatype 3.1-3 has caused the Debian Bug report #1052809, regarding parlatype: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parlatype Version: 3.1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 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 '/<>' > mkdir -p -m0700 /<>/debian/tmp/run > XDG_RUNTIME_DIR=/<>/debian/tmp/run dbus-run-session -- xvfb-run > dh_auto_test > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > MESON_TESTTHREADS=8 meson test > ninja: Entering directory `/<>/obj-x86_64-linux-gnu' > [1/1] Generating config.h with a custom command > 1/9 contribOK 0.05s > 2/9 Validating org.parlatype.Parlatype.desktop OK 0.01s > 3/9 contribFAIL0.05s > killed by signal 6 SIGABRT > >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/libparlatype/src > >>> LANGUAGE=de MALLOC_PERTURB_=164 > >>> /<>/obj-x86_64-linux-gnu/libparlatype/tests/contrib --tap -k > > 4/9 Validating org.parlatype.Parlatype.appdata.xml OK 0.05s > dbus-daemon[213783]: [session uid=1001 pid=213783] Activating service > name='org.a11y.Bus' requested by ':1.1' (uid=1001 pid=213817 > comm="/<>/obj-x86_64-l") > dbus-daemon[213783]: [session uid=1001 pid=213783] Successfully activated > service 'org.a11y.Bus' > 5/9 gstOK 0.20s > 6/9 config OK 0.24s > dbus-daemon[213840]: Activating service name='org.a11y.atspi.Registry' > requested by ':1.0' (uid=1001 pid=213817 comm="/<>/obj-x86_64-l") > dbus-daemon[213840]: Successfully activated service 'org.a11y.atspi.Registry' > SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry > 7/9 waveviewer OK 0.29s > 8/9 player OK 0.33s > 9/9 waveloader OK 0.54s > > Ok: 8 > Expected Fail: 0 > Fail: 1 > Unexpected Pass:0 > Skipped:0 > Timeout:0 > > Full log written to > /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt > ==> meson-logs/testlog.txt <== > Log of Meson test suite run on 2023-09-26T06:34:37.874484 > > Inherited environment: DEB_HOST_GNU_SYSTEM=linux-gnu DFLAGS=-frelease > DEB_BUILD_ARCH_BITS=64 DEB_TARGET_GNU_CPU=x86_64 DEB_HOST_ARCH_OS=linux > USER=user42 CXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection' DEB_BUILD_GNU_TYPE=x86_64-linux-gnu > DEB_TARGET_MULTIARCH=x86_64-linux-gnu OBJCFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' > DH_INTERNAL_OPTIONS=-O--buildsystem=meson DEB_BUILD_ARCH_CPU=amd64 > DEB_HOST_ARCH_LIBC=gnu DEB_HOST_ARCH_ABI=base > HOME=/<>/debian/.debhelper/generated/_source/home > APT_CONFIG=/var/lib/sbuild/apt.conf SCHROOT_CHROOT_NAME=sid-amd64-sbuild > DEB_BUILD_ARCH_ENDIAN=little LDFLAGS='-Wl,-z,relro -Wl,-z,now' > DEB_TARGET_ARCH_BITS=64 DEB_BUILD_GNU_SYSTEM=linux-gnu MAKEFLAGS=w > SCHROOT_UID=1001 > DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-kEPNtso8qh,guid=efbde53607ac79eb3bbe300b65127b7d > DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_TYPE=x86_64-linux-gnu > DEB_TARGET_ARCH_CPU=amd64 LOGNAME=user42 DEB_BUILD_ARCH_LIBC=gnu > DEB_BUILD_ARCH_ABI=base DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little > DH_INTERNAL_OVERRIDE=dh_auto_test DEB_HOST_GNU_CPU=x86_64 LC_COLLATE=C.UTF-8 > DEB_TARGET_GNU_SYSTEM=linux-gnu > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > DEB_TARGET_ARCH_OS=linux CFLAGS='-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection
Bug#1055203: marked as done (git-cola: files in /usr/local/share/{applications,doc,git-cola,locale,metainfo}/)
Your message dated Thu, 02 Nov 2023 17:04:21 +
with message-id
and subject line Bug#1055203: fixed in git-cola 4.3.2-1
has caused the Debian Bug report #1055203,
regarding git-cola: files in
/usr/local/share/{applications,doc,git-cola,locale,metainfo}/
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.)
--
1055203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-cola
Version: 3.12.0-3
Severity: serious
Justification: Policy 9.1.2
According to the FHS and Debian Policy 9.1.2, packages must not put
files in the /usr/local/ directory, but git-cola 3.12.0-3 does that:
https://www.debian.org/doc/debian-policy/ch-opersys.html#site-specific-programs
I note that lintian does produce errors for this situation:
https://udd.debian.org/lintian/?packages=git-cola
Here is the full list of files in the /usr/local/ directory:
$ dpkg -L git-cola | grep /usr/local/
/usr/local/share
/usr/local/share/applications
/usr/local/share/applications/git-cola-folder-handler.desktop
/usr/local/share/applications/git-cola.desktop
/usr/local/share/applications/git-dag.desktop
/usr/local/share/doc
/usr/local/share/doc/git-cola
/usr/local/share/doc/git-cola/git-cola.rst
/usr/local/share/doc/git-cola/git-dag.rst
/usr/local/share/doc/git-cola/hotkeys.html
/usr/local/share/doc/git-cola/hotkeys_de.html
/usr/local/share/doc/git-cola/hotkeys_zh_CN.html
/usr/local/share/doc/git-cola/hotkeys_zh_TW.html
/usr/local/share/doc/git-cola/index.rst
/usr/local/share/doc/git-cola/relnotes.rst
/usr/local/share/doc/git-cola/thanks.rst
/usr/local/share/git-cola
/usr/local/share/git-cola/bin
/usr/local/share/git-cola/bin/ssh-askpass
/usr/local/share/git-cola/bin/ssh-askpass-darwin
/usr/local/share/git-cola/icons
/usr/local/share/git-cola/icons/a-z-order.svg
/usr/local/share/git-cola/icons/arrow-down.svg
/usr/local/share/git-cola/icons/arrow-up.svg
/usr/local/share/git-cola/icons/check.svg
/usr/local/share/git-cola/icons/circle-slash-red.svg
/usr/local/share/git-cola/icons/circle-slash.svg
/usr/local/share/git-cola/icons/dark
/usr/local/share/git-cola/icons/dark/a-z-order.svg
/usr/local/share/git-cola/icons/dark/arrow-down.svg
/usr/local/share/git-cola/icons/dark/arrow-up.svg
/usr/local/share/git-cola/icons/dark/check.svg
/usr/local/share/git-cola/icons/dark/circle-slash-red.svg
/usr/local/share/git-cola/icons/dark/circle-slash.svg
/usr/local/share/git-cola/icons/dark/desktop-download.svg
/usr/local/share/git-cola/icons/dark/diff.svg
/usr/local/share/git-cola/icons/dark/document-save-symbolic.svg
/usr/local/share/git-cola/icons/dark/edit-copy.svg
/usr/local/share/git-cola/icons/dark/edit-cut.svg
/usr/local/share/git-cola/icons/dark/edit-paste.svg
/usr/local/share/git-cola/icons/dark/edit-redo.svg
/usr/local/share/git-cola/icons/dark/edit-select-all.svg
/usr/local/share/git-cola/icons/dark/edit-undo.svg
/usr/local/share/git-cola/icons/dark/ellipsis.svg
/usr/local/share/git-cola/icons/dark/eye.svg
/usr/local/share/git-cola/icons/dark/file-binary.svg
/usr/local/share/git-cola/icons/dark/file-code.svg
/usr/local/share/git-cola/icons/dark/file-directory.svg
/usr/local/share/git-cola/icons/dark/file-download.svg
/usr/local/share/git-cola/icons/dark/file-media.svg
/usr/local/share/git-cola/icons/dark/file-text.svg
/usr/local/share/git-cola/icons/dark/file-zip.svg
/usr/local/share/git-cola/icons/dark/fold.svg
/usr/local/share/git-cola/icons/dark/folder-new.svg
/usr/local/share/git-cola/icons/dark/folder.svg
/usr/local/share/git-cola/icons/dark/gear.svg
/usr/local/share/git-cola/icons/dark/git-branch.svg
/usr/local/share/git-cola/icons/dark/git-cola.svg
/usr/local/share/git-cola/icons/dark/git-commit.svg
/usr/local/share/git-cola/icons/dark/git-compare.svg
/usr/local/share/git-cola/icons/dark/git-merge.svg
/usr/local/share/git-cola/icons/dark/last-first-order.svg
/usr/local/share/git-cola/icons/dark/link-external.svg
/usr/local/share/git-cola/icons/dark/modified.svg
/usr/local/share/git-cola/icons/dark/partial.svg
/usr/local/share/git-cola/icons/dark/pencil.svg
/usr/local/share/git-cola/icons/dark/plus.svg
/usr/local/share/git-cola/icons/dark/primitive-dot.svg
/usr/local/share/git-cola/icons/dark/question-plain.svg
/usr/local/share/git-cola/icons/dark/question.svg
/usr/local/share/git-cola/icons/dark/repo-pull.svg
Bug#1055237: does not conform to the standards for library packaging
Source: catch2 Version: 3.4.0-1 Severity: serious Dear Maintainer, Recently catch2/3.4.0-1 was uploaded to Debian, great. Yet the binary packages do not follow the layout for libraries that is described in Policy Section 8. For instance I think we should provide a shared library and if there are enough reasons not to do so (see Policy 8.3), at least the binary package name should be changed to libcatch2-dev. Also this is not a header-only library anymore, the description of the package should be changed. As a side note, the upload of the major version 3.x came out with many breaking interface changes giving rise to RC bugs in e.g. genomicsdb, netgen, spdlog, therion just to name a few, also to failing autopkgtests in many rdeps. I would have been more comfortable with such a huge version change being advertised and more prepared, with some kind of a library transition process for instance. In any case, thanks for your work on catch2, Best regards, -- Pierre
Bug#1055205: closed by Vincent Blut (Re: Bug#1055205: chrony: SysV problems after upgrade)
On Thu, 02 Nov 2023 12:27:05 + "Debian Bug Tracking System" wrote: Hello Vincent, Ok, thnx for your explanation! I changed it to disable (and indeed there is only a K link) and I'll see at the next upgrade. Richard. > This is an automatic notification regarding your Bug report > which was filed against the chrony package: > > #1055205: chrony: SysV problems after upgrade > > It has been closed by Vincent Blut . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Vincent Blut > by replying to this email. > > -- ___ It is better to remain silent and be thought a fool, than to speak aloud and remove all doubt. +--+ | Richard Lucassen, Utrecht| +--+
Bug#1039883: The issue impacts SSD disks as well
On Monday, 24 July 2023 11:23:19 CET Salvatore Bonaccorso wrote: > On Sun, Jul 02, 2023 at 09:14:50PM +, Hervé Werner wrote: > > I've just faced this issue on the SSD disk as well, so it seems that > > the probability is just lower on a speedier disk. > > Are you able to reliably preoeduce the issue and can bisect it to the > introducing commit? > > Can you retest please with recent kernel, 6.3.11-1 and ideally 6.4.4-1 > as recently uploaded to unstable? Friendly ping. Please test it with kernel(s) currently available in Debian. signature.asc Description: This is a digitally signed message part.
Processed: tagging 1053410, tagging 1055207, tagging 1055228, tagging 1055227
Processing commands for cont...@bugs.debian.org:
> tags 1053410 + experimental
Bug #1053410 {Done: Jonathan Carter } [foliate] foliate:
Failed to load shared library 'libwebkit2gtk-4.0.so.37'
Added tag(s) experimental.
> tags 1055207 - bookworm
Bug #1055207 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable
Removed tag(s) bookworm.
> tags 1055228 + sid trixie
Bug #1055228 [src:plplot] plplot: FTBFS on armhf (test segfault)
Added tag(s) trixie and sid.
> tags 1055227 + sid trixie
Bug #1055227 [src:libgom] libgom: FTBFS on i386
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1053410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053410
1055207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055207
1055227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055227
1055228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054427: marked as done (trafficserver: CVE-2023-41752 CVE-2023-39456 CVE-2023-44487)
Your message dated Thu, 02 Nov 2023 14:36:38 + with message-id and subject line Bug#1054427: fixed in trafficserver 9.2.3+ds-1 has caused the Debian Bug report #1054427, regarding trafficserver: CVE-2023-41752 CVE-2023-39456 CVE-2023-44487 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.) -- 1054427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trafficserver X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for trafficserver. CVE-2023-41752[0]: | Exposure of Sensitive Information to an Unauthorized Actor | vulnerability in Apache Traffic Server.This issue affects Apache | Traffic Server: from 8.0.0 through 8.1.8, from 9.0.0 through 9.2.2. | Users are recommended to upgrade to version 8.1.9 or 9.2.3, which | fixes the issue. https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q https://github.com/apache/trafficserver/commit/334839cb7a6724c71a5542e924251a8d931774b0 (8.1.x) https://github.com/apache/trafficserver/commit/de7c8a78edd5b75e311561dfaa133e9d71ea8a5e (9.2.x) CVE-2023-39456[1]: | Improper Input Validation vulnerability in Apache Traffic Server | with malformed HTTP/2 frames.This issue affects Apache Traffic | Server: from 9.0.0 through 9.2.2. Users are recommended to upgrade | to version 9.2.3, which fixes the issue. https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q https://github.com/apache/trafficserver/commit/4ca137b59bc6aaa25f8b14db2bdd2e72c43502e5 (9.2.x) CVE-2023-44487[2]: | The HTTP/2 protocol allows a denial of service (server resource | consumption) because request cancellation can reset many streams | quickly, as exploited in the wild in August through October 2023. https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q https://github.com/apache/trafficserver/commit/b28ad74f117307e8de206f1de70c3fa716f90682 (9.2.3-rc0) https://github.com/apache/trafficserver/commit/d742d74039aaa548dda0148ab4ba207906abc620 (8.1.x) For oldstable-security let's move to 8.1.8 and for stable-security to 9.2.3? If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-41752 https://www.cve.org/CVERecord?id=CVE-2023-41752 [1] https://security-tracker.debian.org/tracker/CVE-2023-39456 https://www.cve.org/CVERecord?id=CVE-2023-39456 [2] https://security-tracker.debian.org/tracker/CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: trafficserver Source-Version: 9.2.3+ds-1 Done: Jean Baptiste Favre We believe that the bug you reported is fixed in the latest version of trafficserver, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean Baptiste Favre (supplier of updated trafficserver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Nov 2023 13:46:58 +0100 Source: trafficserver Architecture: source Version: 9.2.3+ds-1 Distribution: unstable Urgency: medium Maintainer: Jean Baptiste Favre Changed-By: Jean Baptiste Favre Closes: 1053801 1054427 Changes: trafficserver (9.2.3+ds-1) unstable; urgency=medium . * New upstream version 9.2.3+ds * Update d/trafficserver-experimental-plugins for 9.2.3 release * CVEs fixes (Closes: #1054427, Closes: #1053801) - CVE-2023-39456: Improper Input Validation vulnerability - CVE-2023-41752: Exposure of Sensitive Information to an Unauthorized Actor - CVE-2023-44487: The HTTP/2 protocol allows a denial of service Checksums-Sha1: bc119fbd9efd3175f3995001edb01ba079839533 2989 trafficserver_9.2.3+ds-1.dsc bd4752974c4343d6be0deb34ed61e521157bba21 8942124 trafficserver_9.2.3+ds.orig.tar.xz fad635001981b65d66b3ad1a910ba149f130613e 35788 trafficserver_9.2.3+ds-1.debian.tar.xz
Bug#1053801: marked as done (trafficserver: CVE-2023-44487)
Your message dated Thu, 02 Nov 2023 14:36:38 + with message-id and subject line Bug#1053801: fixed in trafficserver 9.2.3+ds-1 has caused the Debian Bug report #1053801, regarding trafficserver: CVE-2023-44487 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.) -- 1053801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trafficserver X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for trafficserver. CVE-2023-44487[0]: | The HTTP/2 protocol allows a denial of service (server resource | consumption) because request cancellation can reset many streams | quickly, as exploited in the wild in August through October 2023. 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-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Please adjust the affected versions in the BTS as needed. Fixed in 9.2.3: https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q https://github.com/apache/trafficserver/commit/b28ad74f117307e8de206f1de70c3fa716f90682 (9.2.x) --- End Message --- --- Begin Message --- Source: trafficserver Source-Version: 9.2.3+ds-1 Done: Jean Baptiste Favre We believe that the bug you reported is fixed in the latest version of trafficserver, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean Baptiste Favre (supplier of updated trafficserver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Nov 2023 13:46:58 +0100 Source: trafficserver Architecture: source Version: 9.2.3+ds-1 Distribution: unstable Urgency: medium Maintainer: Jean Baptiste Favre Changed-By: Jean Baptiste Favre Closes: 1053801 1054427 Changes: trafficserver (9.2.3+ds-1) unstable; urgency=medium . * New upstream version 9.2.3+ds * Update d/trafficserver-experimental-plugins for 9.2.3 release * CVEs fixes (Closes: #1054427, Closes: #1053801) - CVE-2023-39456: Improper Input Validation vulnerability - CVE-2023-41752: Exposure of Sensitive Information to an Unauthorized Actor - CVE-2023-44487: The HTTP/2 protocol allows a denial of service Checksums-Sha1: bc119fbd9efd3175f3995001edb01ba079839533 2989 trafficserver_9.2.3+ds-1.dsc bd4752974c4343d6be0deb34ed61e521157bba21 8942124 trafficserver_9.2.3+ds.orig.tar.xz fad635001981b65d66b3ad1a910ba149f130613e 35788 trafficserver_9.2.3+ds-1.debian.tar.xz c4a9525306ac032e2a127372747cd6620f00645e 12466 trafficserver_9.2.3+ds-1_source.buildinfo Checksums-Sha256: 379ac21b58337082757b2a42651b3c41913d78f9a6f2d8b2a64f0d8cb0327c7e 2989 trafficserver_9.2.3+ds-1.dsc 0e323e1c4c01d1506cfd49d4c6935dbebd125b187d9ba72fe909bd6b10d81110 8942124 trafficserver_9.2.3+ds.orig.tar.xz 3019ba5c80b2984cfaedc1874693abc32cca1648effcaf13539c85ab584f07e0 35788 trafficserver_9.2.3+ds-1.debian.tar.xz 9c838794911a123d5e5c7cb71ad050ea8b720051c3e19c9b1684f177122802f2 12466 trafficserver_9.2.3+ds-1_source.buildinfo Files: d30aa28b6f3c07a94d218bd3ecb300de 2989 web optional trafficserver_9.2.3+ds-1.dsc f65bf601372c361eb765c1d9150f5755 8942124 web optional trafficserver_9.2.3+ds.orig.tar.xz 2a1cdb9080bce8861831c1943ffa52d5 35788 web optional trafficserver_9.2.3+ds-1.debian.tar.xz 9d60dfd90631ee28d89d9cff20e47d2a 12466 web optional trafficserver_9.2.3+ds-1_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmVDqZFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99 hzdGUw//SKD5qzYmjDQg1H224MKM2lOnq8IcsCXSctxOUc0KhI4rKidLm7QiJ/tL bWMHr643N98Pw9pvikGmXG2I1gh3TvvtXkkVWCG/487lj8Omo/JQ4AvMrzme5jde HANgMO+6DEhsxEf81+7UxneP2fFt2YBMO//kANyQUV5L584BLQuh3ghbTDAOLhUW GwhTRPw66rteTHyf6+RnCMKK7k6AyeHk4Oi2A7MZJByasd4IXlSRMVUOUDe9EpZn
Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected
Hi Graham, Am Sun, Oct 29, 2023 at 10:12:56AM -0100 schrieb Graham Inggs: > I found that in debian/control, r-cran-tmb has Depends: > r-cran-matrix (>= 1.5-3-1~), but this is somehow replaced in the > binary package, presumably by dh-r? dh-r creates a variable R:Depends > Andreas, would it be possible for dh-r to always replace the version > in r-cran-tmb's Depends with r-cran-matrix (>= [the version of > r-cran-matrix it was built with]) ? Well, the *version* was correct even in r-cran-tmb 1.9.6-4. However, due to the '-' in the GNU R Matrix version the dpkg sorting mechanism failed and we need the correct revision of the Debian package. To approach this I decided against hacking this exception into dh-r but rather added override_dh_gencontrol to d/rules where I'm editing the variable accordingly to have the r-cran-matrix Debian package revision that was used at build time. > Then you can avoid modifying Build-Depends and upstream's DESCRIPTION, > and will allow r-cran-tmb to be binNMU'd when needed. It should also > allow for easier backporting. I hope this will also work for backporting but with the current dependency of TMB it also needs Matrix from testing. There is probably one remaining problem. As per file R/zzz.R[2] the function checkMatrixPackageVersion verifies that TMB is running always with the Matrix version it was built against. Do you see some automatic method to approach this which is better than simply waiting for a CI test to fail (which should happen once a r-cran-matrix package of a new Matrix version is uploaded)? Kind regards Andreas. [1] https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/blob/master/debian/rules#L10-13 [2] https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/blob/master/R/zzz.R -- http://fam-tille.de
Bug#1055228: plplot: FTBFS on armhf (test segfault)
Source: plplot
Version: 5.15.0+dfsg2-6
Severity: serious
Hello, I found the package FTBFS on Ubuntu, checked on amdahl and found the
same issue.
/usr/bin/make -f examples/fortran/CMakeFiles/x31f.dir/build.make
examples/fortran/CMakeFiles/x31f.dir/build
make[5]: Entering directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[5]: Nothing to be done for 'examples/fortran/CMakeFiles/x31f.dir/build'.
make[5]: Leaving directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
[ 46%] Built target x31f
/usr/bin/make -f examples/CMakeFiles/test_fortran_svg.dir/build.make
examples/CMakeFiles/test_fortran_svg.dir/depend
make[5]: Entering directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf && /usr/bin/cmake -E
cmake_depends "Unix Makefiles" /home/locutusofborg/plplot-5.15.0+dfsg2
/home/locutusofborg/plplot-5.15.0+dfsg2/examples
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples/CMakeFiles/test_fortran_svg.dir/DependInfo.cmake
"--color="
make[5]: Leaving directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
/usr/bin/make -f examples/CMakeFiles/test_fortran_svg.dir/build.make
examples/CMakeFiles/test_fortran_svg.dir/build
make[5]: Entering directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples &&
/usr/bin/cmake -E echo "Generate fortran results for svg device"
Generate fortran results for svg device
cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples &&
env
EXAMPLES_PREFIX=/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples
SRC_EXAMPLES_PREFIX=/home/locutusofborg/plplot-5.15.0+dfsg2/examples
OUTPUT_DIR=/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples/test_examples_output_dir
/bin/bash
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/plplot_test/plplot-test.sh
--verbose --front-end=fortran --device=svg
Testing front-end fortran
x16af
x00f
x01f
x02f
x03f
x04f
x05f
x06f
x07f
x08f
x09f
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/plplot_test/test_fortran.sh: line 54: 3932208 Bus
error $DEBUG_CMD "$fortrandir"/x${index}f -dev $device -o
"${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> fortran_${device}_test.error >|
"${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt
Program received signal SIGBUS: Access to an undefined portion of a memory
object.
Backtrace for this error:
make[5]: *** [examples/CMakeFiles/test_fortran_svg.dir/build.make:388:
examples/test_examples_output_dir/x00f01.svg] Error 1
make[5]: *** Deleting file 'examples/test_examples_output_dir/x00f01.svg'
make[5]: Leaving directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[4]: *** [CMakeFiles/Makefile2:5049:
examples/CMakeFiles/test_fortran_svg.dir/all] Error 2
make[4]: Leaving directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[3]: *** [CMakeFiles/Makefile2:7121:
examples/CMakeFiles/test_noninteractive.dir/rule] Error 2
make[3]: Leaving directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[2]: *** [Makefile:2243: test_noninteractive] Error 2
make[2]: Leaving directory
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
make[1]: *** [debian/rules:55: override_dh_auto_test] Error 2
make[1]: Leaving directory '/home/locutusofborg/plplot-5.15.0+dfsg2'
make: *** [debian/rules:48: binary] Error 2
Full log attached
G.
log.gz
Description: application/gzip
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1055227: libgom: FTBFS on i386
Source: libgom Version: 0.4-1 Severity: serious libgom fails to build from source on i386 due to a test failing: 3/12 test: test-gom-insert start time: 14:03:26 duration: 0.08s result: killed by signal 6 SIGABRT command: MALLOC_PERTURB_=71 LD_LIBRARY_PATH=... libgom-0.4/obj-i686-linux-gnu/tests/test-gom-insert --- stdout --- TAP version 13 # random seed: R02S7791a8ec950e3900d687ca4fec1d2b7b 1..2 # Start of GomRepository tests # DEBUG: Binding gtype guint (28). # DEBUG: Binding gtype gchararray (64). # DEBUG: Binding gtype gchararray (64). # DEBUG: Binding gtype gchararray (64). # DEBUG: Binding gtype gchararray (64). # DEBUG: Binding gtype gchararray (64). --- stderr --- malloc_consolidate(): unaligned fastbin chunk detected
Bug#1041491: marked as done (yuzu: FTBFS: Unmet build dependencies: glslang-tools:native)
Your message dated Thu, 2 Nov 2023 14:46:24 +0100 with message-id and subject line Re: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native has caused the Debian Bug report #1041491, regarding yuzu: FTBFS: Unmet build dependencies: glslang-tools:native 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.) -- 1041491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yuzu Version: 0-1335+ds-1 Severity: serious Tags: ftbfs sid trixie 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=yuzu=amd64=0-1335%2Bds-1%2Bb1=1689519069=0 dpkg-buildpackage: info: host architecture amd64 dpkg-checkbuilddeps: error: Unmet build dependencies: glslang-tools:native dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 0-1335+ds-1.1 On 2023-11-02 12:34:00 +0100, Santiago Vila wrote: > reopen 1041491 > tags 1041491 + bookworm > fixed 1041491 0-1335+ds-1.1 > thanks > > Hello. I'm reopening this because packages in stable must build in stable. > > Cc:ing all involved parties: Please keep FTBFS bugs open when they happen > in stable, otherwise they become a lot more difficult to find, as they > have a tendency to be archived by the BTS. We do have version tracking. If the bugs was not showing as affecting stable, then the metadata (i.e., the found version) was wrong. Please fix the meta data instead of reopening the bugs. Closing again. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1055205: chrony: SysV problems after upgrade
Hi Vincent, On 02-11-2023 13:21, Vincent Blut wrote: I'm closing this bug report as this is, to me, not something that should handled on the packaging side. Thank you for repairing my lack of looking these things up. I suspected as much (but failed to express that). Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055205: marked as done (chrony: SysV problems after upgrade)
Your message dated Thu, 2 Nov 2023 13:21:58 +0100 with message-id and subject line Re: Bug#1055205: chrony: SysV problems after upgrade has caused the Debian Bug report #1055205, regarding chrony: SysV problems after upgrade 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.) -- 1055205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chrony Version: 4.4-3 Severity: normal I run chronyd supervised. Therefore I removed symlinks in /etc/rc2.d/ (update-rc.d chrony remove). But after an upgrade the deb package installs new symlinks in /etc/rc2.d/ and starts chronyd, even though chronyd is SysV disabled. Please check if /etc/rc2.d/*chrony symlinks exist, if not, don't add these and do not start chronyd. Maybe it's a good idea to just display a warning in that case. Richard. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) 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: sysvinit (via /sbin/init) Versions of packages chrony depends on: ii adduser 3.137 ii init-system-helpers 1.65.2 ii iproute2 6.5.0-4 ii libc62.37-12 ii libcap2 1:2.66-4 ii libedit2 3.1-20230828-1 ii libgnutls30 3.8.1-4+b1 ii libnettle8 3.9.1-2 ii libseccomp2 2.5.4-1+b3 ii tzdata-legacy2023c-10 ii ucf 3.0043+nmu1 chrony recommends no packages. Versions of packages chrony suggests: ii bind9-dnsutils [dnsutils] 1:9.19.17-1 ii dnsutils 1:9.19.17-1 pn networkd-dispatcher -- no debconf information --- End Message --- --- Begin Message --- Hi Richard, Le 2023-11-02 09:01, Richard Lucassen a écrit : > Package: chrony > Version: 4.4-3 > Severity: normal > > I run chronyd supervised. Therefore I removed symlinks in /etc/rc2.d/ > (update-rc.d chrony remove). > But after an upgrade the deb package installs new symlinks in /etc/rc2.d/ and > starts chronyd, even though chronyd is SysV disabled. > > Please check if /etc/rc2.d/*chrony symlinks exist, if not, don't add these > and do not start chronyd. Maybe it's a good idea to just display a warning in > that case. > I'm closing this bug report as this is, to me, not something that should handled on the packaging side. From update-rc.d(8): A common system administration error is to delete the links with the thought that this will "disable" the service, i.e., that this will prevent the service from being started. However, if all links have been deleted then the next time the package is upgraded, the package's postinst script will run update-rc.d again and this will reinstall links at their factory de- fault locations. The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default. In the System V init system this means renam- ing the service's symbolic links from S to K. .P The script .BI /etc/init.d/ name must exist before update-rc.d is run to create the links. Running 'update-rc.d chrony disable' as root should work too. > Richard. Have a good day, Vincent signature.asc Description: PGP signature --- End Message ---
Bug#1055205: chrony: SysV problems after upgrade
Hi Richard, Le 2023-11-02 09:01, Richard Lucassen a écrit : > Package: chrony > Version: 4.4-3 > Severity: normal > > I run chronyd supervised. Therefore I removed symlinks in /etc/rc2.d/ > (update-rc.d chrony remove). > But after an upgrade the deb package installs new symlinks in /etc/rc2.d/ and > starts chronyd, even though chronyd is SysV disabled. > > Please check if /etc/rc2.d/*chrony symlinks exist, if not, don't add these > and do not start chronyd. Maybe it's a good idea to just display a warning in > that case. > I'm closing this bug report as this is, to me, not something that should handled on the packaging side. From update-rc.d(8): A common system administration error is to delete the links with the thought that this will "disable" the service, i.e., that this will prevent the service from being started. However, if all links have been deleted then the next time the package is upgraded, the package's postinst script will run update-rc.d again and this will reinstall links at their factory de- fault locations. The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default. In the System V init system this means renam- ing the service's symbolic links from S to K. .P The script .BI /etc/init.d/ name must exist before update-rc.d is run to create the links. Running 'update-rc.d chrony disable' as root should work too. > Richard. Have a good day, Vincent signature.asc Description: PGP signature
Bug#1054756: marked as done (node-recast: FTBFS: lib/options.ts(1,22): error TS2307: Cannot find module 'ast-types/types' or its corresponding type declarations.)
Your message dated Thu, 02 Nov 2023 12:04:06 + with message-id and subject line Bug#1054756: fixed in node-recast 0.23.4-1 has caused the Debian Bug report #1054756, regarding node-recast: FTBFS: lib/options.ts(1,22): error TS2307: Cannot find module 'ast-types/types' or its corresponding type declarations. 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.) -- 1054756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-recast Version: 0.21.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 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 '/<>' > tsc > lib/options.ts(1,22): error TS2307: Cannot find module 'ast-types/types' or > its corresponding type declarations. > lib/parser.ts(18,15): error TS2532: Object is possibly 'undefined'. > lib/parser.ts(24,15): error TS2532: Object is possibly 'undefined'. > lib/parser.ts(28,12): error TS2532: Object is possibly 'undefined'. > lib/parser.ts(83,24): error TS2532: Object is possibly 'undefined'. > lib/parser.ts(96,7): error TS2532: Object is possibly 'undefined'. > make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/10/27/node-recast_0.21.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=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: node-recast Source-Version: 0.23.4-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-recast, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-recast package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Nov 2023 12:01:32 +0400 Source: node-recast Architecture: source Version: 0.23.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1054756 Changes: node-recast (0.23.4-1) unstable; urgency=medium . * Team upload * Update standards version to 4.6.2, no changes needed * New upstream version 0.23.4 * Refresh patches * Require node-ast-types >= 0.16.1~ (Closes: #1054756) Checksums-Sha1: 0674a2e890474f7109b43e0e05b02718efbacfe7 2215 node-recast_0.23.4-1.dsc acc5d21d9a4d14ac583842f0cac1ecf44571eb1e 195575 node-recast_0.23.4.orig.tar.gz 1b59d4127e72cf8f5834cd36a49321645208a245 5112 node-recast_0.23.4-1.debian.tar.xz Checksums-Sha256: fd13526867dfcd60f499371a4ead78771b8e6f916a3329a251f31da657f850b0 2215 node-recast_0.23.4-1.dsc 8fed4a47aa5eaaffce74a5480f16fa22599dea020efaa2e7960533052a0e61bd 195575 node-recast_0.23.4.orig.tar.gz 839c89d28497471009aa5b026d3db8bf2d216c62dd609b47fdb9956b288d4965 5112 node-recast_0.23.4-1.debian.tar.xz Files: d130898d7e5d4a2474a7889a27f39571 2215 javascript optional node-recast_0.23.4-1.dsc ac72bc25e0ad35b7a6d89845e73992b5 195575 javascript optional node-recast_0.23.4.orig.tar.gz 719025131fae3e734517ab534ad28cbb 5112 javascript optional node-recast_0.23.4-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmVDihsACgkQ9tdMp8mZ 7ukOSQ/+K8Rpq5qGwymxkCh/UWwcVwbrlsEbThGvEAlB+JFtjSkZKmbdFvPid8HX n/fNHVwgIP9TpSuZIkHK7sZArSJWiaJdbjQ/ykaroRZkik/evYzsH/RWzSzf7qDy
Processed: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native
Processing commands for cont...@bugs.debian.org:
> reopen 1041491
Bug #1041491 {Done: Bastian Germann } [src:yuzu] yuzu: FTBFS:
Unmet build dependencies: glslang-tools:native
'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 yuzu/0-1335+ds-1.1.
> tags 1041491 + bookworm
Bug #1041491 [src:yuzu] yuzu: FTBFS: Unmet build dependencies:
glslang-tools:native
Added tag(s) bookworm.
> fixed 1041491 0-1335+ds-1.1
Bug #1041491 [src:yuzu] yuzu: FTBFS: Unmet build dependencies:
glslang-tools:native
The source 'yuzu' and version '0-1335+ds-1.1' do not appear to match any binary
packages
Marked as fixed in versions yuzu/0-1335+ds-1.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1041491: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native
reopen 1041491 tags 1041491 + bookworm fixed 1041491 0-1335+ds-1.1 thanks Hello. I'm reopening this because packages in stable must build in stable. Cc:ing all involved parties: Please keep FTBFS bugs open when they happen in stable, otherwise they become a lot more difficult to find, as they have a tendency to be archived by the BTS. Thanks.
Processed: unarchive for bookworm
Processing commands for cont...@bugs.debian.org:
> unarchive 1041491
Bug #1041491 {Done: Bastian Germann } [src:yuzu] yuzu: FTBFS:
Unmet build dependencies: glslang-tools:native
Unarchived Bug 1041491
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055223: src:slurm-wlm-contrib: fails to migrate to testing for too long: missing binaries
Source: slurm-wlm-contrib Version: 23.02.3-2.1 Severity: serious Control: close -1 23.02.6-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:slurm-wlm-contrib has been trying to migrate for 31 days [2]. Hence, I am filing this bug. This package has build dependencies that exist in non-free, so it can't be build on the buildd [3]. Please upload the binaries for at least amd64. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=slurm-wlm-contrib [3] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#source-and-binary-uploads OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:slurm-wlm-contrib: fails to migrate to testing for too long: missing binaries
Processing control commands: > close -1 23.02.6-1 Bug #1055223 [src:slurm-wlm-contrib] src:slurm-wlm-contrib: fails to migrate to testing for too long: missing binaries The source 'slurm-wlm-contrib' and version '23.02.6-1' do not appear to match any binary packages Marked as fixed in versions slurm-wlm-contrib/23.02.6-1. Bug #1055223 [src:slurm-wlm-contrib] src:slurm-wlm-contrib: fails to migrate to testing for too long: missing binaries Marked Bug as done -- 1055223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:fcoe-utils: fails to migrate to testing for too long: FTBFS on 32 bit archs
Processing control commands:
> close -1 1.0.34-3
Bug #1055217 [src:fcoe-utils] src:fcoe-utils: fails to migrate to testing for
too long: FTBFS on 32 bit archs
Marked as fixed in versions fcoe-utils/1.0.34-3.
Bug #1055217 [src:fcoe-utils] src:fcoe-utils: fails to migrate to testing for
too long: FTBFS on 32 bit archs
Marked Bug as done
> block -1 by 1053685
Bug #1055217 {Done: Paul Gevers } [src:fcoe-utils]
src:fcoe-utils: fails to migrate to testing for too long: FTBFS on 32 bit archs
1055217 was not blocked by any bugs.
1055217 was not blocking any bugs.
Added blocking bug(s) of 1055217: 1053685
--
1055217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055217: src:fcoe-utils: fails to migrate to testing for too long: FTBFS on 32 bit archs
Source: fcoe-utils Version: 1.0.34-2 Severity: serious Control: close -1 1.0.34-3 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1053685 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:fcoe-utils has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails to build on 32 bit archs as reported in bug #1053685. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=fcoe-utils OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed
Processing control commands: > clone -1 -2 Bug #1013520 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed Bug 1013520 cloned as bug 1055207 > close -1 2.4.3-2 Bug #1013520 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed Marked as fixed in versions django-cachalot/2.4.3-2. Bug #1013520 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed Marked Bug as done > retitle -2 django-cachalot: FTBFS: unsatisfiable Bug #1055207 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed Changed Bug title to 'django-cachalot: FTBFS: unsatisfiable' from 'django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed'. > notfound -2 2.4.3-1.1 Bug #1055207 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable No longer marked as found in versions django-cachalot/2.4.3-1.1. > found -2 2.4.3-2 Bug #1055207 [src:django-cachalot] django-cachalot: FTBFS: unsatisfiable Marked as found in versions django-cachalot/2.4.3-2. -- 1013520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013520 1055207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013520: django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed
Control: clone -1 -2 Control: close -1 2.4.3-2 Control: retitle -2 django-cachalot: FTBFS: unsatisfiable build-dependency: python3-django (< 3:3.3~) but 3:4.2.6-1 is to be installed Control: notfound -2 2.4.3-1.1 Control: found -2 2.4.3-2 On Fri, 24 Jun 2022 11:53:48 +0200 Lucas Nussbaum wrote: > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python3-django (< 2:3.3~) but 2:4.0.5-2 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. This has been fixed with the upload of 2.4.3-2, but python3-django since then saw a new upload. Now the failure is: """ Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: autopkgtest-satdep : Depends: python3-django (< 3:3.3~) but 3:4.2.6-1 is to be installed E: Unable to correct problems, you have held broken packages. """ Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1054713: marked as done (libsquashfuse-dev: needed headers (e.g. config.h) are not shipped)
Your message dated Thu, 02 Nov 2023 09:08:17 + with message-id and subject line Bug#1054713: fixed in squashfuse 0.5.0-2 has caused the Debian Bug report #1054713, regarding libsquashfuse-dev: needed headers (e.g. config.h) are not shipped 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.) -- 1054713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libappimage Version: 1.0.4-5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/src/libappimage/core && /usr/bin/c++ > -DENABLE_BINRELOC -DGIT_COMMIT=\"\" -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE_SOURCE -I/<>/src/libappimage_hashlib/include > -I/usr/include/squashfuse -I/<>/src/libappimage/core/.. > -I/<>/include -I/<>/src/libappimage -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fdebug-prefix-map=/<>=../ > -fmacro-prefix-map=/<>=../ -Os -DNDEBUG -Wl,--gc-sections > -std=gnu++11 -fPIC -MD -MT > src/libappimage/core/CMakeFiles/core.dir/impl/TraversalType2.cpp.o -MF > CMakeFiles/core.dir/impl/TraversalType2.cpp.o.d -o > CMakeFiles/core.dir/impl/TraversalType2.cpp.o -c > /<>/src/libappimage/core/impl/TraversalType2.cpp > In file included from /usr/include/squashfuse/dir.h:28, > from /usr/include/squashfuse/squashfuse.h:28, > from > /<>/src/libappimage/core/impl/TraversalType2.cpp:9: > /usr/include/squashfuse/common.h:28:10: fatal error: config.h: No such file > or directory >28 | #include "config.h" > | ^~ > compilation terminated. > make[3]: *** [src/libappimage/core/CMakeFiles/core.dir/build.make:135: > src/libappimage/core/CMakeFiles/core.dir/impl/TraversalType2.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/10/27/libappimage_1.0.4-5-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=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: squashfuse Source-Version: 0.5.0-2 Done: Scarlett Moore We believe that the bug you reported is fixed in the latest version of squashfuse, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scarlett Moore (supplier of updated squashfuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Nov 2023 01:42:28 -0700 Source: squashfuse Architecture: source Version: 0.5.0-2 Distribution: unstable Urgency: medium Maintainer: Scarlett Moore Changed-By: Scarlett Moore Closes: 1054713 Changes: squashfuse (0.5.0-2) unstable; urgency=medium . * Fix "needed headers (e.g. config.h) are not shipped" Add back header file. (Closes: #1054713) Checksums-Sha1: 792095b24fa174cd43174c6f6dd332e1c27bf9e2 2149 squashfuse_0.5.0-2.dsc 0e247316554189602393778c65aa4be8e8096710 74620 squashfuse_0.5.0.orig.tar.gz 93295f8afa5ae63b1fb38b0f04d4415a485ee8d4 4944 squashfuse_0.5.0-2.debian.tar.xz d85a16e7afdd5960c0684c825f5877b61106019b 7867 squashfuse_0.5.0-2_amd64.buildinfo Checksums-Sha256: eac938980213ed61265f6e7adff0149c1996afa27ebb3d4f1c7e7907feadf186 2149 squashfuse_0.5.0-2.dsc
Bug#1053410: marked as done (foliate: Failed to load shared library 'libwebkit2gtk-4.0.so.37')
Your message dated Thu, 02 Nov 2023 08:40:40 + with message-id and subject line Bug#1053410: fixed in foliate 2.6.4-1+dfsg5 has caused the Debian Bug report #1053410, regarding foliate: Failed to load shared library 'libwebkit2gtk-4.0.so.37' 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.) -- 1053410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: foliate Version: 2.6.4-1+dfsg3 Severity: grave Justification: renders package unusable Dear Maintainer, ‣ What led up to the situation? Any attempt to run foliate Exact exception is as follow - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ** (com.github.johnfactotum.Foliate:125952): WARNING **: 16:53:39.078: Failed to load shared library 'libwebkit2gtk-4.0.so.37' referenced by the typelib: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gst_transcoder_get_sync_signal_adapter (com.github.johnfactotum.Foliate:125952): Gjs-CRITICAL **: 16:53:39.082: JS ERROR: Error: Unsupported type void, deriving from fundamental void @resource:///com/github/johnfactotum/Foliate/js/main.js:38:20 @/usr/bin/com.github.johnfactotum.Foliate:9:1 (com.github.johnfactotum.Foliate:125952): Gjs-CRITICAL **: 16:53:39.082: Script /usr/bin/com.github.johnfactotum.Foliate threw an exception - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ‣ What exactly did you do (or not do) that was effective (or ineffective)? I've tried to guess if foliate shows libwebkit2gtk-4.0.so.37 as it's dependency. ‣ What was the outcome of this action? I've found that foliate 2.6.4-1+dfsg3 wants gir1.2-webkit2-4.0, which as of version 2.42.1-1 wants libwebkit2gtk-4.0-37 (= 2.42.1-1). ‣ What outcome did you expect instead? Possibility to run foliate. Yours faithfully -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages foliate depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gir1.2-webkit2-4.0 2.42.1-1 ii gjs 1.76.2-4 ii python3 3.11.4-5+b1 Versions of packages foliate recommends: ii gnome-epub-thumbnailer 1.7-3 foliate suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: foliate Source-Version: 2.6.4-1+dfsg5 Done: Jonathan Carter We believe that the bug you reported is fixed in the latest version of foliate, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated foliate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Nov 2023 09:41:12 +0200 Source: foliate Architecture: source Version: 2.6.4-1+dfsg5 Distribution: unstable Urgency: medium Maintainer: Jonathan Carter Changed-By: Jonathan Carter Closes: 1053410 Changes: foliate (2.6.4-1+dfsg5) unstable; urgency=medium . * Upload to unstable (Closes: #1053410) Checksums-Sha1: 1ec6a35ea0a94ad4ac5e4de491a9f276ef5a91e1 1962 foliate_2.6.4-1+dfsg5.dsc f8d8517fe9e4aea9fd06717b6f9943ed79173384 4823156 foliate_2.6.4.orig.tar.gz 8d29e885b09be95e0ad25089c94765505e3f67fa 3880 foliate_2.6.4-1+dfsg5.debian.tar.xz 0e226a4379e4f236145f60fef98cd0324f74069f 10622 foliate_2.6.4-1+dfsg5_source.buildinfo Checksums-Sha256: 168131f03c0596a68e915ab9d2c8ac60648d9a57e51c2d630e342625d8b618ec 1962 foliate_2.6.4-1+dfsg5.dsc 2a3944d8da7f2b3a670cdb8861e433aa19e22132267bdf54369fa92741331e8d 4823156 foliate_2.6.4.orig.tar.gz b804deace8bf81b67007a4aceeabd3d7070f15940fe4ba707b8dbc161a2118e1 3880
Processed: Re: Bug#1055205: chrony: SysV problems after upgrade
Processing control commands: > severity -1 serious Bug #1055205 [chrony] chrony: SysV problems after upgrade Severity set to 'serious' from 'normal' -- 1055205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1054756 marked as pending in node-recast
Processing control commands: > tag -1 pending Bug #1054756 [node-recast] node-recast: FTBFS: lib/options.ts(1,22): error TS2307: Cannot find module 'ast-types/types' or its corresponding type declarations. Added tag(s) pending. -- 1054756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054756: marked as pending in node-recast
Control: tag -1 pending Hello, Bug #1054756 in node-recast reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-recast/-/commit/92312903ab3d7aa4bea55627f41dd124ffb56035 Require node-ast-types >= 0.16.1~ Closes: #1054756 (this message was generated automatically) -- Greetings https://bugs.debian.org/1054756
Processed: reassign 1054756 to node-recast, found 1054756 in 0.21.1-1
Processing commands for cont...@bugs.debian.org: > reassign 1054756 node-recast Bug #1054756 [node-ast-types] node-recast: FTBFS: lib/options.ts(1,22): error TS2307: Cannot find module 'ast-types/types' or its corresponding type declarations. Bug reassigned from package 'node-ast-types' to 'node-recast'. No longer marked as found in versions node-ast-types/0.16.1-1. Ignoring request to alter fixed versions of bug #1054756 to the same values previously set > found 1054756 0.21.1-1 Bug #1054756 [node-recast] node-recast: FTBFS: lib/options.ts(1,22): error TS2307: Cannot find module 'ast-types/types' or its corresponding type declarations. Marked as found in versions node-recast/0.21.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1055043, bug 1055043 is forwarded to https://salsa.debian.org/qa/qa/-/merge_requests/49
Processing commands for cont...@bugs.debian.org: > tags 1055043 + patch Bug #1055043 [qa.debian.org] Debian carnivore: port from Python 2 to 3 Added tag(s) patch. > forwarded 1055043 https://salsa.debian.org/qa/qa/-/merge_requests/49 Bug #1055043 [qa.debian.org] Debian carnivore: port from Python 2 to 3 Set Bug forwarded-to-address to 'https://salsa.debian.org/qa/qa/-/merge_requests/49'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042659: closed by Debian FTP Masters (reply to Félix Sipma ) (Bug#1042659: fixed in restic 0.16.0-1)
On 2023-11-01 Debian Bug Tracking System wrote: [...] > #1042659: restic: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all > arguments converted during string formatting > It has been closed by Debian FTP Masters > (reply to Félix Sipma ). [...] >* New upstream version 0.16.0 (Closes: #1031235, #1042659) [...] In future could we pretty pretty pretty please have a minimum amount of communication? If you sent something like "I am working on this" or "going to work on this in the next days" to the bug report I would not have wasted time and effort on diagnosing the issue, digging out the patch and preparing and testing a NMU. TIA, cu andreas
