Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues in r-cran-popepi which needs an update
Am Mittwoch, 5. Juni 2024, 22:27:09 CEST schrieb Dirk Eddelbuettel: > On 5 June 2024 at 21:55, Paul Gevers wrote: > | Source: survival > | Version: 3.5-8-1 > | Severity: serious > | Control: close -1 3.6-4-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:survival has been trying to migrate for 40 > | days [2]. Hence, I am filing this bug. The version in unstable triggers > | autopkgtest failure in r-cran-popepi. > | > | 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. > > It is beyond my control that package r-cran-popepi descides to run > autopkgtests that than hijack and blackmail this package of mine. > > Maybe the maintainers of r-cran-popepi should look at their package tracker > and eg attempt to update to a _current_ version? That's how things work at > CRAN. A look at the ChangeLog of popEpi confirms that that package just needs an update: News for version 0.4.12 Unit tests No changes in the package itself — fixed a unit test that used the output of survival::summmary.survfit which had improved slightly in 3.6-4. Should we reassign the bug to r-cran-popepi? Johannes > I am really tired of this here in Debian. If the package gets autoremoved, > so be it. The blame will rest with the so-called maintainer team for these > R package that are effectively taking down maintained packages of mine. > > Dirk > > | Paul > | > | [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html > | [2] https://qa.debian.org/excuses.php?package=survival > | > | x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature]
Bug#1072668: ocplib-simplex: autopkgtest failures (missing zarith)
Package: ocplib-simplex Version: 0.5.1-1 Severity: serious Tags: patch Hello, looks like zarith is a test dependency (but not a runtime dependency). 102s autopkgtest [08:43:49]: test upstream-tests: [--- 102s File "dune", line 13, characters 27-33: 102s 13 | (libraries ocplib-simplex zarith)) 102s ^^ 102s Error: Library "zarith" not found. 102s -> required by _build/default/solveEmpty.exe 102s -> required by _build/default/solveEmpty.output 102s -> required by alias runtest in dune:15 103s autopkgtest [08:43:50]: test upstream-tests: ---] 103s upstream-tests FAIL non-zero exit status 1 103s autopkgtest [08:43:50]: test upstream-tests: - - - - - - - - - - results - - - - - - - - - - 103s autopkgtest [08:43:50]: test upstream-tests: - - - - - - - - - - stderr - - - - - - - - - - 103s File "dune", line 13, characters 27-33: 103s 13 | (libraries ocplib-simplex zarith)) 103s ^^ 103s Error: Library "zarith" not found. 103s -> required by _build/default/solveEmpty.exe 103s -> required by _build/default/solveEmpty.output 103s -> required by alias runtest in dune:15 My proposed solution since this look like not useful at runtime, is to add the dependency to tests/control. * Test depend on libzarith-ocaml-dev, dependency used for testing. Thanks for considering the patch. --- ocplib-simplex-0.5.1/debian/tests/control 2024-06-04 06:26:17.0 +0200 +++ ocplib-simplex-0.5.1/debian/tests/control 2024-06-06 08:03:17.0 +0200 @@ -1,2 +1,2 @@ Tests: upstream-tests -Depends: @, ocaml, ocaml-dune, libnum-ocaml-dev, liblogs-ocaml-dev +Depends: @, ocaml, ocaml-dune, libnum-ocaml-dev, liblogs-ocaml-dev, libzarith-ocaml-dev OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072667: picotool:FTBFS:build failed(picotool.1.in diff)
Source: picotool
Version: 1.1.2-1
Severity: serious
Tags: FTBFS, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear picotool Maintainer,
The picotool package build failed on many archs caused by detecting debian/
picotool.1.in diff.The crucial buildd log below:
```
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: /<>/debian/picotool/usr/bin/picotool
make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu'
dh_install -a
dh_installdocs -a
dh_installchangelogs -a
debian/rules execute_before_dh_installman
make[1]: Entering directory '/<>'
# native build
# verify that the contents of debian/picotool.1.in is up-to-date
help2man -n "interact with RP2040 devices or binaries" --no-info
--help-option=help --output=picotool.1
./obj-riscv64-linux-gnu/picotool
{ \
awk 'NR == 1 && /DO NOT MODIFY THIS FILE! It was generated by
help2man/ { print }' picotool.1; \
sed 's/@@DATE@@/April 2024/' debian/picotool.1.in; \
} | diff -u - picotool.1
--- - 2024-06-04 18:21:26.747621999 +
+++ picotool.1 2024-06-04 18:21:26.722708927 +
@@ -10,11 +10,17 @@
.IP
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] [\-\-bus ]
[\-\-address ] [\-f] [\-F]
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] [\-t ]
-picotool load [\-n] [\-N] [\-u] [\-v] [\-x] [\-t ]
[\-o ] [\-\-bus ] [\-\-address ] [\-f] [\-F]
+picotool load [\-n] [\-N] [\-u] [\-v] [\-x] [\-t ]
[\-o ] [\-\-bus ]
+.IP
+[\-\-address ] [\-f] [\-F]
+.IP
picotool save [\-p] [\-\-bus ] [\-\-address ] [\-f] [\-F]
[\-t ]
picotool save \fB\-a\fR [\-\-bus ] [\-\-address ] [\-f]
[\-F] [\-t ]
picotool save \fB\-r\fR [\-\-bus ] [\-\-address
] [\-f] [\-F] [\-t ]
-picotool verify [\-\-bus ] [\-\-address ] [\-f] [\-F]
[\-t ] [\-r ] [\-o ]
+picotool verify [\-\-bus ] [\-\-address ] [\-f] [\-F]
[\-t ] [\-r
+.IP
+] [\-o ]
+.IP
picotool reboot [\-a] [\-u] [\-\-bus ] [\-\-address ] [\-f] [\-F]
picotool version [\-s]
picotool help []
@@ -22,7 +28,8 @@
.TP
info
Display information from the target device(s) or file.
-Without any arguments, this will display basic information for all
connected RP2040 devices in BOOTSEL mode
+Without any arguments, this will display basic information for all
connected RP2040
+devices in BOOTSEL mode
.TP
load
Load the program / memory range stored in a file onto the device.
@@ -49,11 +56,17 @@
.IP
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] [\-\-bus ]
[\-\-address ] [\-f] [\-F]
picotool info [\-b] [\-p] [\-d] [\-l] [\-a] [\-t ]
-picotool load [\-n] [\-N] [\-u] [\-v] [\-x] [\-t ]
[\-o ] [\-\-bus ] [\-\-address ] [\-f] [\-F]
+picotool load [\-n] [\-N] [\-u] [\-v] [\-x] [\-t ]
[\-o ] [\-\-bus ]
+.IP
+[\-\-address ] [\-f] [\-F]
+.IP
picotool save [\-p] [\-\-bus ] [\-\-address ] [\-f] [\-F]
[\-t ]
picotool save \fB\-a\fR [\-\-bus ] [\-\-address ] [\-f]
[\-F] [\-t ]
picotool save \fB\-r\fR [\-\-bus ] [\-\-address
] [\-f] [\-F] [\-t ]
-picotool verify [\-\-bus ] [\-\-address ] [\-f] [\-F]
[\-t ] [\-r ] [\-o ]
+picotool verify [\-\-bus ] [\-\-address ] [\-f] [\-F]
[\-t ] [\-r
+.IP
+] [\-o ]
+.IP
picotool reboot [\-a] [\-u] [\-\-bus ] [\-\-address ] [\-f] [\-F]
picotool version [\-s]
picotool help []
@@ -61,7 +74,8 @@
.TP
info
Display information from the target device(s) or file.
-Without any arguments, this will display basic information for all
connected RP2040 devices in BOOTSEL mode
+Without any arguments, this will display basic information for all
connected RP2040
+devices in BOOTSEL mode
.TP
load
Load the program / memory range stored in a file onto the device.
make[1]: *** [debian/rules:23: execute_before_dh_installman] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned
exit status 2
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=picotool&arch=riscv64&ver=1.1.2-1&stamp=1717525294&raw=0
I believe this issue has been solved in the latest version on
https://salsa.debian.org/debian/picotool, and I have tested it; it works
well. However, the debian/changelog has not been modified. Maybe you should
update the changelog to trigger a rebuild.
Gui-Yue
Best Regards
Bug#1071007: marked as done (sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py)
Your message dated Thu, 06 Jun 2024 01:34:02 + with message-id and subject line Bug#1071007: fixed in sherlock 0.14.4+git20240531.e5ad3c4-1 has caused the Debian Bug report #1071007, regarding sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py 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.) -- 1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sherlock Version: 0.14.3+git20240511.b83f5be-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + pycrc sherlock has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/__init__.py is contained in the packages * pycrc/0.10.0-2 as present in trixie|unstable * sherlock/0.14.3+git20240511.b83f5be-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: sherlock Source-Version: 0.14.4+git20240531.e5ad3c4-1 Done: Josenilson Ferreira da Silva We believe that the bug you reported is fixed in the latest version of sherlock, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josenilson Ferreira da Silva (supplier of updated sherlock package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 01 Jun 2024 01:28:01 -0300 Source: sherlock Architecture: source Version: 0.14.4+git20240531.e5ad3c4-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Josenilson Ferreira da Silva Closes: 1071007 Changes: sherlock (0.14.4+git20240531.e5ad3c4-1) unstable; urgency=medium . * New upstream version 0.14.4+git20240531.e5ad3c4 * debian/patches: Adjusted directory installation package (Closes: #1071007) * debian/rules: Change to package build * debian/sherlock.install: Replaced by patch in pyproject.toml * debian/sherlock.py: Adjusted module path * debian/watch: Updated project version Checksums-Sha1: d3ed7cfdb363fcc1969f9fb8041f69967de45879 2431 sherlock_0.14.4+git20240531.e5ad3c4-1.dsc 4a34b2dc069581e94eb2c0e3dcffc1194ec750ab 186428 sherlock_0.14.4+git20240531.e5ad3c4.orig.tar.xz f93a3ae72d9ceca95006ab8bf37ee871de42a649 5680 sherlock_0.14.4+git20240531.e5ad3c4-1.debian.tar.xz 64c31df1ea7f3ae382daf50ce2eb6216e24a57a6 9403 sherlock_0.14.4+git20240531.e5ad3c4-1_source.buildinfo Checksums-Sha256: 2cdb3e71ef8de50119dab8bf442bddfb24a3a522bb6886e4db785ff6e959b3e6 2431 sherlock_0.14.4+git20240531.e5ad3c4-1.dsc 48145ef1de8e0ce931fca45490e896e4e340e3dd3eb7fb318da2b88b6b115ef7 186428 sherlock_0.14.4+git20240531.e5ad3c4.orig.tar.xz 01b2b5798cf2a9fcde92c9b7e3830a45dc2bd14e79e867de20a45d9822bcd0dd 5680 sherlock_0.14.4+git20240531.e5ad3c4-1.debian.tar.xz 5d0b5931fc6efecf5004745cd831ae8396b3c8dbbe9b64b25059a3fc27d13df5 9403 sherlock_0.14.4+git20240531.e5ad3c4-1_source.buildinfo Files: c9b5fb3f2b77034a4e8c57d9e26dfa34 2431 misc optional sherlock_0.14.4+git20240531.e5ad3c4-1.dsc a3eb84f35b98826cf54b175763d88923 186428 misc optional sherlock_0.14.4+git20240531.e5ad3c4.orig.tar.xz 85df7a11603bb1a890c64e39370dea54 5680 misc optional sherlock_0.14.4+git20240531.e5ad3c4-1.debian.tar.xz 4b7253160252978e9ec6e8d166fc6a98 9403 misc optional sherlock_0.14.4+git20240531.e5ad3c4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqBlNXRF+LQLfMNMNB6n1YjE0Rs0FAmZhDUAACgkQB6n1YjE0 Rs3iWw//ZT7fVnN862vfO4qOz0xda0sM0cSEoNGTze3Yxq6kYG4WPLJlSkB2JZ4Q Mx1JgXHFCXqGAZrwhTjdgflEIfzTXHvJ+NrSj7/xPKUopDac/NPNBaseL
Bug#1071007:
In accordance with the other Package Uploaders, Debian Developer, Francisco Vilmar. I will be closing the bug. Since the problem itself, with Sherlock installing its modules in the root of the packages, has been fixed. Nilson F. Silva
Bug#1072657: rust-subtile: Fails to build
Source: rust-subtile Version: 0.1.7-1 Severity: serious Tags: ftbfs rust-subtile is failing to build. https://buildd.debian.org/status/package.php?p=rust-subtile Build log excerpt --- error[E0433]: failed to resolve: use of undeclared crate or module `profiling` --> src/image/mod.rs:71:3 | 71 | #[profiling::function] | ^ use of undeclared crate or module `profiling` Thank you, Jeremy Bícha
Bug#1050989: marked as done (firmware-carl9170: undeclared file conflict with firmware-linux-free)
Your message dated Wed, 05 Jun 2024 22:34:06 + with message-id and subject line Bug#1050989: fixed in carl9170fw 1.9.9-399-gcd480b9-1.2 has caused the Debian Bug report #1050989, regarding firmware-carl9170: undeclared file conflict with firmware-linux-free 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.) -- 1050989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-carl9170 Version: 1.9.9-399-gcd480b9-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + firmware-linux-free firmware-carl9170 installs /lib/firmware/carl9170-1.fw, which is also currently installed by firmware-linux-free. I see that this is quite intentional as this piece of firmware is being split out from the larger firmware package. On a packaging level, this needs to be addressed with Replaces, Conflicts or diversions. Failing to do so, results in an unpack error from dpkg. I understand that getting the firmware removed from firmware-linux-free may take a bit and you can only then set up the correct Breaks+Replaces. That's fine. Just keep this bug open until that matter is resolved. Helmut --- End Message --- --- Begin Message --- Source: carl9170fw Source-Version: 1.9.9-399-gcd480b9-1.2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of carl9170fw, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated carl9170fw 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, 05 Jun 2024 21:58:15 + Source: carl9170fw Architecture: source Version: 1.9.9-399-gcd480b9-1.2 Distribution: unstable Urgency: medium Maintainer: John Scott Changed-By: Bastian Germann Closes: 1050989 Changes: carl9170fw (1.9.9-399-gcd480b9-1.2) unstable; urgency=medium . * Non-maintainer upload * Move firmware to /usr hierarchy * Conflict on next firmware-linux-free revision (Closes: #1050989) Checksums-Sha1: 908fd9b4a7726469909650cece3f6b67aca10390 1893 carl9170fw_1.9.9-399-gcd480b9-1.2.dsc 08bb9b2cc2e2126ea4704391d49d154ff6576130 6184 carl9170fw_1.9.9-399-gcd480b9-1.2.debian.tar.xz 1720f089b0a2b6ddf4544edda8050a9ba95d5f08 6193 carl9170fw_1.9.9-399-gcd480b9-1.2_source.buildinfo Checksums-Sha256: 251d5a23cc289121a710eff7fc8b67dde8ce09240716e782160436f77c2d8a6c 1893 carl9170fw_1.9.9-399-gcd480b9-1.2.dsc 2aa231fdfca76e537df64ae61522e40cb490fc4466a01b144cfd90d8de98f34c 6184 carl9170fw_1.9.9-399-gcd480b9-1.2.debian.tar.xz eb55ae2eb9f0adcc579f6688e5493639f2cec7bef6ac0127087cef362e0b21d7 6193 carl9170fw_1.9.9-399-gcd480b9-1.2_source.buildinfo Files: c8e2f8d9b900564d7979184219793c45 1893 kernel optional carl9170fw_1.9.9-399-gcd480b9-1.2.dsc db7d20566f5c34a5d5b04f9e46c267ff 6184 kernel optional carl9170fw_1.9.9-399-gcd480b9-1.2.debian.tar.xz ed74ef1b8883c45ddf64e9b56ae3a37b 6193 kernel optional carl9170fw_1.9.9-399-gcd480b9-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZg5AgQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFLgsDADF1BY1gbnWS5bCyIPtAFxuAw8xr30d7z+u uad1pDOEYO0O3C6dj8WmjoAy65/H/1a7fJh6iUArGAvik0tyrs4pAElGYD9i2mvq CQ91c3SoV1SCSC+WhuzSaQc3xNF9dtoIdZ7HChbHqaimAkTNTLLD41fn3YRZupRr 22o9yXYlf/TAUgqRCKT49+aYfBYS1sukvPvf2g1LjQakEkOll+2gR2tMWxiygtjp Pm3umqkTZu/ex3wpAIjFvzj6LRyGt5m3xuKVVaKCPD8G9lW+B4um/FaQoSp8J4g9 tYRftS5iBlHGKFnWdqjuF3bDwyMlspft9sKlkd9Z3aweEMhYoqT5WbYLS1mexEdg 833P56xWRtm8yT1CeBmdhks4I4/SmhiRLiCTG5GKZ1MGdV3rIIpdy7reqWBjVt4W XQ2I+LZX7ZOqEwGg+TK8cM0RKFzajqbA9eZpubUsaxwPyMts4xIV31jSl/nziuV+ HX64d4VFKKKSKMhdbHB2i9fiJA5vNYE= =ZFBD -END PGP SIGNATURE- pgp58Y2ovxH_j.pgp Description: PGP signature --- End Message ---
Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free
I am fixing this with another NMU.
Processed: tagging 988094
Processing commands for cont...@bugs.debian.org: > tags 988094 - pending Bug #988094 [chkservice] reportbug: chkservice fails to control certain services Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 988094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1024642
Processing commands for cont...@bugs.debian.org: > tags 1024642 - pending Bug #1024642 [src:pgcharts] pgcharts: FTBFS: Fatal NAME-CONFLICT: [...] PGCHARTS.SQL:READ-QUERIES, POSTMODERN:READ-QUERIES Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070395: marked as done (tinyproxy: CVE-2023-49606)
Your message dated Wed, 05 Jun 2024 21:47:14 + with message-id and subject line Bug#1070395: fixed in tinyproxy 1.11.1-2.1+deb12u1 has caused the Debian Bug report #1070395, regarding tinyproxy: CVE-2023-49606 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.) -- 1070395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tinyproxy X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for tinyproxy. CVE-2023-40533[0]: | An uninitialized memory use vulnerability exists in Tinyproxy 1.11.1 | while parsing HTTP requests. In certain configurations, a specially | crafted HTTP request can result in disclosure of data allocated on | the heap, which could contain sensitive information. An attacker can | make an unauthenticated HTTP request to trigger this vulnerability. https://talosintelligence.com/vulnerability_reports/TALOS-2023-1902 CVE-2023-49606[1]: | A use-after-free vulnerability exists in the HTTP Connection Headers | parsing in Tinyproxy 1.11.1 and Tinyproxy 1.10.0. A specially | crafted HTTP header can trigger reuse of previously freed memory, | which leads to memory corruption and could lead to remote code | execution. An attacker needs to make an unauthenticated HTTP request | to trigger this vulnerability. https://talosintelligence.com/vulnerability_reports/TALOS-2023-1889 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-40533 https://www.cve.org/CVERecord?id=CVE-2023-40533 [1] https://security-tracker.debian.org/tracker/CVE-2023-49606 https://www.cve.org/CVERecord?id=CVE-2023-49606 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: tinyproxy Source-Version: 1.11.1-2.1+deb12u1 Done: Moritz Mühlenhoff We believe that the bug you reported is fixed in the latest version of tinyproxy, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Mühlenhoff (supplier of updated tinyproxy 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, 22 May 2024 20:05:05 +0200 Source: tinyproxy Architecture: source Version: 1.11.1-2.1+deb12u1 Distribution: bookworm-security Urgency: medium Maintainer: Mike Gabriel Changed-By: Moritz Mühlenhoff Closes: 1070395 Changes: tinyproxy (1.11.1-2.1+deb12u1) bookworm-security; urgency=medium . * CVE-2023-49606 (Closes: #1070395) Checksums-Sha1: 81a3e2e667e84880b81f0d2cdc798bc5ed1e 2057 tinyproxy_1.11.1-2.1+deb12u1.dsc 215fc3011d16506e26c8f34cb51a34e8378ce391 182080 tinyproxy_1.11.1.orig.tar.xz 18f3addbfb1a8365cdc19a946103f99d208a6d77 24292 tinyproxy_1.11.1-2.1+deb12u1.debian.tar.xz 636840598a1153e734dab0c537d876d634d1577f 7340 tinyproxy_1.11.1-2.1+deb12u1_amd64.buildinfo Checksums-Sha256: 8741be861e85204fa49be56fe782c9b5a57c4d5843d1937dc9c75d4c47b902d9 2057 tinyproxy_1.11.1-2.1+deb12u1.dsc d66388448215d0aeb90d0afdd58ed00386fb81abc23ebac9d80e194fceb40f7c 182080 tinyproxy_1.11.1.orig.tar.xz 42f01e0d126e9f80e5adfc04482df018b988c5f30447e267387906f887deb059 24292 tinyproxy_1.11.1-2.1+deb12u1.debian.tar.xz 54afe4708ff8099834784b2efbf5e20b8f38833679f596107486c4ed0d31202f 7340 tinyproxy_1.11.1-2.1+deb12u1_amd64.buildinfo Files: e2afde3d3cdd92716007f8ff61696af4 2057 web optional tinyproxy_1.11.1-2.1+deb12u1.dsc 19cad9f7c3d45f477a7333f2d8babb62 182080 web optional tinyproxy_1.11.1.orig.tar.xz 17fae3203a607c287ea622e6f1cec279 24292 web optional tinyproxy_1.11.1-2.1+deb12u1.debian.tar.xz 9533ed46b794a541a64fda1b99fb45da 7340 web optional tinyproxy_1.11.1-2.1+deb12u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmZONJEACgkQEMKTtsN8 TjbE2xAAsqPiG0UwG80YXN37O2F8p7uqfBlnTL2Z0BKGH/872W/Y0nCe3TNhaD4n wtqJ3i/NQymI7lwj7gBWcfUz6FZSEsk0cc8Dq7Uph3eBJkF7wyrk67V7jXbzxl6P yr83Zyqbm4/R/se
Bug#1053334: marked as done (galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates)
Your message dated Wed, 05 Jun 2024 21:47:42 + with message-id and subject line Bug#1053334: fixed in galera-4 26.4.18-0+deb11u1 has caused the Debian Bug report #1053334, regarding galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates 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.) -- 1053334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: galera-4 Severity: normal Tags: help Forwarded: https://github.com/codership/galera/issues/647 Currently https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/galera-4.html shows that build 2 is failing in unstable. The difference between build 1 and build 2 is visible in https://tests.reproducible-builds.org/debian/logdiffs/unstable/amd64/galera-4_26.4.16-1.diff.gz Looking at the output the issue has something to do with TLS connections timing out. Could perhaps be something as simple as TLS certificates being expired / not valid in future (if the source code has fixed certificates somewhere). --- End Message --- --- Begin Message --- Source: galera-4 Source-Version: 26.4.18-0+deb11u1 Done: Otto Kekäläinen We believe that the bug you reported is fixed in the latest version of galera-4, 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. Otto Kekäläinen (supplier of updated galera-4 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, 22 Apr 2024 21:00:19 -0700 Source: galera-4 Architecture: source Version: 26.4.18-0+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Otto Kekäläinen Closes: 1053183 1053334 Changes: galera-4 (26.4.18-0+deb11u1) bullseye; urgency=medium . * Switch to upstream aware DEP-14 branch structure in gbp.conf * New upstream release 26.4.18. Includes multiple bug fixes, see https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.18.txt * For previous release details see https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.17.txt https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.16.txt https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.15.txt https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.14.txt * New upstream signing key 3D53839A70BC938B08CDD47F45460A518DA84635, verified from 26.4.17 release notes * New upstream release includes multiple Debian build and post-build test failure fixes: - Generate keys and certificates for SSL tests (Closes: #1053334) - Attempt to bind to UDP and skips tests if not available (Related: #1007954) - Fix 'uuid == WSREP_UUID_UNDEFINED' (Related: #970044) - Fix issues reported -Werror when compiling (Related: #970043) - Fix UBSAN issues (Closes: #1053183, Related: #970042) Checksums-Sha1: 1157c4a9226eaea1c3d8f21ad3575bfd203ca289 2409 galera-4_26.4.18-0+deb11u1.dsc 5c9743a3bc837e12516fb6592079ec120a76aa0a 1542330 galera-4_26.4.18.orig.tar.gz 4cf14545179dcfaa106b48908d906a8839689f70 833 galera-4_26.4.18.orig.tar.gz.asc f4197a16791fb2fc911bcfa03951f32eea6e5eca 19092 galera-4_26.4.18-0+deb11u1.debian.tar.xz 75936ee36097bbf06e7deea54ab4d6d03a7756aa 6865 galera-4_26.4.18-0+deb11u1_source.buildinfo Checksums-Sha256: e78d2a3bc22fb43563793e995f13da4010aa4ba096575aff175e976041073d00 2409 galera-4_26.4.18-0+deb11u1.dsc 03bc52dcebc7372c7b77011aa154a01409024d658321624b07ffd465b1585f89 1542330 galera-4_26.4.18.orig.tar.gz 8afce6fb76bf88651681ec198afd3f2e5d7cf0a77c45a838c2a87aef82e2fc3d 833 galera-4_26.4.18.orig.tar.gz.asc 73ffe7b156d65684b99b5d6e09bb121fb5c2d6e129e8c9ae907f7d4aaeda8c94 19092 galera-4_26.4.18-0+deb11u1.debian.tar.xz 5d52005f1aa2301e6b18677ecc4cc1bafa7bfa03c4ce47bb4e296349b8d6a32d 6865 galera-4_26.4.18-0+deb11u1_source.buildinfo Files: 222608895bf4eff2a091095b0309a3bd 2409 databa
Bug#1053334: marked as done (galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates)
Your message dated Wed, 05 Jun 2024 21:47:08 + with message-id and subject line Bug#1053334: fixed in galera-4 26.4.18-0+deb12u1 has caused the Debian Bug report #1053334, regarding galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates 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.) -- 1053334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: galera-4 Severity: normal Tags: help Forwarded: https://github.com/codership/galera/issues/647 Currently https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/galera-4.html shows that build 2 is failing in unstable. The difference between build 1 and build 2 is visible in https://tests.reproducible-builds.org/debian/logdiffs/unstable/amd64/galera-4_26.4.16-1.diff.gz Looking at the output the issue has something to do with TLS connections timing out. Could perhaps be something as simple as TLS certificates being expired / not valid in future (if the source code has fixed certificates somewhere). --- End Message --- --- Begin Message --- Source: galera-4 Source-Version: 26.4.18-0+deb12u1 Done: Otto Kekäläinen We believe that the bug you reported is fixed in the latest version of galera-4, 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. Otto Kekäläinen (supplier of updated galera-4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Apr 2024 21:52:19 -0700 Source: galera-4 Architecture: source Version: 26.4.18-0+deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Otto Kekäläinen Closes: 1053183 1053334 Changes: galera-4 (26.4.18-0+deb12u1) bookworm; urgency=medium . * Switch to upstream aware DEP-14 branch structure in gbp.conf * New upstream release 26.4.18. Includes multiple bug fixes, see https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.18.txt * For previous release details see https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.17.txt https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.16.txt https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.15.txt https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.14.txt * New upstream signing key 3D53839A70BC938B08CDD47F45460A518DA84635, verified from 26.4.17 release notes * New upstream release includes multiple Debian build and post-build test failure fixes: - Generate keys and certificates for SSL tests (Closes: #1053334) - Attempt to bind to UDP and skips tests if not available (Related: #1007954) - Fix 'uuid == WSREP_UUID_UNDEFINED' (Related: #970044) - Fix issues reported -Werror when compiling (Related: #970043) - Fix UBSAN issues (Closes: #1053183, Related: #970042) Checksums-Sha1: db47a0c6da3138fd516604ffd87e7c8e41f18c15 2380 galera-4_26.4.18-0+deb12u1.dsc 5c9743a3bc837e12516fb6592079ec120a76aa0a 1542330 galera-4_26.4.18.orig.tar.gz 4cf14545179dcfaa106b48908d906a8839689f70 833 galera-4_26.4.18.orig.tar.gz.asc dc76ce014f2dfdad276b44d06aab52f55ab0c49b 19084 galera-4_26.4.18-0+deb12u1.debian.tar.xz 7ab145a0724fd07bfc030922039ab0fdec72fedf 6772 galera-4_26.4.18-0+deb12u1_source.buildinfo Checksums-Sha256: 897d1445b47cf14f3971c4bd868da19cff7eb265c6e816bddf708194714cb099 2380 galera-4_26.4.18-0+deb12u1.dsc 03bc52dcebc7372c7b77011aa154a01409024d658321624b07ffd465b1585f89 1542330 galera-4_26.4.18.orig.tar.gz 8afce6fb76bf88651681ec198afd3f2e5d7cf0a77c45a838c2a87aef82e2fc3d 833 galera-4_26.4.18.orig.tar.gz.asc d6fb556c50c2b973de406b7761d254a40ccac64e307efb9db1dc606f81ed5026 19084 galera-4_26.4.18-0+deb12u1.debian.tar.xz 4fde57542acccfb22095f2aed758c652e5817c4ed70aa08e77cd44ffdc5fc07d 6772 galera-4_26.4.18-0+deb12u1_source.buildinfo Files: 5ae5585c88434a39c2125290f5e356ef 2380 databa
Processed: dt-schema is now broken in sid and testing
Processing commands for cont...@bugs.debian.org: > severity 1063562 grave Bug #1063562 [dt-schema] dt-schema: Please add version dependency for jsonschema Severity set to 'grave' from 'normal' > retitle 1063562 dt-schema: broken with python3-jsonschema 4.18+ Bug #1063562 [dt-schema] dt-schema: Please add version dependency for jsonschema Changed Bug title to 'dt-schema: broken with python3-jsonschema 4.18+' from 'dt-schema: Please add version dependency for jsonschema'. > forwarded 1063562 https://github.com/devicetree-org/dt-schema/issues/109 Bug #1063562 [dt-schema] dt-schema: broken with python3-jsonschema 4.18+ Set Bug forwarded-to-address to 'https://github.com/devicetree-org/dt-schema/issues/109'. > tags 1063562 + upstream Bug #1063562 [dt-schema] dt-schema: broken with python3-jsonschema 4.18+ Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060518: marked as done (resource-agents: Please switch Build-Depends to systemd-dev)
Your message dated Wed, 05 Jun 2024 20:48:17 + with message-id and subject line Bug#1060518: fixed in resource-agents 1:4.14.0-1 has caused the Debian Bug report #1060518, regarding resource-agents: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1060518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: resource-agents Version: 1:4.13.0-1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package resource-agents declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: resource-agents Source-Version: 1:4.14.0-1 Done: Valentin Vidic We believe that the bug you reported is fixed in the latest version of resource-agents, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Valentin Vidic (supplier of updated resource-agents 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, 05 Jun 2024 21:18:06 +0200 Source: resource-agents Architecture: source Version: 1:4.14.0-1 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Valentin Vidic Closes: 1060518 1060759 1071980 1072026 Changes: resource-agents (1:4.14.0-1) unstable; urgency=medium . * New upstream version 4.14.0 * debian/patches: refresh for new version * debian/control: update Standards-Version to 4.7.0 * debian/control: update Build-Depends for systemd-dev (Closes: #1060518, #1071980) * debian/control: drop legacy depends on syslog for ldirectord (Closes: #1072026) * debian/tests: install exim4 for MailTo test (Closes: #1060759) * debian/control: update Build-Depends for pkgconf Checksums-Sha1: 65e669d46dd169c9b5dbd40b01c182b07f00598d 2716 resource-agents_4.14.0-1.dsc fa1aa333cc6022cad7fd8cae80a5f700aac2f4bc 875853 resource-agents_4.14.0.orig.tar.gz c33dea04f5c541b1abedd9e82cb0f95e6fab3618 21192 resource-agents_4.14.0-1.debian.tar.xz 364ecfb0e79dba6fe6591d17fc035c596280bd9b 9201 resource-agents_4.14.0-1_source.buildinfo Checksums-Sha256: ecf0078f206b352d31a346efabff764fc8aed0d9afd23d8a99e1d0165470eab7 2716 resource-agents_4.14.0-1.dsc dea2c5fe34748ba702f501edd5aeb7e8b13969f1c4163999a4a28ac25005af95 875853 resource-agents_4.14.0.orig.tar.gz 20bcc5b5ad330e2fb51892886467aec644dfccbf4a82d6c8f03c07e2444ec2ce 21192 resource-agents_4.14.0-1.debian.tar.xz be2e5985af2dc37235738b25d67c1521bf96b1b2fea7efbc11efbcb06d714d60 9201 resource-agents_4.14.0-1_source.buildinfo Files: 1d2ffd8f3e8d7c8b225db1aa831e9708 2716 admin optional resource-agents_4.14.0-1.dsc 0f48ab395633d2a92a31a54b7b0c018d 875853 admin optional resource
Bug#1072617: marked as done (confget: autopkgtest: invokes feature-check in a partly unsupported way)
Your message dated Wed, 05 Jun 2024 20:34:23 + with message-id and subject line Bug#1072617: fixed in confget 5.1.2-2 has caused the Debian Bug report #1072617, regarding confget: autopkgtest: invokes feature-check in a partly unsupported way 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.) -- 1072617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: confget Version: 5.1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-27, confget's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/c/confget/testing/amd64/ 95s autopkgtest [19:08:12]: test feature-check: [--- 95s error: unexpected argument '-q' found 95s 95s tip: to pass '-q' as a value, use '-- -q' 95s 95s Usage: feature-check [OPTIONS] [EXPRESSIONS]... 95s autopkgtest [19:08:12]: test feature-check: ---] --- End Message --- --- Begin Message --- Source: confget Source-Version: 5.1.2-2 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of confget, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated confget 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, 05 Jun 2024 22:55:42 +0300 Source: confget Architecture: source Version: 5.1.2-2 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 1072617 Changes: confget (5.1.2-2) unstable; urgency=medium . * Declare compliance with Policy 4.7.0 with no changes. * autopkgtest: pass -O-qfeatures as a single argument to feature-check. Closes: #1072617 * Use debhelper compat level 14 and let debhelper add some default dependencies automatically. * Include dpkg's default.mk, let it export flag and option variables. * Declare dpkg-build-api v1, drop the implied Rules-Requires-Root: no. * Use dh-package-notes to record ELF package metadata. * gbp.conf: use the debian/master branch again. Checksums-Sha1: f19eb4e4771da8c669685ae33fd8b7ca8c4bddc2 2626 confget_5.1.2-2.dsc 4f9f0a04bed117aa1ea6f9e643e59b19e36b75bc 11300 confget_5.1.2-2.debian.tar.xz Checksums-Sha256: d725fdb6485561958c3f783eb6f6d9d4bf7bf7d946ff7a06e6b25e3502aeafa5 2626 confget_5.1.2-2.dsc c3b6549beb1d5270990dbf913a487c006673c19bd2da98b99280afcf4fa710f6 11300 confget_5.1.2-2.debian.tar.xz Files: de022fe76954b7c5be3ebe9006837937 2626 text optional confget_5.1.2-2.dsc 663bf2760bc6adfb0ea003b4fdc6ea38 11300 text optional confget_5.1.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmZgxRwQHHJvYW1AZGVi aWFuLm9yZwAKCRBlHu+wJSffE1vdD/9DhtU6U/xYvwKP/FpOxLEp1D+l6RkgWiw8 orYv91O7GgWQWhG7xepbQ2TZEcuYF6AOMK1QOAl/fk0thXRSiPzfq0G6VFxhdsBn STsgmS0Dh5nydyZvroFHc1gPRJnxzdGWFQ3raMOphL+BkxzUbbFG6iECq9lOEHON VG6LkBXJGb4xPsolxFJ5H7/3FtPhM36YVZz18OzpSUkXacTNOsrSkDRmpXiRg2HX 9MeIrFXhKDJVOhs9Azuc6yQ12dbG1X54Q6m44OMHSojSCxlM0WhG5erjPgbsNNtL 3jFBdlj9B/jNMBbpMow1Y8YsbnARA8PgQ+XpzSI5OgKrrSAcHlnTLpx6gNxwRFjM ZQOYV3zWFw3k2fRQLoiCbw8cU4/wdxEn9pqCgfuUMjC5dq/NhsPH/vh/phE4heEO su/EAem5tf4bL+UzVnYbc7yz4RY6qO2/oLO8GEf6IBTQnroDL/1yIq2ekOKp2DkA V7EH7LCRIReaMGvavkVo29mJIKHXrUYMclk1fBxE/fpSyTIpUAlP6gt0WzBFThfN qA750HfIt4Ua68II/SqsvEWQlMXuKPfOmCsKI79A4jdOkgVqkxaiTFPfD4o9JddX DtgADspE6AYgtMTGgfVP7aIbvfsr26QzYTu7xsDB6tl6EI8ct9GeLNAkv7Gfm50v roek1PaKxQ== =cpZd -END PGP SIGNATURE- pgpYbOoweTjrR.pgp Description: PGP signature --- End Message ---
Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64
On 5 June 2024 at 21:57, Paul Gevers wrote: | Source: quantlib-swig | Version: 1.33-1 | Severity: serious | Control: close -1 1.34-1 | Tags: sid trixie ftbfs | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The Release Team considers packages that are out-of-sync between testing | and unstable for more than 30 days as having a Release Critical bug in | testing [1]. Your package src:quantlib-swig has been trying to migrate | for 40 days [2]. Hence, I am filing this bug. The version in unstable | failed to build on armel, armhf, i386 and riscv64. | | 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. I have seen this, and I am torn. Maybe it is just best to let quantlib-swig die and keep keep just quantlib (the C++ library). Dirk | Paul | | [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html | [2] https://qa.debian.org/excuses.php?package=quantlib-swig | | x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature] -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues
On 5 June 2024 at 21:55, Paul Gevers wrote: | Source: survival | Version: 3.5-8-1 | Severity: serious | Control: close -1 3.6-4-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:survival has been trying to migrate for 40 | days [2]. Hence, I am filing this bug. The version in unstable triggers | autopkgtest failure in r-cran-popepi. | | 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. It is beyond my control that package r-cran-popepi descides to run autopkgtests that than hijack and blackmail this package of mine. Maybe the maintainers of r-cran-popepi should look at their package tracker and eg attempt to update to a _current_ version? That's how things work at CRAN. I am really tired of this here in Debian. If the package gets autoremoved, so be it. The blame will rest with the so-called maintainer team for these R package that are effectively taking down maintained packages of mine. Dirk | Paul | | [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html | [2] https://qa.debian.org/excuses.php?package=survival | | x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature] -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1072652: context-modules: Migration blocker
Source: context-modules Version: 20240428-4 Severity: grave Justification: renders package unusable Package should not migrate to testing for now. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 6.6.31+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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#1072651: context: Migration blocker
Source: context Version: 2024.04.01.20240428+dfsg-2 Severity: grave Justification: renders package unusable Package should not migrate to testing for now. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 6.6.31+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64
Source: quantlib-swig Version: 1.33-1 Severity: serious Control: close -1 1.34-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:quantlib-swig has been trying to migrate for 40 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel, armhf, i386 and riscv64. 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=quantlib-swig OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64
Processing control commands: > close -1 1.34-1 Bug #1072650 [src:quantlib-swig] src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64 Marked as fixed in versions quantlib-swig/1.34-1. Bug #1072650 [src:quantlib-swig] src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64 Marked Bug as done -- 1072650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues
Source: survival Version: 3.5-8-1 Severity: serious Control: close -1 3.6-4-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:survival has been trying to migrate for 40 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest failure in r-cran-popepi. 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=survival OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues
Processing control commands: > close -1 3.6-4-1 Bug #1072648 [src:survival] src:survival: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions survival/3.6-4-1. Bug #1072648 [src:survival] src:survival: fails to migrate to testing for too long: triggers autopkgtest issues Marked Bug as done -- 1072648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:openttd: fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug
Processing control commands:
> close -1 14.0-1
Bug #1072647 [src:openttd] src:openttd: fails to migrate to testing for too
long: FTBFS on armel and unresolved RC bug
Marked as fixed in versions openttd/14.0-1.
Bug #1072647 [src:openttd] src:openttd: fails to migrate to testing for too
long: FTBFS on armel and unresolved RC bug
Marked Bug as done
> block -1 by 1070208
Bug #1072647 {Done: Paul Gevers } [src:openttd] src:openttd:
fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug
1072647 was not blocked by any bugs.
1072647 was not blocking any bugs.
Added blocking bug(s) of 1072647: 1070208
--
1072647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1072647: src:openttd: fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug
Source: openttd Version: 13.4-1 Severity: serious Control: close -1 14.0-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1070208 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:openttd has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and has an unresolved RC bug: 1070208. 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=openttd OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072646: src:rust-synstructure: fails to migrate to testing for too long
Source: rust-synstructure Version: 0.12.3-2 Severity: serious Control: close -1 0.13.1-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:rust-synstructure has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The version in unstable isn't installable. 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=rust-synstructure OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:rust-synstructure: fails to migrate to testing for too long
Processing control commands: > close -1 0.13.1-1 Bug #1072646 [src:rust-synstructure] src:rust-synstructure: fails to migrate to testing for too long Marked as fixed in versions rust-synstructure/0.13.1-1. Bug #1072646 [src:rust-synstructure] src:rust-synstructure: fails to migrate to testing for too long Marked Bug as done -- 1072646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072110: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? -- not the case
Hi, On 01-06-2024 5:05 p.m., Philippe SWARTVAGHER wrote: As I understand it (but I can be wrong), the current state of glslang and shaderc in unstable is correct; mixing versions from testing and unstable triggers bugs that are now fixed in unstable. Ok. Does that mean that the version of glslang in unstable "Breaks" the version of shaderc in testing more than the version of glslang in testing, but it's shaderc that is broken either way? On that understanding I have manually triggered the combined test and the packages should migrate. Please close this bug if my understanding above was correct. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#890601: firmware-free: Source Package Doesn't Contain Source
Processing control commands: > tag -1 moreinfo Bug #890601 [firmware-linux-free] firmware-linux-free uses prebuilt blobs instead of building from source Added tag(s) moreinfo. -- 890601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#890601: firmware-free: Source Package Doesn't Contain Source
Control: tag -1 moreinfo On Tue, 2024-06-04 at 18:29 +0200, Bastian Germann wrote: > Control: severity -1 serious > > On Fri, 1 Mar 2024 12:48:42 +0100 Salvatore Bonaccorso wrote: > > Would you be fine with those changes s proposed by Bastian, or want to > > have it handled differently? > > > > https://salsa.debian.org/kernel-team/firmware-free/-/merge_requests/4/diffs?commit_id=487a3891528cdf363f97c5ff20f9c6dcb6f49c33 > > As this is a Policy violation and the issue seems to be ignored I am raising > the severity. Please identify precisely which policy requirement is violated. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processed: Re: RM: libtar -- RoQA; Abandoned upstream
Processing control commands: > severity -1 serious Bug #1072586 [src:libtar] RM: libtar -- RoQA; Abandoned upstream Severity set to 'serious' from 'wishlist' -- 1072586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1039883 is forwarded to https://lore.kernel.org/linux-ext4/zkbhursrs96jd...@eldamar.lan/t/#u
Processing commands for cont...@bugs.debian.org: > forwarded 1039883 > https://lore.kernel.org/linux-ext4/zkbhursrs96jd...@eldamar.lan/t/#u Bug #1039883 [src:linux] linux: ext4 corruption with symlinks Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-ext4/zkbhursrs96jd...@eldamar.lan/t/#u'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1039883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072624: marked as done (gsmartcontrol: Does not start)
Your message dated Wed, 05 Jun 2024 18:04:36 + with message-id and subject line Bug#1072624: fixed in gsmartcontrol 1.1.4+git20240531.25f1c62-2 has caused the Debian Bug report #1072624, regarding gsmartcontrol: Does not start 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.) -- 1072624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gsmartcontrol Version: 1.1.4+git20240531.25f1c62-1 Severity: grave Justification: renders package unusable gsmartcontrol-root [app] hz::data_file_find(): Data file "[ui:]gsc_executor_log_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open file â\x80\x9câ\x80\x9d: No such file or directory [app] hz::data_file_find(): Data file "[ui:]gsc_main_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open file â\x80\x9câ\x80\x9d: No such file or directory [app] Cannot create the main window. Exiting. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.32 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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 gsmartcontrol depends on: ii libatkmm-1.6-1v52.28.4-1+b1 ii libc6 2.39-3 ii libcairo2 1.18.0-3+b1 ii libcairomm-1.0-1v5 1.14.5-1 ii libgcc-s1 14.1.0-1 ii libglib2.0-0t64 2.80.2-2 ii libglibmm-2.4-1t64 2.66.7-1 ii libgtk-3-0t64 3.24.42-1 ii libgtkmm-3.0-1t64 3.24.9-1 ii libpangomm-1.4-1v5 2.46.4-1+b1 ii libsigc++-2.0-0v5 2.12.1-2 ii libstdc++6 14.1.0-1 ii libwhereami00.0~git20240120.c5f6b01-1 ii smartmontools 7.4-2 gsmartcontrol recommends no packages. gsmartcontrol suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gsmartcontrol Source-Version: 1.1.4+git20240531.25f1c62-2 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of gsmartcontrol, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated gsmartcontrol 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, 05 Jun 2024 19:52:18 +0200 Source: gsmartcontrol Architecture: source Version: 1.1.4+git20240531.25f1c62-2 Distribution: unstable Urgency: medium Maintainer: Stephen Kitt Changed-By: Stephen Kitt Closes: 1072624 Changes: gsmartcontrol (1.1.4+git20240531.25f1c62-2) unstable; urgency=medium . * Add the package name to file paths, so gsmartcontrol can start on more systems than mine! Closes: #1072624. Checksums-Sha1: 746607e659630fda7a4213325fe61e9034e76b41 2108 gsmartcontrol_1.1.4+git20240531.25f1c62-2.dsc 777f5bdf770456ed8f592b02bb54256a79ad9982 8692 gsmartcontrol_1.1.4+git20240531.25f1c62-2.debian.tar.xz 41ee8f86e7e705c8b961a878075f87ab9f4fc3a9 16136 gsmartcontrol_1.1.4+git20240531.25f1c62-2_source.buildinfo Checksums-Sha256: 45c4fc59850d560e8c71b24746f4ddd9b72a4a79b675e659365016c380f791dd 2108 gsmartcontrol_1.1.4+git20240531.25f1c62-2.dsc b35d4414db4b725a770f5f0c5ab39fac828bcbc894e576eb5d18d20edcd5f841 8692 gsmartcontrol_1.1.4+git20240531.25f1c62-2.debian.tar.xz ce70049ceed29f845454f0f932c2bcb4c246183da4833c7a6035c7751826a622 16136 gsmartcontrol_1.1.4+git20240531.25f1c62-2_source.buildinfo Files: deb3be2096335ae18e88b8c37be16f09 2108 utils optional gsmartcontrol_1.1.4+git20240531.25f1c62-2.dsc b2ff6d2f7d4600b61e2ef55076494ec2 8692 utils optional gsmartcontrol_1.1.4+git20240531.25f1c62-2.debian.tar.xz eac6551ed5253660be98af0af7266937 16136 utils optional gsmartcontrol_1.1.4+git20240531.25f1c62-2_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#1072643: Regression: po4a fails on valid non-utf8 file
(Adding this note to the cloned bug) Note: If you take a look at the FTBFS bugs I reported yesterday: https://people.debian.org/~sanvila/build-logs/202406/?C=M;O=A you can see that several of them are also a consequence of this change in po4a. So, I fully support that this kind of behaviour change deserves at least an entry in NEWS.Debian. Thanks.
Bug#1070853: strace: test failures on 32bit with 64bit time_t
Hi, On Wed, Jun 5, 2024 at 9:38 PM Emanuele Rocca wrote: > > Control: retitle -1 strace: test failures on multiple architectures when > using libunwind > > On 2024-05-11 12:21, Adrian Bunk wrote: > > The tests also fail on i386 > > And on arm64 as well. > > The problem has to do with libunwind as mentioned on the upstream issue, > and it was introduced with: > https://salsa.debian.org/debian/strace/-/commit/711a9970c553b8fb9a5b9eb3a4b80600eb8112c4 > > With the attached patch strace builds fine on arm64 and armhf. Yeah. but before applying the revert, I was trying to update it with 6.9. hmm, here I use libdw-dev instead of libunwind-dev as upstream suggested. I just have uploaded it to mentor because my mentor did not respond to me for a while. Could you help me to try to build it on arm64 or armhf again? I have tested it on qemu-user, but it failed. ``` To access further information about this package, please visit the following URL: https://mentors.debian.net/package/strace/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/strace/strace_6.9-1.dsc Changes since the last upload: strace (6.9-1) experimental; urgency=medium . * Team upload. * New upstream version 6.9. * Drop 03-fix-arm-time_t-ftbfs.patch which upstream has been applied. * Use libdw-dev instead of libunwind-dev. (Closes: #1070853) ``` Thanks for working on this. BR, Bo > > Cheers, > Emanuele
Processed: Re: Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.
Processing commands for cont...@bugs.debian.org: > clone 1072594 -1 Bug #1072594 [src:goobox] goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114. Bug 1072594 cloned as bug 1072643 > reassign -1 po4a Bug #1072643 [src:goobox] goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114. Bug reassigned from package 'src:goobox' to 'po4a'. No longer marked as found in versions goobox/3.6.0-11. Ignoring request to alter fixed versions of bug #1072643 to the same values previously set > retitle -1 Regression: po4a fails on valid non-utf8 file Bug #1072643 [po4a] goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114. Changed Bug title to 'Regression: po4a fails on valid non-utf8 file' from 'goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.'. > tags 1072594 + pending Bug #1072594 [src:goobox] goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072594 1072643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.
clone 1072594 -1 reassign -1 po4a retitle -1 Regression: po4a fails on valid non-utf8 file tags 1072594 + pending thanks Sorry, forgot to actually use the real bug number … -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1072642: curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest)
Package: curl
Version: 8.8.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hello,
I did a local rebuild on sid which failed:
srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35
~300 ~301 ~303 ~304 ~306 ~309 ~310 ~325 ~364 ~400 ~401 ~403 ~406 ~407 ~408 ~409
~410 ~414 ~417 ~560 ~678 ~987 ~988 ~989 ~1112 ~1272 ~1470 ~1561 ~1562 ~1630
~1631 ~1632 ~2034 ~2037 ~2041 ~3000 ~3001 ~3102
Using curl: ../src/curl
[...]
test 0241...[HTTP-IPv6 GET (using ip6-localhost)]
241: protocol FAILED!
There was no content at all in the file log/5/server.input.
Server glitch? Total curl failure? Returned: 7
== Contents of files in the log/5/ dir after test 241
=== Start of file http_ipv6_server.log
16:19:15.385882 Running HTTP IPv6 version on port 36339
16:19:15.385966 Wrote pid 68256 to log/5/server/http_ipv6_server.pid
16:19:15.385990 Wrote port 36339 to log/5/server/http_ipv6_server.port
16:19:16.348256 > Client connect
16:19:16.348285 accept_connection 3 returned 4
16:19:16.348310 accept_connection 3 returned 0
16:19:16.348377 Read 88 bytes
16:19:16.348397 Process 88 bytes request
16:19:16.348427 Got request: GET /verifiedserver HTTP/1.1
16:19:16.348443 Are-we-friendly question received
16:19:16.348471 Wrote request (88 bytes) input to log/5/server.input
16:19:16.348499 Identifying ourselves as friends
16:19:16.348570 Response sent (56 bytes) and written to log/5/server.response
16:19:16.348589 special request received, no persistency
16:19:16.348604 > Client disconnect 0
=== End of file http_ipv6_server.log
=== Start of file http_ipv6_verify.log
* Trying [::1]:36339...
* Connected to ::1 (::1) port 36339
> GET /verifiedserver HTTP/1.1
> Host: [::1]:36339
> User-Agent: curl/8.8.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Length: 17
<
{ [17 bytes data]
* Connection #0 to host ::1 left intact
=== End of file http_ipv6_verify.log
=== Start of file http_ipv6_verify.out
WE ROOLZ: 68256
=== End of file http_ipv6_verify.out
=== Start of file server.cmd
Testnum 241
=== End of file server.cmd
=== Start of file server.response
HTTP/1.1 200 OK
Content-Length: 17
WE ROOLZ: 68256
=== End of file server.response
=== Start of file stderr241
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to ip6-localhost port 36339 after 106 ms: Couldn't
connect to server
=== End of file stderr241
=== Start of file trace241
16:19:16.524170 == Info: Host ip6-localhost:36339 was resolved.
16:19:16.524215 == Info: IPv6: (none)
16:19:16.524217 == Info: IPv4: 31.15.64.248
16:19:16.524231 == Info: Trying 31.15.64.248:36339...
16:19:16.567508 == Info: connect to 31.15.64.248 port 36339 from
192.168.178.20 port 40168 failed: Connection refused
16:19:16.567523 == Info: Failed to connect to ip6-localhost port 36339 after
106 ms: Couldn't connect to server
16:19:16.567663 == Info: Closing connection
=== End of file trace241
[...]
test 0507...[multi interface get with non-existing host name]
lib507 returned 0, when expecting 6
507: exit FAILED
== Contents of files in the log/31/ dir after test 507
=== Start of file server.cmd
Testnum 507
=== End of file server.cmd
=== Start of file stderr507
URL: http://non-existing-host.haxx.se/
Test ended with result 0
=== End of file stderr507
=== Start of file stdout507
HTTP/1.1 200 OK
Date: Wed, 05 Jun 2024 16:19:18 GMT
Server: Apache/2.4.59 (Debian)
Last-Modified: Sun, 14 Feb 2016 17:00:04 GMT
ETag: "0-52bbdd4e2cd00"
Accept-Ranges: bytes
Content-Length: 0
Content-Type: text/html
=== End of file stdout507
[...]
2)
TESTDONE: 1700 tests were considered during 522 seconds.
TESTINFO: 195 tests were skipped due to these restraints:
TESTINFO: "curl lacks debug support" 99 times (159, 356, 358, 359, 363, 412,
413, 437, 438 and 90 more)
TESTINFO: "curl lacks unittest support" 49 times (1300, 1302, 1303, 1304, 1305,
1306, 1308, 1309, 1323 and 40 more)
TESTINFO: "configured as DISABLED" 16 times (323, 594, 836, 882, 938, 1182,
1184, 1209, 1211 and 7 more)
TESTINFO: "failed starting HTTP/2 server" 7 times (1700, 1701, 1702, 2402,
2403, 2404, 2405)
TESTINFO: "curl lacks Schannel support" 6 times (2033, 2070, 2079, 2087, 3023,
3024)
TESTINFO: "no gnutls-serv (with SRP support)" 4 times (320, 321, 322, 324)
TESTINFO: "curl lacks http/3 support" 3 times (2500, 2502, 2503)
TESTINFO: "curl has idn support" 3 times (959, 960, 961)
TESTINFO: "curl lacks TrackMemory support" 2 times (96, 558)
TESTINFO: "curl has ipv6 support" 1 time (1454)
TESTINFO: "curl has threaded-resolver support" 1 time (506)
TESTINFO: "curl has proxy support" 1 time (375)
TES
Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.
clone 12345 -1
reassign -1 po4a
retitle -1 Regression: po4a fails on valid non-utf8 file
tags 12345 + pending
thanks
Hello Santiago,
hello Po4a maintainers,
excuse the TOFU. The build of goobox currently fails on a po file
encoded in ISO-8859-15. The package builds with this file since at
least 2015, with previous version since 2007. Reading the changelog
(NEWS.gz) I cannot detect any depreciation of ISO-8859-15 files. So
this is a regression introduced with po4a 0.72 (or earlier, not all
previous version were shipped for Debian).
The relevant file (attached) does not show any error, i18nspector
reads it fine and recode latin1..utf8 on the file neither prints an
error.
The fix (workaround) for goobox is simple, recode the file to UTF-8.
I'll prepare an upload probably this weekend.
I thus cloned this bug, for goobox to get building again and for po4a
to fix the regression (or clearly depreciating non utf8 locales, with
appropriate NEWS entry etc.). This might affect lots of users of "old"
translations.
Am Wed, Jun 05, 2024 at 02:16:47AM +0200 schrieb Santiago Vila:
> Package: src:goobox
> Version: 3.6.0-11
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
>
> [...]
> debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8
> meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr
> --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> -Dpython.bytecompile=-1
> The Meson build system
> Version: 1.4.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: goobox
> Project version: 3.6.0
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-25)
> 13.2.0")
> C linker for the host machine: cc ld.bfd 2.42
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency libcoverart found: YES 1.0.0
> Configuring config.h using configuration
> Build-time dependency gio-2.0 found: YES 2.80.2
> Program /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas found: YES
> (/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas)
> Configuring org.gnome.Goobox.desktop.in using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program itstool found: YES (/usr/bin/itstool)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Library m found: YES
> Run-time dependency threads found: YES
> Run-time dependency glib-2.0 found: YES 2.80.2
> Run-time dependency gthread-2.0 found: YES 2.80.2
> Run-time dependency gtk+-3.0 found: YES 3.24.42
> Run-time dependency gstreamer-1.0 found: YES 1.24.4
> Run-time dependency libbrasero-media3 found: YES 3.12.3
> Run-time dependency libmusicbrainz5 found: YES 5.1.0
> Run-time dependency libdiscid found: YES 0.6.4
> Compiler for C supports arguments -Wall: YES
> Dependency gio-2.0 found: YES 2.80.2 (cached)
> Program /usr/bin/glib-compile-resources found: YES
> (/usr/bin/glib-compile-resources)
> Dependency glib-2.0 found: YES 2.80.2 (cached)
> Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal)
> Message: configuration summary:
>
>project: goobox 3.6.0
> prefix: /usr
>libcoverart: true
>
> Build targets in project: 95
> NOTICE: Future-deprecated features used:
> * 0.56.0: {'meson.source_root'}
>
> goobox 3.6.0
>
> User defined options
> buildtype : plain
> libdir: lib/x86_64-linux-gnu
> localstatedir : /var
> prefix: /usr
> sysconfdir: /etc
> wrap_mode : nodownload
> python.bytecompile: -1
>
> Found ninja-1.12.1 at /usr/bin/ninja
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> dh_auto_build
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v
> [1/104] /usr/bin/glib-compile-resources ../src/goobox.gresource.xml
> --sourcedir ../src --c-name goo --internal --generate --target
> src/goo-resources.c --dependency-file src/goo-resources.c.d
> [2/104] /usr/bin/glib-compile-resources ../src/goobox.gresource.xml
> --sourcedir ../src --c-name goo --internal --generate --target
> src/goo-resources.h
> [3/104] /usr/bin/msgfmt ../help/ca/ca.po -o help/ca/goobox-ca.gmo
> [4/104] /usr/bin/msgfmt ../help/cs/cs.po -o help/cs/goobox-cs.gmo
> [5/104] /usr/bin/msgfmt ../help/de/de.po -o help/de/goobox-de.gmo
> [6/104] /usr/bin/msgfmt ../help/el/el.po -o help/el/goobox-el.gmo
> [7/104] /usr/bin/msgfmt ../help/es/es.po -o help/es/goobox-es.gmo
> [8/104] /usr/bin/g
Processed: tags
Processing commands for cont...@bugs.debian.org: > tags 1070419 + ftbfs Bug #1070419 [src:gnome-snapshot] src:gnome-snapshot: unsatisfied build dependency in testing: librust-gst-plugin-gtk4-0.11-dev Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060573: nitrokey-app: Please switch Build-Depends to systemd-dev
Hi, I looked into this issue and it seems to me that the build dependency on udev is outdated since handling udev rules was migrated to libnitrokey (see [0]). Therefore I think that an easy fix for this issue is to remove the build dependency on udev. Best regards, Peter [0] https://github.com/Nitrokey/nitrokey-app/commit/8b9480cae1dc5983a1b1e581b2de084cc08e3733
Bug#1067912: nitrokey-app: Update Build-Depends for the time64 library renames
Hi, I looked into this issue and it seems to me that the build dependency on libqt5concurrent5 is not necessary since it is already covered by qtbase5-dev. Thus I think that an easy fix for this issue is to remove libqt5concurrent5 from the build dependencies. Best regards, Peter
Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.
Hello Santiago, Am Wed, Jun 05, 2024 at 02:16:47AM +0200 schrieb Santiago Vila: > During a rebuild of all packages in unstable, your package failed to build: Thanks for notifying me. … > po4a::sgml: Warning: onsgmls produced some errors. This is usually caused by > po4a, which modifies the input and restores it afterwards, causing the input > of onsgmls to be invalid. This is usually safe, but you may wish to verify > the generated document with onsgmls -wno-valid. > po4a::sgml: To see the error message, rerun po4a with this additional > argument: >-o debug=onsgmls > UTF-8 "\xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm > line 353, <$fh> line 114. > (108 entries) Looks like the updated po4a causes this. I'll investigate in the next days. > If this is really a bug in one of the build-depends, please use > reassign and affects, so that this is still visible in the BTS web > page for this package. At first sight I'll assume this, after investigation I'll take care of this. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Processed: notforwarded 1072480
Processing commands for cont...@bugs.debian.org: > notforwarded 1072480 Bug #1072480 [src:condor] condor: hard-coded dependencies on pre-t64 libraries Unset Bug forwarded-to-address > End of message, stopping processing here. Please contact me if you need assistance. -- 1072480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forwarded 1072480 https://github.com/htcondor/htcondor/pull/2432
Processing commands for cont...@bugs.debian.org: > forwarded 1072480 https://github.com/htcondor/htcondor/pull/2432 Bug #1072480 [src:condor] condor: hard-coded dependencies on pre-t64 libraries Set Bug forwarded-to-address to 'https://github.com/htcondor/htcondor/pull/2432'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1072480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1070853
Processing commands for cont...@bugs.debian.org: > tags 1070853 + patch Bug #1070853 [src:strace] strace: test failures on multiple architectures when using libunwind Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070853: strace: test failures on 32bit with 64bit time_t
Control: retitle -1 strace: test failures on multiple architectures when using libunwind On 2024-05-11 12:21, Adrian Bunk wrote: > The tests also fail on i386 And on arm64 as well. The problem has to do with libunwind as mentioned on the upstream issue, and it was introduced with: https://salsa.debian.org/debian/strace/-/commit/711a9970c553b8fb9a5b9eb3a4b80600eb8112c4 With the attached patch strace builds fine on arm64 and armhf. Cheers, Emanuele diff -Nru strace-6.8/debian/changelog strace-6.8/debian/changelog --- strace-6.8/debian/changelog 2024-05-10 06:53:53.0 + +++ strace-6.8/debian/changelog 2024-06-05 13:09:41.0 + @@ -1,3 +1,9 @@ +strace (6.8-1.1) unstable; urgency=medium + + * Only use libunwind on amd64 (Closes: #1070853) + + -- Emanuele Rocca Wed, 05 Jun 2024 13:09:41 + + strace (6.8-1) unstable; urgency=medium * Team upload. diff -Nru strace-6.8/debian/control strace-6.8/debian/control --- strace-6.8/debian/control 2024-05-10 06:53:53.0 + +++ strace-6.8/debian/control 2024-06-05 13:09:41.0 + @@ -2,7 +2,7 @@ Maintainer: Steve McIntyre <93...@debian.org> Section: utils Priority: optional -Build-Depends: libc6-dev (>= 2.2.2) [!alpha !ia64], libc6.1-dev (>= 2.2.2) [alpha ia64], gcc-multilib [amd64 i386 powerpc ppc64 s390 sparc sparc64 x32], debhelper (>= 10.0.0), gawk, libunwind-dev [!alpha !loong64 !m68k !sparc64 !x32], libiberty-dev, libbluetooth-dev +Build-Depends: libc6-dev (>= 2.2.2) [!alpha !ia64], libc6.1-dev (>= 2.2.2) [alpha ia64], gcc-multilib [amd64 i386 powerpc ppc64 s390 sparc sparc64 x32], debhelper (>= 10.0.0), gawk, libunwind-dev [amd64], libiberty-dev, libbluetooth-dev Standards-Version: 4.1.3 Homepage: https://strace.io Vcs-Git: https://salsa.debian.org/debian/strace.git
Processed: Re: Bug#1070853: strace: test failures on 32bit with 64bit time_t
Processing control commands: > retitle -1 strace: test failures on multiple architectures when using > libunwind Bug #1070853 [src:strace] strace: test failures on 32bit Changed Bug title to 'strace: test failures on multiple architectures when using libunwind' from 'strace: test failures on 32bit'. -- 1070853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060772: [Debian-pan-maintainers] Unifying jupyterlab and node-jupyterlab
Le 02/06/2024 à 10:58, Yadd a écrit : On 6/2/24 12:53, Yadd wrote: On 6/2/24 10:38, Yadd wrote: In my last commit, I added also a fix for #1060772: - jupyter-lab uses yarnpkg by default - in Debian build context, this can be overridden using YARN_COMMAND=pkgjs-install-minimal Better hook with "YARN_COMMAND=pkgjs" which uses the adapted pkgjs-* command And this produces the final bundle without Internet access => fixes #1060772 :-D …wow, you rock. Thanks for all that! I had started a WIP branch but was nowhere near completion like yours. I'll do some testing on my side and see if anything needs to be tweaked on the Python side. Thanks! Roland.
Bug#1071704: marked as done (uc-echo: tests fail with scipy 1.12)
Your message dated Wed, 05 Jun 2024 12:50:49 + with message-id and subject line Bug#1071704: fixed in uc-echo 1.12-19 has caused the Debian Bug report #1071704, regarding uc-echo: tests fail with scipy 1.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.) -- 1071704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uc-echo Version: 1.12-18 Severity: normal uc-echo uses a deprecated scipy API that fails with scipy 1.12 24s autopkgtest [20:33:32]: test runtest: [--- 24s Test for sample data 25s Traceback (most recent call last): 25s File "/usr/lib/uc-echo/ErrorCorrection.py", line 19, in 25s from scipy import floor, ceil 25s ImportError: cannot import name 'floor' from 'scipy' (/usr/lib/python3/dist-packages/scipy/__init__.py) This bug will become serious when scipy 1.12 is uploaded to unstable in the near future. --- End Message --- --- Begin Message --- Source: uc-echo Source-Version: 1.12-19 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of uc-echo, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated uc-echo 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, 05 Jun 2024 13:48:16 +0200 Source: uc-echo Architecture: source Version: 1.12-19 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1071704 Changes: uc-echo (1.12-19) unstable; urgency=medium . * Standards-Version: 4.7.0 (routine-update) * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Do not try to import floor / ceil from scipy Closes: #1071704 Checksums-Sha1: 876233715971043427dd9629ff4397ee223d96c8 2113 uc-echo_1.12-19.dsc 5cb4df77e4a4fe10ed353caec867383b502ad4c9 8988 uc-echo_1.12-19.debian.tar.xz c423dba29c213ad0b12d5e5cb66f5f3e828ae9c0 6803 uc-echo_1.12-19_amd64.buildinfo Checksums-Sha256: beeff309b5f3d1e9d0ca7be284d834acc242db189fee65036c74c2b4830ad10b 2113 uc-echo_1.12-19.dsc 362866f86d4a9140d600ad529acea26cd88de21579597a0f4df5e39a6cb66864 8988 uc-echo_1.12-19.debian.tar.xz b20bd321cbd03e9cf525bf3df5dca520a99260701e39a80332f6992ac4b47c33 6803 uc-echo_1.12-19_amd64.buildinfo Files: f081a9e0f5f83ea6ab2e035f5a344419 2113 science optional uc-echo_1.12-19.dsc af92c597af57fda4b90ae840484da265 8988 science optional uc-echo_1.12-19.debian.tar.xz b83696e39fa4c3a51dea33ecbc08295a 6803 science optional uc-echo_1.12-19_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmZgWlURHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEctQ/+KCdFuYPuQzORVZwzEr0dcUNocRIXm1Ry pqUprnxyAog8GoCGyxEOiZOtMFsBtQloU3XFK7Yt9R28h78rt7I5MD2M5hlC9AWq H52bpKesioONtFX1zoyJngBLhXuV+wbDlJQudIW8wjtaQks3rmXlgu60o5ydthyI Eu5nkVIykpBDLQuVav9vhOYdYH/nSxi8MgumWof+Lg2uhrjl2ICQOwCJur4XFU54 ceyfEcQ3/Ojtqna17AUhIZ4zajy6NDAhq6fuZpyLQ7ZdEdkbqArmyWkHA5CPmYkE lFXOObzQ4qdzKKLee9rZp+lG++PB5kF6/f3ehS3V6gr/I+r7cLtRdlnJOiqZJ5HI S9JS5eLX7xrEIaihQD/Nolac8G5OR4ZqT/i1rJMMKy7NHRpW2034baTid890IShx MiGOhy/cgF5jUAuvF+1bJL16IhSe0Nhcmu4qRl4lUHvevWFYJIn5FWXiAfbxYX/3 5H3ywrIkcmMa4E1EsiyLVF3kGQ1DeT/ocsyjBUkjR3gBHbJQOswcoRmb1RaoON/R JvzFne6DWJYzS1nr4iHmt3Uz4ogI1RWFZqEXRk/2Rl4thFjw1FZ8wm07mQakgG0f Gztb1KCr/oJUMmnaDeIElzq2aO0bfkrwJ5KDAQmDhOofQ6yvCXm/0SUKmMeUc5hV vYSImUfiu6U= =J5w1 -END PGP SIGNATURE- pgp7QRB1Nipby.pgp Description: PGP signature --- End Message ---
Bug#1071050: [PATCH] invoke esbuild with --target es2016
The build system does not specify target for esbuild, so I guess the behavior
depends on esbuild verison.
The attached patch invokes `esbuild --target es2016` to fix this.
--- Pseudo-Headers ---
tag -1 + patch
THIS CORRESPONDENCE CONTAINS CONFIDENTIAL INFORMATION OF YAGEO CORPORATION AND
ITS AFFILIATED COMPANIES.
If you have received this e-mail and it was not intended for you, please let us
know, and then delete it.
We thank you for treating our confidential information in a courteous and
professional manner.
Description: Transpile TS files to es2016 instead of esnext
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: bismuth-3.1.4/src/kwinscript/CMakeLists.txt
===
--- bismuth-3.1.4.orig/src/kwinscript/CMakeLists.txt 2024-06-05 14:04:16.519372442 +0200
+++ bismuth-3.1.4/src/kwinscript/CMakeLists.txt 2024-06-05 14:05:08.836981521 +0200
@@ -39,7 +39,7 @@
set(ESBUILD_COMMAND
"esbuild" "--bundle" "${CMAKE_CURRENT_SOURCE_DIR}/index.ts"
"--outfile=${CMAKE_CURRENT_BINARY_DIR}/bismuth/contents/code/index.mjs"
-"--format=esm" "--platform=neutral")
+"--format=esm" "--platform=neutral" "--target=es2016")
if(USE_NPM)
list(PREPEND ESBUILD_COMMAND "npx")
endif()
Processed: Re: Bug#1072521: fakeroot hangs on some commands with faked-sysv using 100% CPU
Processing control commands: > severity -1 important Bug #1072521 [fakeroot] fakeroot hangs on some commands with faked-sysv using 100% CPU Severity set to 'important' from 'critical' -- 1072521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072521: fakeroot hangs on some commands with faked-sysv using 100% CPU
Control: severity -1 important Hi, On Mon, Jun 03, 2024 at 04:31:39PM +0200, Pierre-Elliott Bécue wrote: > Assigning to fakeroot for now, but not sure it's not something for ftp.d.o (a > binNMU) or libc6. > > Today, after an upgrade, I am not able to build packages with sbuild as > it hanks with this process tree: I suggest that the cause may be something else and we are looking at some red herrings at least. In the mean time, the buildd network is reporting successful builds, Jochen Sprickerhof and I cannot readily reproduce the problem. I'm relatively certain that it doesn't affect everyone at this time and hence downgrading the report. > In parallel, one can find a faked-sysv process eating all a CPU resources. > > peb 225847 100 0.0 2440 648 pts/4R+ 16:25 0:02 \_ > /usr/bin/faked-sysv I think I have a plausible explanation for the CPU consumption. > strace: Process 230857 attached > close(200453) = -1 EBADF (Bad file descriptor) > close(200454) = -1 EBADF (Bad file descriptor) > close(200455) = -1 EBADF (Bad file descriptor) ... > close(200511) = -1 EBADF (Bad file descriptor) > ... and so on What we see here is a loop closing increasing file descriptors. I looked into fakeroot's source code and indeed there is such a loop that may correspond to this trace. https://sources.debian.org/src/fakeroot-ng/0.18-4.1/daemon.cpp/?hl=411#L414 | int fd_limit=getdtablesize(); | for( int i=0; i An hypothesis is that a rebuild against the current sid could solve the issue. > I will try that and report back. This no longer feels plausible to me. I have a few other ones: A. Your machine is relatively slow and closing 1e6 fds (for whatever reason) takes it very long time leaving the impression of hanging. B. Your file descriptor limit is even higher than 1e6 and in that case, the close loop really can take very long. C. You captured part of the close loop (with a higher than usual file descriptor limit), but it is not the cause of the hang. Rather it hangs for other reasons after having closed all those file descriptors. > Feel free to reassign. >From what I can tell, fakeroot would be better served with using close_range(2). That would lower the CPU consumption with a higher resource limit and make the real problem more apparent or disappear. Hope this helps, but I am fairly convinced now that this is not a glibc regression. Helmut
Bug#1072634: r-cran-testthat: autopkgtest regression in testing
Source: r-cran-testthat
Version: 3.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-27, r-cran-testthat's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-testthat/testing/amd64/
105s ══ Failed tests
105s ── Error ('test-mock2.R:62:1'): can mock bindings in another
package ───
105s Error in `call_type(call)`: corrupt language object
105s ── Failure ('test-reporter-list.R:54:3'): exercise ListReporter
105s expectation_type(res[[4]]$results[[1]]) (`actual`) not identical
to "failure" (`expected`).
105s
105s `actual`: "warning"
105s `expected`: "failure"
105s ── Failure ('test-reporter-list.R:57:3'): exercise ListReporter
105s df$error (`actual`) not equal to c(FALSE, FALSE, FALSE, FALSE,
TRUE) (`expected`).
105s
105s `actual[2:5]`: FALSE FALSE FALSE FALSE
105s `expected[2:5]`: FALSE FALSE FALSE TRUE
105s ── Failure ('test-reporter-debug.R:51:3'): debug reporter is not
called for successes ──
105s get_frame_from_debug_reporter(2, success_fun) is not NULL
105s
105s `actual` is an environment
105s `expected` is NULL
105s ── Failure ('test-srcrefs.R:19:3'): line numbers captured for
expectations and warnings ──
105s `lines` (`actual`) not equal to c(2, 3) (`expected`).
105s
105s `actual`: 2 2 3
105s `expected`: 2 3
105s ── Failure ('test-srcrefs.R:32:3'): line numbers captured when
called indirectly ──
105s `lines` (`actual`) not equal to 4 (`expected`).
105s
105s `actual`: 4 4
105s `expected`: 4
105s ── Failure ('test-srcrefs.R:42:3'): line numbers captured when
called indirectly ──
105s `lines` (`actual`) not equal to 5 (`expected`).
105s
105s `actual`: 5 5
105s `expected`: 5
105s ── Failure ('test-srcrefs.R:51:3'): line numbers captured inside
a loop
105s `lines` (`actual`) not equal to rep(2, 4) (`expected`).
105s
105s `actual[2:8]`: 2 2 2 2 2 2 2
105s `expected[2:4]`: 2 2 2
105s ── Error ('test-test-that.R:55:5'): infinite recursion is
captured ─
105s
105s Error: evaluation nested too deeply: infinite recursion /
options(expressions=)?
105s Backtrace:
105s ▆
105s 1. ├─testthat::with_reporter(...) at test-test-that.R:54:3
105s 2. │ └─base::tryCatch(...)
105s 3. │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
105s 4. │ └─base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
105s 5. │ └─base (local) doTryCatch(return(expr), name, parentenv, handler)
105s 6. ├─withr::with_options(...) at test-test-that.R:55:5
105s 7. │ └─base::force(code)
105s 8. ├─testthat::test_that(...)
105s 9. │ └─testthat::local_test_context()
105s 10. │ └─testthat::local_reproducible_output(.env = .env)
105s 11. │ └─withr::local_language(lang, .local_envir = .env)
105s 12. │ └─withr:::check_language_envvar("LC_ALL")
105s 13. │ └─base::warning(...)
105s 14. ├─base::.signalSimpleWarning(...)
105s 15. │ └─base::withRestarts(...)
105s 16. │ └─base (local) withOneRestart(expr, restarts[[1L]])
105s 17. │ └─base (local) doWithOneRestart(return(expr), restart)
105s 18. ├─testthat (local) ``(``)
105s 19. │ └─rlang::cnd_entrace(e)
105s 20. │ └─rlang::trace_back(top = top, bottom = bottom)
105s 21. │ └─rlang:::map(calls, call_zap_inline)
105s 22. │ └─base::lapply(.x, .f, ...)
105s 23. │ └─rlang (local) FUN(X[[i]], ...)
105s 24. └─rlang:::call_type_sum(x)
105s 25. ├─rlang::sym(sprintf("<%s>", rlang_type_sum(x)))
105s 26. │ └─rlang::is_symbol(x)
105s 27. ├─base::sprintf("<%s>", rlang_type_sum(x))
105s 28. └─rlang:::rlang_type_sum(x)
105s 29. └─rlang::is_installed("pillar")
105s 30. └─rlang:::detect_installed(info)
105s 31. ├─rlang:::list_c(...)
105s 32. │ └─rlang::inject(c(!!!x))
105s 33. │ └─rlang::enexpr(expr)
105s 34. └─rlang:::pmap(...)
105s 35. └─rlang:::.rlang_purrr_args_recycle(.l)
105s 36. └─rlang:::map_int(args, length)
105s 37. └─rlang:::.rlang_purrr_map_mold(.x, .f, integer(1), ...)
105s 38. └─base::vapply(.x, .f, .mold, ..., USE.NAMES = FALSE)
105s ── Failure ('test-test-that.R:102:3'): no braces required in
testthat 2e ───
105s `test_that("", expect_true(TRUE))` generated warnings:
105s * Changing language has no effect when envvar LC_ALL='C.UTF-8'
105s
105s [ FAIL 10 | WARN 1412 | SKIP 122 | PASS 819 ]
105s Deleting unused snapshots:
105s • R4.0/snapshot-file/version.txt
105s • R4.1/snapshot-file/version.txt
105s • R4.2/snapshot-file/version.txt
105s • R4.3/snapshot-file/version.txt
105s • snapshot-file/a.txt
105s • snapshot-file/foo.csv
105s • snapshot-file/foo.png
105s • snapshot-file/foo.r
105s • snapshot-file/secret.txt
106s Error: Test failures
106s Execution halted
Bug#1072632: r-cran-rsqlite: autopkgtest regression in testing
Source: r-cran-rsqlite
Version: 2.3.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-16, r-cran-rsqlite's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-rsqlite/testing/amd64/
68s ══ Failed tests
68s ── Failure ('test-affinity.R:98:3'): affinity checks for dbFetch()
─
68s `expect_equal(class(dbFetch(rs, 1)$a), real_type)` threw an
unexpected warning.
68s Message: Changing language has no effect when envvar LC_ALL='C.UTF-8'
68s Class: simpleWarning/warning/condition
68s Backtrace:
68s ▆
68s 1. ├─... %>% expect_warning("coercing") at test-affinity.R:98:3
68s 2. ├─testthat::expect_warning(., "coercing")
68s 3. │ └─testthat:::expect_condition_matching(...)
68s 4. │ └─testthat:::quasi_capture(...)
68s 5. │ ├─testthat (local) .capture(...)
68s 6. │ │ └─base::withCallingHandlers(...)
68s 7. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 8. ├─testthat::expect_warning(., "coercing")
68s 9. │ └─testthat:::expect_condition_matching(...)
68s 10. │ └─testthat:::quasi_capture(...)
68s 11. │ ├─testthat (local) .capture(...)
68s 12. │ │ └─base::withCallingHandlers(...)
68s 13. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 14. ├─testthat::expect_warning(., "coercing")
68s 15. │ └─testthat:::expect_condition_matching(...)
68s 16. │ └─testthat:::quasi_capture(...)
68s 17. │ ├─testthat (local) .capture(...)
68s 18. │ │ └─base::withCallingHandlers(...)
68s 19. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 20. ├─testthat::expect_warning(., "coercing")
68s 21. │ └─testthat:::expect_condition_matching(...)
68s 22. │ └─testthat:::quasi_capture(...)
68s 23. │ ├─testthat (local) .capture(...)
68s 24. │ │ └─base::withCallingHandlers(...)
68s 25. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 26. ├─testthat::expect_warning(., "coercing")
68s 27. │ └─testthat:::expect_condition_matching(...)
68s 28. │ └─testthat:::quasi_capture(...)
68s 29. │ ├─testthat (local) .capture(...)
68s 30. │ │ └─base::withCallingHandlers(...)
68s 31. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 32. ├─testthat::expect_warning(., "coercing")
68s 33. │ └─testthat:::expect_condition_matching(...)
68s 34. │ └─testthat:::quasi_capture(...)
68s 35. │ ├─testthat (local) .capture(...)
68s 36. │ │ └─base::withCallingHandlers(...)
68s 37. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 38. ├─testthat::expect_warning(., "coercing")
68s 39. │ └─testthat:::expect_condition_matching(...)
68s 40. │ └─testthat:::quasi_capture(...)
68s 41. │ ├─testthat (local) .capture(...)
68s 42. │ │ └─base::withCallingHandlers(...)
68s 43. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 44. ├─testthat::expect_warning(., "coercing")
68s 45. │ └─testthat:::expect_condition_matching(...)
68s 46. │ └─testthat:::quasi_capture(...)
68s 47. │ ├─testthat (local) .capture(...)
68s 48. │ │ └─base::withCallingHandlers(...)
68s 49. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 50. └─RSQLite (local) check_affinity_fetch("BLOB", class(blob()),
class(blob()))
68s 51. ├─testthat::expect_warning(...) at test-affinity.R:60:3
68s 52. │ └─testthat:::expect_condition_matching(...)
68s 53. │ └─testthat:::quasi_capture(...)
68s 54. │ ├─testthat (local) .capture(...)
68s 55. │ │ └─base::withCallingHandlers(...)
68s 56. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 57. └─testthat::expect_equal(class(dbFetch(rs, 1)$a), real_type)
68s 58. └─testthat:::expect_waldo_equal("equal", act, exp, info, ...,
tolerance = tolerance)
68s 59. └─testthat:::waldo_compare(...)
68s 60. └─testthat:::local_reporter_output()
68s 61. └─reporter$local_user_output(.env)
68s 62. └─testthat::local_reproducible_output(...)
68s 63. └─withr::local_language(lang, .local_envir = .env)
68s 64. └─withr:::check_language_envvar("LC_ALL")
68s
68s [ FAIL 1 | WARN 842 | SKIP 8 | PASS 684 ]
68s Error: Test failures
68s In addition: Warning message:
68s call dbDisconnect() when finished working with a connection
68s Execution halted
Bug#1072631: r-cran-mockr: autopkgtest regression in testing
Source: r-cran-mockr
Version: 0.2.1-1
Severity: serious
Tags: trixie sid
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-03-01, r-cran-mockr's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-mockr/testing/amd64/
76s == Failed tests
76s -- Failure ('test-mock.R:116:3'): empty or no-op mock
--
76s `expect_null(with_mock())` produced unexpected warnings.
76s Expected match: Not (?:mocking|evaluating) anything
76s Actual values:
76s * Not mocking anything. Please use named arguments to specify the
functions you want to mock.
76s * Not evaluating anything. Please use unnamed arguments to specify
expressions you want to evaluate.
76s * Changing language has no effect when envvar LC_ALL='C'
76s
76s [ FAIL 1 | WARN 27 | SKIP 0 | PASS 51 ]
76s Error: Test failures
76s Execution halted
Bug#1072630: r-cran-dplyr: autopkgtest regression in testing
Source: r-cran-dplyr
Version: 1.1.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-16, r-cran-dplyr's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-dplyr/testing/amd64/
157s ══ Failed tests
157s ── Failure ('test-rows.R:161:3'): rows_update() works
──
157s `expect_identical(...)` produced warnings.
157s ── Failure ('test-rows.R:258:3'): rows_patch() works
───
157s `expect_identical(...)` produced warnings.
157s
157s [ FAIL 2 | WARN 5031 | SKIP 329 | PASS 2860 ]
159s Error: Test failures
159s Execution halted
Bug#1072629: r-cran-dials: autopkgtest regression in testing
Source: r-cran-dials
Version: 1.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-15, r-cran-dials' autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-dials/testing/amd64/
53s > library(testthat)
53s > library(dials)
53s Loading required package: scales
54s >
54s > if (requireNamespace("xml2")) {
54s + test_check("dials", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"),
CheckReporter$new(
54s + } else {
54s + test_check("dials")
54s + }
54s Loading required namespace: xml2
54s Error in UseMethod("xml_add_child") :
54s no applicable method for 'xml_add_child' applied to an object of
class "NULL"
54s Calls: test_check ... o_apply -> lapply -> FUN -> ->
54s Execution halted
Bug#1072628: graphlan: autopkgtest regression in testing
Source: graphlan Version: 1.1.3-4 Severity: serious Tags: trixie sid User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-05-22, graphlan's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/g/graphlan/testing/amd64/ 43s Some packages could not be installed. This may mean that you have 43s requested an impossible situation or if you are using the unstable 43s distribution that some required packages have not yet been created 43s or been moved out of Incoming. 43s The following information may help to resolve the situation: 43s 43s The following packages have unmet dependencies: 43s satisfy:command-line : Depends: r-cran-randomfields but it is not installable 43s E: Unable to correct problems, you have held broken packages.
Bug#1072394: marked as done (fcgiwrap: autopkgtest failures: The requested URL returned error: 500)
Your message dated Wed, 05 Jun 2024 11:19:29 +
with message-id
and subject line Bug#1072394: fixed in fcgiwrap 1.1.0-15
has caused the Debian Bug report #1072394,
regarding fcgiwrap: autopkgtest failures: The requested URL returned error: 500
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.)
--
1072394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fcgiwrap
Version: 1.1.0-14
Severity: serious
Hello, since some days, the package starting return autopkgtest errors. I don't
know if this
is related to new git, or new nginx or something else.
https://ci.debian.net/packages/f/fcgiwrap/unstable/amd64/47141721/
34s autopkgtest [14:25:27]: test git-http-backend: [---
34s + cd /tmp/autopkgtest-lxc.9ukljw6a/downtmp/autopkgtest_tmp
34s + export GIT_AUTHOR_NAME=root
34s + export GIT_AUTHOR_EMAIL=root@localhost
34s + export GIT_AUTHOR_DATE=@1234567890 +
34s + export GIT_COMMITTER_NAME=root
34s + export GIT_COMMITTER_EMAIL=root@localhost
34s + export GIT_COMMITTER_DATE=@1234567890 +
34s + git init test1
34s hint: Using 'master' as the name for the initial branch. This default
branch name
34s hint: is subject to change. To configure the initial branch name to use in
all
34s hint: of your new repositories, which will suppress this warning, call:
34s hint:
34s hint: git config --global init.defaultBranch
34s hint:
34s hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
34s hint: 'development'. The just-created branch can be renamed via this
command:
34s hint:
34s hint: git branch -m
34s Initialized empty Git repository in
/tmp/autopkgtest-lxc.9ukljw6a/downtmp/autopkgtest_tmp/test1/.git/
34s + git -C test1 commit --allow-empty -m test
34s [master (root-commit) 0f8c7c0] test
34s + tee /etc/nginx/sites-available/default
34s server {
34slisten 80;
34s
34slocation / {
34sfastcgi_pass unix:/run/fcgiwrap.socket;
34sinclude fastcgi_params;
34sfastcgi_param SCRIPT_FILENAME
/usr/lib/git-core/git-http-backend;
34sfastcgi_param GIT_PROJECT_ROOT
"/tmp/autopkgtest-lxc.9ukljw6a/downtmp/autopkgtest_tmp";
34sfastcgi_param GIT_HTTP_EXPORT_ALL "";
34sfastcgi_param PATH_INFO $uri;
34sfastcgi_param NO_BUFFERING "";
34sfastcgi_buffering off;
34sgzip off;
34s}
34s }
34s + systemctl restart nginx
34s + git clone http://localhost/test1 test2
34s Cloning into 'test2'...
34s fatal: unable to access 'http://localhost/test1/': The requested URL
returned error: 500
35s autopkgtest [14:25:28]: test git-http-backend: ---]
Please have a look,
thanks
Gianfranco
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: fcgiwrap
Source-Version: 1.1.0-15
Done: Jordi Mallach
We believe that the bug you reported is fixed in the latest version of
fcgiwrap, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jordi Mallach (supplier of updated fcgiwrap 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, 05 Jun 2024 12:56:01 +0200
Source: fcgiwrap
Architecture: source
Version: 1.1.0-15
Distribution: unstable
Urgency: medium
Maintainer: Debian fcgiwrap Maintainers
Changed-By: Jordi Mallach
Closes: 1072394
Changes:
fcgiwrap (1.1.0-15) unstable; urgency=medium
.
[ Mitchell Dzurick ]
* d/t/git-http-backend: make www-data own $AUTOPKGTEST_TMP/test1/.git
git introduced more aggressive security checking, so the dep8 test needs
to explicitly change ownership of the new git directory.
(LP: #2067942, Closes: #1072394)
.
[ Jordi Mallach ]
* Update Standards-Version to 4.7.0, with no changes needed.
* Update copyright years.
* Replace pkg-config with pkgconf in Build-Depends.
* Remove obsolete dependency on lsb-base.
* Add a Documentation key to systemd service file pointing to manpage.
Bug#1072624: gsmartcontrol: Does not start
Package: gsmartcontrol Version: 1.1.4+git20240531.25f1c62-1 Severity: grave Justification: renders package unusable gsmartcontrol-root [app] hz::data_file_find(): Data file "[ui:]gsc_executor_log_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open file â\x80\x9câ\x80\x9d: No such file or directory [app] hz::data_file_find(): Data file "[ui:]gsc_main_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open file â\x80\x9câ\x80\x9d: No such file or directory [app] Cannot create the main window. Exiting. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.32 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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 gsmartcontrol depends on: ii libatkmm-1.6-1v52.28.4-1+b1 ii libc6 2.39-3 ii libcairo2 1.18.0-3+b1 ii libcairomm-1.0-1v5 1.14.5-1 ii libgcc-s1 14.1.0-1 ii libglib2.0-0t64 2.80.2-2 ii libglibmm-2.4-1t64 2.66.7-1 ii libgtk-3-0t64 3.24.42-1 ii libgtkmm-3.0-1t64 3.24.9-1 ii libpangomm-1.4-1v5 2.46.4-1+b1 ii libsigc++-2.0-0v5 2.12.1-2 ii libstdc++6 14.1.0-1 ii libwhereami00.0~git20240120.c5f6b01-1 ii smartmontools 7.4-2 gsmartcontrol recommends no packages. gsmartcontrol suggests no packages. -- no debconf information
Bug#1069507: marked as done (dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in bit-field 'verify_error_if_negative_size__')
Your message dated Wed, 05 Jun 2024 08:34:30 +
with message-id
and subject line Bug#1069507: fixed in dc3dd 7.3.1-3
has caused the Debian Bug report #1069507,
regarding dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in
bit-field 'verify_error_if_negative_size__'
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.)
--
1069507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dc3dd
Version: 7.3.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi,
During a rebuild of all packages in sid, your package failed to build
on armhf.
Relevant part (hopefully):
> gcc -I. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
> -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 -c -o localcharset.o localcharset.c
> In file included from getdate.y:40:
> verify.h:132:30: error: negative width in bit-field
> 'verify_error_if_negative_size__'
> 132 | (struct { unsigned int verify_error_if_negative_size__: (R) ? 1
> : -1; }))
> | ^~~
> verify.h:138:61: note: in expansion of macro 'verify_true'
> 138 | # define verify(R) extern int (* verify_function__ (void))
> [verify_true (R)]
> |
> ^~~
> getdate.y:116:1: note: in expansion of macro 'verify'
> 116 | verify (LONG_MIN <= TYPE_MINIMUM (time_t) && TYPE_MAXIMUM (time_t) <=
> LONG_MAX);
> | ^~
> make[4]: *** [Makefile:1471: getdate.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/dc3dd_7.3.1-2_unstable-armhf.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: dc3dd
Source-Version: 7.3.1-3
Done: Arnaud Rebillout
We believe that the bug you reported is fixed in the latest version of
dc3dd, 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.
Arnaud Rebillout (supplier of updated dc3dd 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, 05 Jun 2024 14:42:59 +0700
Source: dc3dd
Architecture: source
Version: 7.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Arnaud Rebillout
Closes: 1069507
Changes:
dc3dd (7.3.1-3) unstable; urgency=medium
.
* Update upstream URL
* Fix FTBFS on armhf/armel (Closes: #1069507)
* Minor adjustments in tests
* Bump Std-Ver to 4.7.0
Checksums-Sha1:
fb5eaa1c01ba9c4c20cd803abfac77f02b8a8f52 1945 dc3dd_7.3.1-3.dsc
a039248207a44f4af8c21dccf0ab51bbbab117fd 13784 dc3dd_7.3.1-3.debian.tar.xz
4abe69d572812a0bcfa9383ba903403549c332a2 6021 dc3dd_7.3.1-3_source.buildinfo
Checksums-Sha256:
b512b50cea3f66599224ac8b545859abee800ff9d49e0b9aa63d56f237b0a704 1945
dc3dd_7.3.1-3.dsc
6f9a9b4c8887593752b28bb78f88cecfb5250a301f457dd61429081570fddaba 13784
dc3dd_7.3.1-3.debian.tar.xz
ac6f201fc86be105e413b6e6fb22dd546bb5bb234ea040268ff56f2ebb9c64cb 6021
dc3dd_7.3.1-3_source.buildinfo
Files:
770383d99bcde14e9d142c14edd434bc 1945 utils option
Bug#1069507: marked as pending in dc3dd
Control: tag -1 pending Hello, Bug #1069507 in dc3dd 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/pkg-security-team/dc3dd/-/commit/c848b6a12af7414b95be2de78a70c5e900e23218 Fix FTBFS on armhf/armel (Closes: #1069507) This new FTBFS is due to the fact that the size of the time_t type went from 32-bit to 64-bit for armel and armhf architectures, cf [1]. It seems that getdate.y didn't support the situation at the time it was bundled into the dc3dd source code, but after digging a bit into the gnulib git history, we find that it was fixed back in 2009, cf [2]. Without being familiar with the code of dc3dd, it's hard to be 100% sure that it's the exact right fix, and it's not breaking anything, so I opened a bug upstream to see if I can get confirmation that it's indeed the right fix to apply, cf [3]. [1]: https://wiki.debian.org/ReleaseGoals/64bit-time [2]: https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=a68c9ab3cfc8ac7cf2a709b0c1aa93229f8635e6 [3]: https://sourceforge.net/p/dc3dd/bugs/23/ (this message was generated automatically) -- Greetings https://bugs.debian.org/1069507
Processed: Bug#1069507 marked as pending in dc3dd
Processing control commands: > tag -1 pending Bug #1069507 [src:dc3dd] dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in bit-field 'verify_error_if_negative_size__' Added tag(s) pending. -- 1069507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: clone the -O-qfeatures bug back into confget's pool
Processing commands for cont...@bugs.debian.org: > clone 1071683 -1 Bug #1071683 [feature-check] feature-check: Rust: -O fails on values starting with dashes Bug 1071683 cloned as bug 1072617 > reassign -1 confget Bug #1072617 [feature-check] feature-check: Rust: -O fails on values starting with dashes Bug reassigned from package 'feature-check' to 'confget'. No longer marked as found in versions feature-check/2.1.0-1. Ignoring request to alter fixed versions of bug #1072617 to the same values previously set > retitle -1 confget: autopkgtest: invokes feature-check in a partly > unsupported way Bug #1072617 [confget] feature-check: Rust: -O fails on values starting with dashes Changed Bug title to 'confget: autopkgtest: invokes feature-check in a partly unsupported way' from 'feature-check: Rust: -O fails on values starting with dashes'. > found -1 2.1.1-1 Bug #1072617 [confget] confget: autopkgtest: invokes feature-check in a partly unsupported way Marked as found in versions confget/2.1.1-1. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 1071683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071683 1072617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065387: marked as done (budgie-session: Please switch Build-Depends to systemd-dev)
Your message dated Wed, 05 Jun 2024 07:19:01 + with message-id and subject line Bug#1065387: fixed in budgie-session 0.9.1-3 has caused the Debian Bug report #1065387, regarding budgie-session: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: budgie-session Version: 0.9.1-1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package budgie-session declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: budgie-session Source-Version: 0.9.1-3 Done: David Mohammed We believe that the bug you reported is fixed in the latest version of budgie-session, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Mohammed (supplier of updated budgie-session package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 05 Jun 2024 07:52:43 +0100 Source: budgie-session Built-For-Profiles: noudeb Architecture: source Version: 0.9.1-3 Distribution: unstable Urgency: medium Maintainer: David Mohammed Changed-By: David Mohammed Closes: 1065387 Changes: budgie-session (0.9.1-3) unstable; urgency=medium . * Packaging Change - add B/D on systemd-dev (Closes: #1065387) Checksums-Sha1: 43a66b945d47694b817eed6bdb175ff58f32a208 2568 budgie-session_0.9.1-3.dsc fc065649a1962bbb2137ce42f273f43aeabcb3dc 10940 budgie-session_0.9.1-3.debian.tar.xz eded7dd88737d0dac439a240cf46e321d2cac58c 18266 budgie-session_0.9.1-3_source.buildinfo Checksums-Sha256: 7ae102b747d93e88d49cfcb9d7c2de2b4b926e616dee8848b41aeae953bc4ecf 2568 budgie-session_0.9.1-3.dsc 16020116837245d3bf5fd1481fa2653907b4c2c8050be761c77291424912c527 10940 budgie-session_0.9.1-3.debian.tar.xz 3398617c1e2724cc9f376e23a267c557e16699e45222543a57a5463e16c0ecc0 18266 budgie-session_0.9.1-3_source.buildinfo Files: 9cb9084b2acbcf3762d84f82c6462cc7 2568 misc optional budgie-session_0.9.1-3.dsc 4901ec5cc8e7869b7cce063a2cb34cab 10940 misc optional budgie-session_0.9.1-3.debian.tar.xz 3ee6e62b7bc49e929e1dfb41a0e20651 18266 misc optional budgie-session_0.9.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHh+wAXyZiorixJimwuqoomrcWe4FAmZgC9YACgkQwuqoomrc We7fYw//cpTYrykRGLVb+qWiwrtCA8Mlxd7CE99J0bMgdKc8kzZjNg9RIkjzmH3K 2+pS6TZvG3B7z9duG1LBTJds6fMKOctA2rx7GDybLNejWmgsJKtiMt1q5ROn5mbw TvXYK3Z5DtmDwikSWDf9C1zQF139/Dk+fbNgX8cMF1nARaboumVvMZyry55lf1cg uuTsZBBoJhxOF3/idX3NrbmqwWYiMPLafdVyWycuU/EKuz59OH++yrU29ZGiWDA8 MifcXPHOmj9TzzgXLiUvpMf5N42v7eJvlxDQkSjDDRejOtDGR1s1y8Zxd3E1UZNx +5iGf1i5lorRT+PRiz5adIa7dmNRBa73a5mosfocdkUBmeEabS/m3g96Sy
