Bug#1011409: src:victoriametrics: fails to migrate to testing for too long: FTBFS on armel
Source: victoriametrics Version: 1.74.0+ds1-1 Severity: serious Control: close -1 1.75.0+ds1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1010544 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:victoriametrics has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build from source, which has been reported in bug #1010544. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=victoriametrics OpenPGP_signature Description: OpenPGP digital signature
Processed: src:victoriametrics: fails to migrate to testing for too long: FTBFS on armel
Processing control commands:
> close -1 1.75.0+ds1-1
Bug #1011409 [src:victoriametrics] src:victoriametrics: fails to migrate to
testing for too long: FTBFS on armel
Marked as fixed in versions victoriametrics/1.75.0+ds1-1.
Bug #1011409 [src:victoriametrics] src:victoriametrics: fails to migrate to
testing for too long: FTBFS on armel
Marked Bug as done
> block -1 by 1010544
Bug #1011409 {Done: Paul Gevers } [src:victoriametrics]
src:victoriametrics: fails to migrate to testing for too long: FTBFS on armel
1011409 was not blocked by any bugs.
1011409 was not blocking any bugs.
Added blocking bug(s) of 1011409: 1010544
--
1011409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries
Processing control commands: > clone -1 -2 Bug #1011407 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries Bug 1011407 cloned as bug 1011408 > close -1 1.22.1-3 Bug #1011407 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries Marked as fixed in versions v4l-utils/1.22.1-3. Bug #1011407 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries Marked Bug as done > notfound -2 1.22.1-2 Bug #1011408 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries No longer marked as found in versions v4l-utils/1.22.1-2. > found -2 1.22.1-3 Bug #1011408 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries Marked as found in versions v4l-utils/1.22.1-3. > tags -2 ftbfs Bug #1011408 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries Added tag(s) ftbfs. > retitle -2 v4l-utils FTBFS on armel and armhf: missing files Bug #1011408 [src:v4l-utils] src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries Changed Bug title to 'v4l-utils FTBFS on armel and armhf: missing files' from 'src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries'. -- 1011407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011407 1011408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011407: src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries
Source: v4l-utils Version: 1.22.1-2 Severity: serious Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: clone -1 -2 Control: close -1 1.22.1-3 Control: notfound -2 1.22.1-2 Control: found -2 1.22.1-3 Control: tags -2 ftbfs Control: retitle -2 v4l-utils FTBFS on armel and armhf: missing files Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:v4l-utils has been trying to migrate for 61 days [2]. Hence, I am filing this bug [nr -1]. Your package fails to build from source on armel and armhf where it built successfully in the past, for which I cloned bug -1 as -2. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=v4l-utils FTBFS log ends like this: dh_install: warning: qvidcap missing files: usr/bin/qvidcap dh_install: warning: Cannot find (any matches for) "usr/share/applications/qvidcap.desktop" (tried in ., debian/tmp) dh_install: warning: qvidcap missing files: usr/share/applications/qvidcap.desktop dh_install: warning: Cannot find (any matches for) "usr/share/icons/hicolor/*/apps/qvidcap.*" (tried in ., debian/tmp) dh_install: warning: qvidcap missing files: usr/share/icons/hicolor/*/apps/qvidcap.* dh_install: warning: Cannot find (any matches for) "usr/share/man/man1/qvidcap.1" (tried in ., debian/tmp) dh_install: warning: qvidcap missing files: usr/share/man/man1/qvidcap.1 dh_install: error: missing files, aborting make[1]: *** [debian/rules:33: override_dh_install] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:11: binary-arch] Error 2 OpenPGP_signature Description: OpenPGP digital signature
Bug#999053: cl-irc: diff for NMU version 1:0.9.2+dfsg1-2.1
Control: tags 999053 + patch
Control: tags 999053 + pending
Dear maintainer,
I've prepared an NMU for cl-irc (versioned as 1:0.9.2+dfsg1-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru cl-irc-0.9.2+dfsg1/debian/changelog cl-irc-0.9.2+dfsg1/debian/changelog
--- cl-irc-0.9.2+dfsg1/debian/changelog 2018-04-07 05:57:16.0 -0300
+++ cl-irc-0.9.2+dfsg1/debian/changelog 2022-05-12 14:12:47.0 -0300
@@ -1,3 +1,10 @@
+cl-irc (1:0.9.2+dfsg1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules: Add build-{arch,indep} (Closes: #999053).
+
+ -- Marcos Talau Thu, 12 May 2022 14:12:47 -0300
+
cl-irc (1:0.9.2+dfsg1-2) unstable; urgency=medium
* Team upload.
diff -Nru cl-irc-0.9.2+dfsg1/debian/rules cl-irc-0.9.2+dfsg1/debian/rules
--- cl-irc-0.9.2+dfsg1/debian/rules 2018-04-07 05:48:44.0 -0300
+++ cl-irc-0.9.2+dfsg1/debian/rules 2022-05-12 14:12:47.0 -0300
@@ -73,5 +73,7 @@
dh_builddeb
binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure
Processed: cl-irc: diff for NMU version 1:0.9.2+dfsg1-2.1
Processing control commands: > tags 999053 + patch Bug #999053 [src:cl-irc] cl-irc: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999053 + pending Bug #999053 [src:cl-irc] cl-irc: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1010998 is important
Processing commands for cont...@bugs.debian.org: > # does not affect Debian yet > severity 1010998 important Bug #1010998 [simh] simh: Upstream license change conflicts with DFSG Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1010998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 1010998 in 3.8.12-1, found 1010998 in 3.12-1
Processing commands for cont...@bugs.debian.org: > notfound 1010998 3.8.12-1 Bug #1010998 [simh] simh: Upstream license change conflicts with DFSG There is no source info for the package 'simh' at version '3.8.12-1' with architecture '' Unable to make a source version for version '3.8.12-1' No longer marked as found in versions 3.8.12-1. > found 1010998 3.12-1 Bug #1010998 [simh] simh: Upstream license change conflicts with DFSG There is no source info for the package 'simh' at version '3.12-1' with architecture '' Unable to make a source version for version '3.12-1' Marked as found in versions 3.12-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974197: marked as done (rust-hdrhistogram: unsatisfiable build-dependency)
Your message dated Sun, 22 May 2022 01:33:52 + with message-id and subject line Bug#974197: fixed in rust-hdrhistogram 7.5.0-1 has caused the Debian Bug report #974197, regarding rust-hdrhistogram: unsatisfiable build-dependency 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.) -- 974197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-hdrhistogram Version: 6.3.4-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, rust-hdrhistogram build-depends on librust-base64-0.11+default-dev | librust-base64-0.10+default-dev. However, neither of these exists in sid or in the NEW queue. -Ralf. --- End Message --- --- Begin Message --- Source: rust-hdrhistogram Source-Version: 7.5.0-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-hdrhistogram, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-hdrhistogram package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 May 2022 00:45:47 + Source: rust-hdrhistogram Architecture: source Version: 7.5.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 974197 Changes: rust-hdrhistogram (7.5.0-1) unstable; urgency=medium . * Team upload. * Package hdrhistogram 7.5.0 from crates.io using debcargo 2.5.0 (Closes: 974197) * Eliminate dev-dependencies on ieee754 and rug so the rest of the testsuite can run. * Fix tests when run with no-default-features. Checksums-Sha1: 46d3b500cbe733af0734e77ae804cb85907ce969 3202 rust-hdrhistogram_7.5.0-1.dsc 408e76b65c7a1c93d6c29ca6ceedf1f09ac75d35 316110 rust-hdrhistogram_7.5.0.orig.tar.gz e75b92ada2adf98c6de04ece2bd4f666d597b5e5 4836 rust-hdrhistogram_7.5.0-1.debian.tar.xz 7206a48464b382b81690f703e38054507f0d5260 7808 rust-hdrhistogram_7.5.0-1_source.buildinfo Checksums-Sha256: 9469af543c14c100a74666d5c37611792542f141c386ae9c982659c58a5d2459 3202 rust-hdrhistogram_7.5.0-1.dsc 31672b7011be2c4f7456c4ddbcb40e7e9a4a9fad8efe49a6ebaf5f307d0109c0 316110 rust-hdrhistogram_7.5.0.orig.tar.gz 8cca378e47f890363a3859142d14cb2ba51783dfea916b549966b79db39b47c8 4836 rust-hdrhistogram_7.5.0-1.debian.tar.xz 68694b2401a9dd1259f0415b72e03fd8f533dceb14209c100058ecb682f6c0d8 7808 rust-hdrhistogram_7.5.0-1_source.buildinfo Files: b0e63df8d1713d86ed6f1827bcbb11b0 3202 rust optional rust-hdrhistogram_7.5.0-1.dsc 635b2a48d8d0b5d15004462bfc0857dd 316110 rust optional rust-hdrhistogram_7.5.0.orig.tar.gz 5d65e2a5798935d45e17e8fbb936aece 4836 rust optional rust-hdrhistogram_7.5.0-1.debian.tar.xz 80e8a3ea932bb2cb26c8537bb82b4d00 7808 rust optional rust-hdrhistogram_7.5.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmKJjH4UHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsDBA//RE5IPssuAHJrmmBuXxapF9mJPSjz vTCgYc7PXj4scfb7x1OtcTihWDDXnbBiSmVQnC+3Odfes1uACn/TmuvYgMCYWALM A3TbbDT/RLnDqcaropFMr3bS5TcmIGmYZfD4ZBFbxSwb42u25aqCq7Ug8ptlgWlp oitVGBIv6H+CkIKd6Hsqo6y/aOkJzVcxRGBqcl3ztdVK2DlmWnSFct/kEua4ig8H tWpILL6ZD52AVWXqaLyhbAldcIIZuxchQKcLAgvd74WNkwwTLSTvYeoFqpkalGJH ix7Acac0dLptNBGHII088teqqLXcLwVYUDWKdBg/UD/vtJDvrW2VLI4N4qUIqLI3 vaf4ZL5KdqGbBPgESeX/MzzMqMWUfeweG//5BsxDMaz9WOPJQ+MMTeW3z206vN1C t6SsTLeiyQs3IipQA5UnE//CmVvqKIpLDOzR3x/5p1MV8PX/Uigv0MeynPU9lEj6 8dewEzL9CAgk0Yf0S5t9u6v/+tXMlPCEUj7xdLVQvtHxjx/pGmTYN/AZ7avW1TBS RZvKZD7NT2qlsOL4PLE97eNbz7g4sS4G1BfX25o1b64FgYvEg4xVnvm5CWxZcxEx 4peU6LuccIbdqHMcigSs0hqfw+rtJ72pqNhWybV1gIvIBuHdG/DdPbkwyHhx0G5r JLe5ZYOMAi6/FD8= =YE95 -END PGP SIGNATURE End Message ---
Bug#1011386: marked as done (openblas FTBFS due to *combssq deprecated from lapack)
Your message dated Sat, 21 May 2022 21:04:05 + with message-id and subject line Bug#1011386: fixed in openblas 0.3.20+ds-2 has caused the Debian Bug report #1011386, regarding openblas FTBFS due to *combssq deprecated from lapack 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.) -- 1011386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openblas Version: 0.3.20+ds-1 Severity: serious Justification: FTBFS According to lapack 3.10.1 release note and upstream pull request 570, xCOMBSSQ has been deprecated. Openblas upstream source has not yet adapted to this change. And thus FTBFS due to missing the following two symbols (fortran ABI): scombssq_ dcombssq_ I think this should be straightforward to fix as long as we remove the two symbols from openblas symbol check. --- End Message --- --- Begin Message --- Source: openblas Source-Version: 0.3.20+ds-2 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of openblas, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated openblas 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, 21 May 2022 16:25:13 -0400 Source: openblas Architecture: source Version: 0.3.20+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Mo Zhou Closes: 1011386 Changes: openblas (0.3.20+ds-2) unstable; urgency=medium . * Remove deprecated xCOMBSSQ lapack routines. (Closes: #1011386) * Remove bin:libjulia-openblas64, which is no longer needed. Exporting libopenblas64_.so with SYMBOLSUFFIX=64_ in Julia private library as an external dependency introduces complication in Julia package compiling process. We currently do not have proposal to put libopenblas64_.so (with symbol suffix) in the public library, because that will eventually lead to NINE variants to build for amd64: (1) LP64 (32-bit indexing), three threading models, default; (2) ILP64 (64-bit indexing), three threading models, no symbol suffix; (3) ILP64 (64-bit indexing), three threading models, symbols suffix 64_. Currently we only provide the (1) and (2) combinations, because BLAS libraries without symbol mangling can still be alternated to e.g. MKL. Checksums-Sha1: 7f512fd8c8141858e60befe4b1db03ddad0931cc 5007 openblas_0.3.20+ds-2.dsc 29c35c88fb5e61fb52683c52d741683d0db8383a 23500 openblas_0.3.20+ds-2.debian.tar.xz ce8b49dddfe86c111afc9dd6a0e1075e4309cdca 6127 openblas_0.3.20+ds-2_source.buildinfo Checksums-Sha256: 93967629e83ff43714a8787d56c5e488a28503278113a628cdf4ab6abbfee99c 5007 openblas_0.3.20+ds-2.dsc 985cc117515bc056920f03bb30bf03c998f6b574b8c7c64d1739ba0cbe5633e8 23500 openblas_0.3.20+ds-2.debian.tar.xz 11a82ce6389db8b540f17d69172d97ea572ed17f57e430c93840938c68f845d5 6127 openblas_0.3.20+ds-2_source.buildinfo Files: 7457d9209866c8dc31eec526ccf95be1 5007 devel optional openblas_0.3.20+ds-2.dsc 9b9bfab505898f6e79c0f58386f0c862 23500 devel optional openblas_0.3.20+ds-2.debian.tar.xz b8dc99fbfe466a8b095930ed15e0a3cf 6127 devel optional openblas_0.3.20+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmKJS1wRHGx1bWluQGRl Ymlhbi5vcmcACgkQYmRes19oaoohXQ/8Cl7OC8QIUB213Q6/7Kv4YeIQ7pfCe6uS JU5ULGGXBRQIg+09GRHEQ9g/1iCezmuS5hdOdq/Jo8bu1HTk9H4upthYuHP+xlBj tqqlQiWzoPWssdybd29NdqoXctNgzIU+GAovEkdWSRSIz0QGys6e4m2/1mdXrPgD 3Hyges9l3QqacznT2/ZJ7hYY02ey8WiAnaBCnOJVcRQeulP2yXwGkLnuR/UTSlYu R6v+v1Ha0KJwsCIwIlxCbGcsFXYLQVetfA8gJQ4ZVAkysyKIGAKSnl79suj5/cDC yDwWwmZSywqnRzNKZApDzxfSc/2vXXdsOw8hNrmm2k8Pv1TlDq4RSB9c59wZkqnG D9WKoBS9xYegGLwY6lt/EUxBrGYpybrcbRWtEiEqMwAaNwrSjgdpUDquSu/GuXWO 1LN5ClYj7E56jAImK30FDEHXeK3tym12bW9JKmXK6qukiUgAoS+gOIcyu9qAGrrs GPs4UJRGQ8nPCpLjkIHnChH5YqsfCcTQJwi/RYQhMPjtc29V3FrXv9z+gH4BXbuE 2LZzN0Jtv8VoZh/gIrB7ibE2IhifmwO0edbIKMuRqWLtsZI20s1vKDUI72c5kJuK sf5f3QRs75lRAM0mHzAKdKJvXnoBhsAD/VkuRTWmXM/F8KKOZj7uCBf7AitZH5a3 1aEq19IKXoQ= =kiyu -END PGP SIGNATURE
Bug#1010623: more debug info needed
Hi,
I've just called dracut --debug /tmp/tempfile on my machine Debian
bullseye, kernel 5.10.0-14-amd64, no crypto partition.
I can see, that dracut adds the ccm module by itself and also installs
the ccm.ko into the initrd.
dracut-install: Adding module 'ccm' to hostonly module list
.
.
dracut-install: Handling /lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko
dracut-install: dracut_install
'/lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko'
'/lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko'
dracut-install:
dracut_install('/lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko',
'/lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko', 0, 0, 1)
dracut-install: dracut_install ret = 0
dracut-install: cp '/lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko'
'/var/tmp/dracut.weYWqU/initramfs/lib/modules/5.10.0-14-amd64//kernel/crypto/ccm.ko'
dracut-install: cp ret = 0
dracut-install: dracut_install ret = 0
dracut-install: dracut_install 'ccm' OK
You should also debug your setup using dracut --debug /tmp/tempfile.
Maybe uyou can alos provide some information about the
encrypted root file system. I do not know how crypt setups work, but I
guess we need the encryption type of the file system and maybe other
infos about it.
--
regards Thomas
Bug#995634: marked as done (autobahn-cpp: FTBFS with OpenSSL 3.0: Uses -Werror and deprecated functions)
Your message dated Sat, 21 May 2022 19:04:05 + with message-id and subject line Bug#995634: fixed in autobahn-cpp 17.5.1+git7cc5d37-2.2 has caused the Debian Bug report #995634, regarding autobahn-cpp: FTBFS with OpenSSL 3.0: Uses -Werror and deprecated functions 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.) -- 995634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autobahn-cpp Version: 17.5.1+git7cc5d37-2.1 Severity: important User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is building using -Werror and is using functions that have been deprecated in OpenSSL 3.0. The log contains errors like: In file included from /<>/autobahn/wamp_session.ipp:48, from /<>/autobahn/wamp_session.hpp:403, from /<>/autobahn/autobahn.hpp:42, from /<>/examples/callee.cpp:33: /<>/autobahn/wamp_auth_utils.hpp: In function std::string compute_wcs(const string&, const string&): /<>/autobahn/wamp_auth_utils.hpp:169:35: error: HMAC_CTX* HMAC_CTX_new() is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 169 | HMAC_CTX *hmac = HMAC_CTX_new(); | ^ The short time solution is to remove the -Werror, which will turn it into a warning. For a longer term solution, see https://www.openssl.org/docs/man3.0/man7/migration_guide.html#Deprecated-low-level-MAC-functions Kurt --- End Message --- --- Begin Message --- Source: autobahn-cpp Source-Version: 17.5.1+git7cc5d37-2.2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of autobahn-cpp, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated autobahn-cpp 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, 21 May 2022 20:46:38 +0200 Source: autobahn-cpp Architecture: source Version: 17.5.1+git7cc5d37-2.2 Distribution: unstable Urgency: medium Maintainer: Konstantinos Margaritis Changed-By: Bastian Germann Closes: 995634 Changes: autobahn-cpp (17.5.1+git7cc5d37-2.2) unstable; urgency=medium . * Non-maintainer upload. * Add -Wno-error=deprecated-declarations flag. (Closes: #995634) * d/control: Remove non-existing Vcs-* fields. Checksums-Sha1: ee2beda212a360c7cf3b192c645619b872557bd1 1918 autobahn-cpp_17.5.1+git7cc5d37-2.2.dsc df322cebc207708112c3f15a4f91650aeacd72fb 3900 autobahn-cpp_17.5.1+git7cc5d37-2.2.debian.tar.xz 596000be7679728ad6f6ab2aca7af43c091d53ab 6415 autobahn-cpp_17.5.1+git7cc5d37-2.2_source.buildinfo Checksums-Sha256: 72c35cf1364fe49707df49e2d5517a13e2f4081f192951e439aafd27adb2f55c 1918 autobahn-cpp_17.5.1+git7cc5d37-2.2.dsc 1f5316d46011d0778dccec2bacd666955ae1636396f214b50c388e73e7867690 3900 autobahn-cpp_17.5.1+git7cc5d37-2.2.debian.tar.xz e6fdf129a8667cb309061db37fd3d49e14b29874fbd573f562a798661a75a5ef 6415 autobahn-cpp_17.5.1+git7cc5d37-2.2_source.buildinfo Files: 752a250b879caaf597ebbbf11bb85b54 1918 libs optional autobahn-cpp_17.5.1+git7cc5d37-2.2.dsc e57ecc01b582c65a6242ae8775fca8b5 3900 libs optional autobahn-cpp_17.5.1+git7cc5d37-2.2.debian.tar.xz 1d46560622ce8495315dd4b1dcb0c619 6415 libs optional autobahn-cpp_17.5.1+git7cc5d37-2.2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmKJND4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFIfhC/9wFzyyt2NLwzgV2wzV1hFa2OZdcWhVQT1e Lcp+TPDG4kTjw+wNNFIP6PwVfD94wII7U0J7Iq4flr0h22VIvndfNjDusWRmca5R zJKTI7HGh4r/FmRU2DSqIy1Ql/SV/rqhvX88HW7K8D+4ecnZ8bHcMP5fOHt/02RK rmZY3W0HHYzfanMh2mY+nVdVvbkm5AdUlgvjV/Bp9DyOmulPyAxsCVFq4iHxzLRl kWPUScM93hq8DPWjgjmHR4XZt3KcSD8n//MoSs2eN6MbjjyxtH51PWjIVh+SmtdG YYMwzwTuuxab8cFJfBoIPUuiEvBMLSoN968fwQ8OnFPvKlIG/CiXWjow7rK3W1ZC 2zcvl322VlmMrAtZLIgR1XieGHQUAtjarmb7tpEVkmaeKu9H44JdGqGbNvZUeOan oX/Lg9vn8N1RNljAqi4vF5mztbr+wzHnoQmnNSk3L/y64OkGv1E3/jokVPgyNJDM f7T+0UzBnlf52qCnQAZZEWvMHGm90RM= =IBP2 -END PGP SIGNATURE End Message ---
Bug#1011396: posterazor: Unable to load compatible files (PDF, SVG...)
Package: posterazor Version: 1.5.1-10 Severity: grave Justification: renders package unusable The app is unable to load supposedly compatible files (PDF, SVG). It just fails rendering a "cannot load file" error. Running the app on the command-line shows no further info. Regards, Antonio -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages posterazor depends on: ii libc6 2.31-13+deb11u3 ii libfltk-images1.3 1.3.5-3 ii libfltk1.3 1.3.5-3 ii libfreeimage3 3.18.0+ds2-6 ii libgcc-s1 10.2.1-6 ii libstdc++6 10.2.1-6 ii libx11-6 2:1.7.2-1 ii libxpm41:3.5.12-1 posterazor recommends no packages. posterazor suggests no packages.
Bug#982766: marked as done (node-webpack: remove dependency on node-uglifyjs-webpack-plugin)
Your message dated Sun, 22 May 2022 00:28:04 +0530 with message-id and subject line Re: [Pkg-javascript-devel] Bug#982766: Bug#982766: node-webpack: remove dependency on node-uglifyjs-webpack-plugin has caused the Debian Bug report #982766, regarding node-webpack: remove dependency on node-uglifyjs-webpack-plugin 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.) -- 982766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-webpack Version: 4.43.0-6 Severity: serious webpack depends on node-uglifyjs-webpack-plugin, which in turn has a serious bug report against it because it is abandoned upstream. According to webpack/package.json, webpack does not seem to actually depend on this plugin, so it should be find to just remove this dependency. If this dependency is left, node-webpack will be dropped from bullseye. Best wishes, Julian --- End Message --- --- Begin Message --- On Tue, 3 May 2022 17:31:59 +0200 Paul Gevers wrote: > Control: block 977311 by -1 > > On Sun, 14 Mar 2021 11:44:31 +0530 Pirate Praveen > wrote: > > 2. Yadd already discussed about node-uglifyjs-webpack-plugin with release team. > > I don't recall that discussion now, can somebody please add a pointer to > this bug report such that we can judge what to do with this RC bug for > bookworm? That was probably for bullseye. This dependency is now removed in webpack 5 recently uploaded to unstable.--- End Message ---
Bug#995634: NMU: autobahn-cpp: FTBFS with OpenSSL 3.0: Uses -Werror and deprecated functions
I have just uploaded a NMU for this not to block openssl migration. debdiff is attached.diff -Nru autobahn-cpp-17.5.1+git7cc5d37/debian/changelog autobahn-cpp-17.5.1+git7cc5d37/debian/changelog --- autobahn-cpp-17.5.1+git7cc5d37/debian/changelog 2021-02-08 21:23:04.0 +0100 +++ autobahn-cpp-17.5.1+git7cc5d37/debian/changelog 2022-05-21 20:46:38.0 +0200 @@ -1,3 +1,11 @@ +autobahn-cpp (17.5.1+git7cc5d37-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add -Wno-error=deprecated-declarations flag. (Closes: #995634) + * d/control: Remove non-existing Vcs-* fields. + + -- Bastian Germann Sat, 21 May 2022 20:46:38 +0200 + autobahn-cpp (17.5.1+git7cc5d37-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru autobahn-cpp-17.5.1+git7cc5d37/debian/control autobahn-cpp-17.5.1+git7cc5d37/debian/control --- autobahn-cpp-17.5.1+git7cc5d37/debian/control 2017-11-21 22:05:36.0 +0100 +++ autobahn-cpp-17.5.1+git7cc5d37/debian/control 2022-05-21 20:46:38.0 +0200 @@ -5,8 +5,6 @@ Standards-Version: 3.9.8 Section: libs Homepage: http://autobahn.ws -Vcs-Git: https://anonscm.debian.org/collab-maint/autobahn-cpp.git -Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/autobahn-cpp.git Package: autobahn-cpp-dev Section: libdevel diff -Nru autobahn-cpp-17.5.1+git7cc5d37/debian/rules autobahn-cpp-17.5.1+git7cc5d37/debian/rules --- autobahn-cpp-17.5.1+git7cc5d37/debian/rules 2017-11-21 21:34:17.0 +0100 +++ autobahn-cpp-17.5.1+git7cc5d37/debian/rules 2022-05-21 20:46:38.0 +0200 @@ -3,7 +3,7 @@ # output every command that modifies files on the build system. #export DH_VERBOSE = 1 -export DEB_CXXFLAGS_MAINT_APPEND = -DMSGPACK_DEFAULT_API_VERSION=1 +export DEB_CXXFLAGS_MAINT_APPEND = -DMSGPACK_DEFAULT_API_VERSION=1 -Wno-error=deprecated-declarations %: dh $@ --parallel
Bug#993693: marked as done (ReferenceError: options is not defined)
Your message dated Sat, 21 May 2022 23:22:56 +0530 with message-id <80v8cr.6ouj1ej59...@onenetbeyond.org> and subject line Re: ReferenceError: options is not defined has caused the Debian Bug report #993693, regarding ReferenceError: options is not defined 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.) -- 993693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: webpack Version: 5.6.0+~cs6.4.0-1~exp2 Severity: grave I was trying to update another js-team package and couldn't understand what was wrong until I tried to just run webpack by itself in another directory: $ webpack [webpack-cli] ReferenceError: options is not defined at Object.apply (/usr/share/nodejs/webpack/lib/config/defaults.js:873:30) at WebpackOptionsApply.process (/usr/share/nodejs/webpack/lib/WebpackOptionsApply.js:453:16) at createCompiler (/usr/share/nodejs/webpack/lib/webpack.js:78:28) at create (/usr/share/nodejs/webpack/lib/webpack.js:115:15) at webpack (/usr/share/nodejs/webpack/lib/webpack.js:123:46) at f (/usr/share/nodejs/webpack/lib/index.js:35:15) at WebpackCLI.createCompiler (/usr/share/nodejs/webpack- cli/lib/webpack-cli.js:176:24) at WebpackCLI.run (/usr/share/nodejs/webpack-cli/lib/webpack- cli.js:268:25) at async runCLI (/usr/share/nodejs/webpack- cli/lib/bootstrap.js:59:9) This means it's broken ; installing unstable's 4.43.0-6 made the error go away, so it's a problem only with the new version. Cheers, J.Puydt --- End Message --- --- Begin Message --- On Sat, 04 Sep 2021 23:13:50 +0200 Julien Puydt wrote: > I was trying to update another js-team package and couldn't understand > what was wrong until I tried to just run webpack by itself in another > directory: This is an obsolete bug, this has since been fixed in newer versions in experimental and now it is available in unstable.--- End Message ---
Processed: block 1007170 with 1011009
Processing commands for cont...@bugs.debian.org: > block 1007170 with 1011009 Bug #1007170 [release.debian.org] transition: qtbase-opensource-src 1007170 was blocked by: 1007831 1007170 was not blocking any bugs. Added blocking bug(s) of 1007170: 1011009 > thanks Stopping processing here. Please contact me if you need assistance. -- 1007170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002494: marked as done (webpack 5 unusable: TypeError: this.program.configureOutput)
Your message dated Sat, 21 May 2022 23:06:11 +0530 with message-id and subject line Re: webpack 5 unusable: TypeError: this.program.configureOutput has caused the Debian Bug report #1002494, regarding webpack 5 unusable: TypeError: this.program.configureOutput 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.) -- 1002494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: webpack Version: 5.65.0+dfsg+~cs9.20.9-1 Severity: grave Justification: renders package unusable When trying to use webpack5, I got the following error: make[1]: Entering directory '/<>' webpack --mode production (node:647989) UnhandledPromiseRejectionWarning: TypeError: this.program.configureOutput is not a function at new WebpackCLI (/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:19:18) at runCLI (/usr/share/nodejs/webpack-cli/lib/bootstrap.js:5:15) at Object. (/usr/share/nodejs/webpack-cli/bin/cli.js:17:1) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) at Module.require (internal/modules/cjs/loader.js:887:19) at require (internal/modules/cjs/helpers.js:74:18) at runCli (/usr/share/nodejs/webpack/bin/webpack.js:69:2) (node:647989) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:647989) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. make[1]: Leaving directory '/<>' By the way at least to dependencies are missing: * node-execa * node-import-local (provided by node-jest-bundle) Cheers, Yadd --- End Message --- --- Begin Message --- On Thu, 23 Dec 2021 09:51:27 +0100 Yadd wrote: > When trying to use webpack5, I got the following error: > This looks like an obsolete bug report. > make[1]: Entering directory '/<>' > webpack --mode production > (node:647989) UnhandledPromiseRejectionWarning: TypeError: this.program.configureOutput is not a function > By the way at least to dependencies are missing: > * node-execa > * node-import-local (provided by node-jest-bundle) node-import-local dependency was added in a recent upload.--- End Message ---
Processed: yubico-piv-tool: diff for NMU version 2.2.0-1.1
Processing control commands: > tags 1006241 + pending Bug #1006241 [src:yubico-piv-tool] yubico-piv-tool: FTBFS with OpenSSL 3.0 Added tag(s) pending. -- 1006241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006241: yubico-piv-tool: diff for NMU version 2.2.0-1.1
Control: tags 1006241 + pending Dear maintainer, I've prepared an NMU for yubico-piv-tool (versioned as 2.2.0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru yubico-piv-tool-2.2.0/debian/changelog yubico-piv-tool-2.2.0/debian/changelog --- yubico-piv-tool-2.2.0/debian/changelog 2021-01-31 16:58:55.0 +0100 +++ yubico-piv-tool-2.2.0/debian/changelog 2022-05-21 19:24:52.0 +0200 @@ -1,3 +1,11 @@ +yubico-piv-tool (2.2.0-1.1) unstable; urgency=medium + + [ Simon Chopin ] + * d/p/OpenSSL3-header-conflict.patch: cherry-picked from upstream +to fix the build against OpenSSL 3.0 (Closes: #1006241) + + -- Sebastian Ramacher Sat, 21 May 2022 19:24:52 +0200 + yubico-piv-tool (2.2.0-1) unstable; urgency=medium * New upstream version 2.2.0 (2021-01-20) diff -Nru yubico-piv-tool-2.2.0/debian/patches/OpenSSL3-header-conflict.patch yubico-piv-tool-2.2.0/debian/patches/OpenSSL3-header-conflict.patch --- yubico-piv-tool-2.2.0/debian/patches/OpenSSL3-header-conflict.patch 1970-01-01 01:00:00.0 +0100 +++ yubico-piv-tool-2.2.0/debian/patches/OpenSSL3-header-conflict.patch 2022-05-21 19:24:15.0 +0200 @@ -0,0 +1,33 @@ +From 81b063f53db8a3d74077522a6ff4f1640cc3fe70 Mon Sep 17 00:00:00 2001 +From: Clemens Lang +Date: Sun, 14 Nov 2021 18:21:28 +0100 +Subject: [PATCH] Avoid header include guard conflict with OpenSSL 3 +Origin: https://github.com/Yubico/yubico-piv-tool/pull/334 + +OpenSSL 3.x ships an openssl/types.h header that's protected with an +OPENSSL_TYPES_H include guard macro. OpenSSL's headers fail to parse +when ykcs11/openssl_types.h defines this symbol. + +Switch the include guard for the file to YKCS11_OPENSSL_TYPES_H to +prevent this from happening. + +Signed-off-by: Clemens Lang +--- + ykcs11/openssl_types.h | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/ykcs11/openssl_types.h b/ykcs11/openssl_types.h +index c526d815..f3e1a7c0 100644 +--- a/ykcs11/openssl_types.h b/ykcs11/openssl_types.h +@@ -28,8 +28,8 @@ + * + */ + +-#ifndef OPENSSL_TYPES_H +-#define OPENSSL_TYPES_H ++#ifndef YKCS11_OPENSSL_TYPES_H ++#define YKCS11_OPENSSL_TYPES_H + + #include + #include diff -Nru yubico-piv-tool-2.2.0/debian/patches/series yubico-piv-tool-2.2.0/debian/patches/series --- yubico-piv-tool-2.2.0/debian/patches/series 2021-01-31 16:58:55.0 +0100 +++ yubico-piv-tool-2.2.0/debian/patches/series 2022-05-21 19:24:15.0 +0200 @@ -1,2 +1,3 @@ Do-not-force-enable-INSTALL_RPATH.patch yubico-piv-tool-Put-useful-description-in-manpage.patch +OpenSSL3-header-conflict.patch
Bug#1011393: openpace: FTBFS on arm64, armel and mips64el
Source: openpace Version: 1.1.2+ds+git20220117+453c3d6b03a0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=openpace=arm64=1.1.2%2Bds%2Bgit20220117%2B453c3d6b03a0-1=1652780709=0 libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto make[6]: Leaving directory '/<>/src' /usr/bin/help2man \ --output=cvc-print.1 \ --no-info \ --source='OpenPACE 1.1.2' \ ./cvc-print /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o libeac.la libvc.la -lcrypto help2man: can't get `--help' info from ./cvc-print Try `--no-discard-stderr' if option outputs to stderr make[5]: *** [Makefile:1532: cvc-print.1] Error 127 make[5]: *** Waiting for unfinished jobs libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/eactest eactest-eactest.o eactest-ssl_compat.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o cvc-create cvc_create-cvc-create.o cvc_create-read_file.o cvc_create-cvc-create-cmdline.o libeac.la libvc.la -lcrypto libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-create cvc_create-cvc-create.o cvc_create-read_file.o cvc_create-cvc-create-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto make[6]: Leaving directory '/<>/src' /usr/bin/help2man \ --output=cvc-create.1 \ --no-info \ --source='OpenPACE 1.1.2' \ ./cvc-create make[5]: Leaving directory '/<>/src' make[4]: *** [Makefile:1149: all-recursive] Error 1 make[4]: Leaving directory '/<>/src' make[3]: *** [Makefile:566: all] Error 2 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:522: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:433: all] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j4 returned exit code 2 make: *** [debian/rules:11: binary-arch] Error 25 Cheers -- Sebastian Ramacher
Bug#995642: marked as done (cfengine3: FTBFS with OpenSSL 3.0)
Your message dated Sat, 21 May 2022 17:03:57 + with message-id and subject line Bug#995642: fixed in cfengine3 3.15.2-3.1 has caused the Debian Bug report #995642, regarding cfengine3: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 995642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cfengine3 Version: 3.15.2-3 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Hi, Your package is failing to build using OpenSSL 3.0 with the following error: In file included from hash.c:33: ./hash.h:64:28: error: unknown type name RSA 64 | Hash *HashNewFromKey(const RSA *rsa, HashMethod method); |^~~ ./hash.h:163:23: error: unknown type name RSA 163 | void HashPubKey(const RSA *key, unsigned char digest[EVP_MAX_MD_SIZE + 1], HashMethod type); | ^~~ hash.c:214:28: error: unknown type name RSA 214 | Hash *HashNewFromKey(const RSA *rsa, HashMethod method) |^~~ hash.c: In function HashNewFromKey: hash.c:226:5: error: implicit declaration of function RSA_get0_key [-Werror=implicit-function-declaration] 226 | RSA_get0_key(rsa, , , NULL); | ^~~~ hash.c: At top level: hash.c:531:11: error: unknown type name RSA 531 | const RSA *const key, | ^~~ cc1: some warnings being treated as errors I'm not sure why you don't get the RSA type, it should still exists. However, those functions have been deprecated, so you'll need to replace them at some point. For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Kurt --- End Message --- --- Begin Message --- Source: cfengine3 Source-Version: 3.15.2-3.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of cfengine3, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated cfengine3 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, 21 May 2022 18:25:35 +0200 Source: cfengine3 Architecture: source Version: 3.15.2-3.1 Distribution: unstable Urgency: medium Maintainer: Antonio Radici Changed-By: Sebastian Ramacher Closes: 852674 995642 Changes: cfengine3 (3.15.2-3.1) unstable; urgency=medium . * Non-maintainer upload. * debian/control: Make cfengine3 depend on exact version of libpromises3 (Closes: #852674) * debian/patches/openssl3.patch: Fix FTBFS with OpenSSL 3 (Closes: #995642) Checksums-Sha1: 56c31ba285ba29e5e565c2e79d6d880d944a978a 2328 cfengine3_3.15.2-3.1.dsc eb39b333e105673f0f1142bdc1381ae431ddcf01 19820 cfengine3_3.15.2-3.1.debian.tar.xz Checksums-Sha256: ff80e2e566ff00350333682ec7e4c4598474ae611c104e6092dc9abc4e3fd47e 2328 cfengine3_3.15.2-3.1.dsc d237a3e7023205a134d0eaa4f09d12373188cdfaf2d4d06aae5edeccc2b001f7 19820 cfengine3_3.15.2-3.1.debian.tar.xz Files: 3b85a0327b92a4a7b381c01df985d80d 2328 admin optional cfengine3_3.15.2-3.1.dsc abe03433e76b079cece411d0845e7598 19820 admin optional cfengine3_3.15.2-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmKJGnAACgkQafL8UW6n GZMZ7BAAmfe+/ckQN6jrTVaJd+K6CS//4fmVqNiEDGknDc6IYQK/C4QbTyUATzTO 2ob+kCSbQFU2VqTjrfzailvVyQc4X2NkFJ75WR16TyhOVspq93NfKr7ZlNBYXqwU SQMsphE7LvNX3j0xWiP6R56ccDHJK235P6c4xo2Brf7lnrQmyB92sMFwVyTEgBZP RxiWgS1WsfJEAhnEb5LAv6AaHinBm1zet39naGm6QmiVcF5F9EwCztJJz7k+ctiI v4BQzf6xvdPTLEJKRAovr7GlB7eNIpdtpkDBi5twN1WbhOlNzrKr32MyoO7vbHda OuUIAw+cV57HgZ4jSBkDkPJ5k9t9YLOoI1N3uegNEUxmCa7Cva3Kg7KKDuAWUMM6 Jv/cCcJw/erpo/QcyGnYKjiT9t21sKZ+EBWXQrUnwdyp3jeBSFTi8fsCVknZqvpi c786F84mZTmqWw4JtO1xLAB98Txfny0AASHppIa7D7A6A2veD71CgXpwpzX7Pl+c ygxZMEGaY00QtcCUdL3BB0XWP1YX+mnhyKXwDS418OlYPqSRxFMz5UFJ1NRTql0W NMAs2WYjP989Q+70Dnv0AO7OKgMNydtI1FaGDb9U+qEMD/rxhD5TFlvqnjPb3gQm Q50Xu+aoIiXqzC4moiWOJcNgRGKfWN6XjuIuobbgxucvQylFHkM= =PHqq -END PGP SIGNATURE End Message ---
Bug#852674: marked as done (cfengine3: should depend on exact version of libpromises3)
Your message dated Sat, 21 May 2022 17:03:57 +
with message-id
and subject line Bug#852674: fixed in cfengine3 3.15.2-3.1
has caused the Debian Bug report #852674,
regarding cfengine3: should depend on exact version of libpromises3
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.)
--
852674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cfengine3
Version: 3.9.1-4.1
Severity: normal
Dear Maintainer,
cfengine3 depends on libpromises3 without version information.
It should depend on the exact version which also cfengine3 has.
If you mix versions from cfengine3 from testing and libpromises3 from
stable you get undefined symbols.
Please use
libpromises3 (= ${binary:Version})
in the control file
Christoph
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (700, 'stable-updates'), (700, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cfengine3 depends on:
ii libacl1 2.2.52-2
ii libc6 2.19-18+deb8u7
ii liblmdb0 0.9.14-1
ii libpam0g 1.1.8-3.1+deb8u2
ii libpcre3 2:8.35-3.3+deb8u4
ii libpromises3 3.9.1-4.1
ii libssl1.1 1.1.0c-4
ii libvirt0 1.2.9-9+deb8u3
ii libxml2 2.9.1+dfsg1-5+deb8u4
ii lsb-base 4.1+Debian13+nmu1
Versions of packages cfengine3 recommends:
ii python 2.7.9-1
cfengine3 suggests no packages.
-- no debconf information
--
Christoph Martin, Leiter Unix-Systeme
Zentrum für Datenverarbeitung, Uni-Mainz, Germany
Anselm Franz von Bentzel-Weg 12, 55128 Mainz
Telefon: +49(6131)3926337
Instant-Messaging: Jabber: mar...@jabber.uni-mainz.de
(Siehe http://www.zdv.uni-mainz.de/4010.php)
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cfengine3
Source-Version: 3.15.2-3.1
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
cfengine3, 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 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated cfengine3
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, 21 May 2022 18:25:35 +0200
Source: cfengine3
Architecture: source
Version: 3.15.2-3.1
Distribution: unstable
Urgency: medium
Maintainer: Antonio Radici
Changed-By: Sebastian Ramacher
Closes: 852674 995642
Changes:
cfengine3 (3.15.2-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/control: Make cfengine3 depend on exact version of libpromises3
(Closes: #852674)
* debian/patches/openssl3.patch: Fix FTBFS with OpenSSL 3 (Closes: #995642)
Checksums-Sha1:
56c31ba285ba29e5e565c2e79d6d880d944a978a 2328 cfengine3_3.15.2-3.1.dsc
eb39b333e105673f0f1142bdc1381ae431ddcf01 19820
cfengine3_3.15.2-3.1.debian.tar.xz
Checksums-Sha256:
ff80e2e566ff00350333682ec7e4c4598474ae611c104e6092dc9abc4e3fd47e 2328
cfengine3_3.15.2-3.1.dsc
d237a3e7023205a134d0eaa4f09d12373188cdfaf2d4d06aae5edeccc2b001f7 19820
cfengine3_3.15.2-3.1.debian.tar.xz
Files:
3b85a0327b92a4a7b381c01df985d80d 2328 admin optional cfengine3_3.15.2-3.1.dsc
abe03433e76b079cece411d0845e7598 19820 admin optional
cfengine3_3.15.2-3.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmKJGnAACgkQafL8UW6n
GZMZ7BAAmfe+/ckQN6jrTVaJd+K6CS//4fmVqNiEDGknDc6IYQK/C4QbTyUATzTO
2ob+kCSbQFU2VqTjrfzailvVyQc4X2NkFJ75WR16TyhOVspq93NfKr7ZlNBYXqwU
SQMsphE7LvNX3j0xWiP6R56ccDHJK235P6c4xo2Brf7lnrQmyB92sMFwVyTEgBZP
RxiWgS1WsfJEAhnEb5LAv6AaHinBm1zet39naGm6QmiVcF5F9EwCztJJz7k+ctiI
v4BQzf6xvdPTLEJKRAovr7GlB7eNIpdtpkDBi5twN1WbhOlNzrKr32MyoO7vbHda
OuUIAw+cV57HgZ4jSBkDkPJ5k9t9YLOoI1N3uegNEUxmCa7Cva3Kg7KKDuAWUMM6
Jv/cCcJw/erpo/QcyGnYKjiT9t21sKZ+EBWXQrUnwdyp3jeBSFTi8fsCVknZqvpi
Processed: cfengine3: diff for NMU version 3.15.2-3.1
Processing control commands: > tags 852674 + patch Bug #852674 [cfengine3] cfengine3: should depend on exact version of libpromises3 Ignoring request to alter tags of bug #852674 to the same tags previously set > tags 995642 + patch Bug #995642 [src:cfengine3] cfengine3: FTBFS with OpenSSL 3.0 Ignoring request to alter tags of bug #995642 to the same tags previously set -- 852674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852674 995642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cfengine3: diff for NMU version 3.15.2-3.1
Processing control commands: > tags 852674 + patch Bug #852674 [cfengine3] cfengine3: should depend on exact version of libpromises3 Added tag(s) patch. > tags 995642 + patch Bug #995642 [src:cfengine3] cfengine3: FTBFS with OpenSSL 3.0 Added tag(s) patch. -- 852674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852674 995642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#852674: cfengine3: diff for NMU version 3.15.2-3.1
Control: tags 852674 + patch
Control: tags 995642 + patch
Dear maintainer,
I've prepared an NMU for cfengine3 (versioned as 3.15.2-3.1). The diff
is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru cfengine3-3.15.2/debian/changelog cfengine3-3.15.2/debian/changelog
--- cfengine3-3.15.2/debian/changelog 2020-09-14 09:00:24.0 +0200
+++ cfengine3-3.15.2/debian/changelog 2022-05-21 18:25:35.0 +0200
@@ -1,3 +1,12 @@
+cfengine3 (3.15.2-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: Make cfengine3 depend on exact version of libpromises3
+(Closes: #852674)
+ * debian/patches/openssl3.patch: Fix FTBFS with OpenSSL 3 (Closes: #995642)
+
+ -- Sebastian Ramacher Sat, 21 May 2022 18:25:35 +0200
+
cfengine3 (3.15.2-3) unstable; urgency=medium
[ Antonio Radici ]
diff -Nru cfengine3-3.15.2/debian/control cfengine3-3.15.2/debian/control
--- cfengine3-3.15.2/debian/control 2020-09-14 09:00:24.0 +0200
+++ cfengine3-3.15.2/debian/control 2022-05-21 18:13:41.0 +0200
@@ -20,7 +20,7 @@
Package: cfengine3
Architecture: any
-Depends: lsb-base (>= 3.0-6), e2fsprogs, ${shlibs:Depends}, ${misc:Depends}
+Depends: lsb-base (>= 3.0-6), e2fsprogs, ${shlibs:Depends}, ${misc:Depends}, libpromises3 (= ${binary:Version})
Recommends: python
Description: tool for configuring and maintaining network machines
Cfengine is a suite of programs for integrated autonomic management
diff -Nru cfengine3-3.15.2/debian/patches/openssl3.patch cfengine3-3.15.2/debian/patches/openssl3.patch
--- cfengine3-3.15.2/debian/patches/openssl3.patch 1970-01-01 01:00:00.0 +0100
+++ cfengine3-3.15.2/debian/patches/openssl3.patch 2022-05-21 18:25:35.0 +0200
@@ -0,0 +1,70 @@
+Description: Allow the use of deprected OpenSSL functions
+ Also load legacy provider for blowfish.
+Author: Sebastian Ramacher
+Last-Update: 2022-05-21
+
+--- a/configure.ac
b/configure.ac
+@@ -462,10 +462,6 @@
+#endif
+]])],[AC_MSG_RESULT(OK)],[AC_MSG_ERROR(This release of CFEngine requires OpenSSL >= 0.9.7)])
+
+- if test "x$ac_cv_lib_crypto_RSA_generate_key_ex" = "xyes" ; then
+- AC_DEFINE(OPENSSL_NO_DEPRECATED, 1, [Define if non deprecated API is available.])
+- fi
+-
+if test "x$ac_cv_lib_crypto_RSA_generate_key_ex" = "xno" && \
+ test "x$ac_cv_lib_crypto_RSA_generate_key" = "xno" ; then
+ AC_MSG_ERROR(Cannot find OpenSSL)
+--- a/libntech/configure.ac
b/libntech/configure.ac
+@@ -431,10 +431,6 @@
+ #endif
+ ]])],[AC_MSG_RESULT(OK)],[AC_MSG_ERROR(This release of CFEngine requires OpenSSL >= 0.9.7)])
+
+-if test "x$ac_cv_lib_crypto_RSA_generate_key_ex" = "xyes" ; then
+- AC_DEFINE(OPENSSL_NO_DEPRECATED, 1, [Define if non deprecated API is available.])
+-fi
+-
+ if test "x$ac_cv_lib_crypto_RSA_generate_key_ex" = "xno" && \
+test "x$ac_cv_lib_crypto_RSA_generate_key" = "xno" ; then
+AC_MSG_ERROR(Cannot find OpenSSL)
+--- a/libpromises/crypto.c
b/libpromises/crypto.c
+@@ -27,6 +27,7 @@
+ #include /* ERR_* */
+ #include/* RAND_* */
+ #include /* BN_* */
++#include
+ #include
+
+ #include
+@@ -60,6 +61,8 @@
+ /* TODO move crypto.[ch] to libutils. Will need to remove all manipulation of
+ * lastseen db. */
+
++static OSSL_PROVIDER* legacy_provider = NULL;
++static OSSL_PROVIDER* default_provider = NULL;
+ static bool crypto_initialized = false; /* GLOBAL_X */
+
+ const char *CryptoLastErrorString()
+@@ -75,6 +78,8 @@
+ SetupOpenSSLThreadLocks();
+ OpenSSL_add_all_algorithms();
+ OpenSSL_add_all_digests();
++legacy_provider = OSSL_PROVIDER_load(NULL, "legacy");
++default_provider = OSSL_PROVIDER_load(NULL, "default");
+ ERR_load_crypto_strings();
+
+ RandomSeed();
+@@ -103,6 +108,10 @@
+ }
+
+ chmod(randfile, 0600);
++
++OSSL_PROVIDER_unload(legacy_provider);
++OSSL_PROVIDER_unload(default_provider);
++
+ EVP_cleanup();
+ CleanupOpenSSLThreadLocks();
+ ERR_free_strings();
diff -Nru cfengine3-3.15.2/debian/patches/series cfengine3-3.15.2/debian/patches/series
--- cfengine3-3.15.2/debian/patches/series 2020-09-14 09:00:24.0 +0200
+++ cfengine3-3.15.2/debian/patches/series 2022-05-21 18:19:58.0 +0200
@@ -9,3 +9,4 @@
0011-fix_interpreters.patch
0012-CFE-3401-remove_unused_buffer.patch
0013-rename_package_to_cfengine3.patch
+openssl3.patch
Processed: bug 995642 is forwarded to https://tracker.mender.io/browse/CFE-3798
Processing commands for cont...@bugs.debian.org: > forwarded 995642 https://tracker.mender.io/browse/CFE-3798 Bug #995642 [src:cfengine3] cfengine3: FTBFS with OpenSSL 3.0 Set Bug forwarded-to-address to 'https://tracker.mender.io/browse/CFE-3798'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995640: boxbackup: FTBFS with OpenSSL 3.0
On Thu, 12 May 2022 15:38:47 + Ileana Dumitrescu wrote: I recently uploaded a new upstream version of boxbackup (0.13~~git20220405.g7703ac8-1). Can this openssl test be re-run? Without a full build log I cannot properly debug this. Your current version FTBFS with: configure.ac:24: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: error: /usr/bin/autoconf failed with exit status: 1 dh_autoreconf: error: autoreconf -f -i returned exit code 1 make[1]: *** [debian/rules:29: override_dh_autoreconf] Error 255 I suspect this is due to a newer autoconf version. Please fix this first to see if the openssl error will still hold.
Bug#1011304: marked as done (please replace (build) dependency luajit with lua on ppc64el)
Your message dated Sat, 21 May 2022 16:05:25 + with message-id and subject line Bug#1011304: fixed in obs-studio 27.2.4+dfsg1-2 has caused the Debian Bug report #1011304, regarding please replace (build) dependency luajit with lua on ppc64el 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.) -- 1011304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: luajit, knot-resolver Control: found -1 luajit/2.1.0~beta3+git20210112+dfsg-2 Control: found -1 knot-resolver/5.4.4-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of luajit the autopkgtest of knot-resolver fails in testing when that autopkgtest is run with the binary packages of luajit from unstable. It passes when run with only packages from testing. In tabular form: passfail luajit from testing2.1.0~beta3+git20210112+dfsg-2 knot-resolver from testing5.4.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of luajit to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=luajit https://ci.debian.net/data/autopkgtest/testing/ppc64el/k/knot-resolver/18781119/log.gz /usr/sbin/kresd + /usr/bin/kdig roundtrip tests workdir: /tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts IP addr: 127.148.62.213 kresd args: --addr=127.148.62.213@8053 --tls=127.148.62.213@8853 --noninteractive --config=/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.conf --verbose --verbose --verbose make Certificate Authority key and certificate -- Generating a 3072 bit RSA private key... Generating a self signed certificate... X.509 Certificate Information: Version: 3 Serial Number (hex): 2b34f0d7e93fd713653dda432ddeffed7f9f834b Validity: Not Before: Fri Jan 28 19:35:43 UTC 2022 Not After: Wed Feb 09 19:35:43 UTC 2022 Subject: CN=testing certificate authority (NOT FOR PRODUCTION) Subject Public Key Algorithm: RSA Algorithm Security Level: High (3072 bits) Modulus (bits 3072): 00:98:66:36:e9:ce:d2:58:89:bc:a9:ec:ac:21:5e:4b d2:f3:70:af:5c:41:11:d2:0f:fa:e2:f1:54:65:bc:86 06:4c:55:9f:0e:c3:72:8a:81:75:c3:be:2a:37:20:6a ce:45:4d:22:00:92:d8:f3:ff:0c:d1:c3:9e:1b:0e:f9 c4:48:38:22:84:f7:a0:6a:bd:e9:34:9d:91:35:00:7b 97:28:c7:6b:49:14:ed:50:81:07:7e:cc:cb:3c:79:cb fb:52:3d:3c:e0:c5:d9:1d:b5:1f:49:f4:55:74:db:a9 e7:58:fd:83:b6:56:ef:82:07:8f:6f:af:ec:26:b5:40 b4:23:1f:5c:b5:13:47:28:13:8a:58:58:19:f4:8f:3d 7e:12:c2:75:0c:7e:bd:f3:7d:89:f6:b6:3f:8f:63:99 1b:9d:e6:0c:63:fa:a5:5c:5e:08:27:d7:fd:af:3f:7c 54:74:4d:44:3b:ed:66:1a:05:ca:60:94:87:6d:47:c2 5e:8c:3f:1b:d9:60:21:4f:a4:30:1c:0a:21:da:34:0d a5:cc:df:70:f4:82:71:d4:05:eb:31:0a:2f:59:db:dd 5a:38:15:2a:39:c0:1c:14:2c:cc:3e:b1:dc:97:3d:d7 ff:95:3c:b7:9a:c9:e4:e4:d1:ee:8e:5f:f0:41:d1:f8 2d:4b:6a:36:8d:e8:33:ad:92:b1:7d:65:07:29:56:36 4a:ee:62:75:58:70:f0:99:31:b5:d9:08:8c:68:13:a2 f6:93:38:a9:d7:f9:84:a2:06:29:6f:c8:4c:53:ec:de 37:4b:0a:3c:a9:69:df:57:fd:f0:94:da:d1:a8:5a:8d 40:80:e4:80:5d:85:4c:4a:2f:94:81:9f:e5:a6:a2:49 10:bf:ff:10:11:9f:c6:9d:4d:04:d4:46:f3:25:7c:62 93:7a:43:c9:2d:6a:d5:5a:f2:4a:b7:35:5e:a1:08:f4 a7:30:7a:50:a2:67:c1:f7:2b:17:43:29:0e:3b:34:48 c5 Exponent (bits 24): 01:00:01
Bug#1011386: openblas FTBFS due to *combssq deprecated from lapack
Source: openblas Version: 0.3.20+ds-1 Severity: serious Justification: FTBFS According to lapack 3.10.1 release note and upstream pull request 570, xCOMBSSQ has been deprecated. Openblas upstream source has not yet adapted to this change. And thus FTBFS due to missing the following two symbols (fortran ABI): scombssq_ dcombssq_ I think this should be straightforward to fix as long as we remove the two symbols from openblas symbol check.
Bug#1011302: marked as done (please replace (build) dependency luajit with lua on ppc64el)
Your message dated Sat, 21 May 2022 14:34:55 + with message-id and subject line Bug#1011302: fixed in nageru 2.1.0-2 has caused the Debian Bug report #1011302, regarding please replace (build) dependency luajit with lua on ppc64el 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.) -- 1011302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: luajit, knot-resolver Control: found -1 luajit/2.1.0~beta3+git20210112+dfsg-2 Control: found -1 knot-resolver/5.4.4-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of luajit the autopkgtest of knot-resolver fails in testing when that autopkgtest is run with the binary packages of luajit from unstable. It passes when run with only packages from testing. In tabular form: passfail luajit from testing2.1.0~beta3+git20210112+dfsg-2 knot-resolver from testing5.4.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of luajit to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=luajit https://ci.debian.net/data/autopkgtest/testing/ppc64el/k/knot-resolver/18781119/log.gz /usr/sbin/kresd + /usr/bin/kdig roundtrip tests workdir: /tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts IP addr: 127.148.62.213 kresd args: --addr=127.148.62.213@8053 --tls=127.148.62.213@8853 --noninteractive --config=/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.conf --verbose --verbose --verbose make Certificate Authority key and certificate -- Generating a 3072 bit RSA private key... Generating a self signed certificate... X.509 Certificate Information: Version: 3 Serial Number (hex): 2b34f0d7e93fd713653dda432ddeffed7f9f834b Validity: Not Before: Fri Jan 28 19:35:43 UTC 2022 Not After: Wed Feb 09 19:35:43 UTC 2022 Subject: CN=testing certificate authority (NOT FOR PRODUCTION) Subject Public Key Algorithm: RSA Algorithm Security Level: High (3072 bits) Modulus (bits 3072): 00:98:66:36:e9:ce:d2:58:89:bc:a9:ec:ac:21:5e:4b d2:f3:70:af:5c:41:11:d2:0f:fa:e2:f1:54:65:bc:86 06:4c:55:9f:0e:c3:72:8a:81:75:c3:be:2a:37:20:6a ce:45:4d:22:00:92:d8:f3:ff:0c:d1:c3:9e:1b:0e:f9 c4:48:38:22:84:f7:a0:6a:bd:e9:34:9d:91:35:00:7b 97:28:c7:6b:49:14:ed:50:81:07:7e:cc:cb:3c:79:cb fb:52:3d:3c:e0:c5:d9:1d:b5:1f:49:f4:55:74:db:a9 e7:58:fd:83:b6:56:ef:82:07:8f:6f:af:ec:26:b5:40 b4:23:1f:5c:b5:13:47:28:13:8a:58:58:19:f4:8f:3d 7e:12:c2:75:0c:7e:bd:f3:7d:89:f6:b6:3f:8f:63:99 1b:9d:e6:0c:63:fa:a5:5c:5e:08:27:d7:fd:af:3f:7c 54:74:4d:44:3b:ed:66:1a:05:ca:60:94:87:6d:47:c2 5e:8c:3f:1b:d9:60:21:4f:a4:30:1c:0a:21:da:34:0d a5:cc:df:70:f4:82:71:d4:05:eb:31:0a:2f:59:db:dd 5a:38:15:2a:39:c0:1c:14:2c:cc:3e:b1:dc:97:3d:d7 ff:95:3c:b7:9a:c9:e4:e4:d1:ee:8e:5f:f0:41:d1:f8 2d:4b:6a:36:8d:e8:33:ad:92:b1:7d:65:07:29:56:36 4a:ee:62:75:58:70:f0:99:31:b5:d9:08:8c:68:13:a2 f6:93:38:a9:d7:f9:84:a2:06:29:6f:c8:4c:53:ec:de 37:4b:0a:3c:a9:69:df:57:fd:f0:94:da:d1:a8:5a:8d 40:80:e4:80:5d:85:4c:4a:2f:94:81:9f:e5:a6:a2:49 10:bf:ff:10:11:9f:c6:9d:4d:04:d4:46:f3:25:7c:62 93:7a:43:c9:2d:6a:d5:5a:f2:4a:b7:35:5e:a1:08:f4 a7:30:7a:50:a2:67:c1:f7:2b:17:43:29:0e:3b:34:48 c5 Exponent (bits 24): 01:00:01 Extensions:
Bug#1011362: marked as done (network-manager-openconnect: network-manager can't connect to VPNS, GUI says "Error: unable to load VPN connection editor")
Your message dated Sat, 21 May 2022 14:35:07 + with message-id and subject line Bug#1011362: fixed in network-manager-openconnect 1.2.8-3 has caused the Debian Bug report #1011362, regarding network-manager-openconnect: network-manager can't connect to VPNS, GUI says "Error: unable to load VPN connection editor" 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.) -- 1011362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: network-manager-openconnect Version: 1.2.6-4 Severity: grave Justification: renders package unusable Dear Maintainer, Using gnome to connect to openconnect VPNS has stopped working. Also, if you try to edit the VPN through the gnome control panel, you get the message "Error: unabled to load VPN connection editor" Installing version 1.2.8-2 from experimental seems to fix both problems. Also see: https://gitlab.gnome.org/GNOME/gtk/-/issues/4740 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (2000, 'unstable'), (1999, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-openconnect depends on: ii adduser 3.121 ii libc62.33-7 ii libglib2.0-0 2.72.1-1 ii libnm0 1.38.0-1 ii libopenconnect5 9.01-1 ii network-manager 1.38.0-1 ii openconnect 9.01-1 network-manager-openconnect recommends no packages. network-manager-openconnect suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: network-manager-openconnect Source-Version: 1.2.8-3 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of network-manager-openconnect, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated network-manager-openconnect 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, 21 May 2022 14:35:15 +0100 Source: network-manager-openconnect Architecture: source Version: 1.2.8-3 Distribution: unstable Urgency: medium Maintainer: Mike Miller Changed-By: Luca Boccassi Closes: 1009101 1011362 Changes: network-manager-openconnect (1.2.8-3) unstable; urgency=medium . * Bump Standards-Version to 4.6.1, no changes * Upload to unstable. (Closes: #1011362) . network-manager-openconnect (1.2.8-2) experimental; urgency=medium . * Really enable GTK 4 support (Closes: #1009101) * Use execute_before instead of override in d/rules . network-manager-openconnect (1.2.8-1) experimental; urgency=medium . * Update upstream source from tag 'upstream/1.2.8' - ported to GTK4 * Drop merged bugfix patches and refresh pending SAML patch * Build-depend on libgtk4-dev and libnma-dev * Drop gnome-vpn-properties from install file, no longer built Checksums-Sha1: d1c7676ddccc11f4fd2497b7e02ff73da54e97d2 2402 network-manager-openconnect_1.2.8-3.dsc 745292ba289757381cc1182ce0b68c4f4a73b666 10808 network-manager-openconnect_1.2.8-3.debian.tar.xz f21ce3654bce3791ddd13db97fb9d9a8028e9938 20347 network-manager-openconnect_1.2.8-3_source.buildinfo Checksums-Sha256: c38334cc19690e156a986663d79e8d54d1ad20f31e63f9346942b7120be9502c 2402 network-manager-openconnect_1.2.8-3.dsc de9c003f70878dd79b75e5e2b8f6128d99f63108759acab11a381b4a3c8e9395 10808 network-manager-openconnect_1.2.8-3.debian.tar.xz b2fe59ffc7cd730df8db03aacef305a79b5bb788ab31ee7bbb1660d2359b3090 20347 network-manager-openconnect_1.2.8-3_source.buildinfo Files: 1cbfdd6a23003305029d790bb5094ef3 2402 net optional network-manager-openconnect_1.2.8-3.dsc fc87bf118e39641980fe802bd8d168ef 10808 net optional
Bug#1011308: Bug#1004511 closed by Debian FTP Masters (reply to Jean Baptiste Favre ) (Bug#1004511: fixed in trafficserver 9.1.2+ds-2)
reopen 1004511 fixed 1011308 9.1.2+ds-3 On Sat, 21 May 2022 13:18:09 +0200 Paul Gevers wrote: Control: reopen 1004511 Control: fixed 1011308 9.1.2+ds-2 On 21-05-2022 11:51, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the ftp.debian.org package: > > #1004511: RM: luajit [ppc64el] -- ROP; segfaults > > It has been closed by Debian FTP Masters (reply to Jean Baptiste Favre ). The upload of trafficserver closed the wrong bug. Paul Referenced the wrong bug again (missed the first reopen message). Sorry for the noise Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Bug#1001337: marked as done (pam-p11: FTBFS with openssl 3)
Your message dated Sat, 21 May 2022 13:04:33 + with message-id and subject line Bug#1001337: fixed in pam-p11 0.3.1-1.1 has caused the Debian Bug report #1001337, regarding pam-p11: FTBFS with openssl 3 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.) -- 1001337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pam-p11 Version: 0.3.1-1 Severity: serious Tags: patch experimental Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Hi Eric, In Ubuntu, pam-p11 is failing to build from source because of the update to openssl 3, and pam-p11's use of some functions which are now deprecated: [...] gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -DLOCALEDIR=\"/usr/share/locale\" -DLIBDIR=\"/lib/x86_64-linux-gnu\" -DTEST -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -Wno-unused-parameter -Werror -c -o test_login-match_openssh.o `test -f 'match_openssh.c' || echo './'`match_openssh.c match_openssh.c: In function ‘ssh1_line_to_key’: match_openssh.c:71:9: error: ‘RSA_new’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 71 | rsa = RSA_new(); | ^~~ In file included from /usr/include/openssl/x509.h:36, from match_openssh.c:11: /usr/include/openssl/rsa.h:201:28: note: declared here 201 | OSSL_DEPRECATEDIN_3_0 RSA *RSA_new(void); |^~~ match_openssh.c:142:9: error: ‘RSA_set0_key’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 142 | if (!RSA_set0_key(rsa, rsa_n, rsa_e, NULL)) | ^~ In file included from /usr/include/openssl/x509.h:36, from match_openssh.c:11: /usr/include/openssl/rsa.h:207:27: note: declared here 207 | OSSL_DEPRECATEDIN_3_0 int RSA_set0_key(RSA *r, BIGNUM *n, BIGNUM *e, BIGNUM *d); | ^~~~ [...] (https://launchpad.net/ubuntu/+source/pam-p11/0.3.1-1build2/+build/22576460) OpenSSL 3 is currently only in experimental in Debian, but is expected to be the version shipped in the next release of Debian. In Ubuntu, I've applied the following patch to let pam-p11 build by ignoring the deprecation warnings. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru pam-p11-0.3.1/debian/rules pam-p11-0.3.1/debian/rules --- pam-p11-0.3.1/debian/rules 2019-10-27 22:36:24.0 -0700 +++ pam-p11-0.3.1/debian/rules 2021-12-08 13:18:20.0 -0800 @@ -1,5 +1,7 @@ #!/usr/bin/make -f +export DEB_CFLAGS_MAINT_APPEND = -Wno-error=deprecated-declarations + DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) %: --- End Message --- --- Begin Message --- Source: pam-p11 Source-Version: 0.3.1-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of pam-p11, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated pam-p11 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, 21 May 2022 14:54:14 +0200 Source: pam-p11 Architecture: source Version: 0.3.1-1.1 Distribution: unstable Urgency: low Maintainer: Debian OpenSC Maintainers Changed-By: Bastian Germann Closes: 1001337 Changes: pam-p11 (0.3.1-1.1) unstable; urgency=low . * Non-maintainer upload . [ Steve Langasek ] * Build with -Wno-error=deprecated-declarations for compatibility with OpenSSL 3 (Closes: #1001337) . [ Debian Janitor ] * Use secure copyright file specification URI. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse.
Bug#1001337: NMU: pam-p11: FTBFS with openssl 3
Hi, This is blocking the openssl migration, so I NMU this package with the maintainer's git changes and the Ubuntu patch by Steve. debdiff attached. Thanks, Bastiandiff -Nru pam-p11-0.3.1/debian/changelog pam-p11-0.3.1/debian/changelog --- pam-p11-0.3.1/debian/changelog 2019-10-28 06:36:24.0 +0100 +++ pam-p11-0.3.1/debian/changelog 2022-05-21 14:54:14.0 +0200 @@ -1,3 +1,18 @@ +pam-p11 (0.3.1-1.1) unstable; urgency=low + + * Non-maintainer upload + + [ Steve Langasek ] + * Build with -Wno-error=deprecated-declarations for compatibility with +OpenSSL 3 (Closes: #1001337) + + [ Debian Janitor ] + * Use secure copyright file specification URI. + * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, +Repository-Browse. + + -- Bastian Germann Sat, 21 May 2022 14:54:14 +0200 + pam-p11 (0.3.1-1) unstable; urgency=medium * New upstream release (Closes: 925802, 939664) diff -Nru pam-p11-0.3.1/debian/copyright pam-p11-0.3.1/debian/copyright --- pam-p11-0.3.1/debian/copyright 2019-10-28 06:36:24.0 +0100 +++ pam-p11-0.3.1/debian/copyright 2022-05-21 14:49:00.0 +0200 @@ -1,4 +1,4 @@ -Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pam_p11 Upstream-Contact: https://github.com/OpenSC/pam_p11 Source: https://github.com/OpenSC/pam_p11 diff -Nru pam-p11-0.3.1/debian/rules pam-p11-0.3.1/debian/rules --- pam-p11-0.3.1/debian/rules 2019-10-28 06:36:24.0 +0100 +++ pam-p11-0.3.1/debian/rules 2022-05-21 14:51:40.0 +0200 @@ -1,5 +1,7 @@ #!/usr/bin/make -f +export DEB_CFLAGS_MAINT_APPEND = -Wno-error=deprecated-declarations + DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) %: diff -Nru pam-p11-0.3.1/debian/upstream/metadata pam-p11-0.3.1/debian/upstream/metadata --- pam-p11-0.3.1/debian/upstream/metadata 1970-01-01 01:00:00.0 +0100 +++ pam-p11-0.3.1/debian/upstream/metadata 2022-05-21 14:49:00.0 +0200 @@ -0,0 +1,5 @@ +--- +Bug-Database: https://github.com/OpenSC/pam_p11/issues +Bug-Submit: https://github.com/OpenSC/pam_p11/issues/new +Repository: https://github.com/OpenSC/pam_p11.git +Repository-Browse: https://github.com/OpenSC/pam_p11
Bug#1011364: phcpack: FTBFS with gnat-11
On Fri 20 May 2022 05:37:23 PM EDT, Sebastian Ramacher wrote: Source: phcpack Version: 2.4.85+dfsg-5 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org debian/rules clean /usr/share/ada/debian_packaging-11.mk:31: *** Please include /usr/share/dpkg/default.mk (or the more specific buildflags.mk and buildopts.mk) before /usr/share/ada/debian_packaging-11.mk. Stop. dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 Thanks for the report! The fix for this particular bug is very simple (see [1]). However, the build then fails later on: gnatbind -n -static use_c2phc -o use_c2phc_binder.adb raised STORAGE_ERROR : stack overflow or erroneous memory access make[3]: *** [makefile_unix:4102: phcpy2c3.so] Error 1 I'll investigate further and hopefully upload a new package soon that fixes both issues. Doug [1] https://salsa.debian.org/math-team/phcpack/-/commit/b38a6ba signature.asc Description: PGP signature
Bug#1010441: marked as done (torbrowser-launcher fails to download browser bundle when launched for the first time)
Your message dated Sat, 21 May 2022 12:05:17 + with message-id and subject line Bug#1010441: fixed in torbrowser-launcher 0.3.5-3 has caused the Debian Bug report #1010441, regarding torbrowser-launcher fails to download browser bundle when launched for the first time 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.) -- 1010441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: torbrowser-launcher Version: 0.3.5-2 Severity: important X-Debbugs-Cc: p...@cock.li Dear Maintainer, Current version of torbrowser-launcher in Sid fails to download tor browser when launched for the first time (ie when ~/.local/share/torbrowser/tbb/ does not exist) with the following error: Tor Browser Launcher By Micah Lee, licensed under MIT version 0.3.5 https://github.com/micahflee/torbrowser-launcher Downloading Tor Browser for the first time. Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US Traceback (most recent call last): File "/usr/bin/torbrowser-launcher", line 30, in torbrowser_launcher.main() File "/usr/lib/python3/dist-packages/torbrowser_launcher/__init__.py", line 98, in main gui.move( TypeError: arguments did not match any overloaded call: move(self, QPoint): argument 1 has unexpected type 'float' move(self, int, int): argument 1 has unexpected type 'float' Changing both arguments to int works to the following workaround may be used: --- /usr/lib/python3/dist-packages/torbrowser_launcher/__init__.py.orig 2022-05-01 17:44:35.369210869 +0200 +++ /usr/lib/python3/dist-packages/torbrowser_launcher/__init__.py 2022-05-01 17:45:16.697352319 +0200 @@ -96,8 +96,8 @@ desktop = app.desktop() window_size = gui.size() gui.move( -(desktop.width() - window_size.width()) / 2, -(desktop.height() - window_size.height()) / 2 +int((desktop.width() - window_size.width()) / 2), +int((desktop.height() - window_size.height()) / 2) ) gui.show() sys.exit(app.exec_()) -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages torbrowser-launcher depends on: ii ca-certificates20211016 ii gnupg 2.2.35-2 ii libdbus-glib-1-2 0.112-2 ii python33.10.4-1 ii python3-gpg1.16.0-1.2 ii python3-packaging 21.3-1 ii python3-pyqt5 5.15.6+dfsg-1+b2 ii python3-requests 2.27.1+dfsg-1 ii python3-socks 1.7.1+dfsg-1 Versions of packages torbrowser-launcher recommends: ii tor 0.4.7.7-1 Versions of packages torbrowser-launcher suggests: ii apparmor 3.0.4-2 -- no debconf information --- End Message --- --- Begin Message --- Source: torbrowser-launcher Source-Version: 0.3.5-3 Done: Roger Shimizu We believe that the bug you reported is fixed in the latest version of torbrowser-launcher, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Shimizu (supplier of updated torbrowser-launcher 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, 21 May 2022 20:41:30 +0900 Source: torbrowser-launcher Architecture: source Version: 0.3.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Roger Shimizu Closes: 1010441 Changes: torbrowser-launcher (0.3.5-3) unstable; urgency=medium . * debian/patches: - Cherry pick patch 12 from upstream to fix runtime issue under Python 3.10 (Closes: #1010441). Checksums-Sha1: acdf6e54705ce879521bda808dab2d40f0d7b186 2281 torbrowser-launcher_0.3.5-3.dsc 4cf893cd6b04f85da7ec28097b6d9fd35c628ce6 20992
Bug#1004740: marked as done (exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen)
Your message dated Sat, 21 May 2022 11:33:55 + with message-id and subject line Bug#1004740: fixed in exim4 4.96~RC1-1 has caused the Debian Bug report #1004740, regarding exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen 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.) -- 1004740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: exim4 Version: 4.95-3 Severity: serious When sending a mail: [...] 2022-02-01 14:23:22 1nEt2b-0008jG-97 H=mx2.mailchannels.net [34.214.163.59]: SMTP error from remote mail server after DATA: 450 [S09] Try Again Later 2022-02-01 14:23:22 1nEt2b-0008jG-97 H=mx2.mailchannels.net [34.214.163.59] TLS error on connection (recv): The TLS connection was non-properly terminated. 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to immutable memory) 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of 7 bytes (pipeheader) from transport process 35015 for transport smtp 2022-02-01 14:23:23 1nEt2b-0008jG-97 == xxx@yyy R=dnslookup T=remote_smtp defer (-1): smtp transport process returned non-zero status 0x000b: terminated by signal 11 2022-02-01 14:23:23 1nEt7z-00096o-IX <= <> R=1nEt2b-0008jG-97 U=Debian-exim P=local S=783 2022-02-01 14:23:23 1nEt2b-0008jG-97 Frozen 2022-02-01 14:23:23 1nEt7z-00096o-IX => vlefevre R=local_user T=maildir_home 2022-02-01 14:23:23 1nEt7z-00096o-IX Completed 2022-02-01 14:23:23 End queue run: pid=35012 2022-02-01 14:28:19 Start queue run: pid=35460 2022-02-01 14:28:19 1nEt2b-0008jG-97 Message is frozen 2022-02-01 14:28:19 End queue run: pid=35460 [...] The consequence is that the mail is not sent, there are no retries, and the end user is not warned. So, from the end user point of view, the message is *silently lost*. -- Package-specific info: Exim version 4.95 #2 built 16-Dec-2021 18:26:32 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2020 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS TLS_resume move_frozen_messages DANE DKIM DNSSEC Event I18N OCSP PIPE_CONNECT PRDR Experimental_Queue_Ramp SOCKS SRS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 external plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='internet' dc_other_hostnames='cventin.lip.ens-lyon.fr' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' mailname:cventin.lip.ens-lyon.fr # /etc/default/exim4 EX4DEF_VERSION='' # 'combined' - one daemon running queue and listening on SMTP port # 'no' - no daemon running the queue # 'separate' - two separate daemons # 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4. # 'nodaemon' - no daemon is started at all. # 'queueonly' - only a queue running daemon is started, no SMTP listener. # setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4 QUEUERUNNER='combined' # how often should we run the queue QUEUEINTERVAL='5m' # options common to quez-runner and listening daemon COMMONOPTIONS='' # more options for the daemon/process running the queue (applies to the one # started in
Bug#1011308: marked as done (please replace (build) dependency luajit with lua on ppc64el)
Your message dated Sat, 21 May 2022 13:18:09 +0200 with message-id and subject line Re: Bug#1004511 closed by Debian FTP Masters (reply to Jean Baptiste Favre ) (Bug#1004511: fixed in trafficserver 9.1.2+ds-2) has caused the Debian Bug report #1011308, regarding please replace (build) dependency luajit with lua on ppc64el 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.) -- 1011308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: luajit, knot-resolver Control: found -1 luajit/2.1.0~beta3+git20210112+dfsg-2 Control: found -1 knot-resolver/5.4.4-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of luajit the autopkgtest of knot-resolver fails in testing when that autopkgtest is run with the binary packages of luajit from unstable. It passes when run with only packages from testing. In tabular form: passfail luajit from testing2.1.0~beta3+git20210112+dfsg-2 knot-resolver from testing5.4.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of luajit to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=luajit https://ci.debian.net/data/autopkgtest/testing/ppc64el/k/knot-resolver/18781119/log.gz /usr/sbin/kresd + /usr/bin/kdig roundtrip tests workdir: /tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts IP addr: 127.148.62.213 kresd args: --addr=127.148.62.213@8053 --tls=127.148.62.213@8853 --noninteractive --config=/tmp/autopkgtest-lxc.7e24ymsu/downtmp/roundtrip-artifacts/kresd.conf --verbose --verbose --verbose make Certificate Authority key and certificate -- Generating a 3072 bit RSA private key... Generating a self signed certificate... X.509 Certificate Information: Version: 3 Serial Number (hex): 2b34f0d7e93fd713653dda432ddeffed7f9f834b Validity: Not Before: Fri Jan 28 19:35:43 UTC 2022 Not After: Wed Feb 09 19:35:43 UTC 2022 Subject: CN=testing certificate authority (NOT FOR PRODUCTION) Subject Public Key Algorithm: RSA Algorithm Security Level: High (3072 bits) Modulus (bits 3072): 00:98:66:36:e9:ce:d2:58:89:bc:a9:ec:ac:21:5e:4b d2:f3:70:af:5c:41:11:d2:0f:fa:e2:f1:54:65:bc:86 06:4c:55:9f:0e:c3:72:8a:81:75:c3:be:2a:37:20:6a ce:45:4d:22:00:92:d8:f3:ff:0c:d1:c3:9e:1b:0e:f9 c4:48:38:22:84:f7:a0:6a:bd:e9:34:9d:91:35:00:7b 97:28:c7:6b:49:14:ed:50:81:07:7e:cc:cb:3c:79:cb fb:52:3d:3c:e0:c5:d9:1d:b5:1f:49:f4:55:74:db:a9 e7:58:fd:83:b6:56:ef:82:07:8f:6f:af:ec:26:b5:40 b4:23:1f:5c:b5:13:47:28:13:8a:58:58:19:f4:8f:3d 7e:12:c2:75:0c:7e:bd:f3:7d:89:f6:b6:3f:8f:63:99 1b:9d:e6:0c:63:fa:a5:5c:5e:08:27:d7:fd:af:3f:7c 54:74:4d:44:3b:ed:66:1a:05:ca:60:94:87:6d:47:c2 5e:8c:3f:1b:d9:60:21:4f:a4:30:1c:0a:21:da:34:0d a5:cc:df:70:f4:82:71:d4:05:eb:31:0a:2f:59:db:dd 5a:38:15:2a:39:c0:1c:14:2c:cc:3e:b1:dc:97:3d:d7 ff:95:3c:b7:9a:c9:e4:e4:d1:ee:8e:5f:f0:41:d1:f8 2d:4b:6a:36:8d:e8:33:ad:92:b1:7d:65:07:29:56:36 4a:ee:62:75:58:70:f0:99:31:b5:d9:08:8c:68:13:a2 f6:93:38:a9:d7:f9:84:a2:06:29:6f:c8:4c:53:ec:de 37:4b:0a:3c:a9:69:df:57:fd:f0:94:da:d1:a8:5a:8d 40:80:e4:80:5d:85:4c:4a:2f:94:81:9f:e5:a6:a2:49 10:bf:ff:10:11:9f:c6:9d:4d:04:d4:46:f3:25:7c:62 93:7a:43:c9:2d:6a:d5:5a:f2:4a:b7:35:5e:a1:08:f4 a7:30:7a:50:a2:67:c1:f7:2b:17:43:29:0e:3b:34:48
Processed: Re: Bug#1004511 closed by Debian FTP Masters (reply to Jean Baptiste Favre ) (Bug#1004511: fixed in trafficserver 9.1.2+ds-2)
Processing control commands:
> reopen 1004511
Bug #1004511 {Done: Jean Baptiste Favre } [ftp.debian.org]
RM: luajit [ppc64el] -- ROP; segfaults
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions trafficserver/9.1.2+ds-2.
> fixed 1011308 9.1.2+ds-2
Bug #1011308 [src:trafficserver] please replace (build) dependency luajit with
lua on ppc64el
Marked as fixed in versions trafficserver/9.1.2+ds-2.
--
1004511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004511
1011308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1011297, tagging 999724, found 1011114 in 11.5.1-1, tagging 1011303, tagging 1008069 ...
Processing commands for cont...@bugs.debian.org:
> tags 1011297 =
Bug #1011297 [src:luajit] please prevent successful build on ppc64el until it
works
Removed tag(s) sid and bookworm.
> tags 999724 + experimental
Bug #999724 {Done: Mohammed Bilal }
[src:ruby-omniauth-salesforce] ruby-omniauth-salesforce: FTBFS with
ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in
activate_dependencies': Could not find 'omniauth' (~> 1.0) among 85 total
gem(s) (Gem::MissingSpecError)
Added tag(s) experimental.
> found 104 11.5.1-1
Bug #104 [src:nvidia-cuda-toolkit] nivdia-cuda-toolkit: hardcodes
dependencies on libssl1.1
Bug #1011243 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: Hard dependency on
libssl1.1
Marked as found in versions nvidia-cuda-toolkit/11.5.1-1.
Marked as found in versions nvidia-cuda-toolkit/11.5.1-1.
> tags 1011303 =
Bug #1011303 [src:nginx] please replace (build) dependency luajit with lua on
ppc64el
Removed tag(s) bookworm and sid.
> tags 1008069 =
Bug #1008069 {Done: Paul Gevers } [src:luajit] src:luajit:
fails to migrate to testing for too long: SEGFAULT on ppc64el
Removed tag(s) bookworm and sid.
> notfixed 1005258 3.0.1+dfsg1-3+b2
Bug #1005258 {Done: Reinhard Tartler } [podman] podman:
current podman version does not pass seccomp options to buildah
No longer marked as fixed in versions 3.0.1+dfsg1-3+b2.
> tags 1010998 + sid bookworm
Bug #1010998 [simh] simh: Upstream license change conflicts with DFSG
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1005258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005258
1008069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008069
1010998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010998
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
1011243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011243
1011297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011297
1011303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011303
999724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1006586: marked as done (tpm2-pkcs11: FTBFS with OpenSSL 3.0)
Your message dated Sat, 21 May 2022 09:19:06 + with message-id and subject line Bug#1006586: fixed in tpm2-pkcs11 1.7.0-1.1 has caused the Debian Bug report #1006586, regarding tpm2-pkcs11: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1006586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tpm2-pkcs11 Version: 1.7.0-1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is failing to build using OpenSSL 3.0 with the following error: | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./src/lib -Wdate-time -D_FORTIFY_SOURCE=2 -I./src -I./src/lib -Wall -Wextra -Werror -Wformat -Wformat-security -Wstack-protector -fstack-protector-all -Wstrict-overflow=5 -O2 -fPIC -I/usr/include/tss2 -I/usr/include/tss2 -I/usr/include/tss2 -I/usr/include/tss2 -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -c src/lib/mech.c -fPIC -DPIC -o src/lib/.libs/mech.o | src/lib/mech.c: In function ‘rsa_pkcs_synthesizer’: | src/lib/mech.c:860:5: error: ‘RSA_padding_add_PKCS1_type_1’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 860 | int rc = RSA_padding_add_PKCS1_type_1(outbuf, padded_len, | | ^~~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:376:5: note: declared here | 376 | int RSA_padding_add_PKCS1_type_1(unsigned char *to, int tlen, | | ^~~~ | src/lib/mech.c: In function ‘rsa_pkcs_unsynthesizer’: | src/lib/mech.c:896:5: error: ‘RSA_padding_check_PKCS1_type_2’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 896 | int rc = RSA_padding_check_PKCS1_type_2(buf, sizeof(buf), | | ^~~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:386:5: note: declared here | 386 | int RSA_padding_check_PKCS1_type_2(unsigned char *to, int tlen, | | ^~ | src/lib/mech.c: In function ‘rsa_pss_synthesizer’: | src/lib/mech.c:972:5: error: ‘RSA_new’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 972 | RSA *rsa = RSA_new(); | | ^~~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:201:28: note: declared here | 201 | OSSL_DEPRECATEDIN_3_0 RSA *RSA_new(void); | |^~~ | src/lib/mech.c:978:5: error: ‘RSA_set0_key’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 978 | int rc = RSA_set0_key(rsa, n, e, NULL); | | ^~~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:207:27: note: declared here | 207 | OSSL_DEPRECATEDIN_3_0 int RSA_set0_key(RSA *r, BIGNUM *n, BIGNUM *e, BIGNUM *d); | | ^~~~ | src/lib/mech.c:983:9: error: ‘RSA_free’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 983 | RSA_free(rsa); | | ^~~~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:293:28: note: declared here | 293 | OSSL_DEPRECATEDIN_3_0 void RSA_free(RSA *r); | |^~~~ | src/lib/mech.c:987:5: error: ‘RSA_padding_add_PKCS1_PSS’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 987 | rc = RSA_padding_add_PKCS1_PSS(rsa, outbuf, | | ^~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:428:5: note: declared here | 428 | int RSA_padding_add_PKCS1_PSS(RSA *rsa, unsigned char *EM, | | ^ | src/lib/mech.c:989:5: error: ‘RSA_free’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 989 | RSA_free(rsa); | | ^~~~ | In file included from src/lib/mech.c:10: | /usr/include/openssl/rsa.h:293:28: note: declared here | 293 | OSSL_DEPRECATEDIN_3_0 void RSA_free(RSA *r); | |^~~~ | cc1: all warnings being treated as errors | make[1]: *** [Makefile:2009: src/lib/mech.lo] Error 1 For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Sebastian --- End Message --- --- Begin Message --- Source: tpm2-pkcs11 Source-Version: 1.7.0-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of tpm2-pkcs11, which is due to be installed in the Debian FTP archive. A summary of the changes between
Bug#1006586: NMU: tpm2-pkcs11: FTBFS with OpenSSL 3.0
I uploaded a NMU with the enclosed changes to unblock the openssl migration.diff -Nru tpm2-pkcs11-1.7.0/debian/changelog tpm2-pkcs11-1.7.0/debian/changelog --- tpm2-pkcs11-1.7.0/debian/changelog 2021-10-17 11:06:37.0 +0200 +++ tpm2-pkcs11-1.7.0/debian/changelog 2022-05-21 10:49:57.0 +0200 @@ -1,3 +1,10 @@ +tpm2-pkcs11 (1.7.0-1.1) unstable; urgency=medium + + * Non-maintainer upload + * Correct version number patch (disables -Werror, Closes: #1006586) + + -- Bastian Germann Sat, 21 May 2022 10:49:57 +0200 + tpm2-pkcs11 (1.7.0-1) unstable; urgency=medium * Import new upstream release (Closes: #984368) diff -Nru tpm2-pkcs11-1.7.0/debian/patches/remove-aclocal-git-command.patch tpm2-pkcs11-1.7.0/debian/patches/remove-aclocal-git-command.patch --- tpm2-pkcs11-1.7.0/debian/patches/remove-aclocal-git-command.patch 2021-01-22 07:54:34.0 +0100 +++ tpm2-pkcs11-1.7.0/debian/patches/remove-aclocal-git-command.patch 2022-05-21 10:49:57.0 +0200 @@ -11,11 +11,12 @@ index d984249..eea8ece 100644 --- a/configure.ac +++ b/configure.ac -@@ -1,7 +1,6 @@ +@@ -1,7 +1,7 @@ # SPDX-License-Identifier: BSD-2-Clause AC_INIT([tpm2-pkcs11], - [m4_esyscmd_s([git describe --tags --always --dirty])], ++ [$DEB_VERSION_UPSTREAM], [https://github.com/tpm2-software/tpm2-pkcs11/issues], [], [https://github.com/tpm2-software/tpm2-pkcs11])
Bug#1010623: more debug info needed
On 5/20/22 11:38 PM, Thomas Lange wrote: Can you please provide the output of # lsinitrd /boot/initrd.img-.. on the old and new system? PLease also create a new temp initrd on the new system to see the log of the creation process: # dracut -v /tmp/tempfile I attach tar archive: 1) contents of initrd for 5.4.0-0.bpo-amd64 (aka "old system") as dracut-5.4.0-0.bpo-amd64.lst 2) contents of initrd for 5.10.0-13-amd64 (aka "new system") as dracut-5.10.0-13-amd64.lst but note this was built with drivers+=" ccm ecb " applied. 3) log of build for 5.10.0-13-amd64 as dracut-build.log but note the drivers+=... NOT applied. I hope that's helpful Dick dracut-debug-info.tar.gz Description: application/gzip
Bug#1006391: NMU: libengine-gost-openssl1.1: FTBFS with OpenSSL 3.0
Thanks for the NMU! The package isn't abandoned, I just discovered I have some technical problems with my DD key :( Once that is resolved, I will upload latest engine version which is intended to work in 3.0 environment. On Sat, May 21, 2022, 02:00 Bastian Germann wrote: > The right thing to do to solve this would be importing the new release. > I NMU this with the already existing Ubuntu patches so it does not block > the openssl migration. > > As the package seems to be abandoned, add already handed-in cross-compile > patch as well. > The debidff is enclosed.
Bug#1011051: libssl3: upgrade to libssl3 broke my dovecot setup
Hello, I think Ubuntu already did cherry-pick a fedora dovecot change for new openssl 3.0 https://patches.ubuntu.com/d/dovecot/dovecot_1:2.3.16+dfsg1-3ubuntu3.patch Maybe it can fix this specific issue. G. On Fri, 20 May 2022 11:27:54 + nona wrote: I can confirm this bug. The fix Skibbi proposed enables my mailserver to receive e-mails again. But I cannot login via IMAP receiving the following errors: # connecting from a laptop to the mail server: Socket error: secure connect to example.org (1.2.3.4:143): error:1408F10B:SSL routines:ssl3_get_record:wrong version number # mail server log /var/log/mail.log: May 20 13:22:59 mail dovecot: imap-login: Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): error:25066067:DSO support routines:dlfcn_load:could not load the shared library: filename(libproviders.so): libproviders.so: cannot open shared object file: No such file or directory, error:25070067:DSO support routines:DSO_load:could not load the shared library, error:0E07506E:configuration file routines:module_load_dso:error loading dso: module=providers, path=providers, error:0E076071:configuration file routines:module_run:unknown module name: module=providers: user=<>, rip=5.6.7.8, lip=1.2.3.4, session=<5vd2tm/faYY+1vxS> May 20 13:22:59 mail dovecot: imap-login: Disconnected: TLS initialization failed. (no auth attempts in 0 secs): user=<>, rip=5.6.7.8, lip=1.2.3.4, session=<5vd2tm/faYY+1vxS>
Processed: transmission: diff for NMU version 3.00-2.1
Processing control commands: > tags 1006584 + patch Bug #1006584 [src:transmission] transmission: FTBFS with OpenSSL 3.0 Added tag(s) patch. > tags 1006584 + pending Bug #1006584 [src:transmission] transmission: FTBFS with OpenSSL 3.0 Added tag(s) pending. -- 1006584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006584: transmission: diff for NMU version 3.00-2.1
Control: tags 1006584 + patch
Control: tags 1006584 + pending
Dear maintainer,
I've prepared an NMU for transmission (versioned as 3.00-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru transmission-3.00/debian/changelog transmission-3.00/debian/changelog
--- transmission-3.00/debian/changelog 2021-12-19 06:23:43.0 +0100
+++ transmission-3.00/debian/changelog 2022-05-21 09:22:10.0 +0200
@@ -1,3 +1,11 @@
+transmission (3.00-2.1) unstable; urgency=low
+
+ [ Steve Langasek ]
+ * debian/patches/openssl3-compat.patch: Compatibility with OpenSSL 3.
+(Closes: #1006584)
+
+ -- Sebastian Ramacher Sat, 21 May 2022 09:22:10 +0200
+
transmission (3.00-2) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru transmission-3.00/debian/patches/openssl3-compat.patch transmission-3.00/debian/patches/openssl3-compat.patch
--- transmission-3.00/debian/patches/openssl3-compat.patch 1970-01-01 01:00:00.0 +0100
+++ transmission-3.00/debian/patches/openssl3-compat.patch 2022-05-21 09:21:15.0 +0200
@@ -0,0 +1,130 @@
+Description: Compatibility with OpenSSL 3
+ We rely on RC4 because of the torrent protocol we're implementing, but this
+ is no longer available in the default provider.
+Author: Steve Langasek
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1946215
+Last-Update: 2021-12-13
+Forwarded: no
+
+Index: transmission-3.00/libtransmission/crypto-utils-openssl.c
+===
+--- transmission-3.00.orig/libtransmission/crypto-utils-openssl.c
transmission-3.00/libtransmission/crypto-utils-openssl.c
+@@ -20,6 +20,9 @@
+ #include
+ #include
+ #include
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++#include
++#endif
+
+ #include "transmission.h"
+ #include "crypto-utils.h"
+@@ -182,46 +185,86 @@
+
+ #endif
+
++typedef struct tr_rc4_ctx {
++EVP_CIPHER_CTX *cipher_ctx;
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++OSSL_LIB_CTX *lib_ctx;
++#endif
++} tr_rc4_ctx;
++
+ tr_rc4_ctx_t tr_rc4_new(void)
+ {
+-EVP_CIPHER_CTX* handle = EVP_CIPHER_CTX_new();
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++OSSL_PROVIDER *legacy_provider = NULL;
++OSSL_PROVIDER *default_provider = NULL;
++#endif
++const EVP_CIPHER *cipher;
+
+-if (check_result(EVP_CipherInit_ex(handle, EVP_rc4(), NULL, NULL, NULL, -1)))
++tr_rc4_ctx *handle = malloc(sizeof(tr_rc4_ctx));
++
++handle->cipher_ctx = EVP_CIPHER_CTX_new();
++
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++handle->lib_ctx = OSSL_LIB_CTX_new();
++TR_ASSERT(handle->lib_ctx);
++legacy_provider = OSSL_PROVIDER_load(handle->lib_ctx, "legacy");
++TR_ASSERT(legacy_provider);
++default_provider = OSSL_PROVIDER_load(handle->lib_ctx, "default");
++TR_ASSERT(default_provider);
++
++cipher = EVP_CIPHER_fetch(handle->lib_ctx, "RC4", NULL);
++#else
++cipher = EVP_rc4();
++#endif
++
++if (check_result(EVP_CipherInit_ex(handle->cipher_ctx, cipher, NULL, NULL,
++ NULL, -1)))
+ {
+ return handle;
+ }
+
+-EVP_CIPHER_CTX_free(handle);
++EVP_CIPHER_CTX_free(handle->cipher_ctx);
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++OSSL_LIB_CTX_free(handle->lib_ctx);
++#endif
+ return NULL;
+ }
+
+-void tr_rc4_free(tr_rc4_ctx_t handle)
++void tr_rc4_free(tr_rc4_ctx_t h)
+ {
+-if (handle == NULL)
++if (h == NULL)
+ {
+ return;
+ }
+
+-EVP_CIPHER_CTX_free(handle);
++tr_rc4_ctx *handle = (tr_rc4_ctx *)h;
++
++EVP_CIPHER_CTX_free(handle->cipher_ctx);
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++OSSL_LIB_CTX_free(handle->lib_ctx);
++#endif
++free(handle);
+ }
+
+-void tr_rc4_set_key(tr_rc4_ctx_t handle, uint8_t const* key, size_t key_length)
++void tr_rc4_set_key(tr_rc4_ctx_t h, uint8_t const* key, size_t key_length)
+ {
+-TR_ASSERT(handle != NULL);
++TR_ASSERT(h != NULL);
+ TR_ASSERT(key != NULL);
+
+-if (!check_result(EVP_CIPHER_CTX_set_key_length(handle, key_length)))
++tr_rc4_ctx *handle = (tr_rc4_ctx *)h;
++if (!check_result(EVP_CIPHER_CTX_set_key_length(handle->cipher_ctx, key_length)))
+ {
+ return;
+ }
+
+-check_result(EVP_CipherInit_ex(handle, NULL, NULL, key, NULL, -1));
++check_result(EVP_CipherInit_ex(handle->cipher_ctx, NULL, NULL, key, NULL, -1));
+ }
+
+-void tr_rc4_process(tr_rc4_ctx_t handle, void const* input, void* output, size_t length)
++void tr_rc4_process(tr_rc4_ctx_t h, void const* input, void* output, size_t length)
+ {
+-TR_ASSERT(handle != NULL);
++TR_ASSERT(h != NULL);
+
++tr_rc4_ctx *handle = (tr_rc4_ctx *)h;
+ if (length == 0)
+ {
+ return;
+@@ -232,7 +275,7 @@
+
+ int output_length;
+
+-check_result(EVP_CipherUpdate(handle, output, _length, input, length));
++check_result(EVP_CipherUpdate(handle->cipher_ctx, output, _length, input,
Bug#997511: marked as done (softhsm2: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Sat, 21 May 2022 07:04:53 + with message-id and subject line Bug#997511: fixed in softhsm2 2.6.1-2.1 has caused the Debian Bug report #997511, regarding softhsm2: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: softhsm2 Version: 2.6.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[6]: Entering directory '/<>/src/lib/test' > FAIL: p11test > >SoftHSM 2.6.1: src/lib/test/test-suite.log > > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: p11test > = > > F...F...F..F.F..F...F..F.F.F.F.F.F.F..F..F...F.F.F..F..F.F.F..F...F...F.F.F...FF.FF..F.FF..F.F.F.F...F.F.F.F.F.F...F.FF.F > > > !!!FAILURES!!! > Test Results: > Run: 77 Failures: 13 Errors: 0 > > > 1) test: InfoTests::testGetSlotInfo (F) line: 142 InfoTests.cpp > assertion failed > - Expression: rv == CKR_ARGUMENTS_BAD > > > 2) test: InfoTests::testWaitForSlotEvent (F) line: 124 TestsNoPINInitBase.cpp > setUp() failed > - equality assertion failed > - Expected: 0 > - Actual : 48 > > > 3) test: ObjectTests::testCopyObject (F) line: 939 ObjectTests.cpp > assertion failed > - Expression: rv == CKR_OK > > > 4) test: ObjectTests::testDestroyObject (F) line: 124 TestsNoPINInitBase.cpp > setUp() failed > - equality assertion failed > - Expected: 0 > - Actual : 48 > > > 5) test: ObjectTests::testSetAttributeValue (F) line: 1322 ObjectTests.cpp > assertion failed > - Expression: rv==CKR_OK > > > 6) test: ObjectTests::testGenerateKeys (F) line: 1511 ObjectTests.cpp > assertion failed > - Expression: rv==CKR_OK > > > 7) test: ObjectTests::testGetInvalidAttribute (F) line: 1954 ObjectTests.cpp > assertion failed > - Expression: rv == CKR_OK > > > 8) test: SignVerifyTests::testEcSignVerify (F) line: 530 SignVerifyTests.cpp > assertion failed > - Expression: rv == CKR_OK > > > 9) test: SignVerifyTests::testEdSignVerify with parameter: Ed25519 (F) line: > 247 SignVerifyTests.cpp > assertion failed > - Expression: rv==CKR_OK > > > 10) test: SignVerifyTests::testMacSignVerify (F) line: 770 SignVerifyTests.cpp > assertion failed > - Expression: rv==CKR_OK > > > 11) test: SymmetricAlgorithmTests::testAesEncryptDecrypt (F) line: 728 > SymmetricAlgorithmTests.cpp > assertion failed > - Expression: rv==CKR_OK > > > 12) test: SymmetricAlgorithmTests::testDesEncryptDecrypt (F) line: 48 > TestsBase.cpp > setUp() failed > - assertion failed > - Expression: CRYPTOKI_F_PTR( C_InitPIN(hSession, m_userPin1, > m_userPin1Length)==CKR_OK ) > > > 13) test: UserTests::testSetPIN (F) line: 239 UserTests.cpp > assertion failed > - Expression: rv == CKR_OK > > > F. > > > !!!FAILURES!!! > Test Results: > Run: 77 Failures: 17 Errors: 0 > > > 1) test: InfoTests::testGetSlotInfo (F) line: 124 TestsNoPINInitBase.cpp > setUp() failed > - equality assertion failed > - Expected: 0 > - Actual : 48 > > > 2) test: InfoTests::testGetSlotInfoAlt (F) line: 187 InfoTests.cpp > assertion failed > - Expression: rv == CKR_ARGUMENTS_BAD > > > 3) test: ObjectTests::testCreateObject (F) line: 754 ObjectTests.cpp > assertion failed > - Expression: rv==CKR_OK > > > 4) test: ObjectTests::testDestroyObject (F) line: 1119 ObjectTests.cpp > assertion failed > - Expression: rv == CKR_SESSION_READ_ONLY > > > 5) test: ObjectTests::testGetObjectSize (F) line: 124 TestsNoPINInitBase.cpp > setUp() failed > - equality assertion failed > - Expected: 0 > - Actual : 5 > > > 6) test: ObjectTests::testGetAttributeValue (F) line: 1214 ObjectTests.cpp > assertion failed > - Expression: rv == CKR_OK > > > 7) test: ObjectTests::testSetAttributeValue (F) line: 79 > TestsNoPINInitBase.cpp > setUp() failed > - assertion failed > - Expression: CRYPTOKI_F_PTR( C_GetTokenInfo(*i, )==CKR_OK ) > > > 8) test: ObjectTests::testFindObjects (F) line: 1432 ObjectTests.cpp > assertion failed > -
Bug#997511: softhsm2: diff for NMU version 2.6.1-2.1
On 2022-05-21 00:10:47 +0200, Ondřej Surý wrote:
> Hi,
>
> feel free to upload the NMU directly, I think I do have lowNMU threshold set
> (somewhere)
Thanks, done!
Cheers
>
> --
> Ondřej Surý (He/Him)
>
> > On 20. 5. 2022, at 23:27, Sebastian Ramacher wrote:
> >
> > Control: tags 997511 + patch
> > Control: tags 997511 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for softhsm2 (versioned as 2.6.1-2.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> >
> > Cheers
> > --
> > Sebastian Ramacher
> diff -Nru softhsm2-2.6.1/debian/changelog softhsm2-2.6.1/debian/changelog
> --- softhsm2-2.6.1/debian/changelog 2020-05-15 11:41:43.0 +0200
> +++ softhsm2-2.6.1/debian/changelog 2022-05-20 23:23:22.0 +0200
> @@ -1,3 +1,10 @@
> +softhsm2 (2.6.1-2.1) unstable; urgency=medium
> +
> + [ William 'jawn-smith' Wilson ]
> + * Disable some tests that are failing with openssl v3 (Closes: #997511)
> +
> + -- Sebastian Ramacher Fri, 20 May 2022 23:23:22
> +0200
> +
> softhsm2 (2.6.1-2) unstable; urgency=medium
>
>* Explicitly enable ECC and EDDSA curves (Closes: #942419)
> diff -Nru softhsm2-2.6.1/debian/patches/0003-fix-ftbfs-with-opensslv3.patch
> softhsm2-2.6.1/debian/patches/0003-fix-ftbfs-with-opensslv3.patch
> --- softhsm2-2.6.1/debian/patches/0003-fix-ftbfs-with-opensslv3.patch
> 1970-01-01 01:00:00.0 +0100
> +++ softhsm2-2.6.1/debian/patches/0003-fix-ftbfs-with-opensslv3.patch
> 2022-05-20 23:14:03.0 +0200
> @@ -0,0 +1,1103 @@
> +From 643f061e6fbe04552a2c49bd00528e61a9a77064 Mon Sep 17 00:00:00 2001
> +From: Alexander Bokovoy
> +Date: Wed, 26 May 2021 20:03:25 +0300
> +Subject: [PATCH 1/4] openssl 3.0: Run DES tests only if OpenSSL allows it
> +
> +OpenSSL 3.0 moves DES into a legacy provider which has to be loaded
> +explicitly. By default, it will not be loaded and DES methods in tests
> +will fail. Nest test blocks under successful initialization.
> +
> +Signed-off-by: Alexander Bokovoy
> +---
> + src/lib/crypto/test/DESTests.cpp | 350 ---
> + 1 file changed, 182 insertions(+), 168 deletions(-)
> +
> +Index: softhsm2-2.6.1/src/lib/crypto/test/DESTests.cpp
> +===
> +--- softhsm2-2.6.1.orig/src/lib/crypto/test/DESTests.cpp
> softhsm2-2.6.1/src/lib/crypto/test/DESTests.cpp
> +@@ -259,54 +259,58 @@
> +
> + // Now, do the same thing using our DES implementation
> + shsmCipherText.wipe();
> +-CPPUNIT_ASSERT(des->encryptInit(,
> SymMode::CBC, IV));
> ++if (des->encryptInit(, SymMode::CBC, IV)) {
> +
> +-CPPUNIT_ASSERT(des->encryptUpdate(plainText, OB));
> +-shsmCipherText += OB;
> ++CPPUNIT_ASSERT(des->encryptUpdate(plainText,
> OB));
> ++shsmCipherText += OB;
> +
> +-CPPUNIT_ASSERT(des->encryptFinal(OB));
> +-shsmCipherText += OB;
> ++CPPUNIT_ASSERT(des->encryptFinal(OB));
> ++shsmCipherText += OB;
> +
> +-CPPUNIT_ASSERT(shsmCipherText == cipherText);
> ++CPPUNIT_ASSERT(shsmCipherText == cipherText);
> +
> +-// Check that we can get the plain text
> +-shsmPlainText.wipe();
> +-CPPUNIT_ASSERT(des->decryptInit(,
> SymMode::CBC, IV));
> ++// Check that we can get the plain text
> ++shsmPlainText.wipe();
> ++CPPUNIT_ASSERT(des->decryptInit(,
> SymMode::CBC, IV));
> +
> +-CPPUNIT_ASSERT(des->decryptUpdate(shsmCipherText, OB));
> +-shsmPlainText += OB;
> ++
> CPPUNIT_ASSERT(des->decryptUpdate(shsmCipherText, OB));
> ++shsmPlainText += OB;
> +
> +-CPPUNIT_ASSERT(des->decryptFinal(OB));
> +-shsmPlainText += OB;
> ++CPPUNIT_ASSERT(des->decryptFinal(OB));
> ++shsmPlainText += OB;
> +
> +-CPPUNIT_ASSERT(shsmPlainText == plainText);
> ++CPPUNIT_ASSERT(shsmPlainText == plainText);
> ++
> ++}
> +
> + // Test 112-bit key
> + cipherText = ByteString(testResult[i][j][1]);
> +
> + // Now, do the same thing using our DES implementation
> + shsmCipherText.wipe();
> +-CPPUNIT_ASSERT(des->encryptInit(,
> SymMode::CBC, IV));
> ++if (des->encryptInit(, SymMode::CBC, IV)) {
> +
> +-CPPUNIT_ASSERT(des->encryptUpdate(plainText, OB));
> +-
