On Sun, Dec 10, 2023 at 08:18:03PM +0100, Santiago Vila wrote: > Package: src:libjose4j-java > Version: 0.7.12-2 > Severity: serious > Tags: ftbfs > > [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.063 > s <<< FAILURE! - in org.jose4j.jwk.EllipticCurveJsonWebKeyTest > [ERROR] > testParseExampleWithPrivate256(org.jose4j.jwk.EllipticCurveJsonWebKeyTest) > Time elapsed: 0.031 s <<< FAILURE! > java.lang.AssertionError: > expected:<EC Private Key > [8b:e2:14:0f:3a:17:e9:25:d1:ae:df:18:a3:b2:9a:fd:63:04:41:11] > X: > 7fcdce2770f6c45d4183cbee6fdb4b7b580733357be9ef13bacf6e3c7bd15445 > Y: > c7f144cd1bbd9b7e872cdfedb9eeb9f4b3695d6ea90b24ad8a4623288588e5ad > > but was:<sun.security.ec.ECPrivateKeyImpl@f7754045> > at > org.jose4j.jwk.EllipticCurveJsonWebKeyTest.testParseExampleWithPrivate256(EllipticCurveJsonWebKeyTest.java:53) > ... > > If required, the full build log is available here: > > https://people.debian.org/~sanvila/build-logs/202312/
Thank you for making this available. > About the archive rebuild: The build was made using virtual machines > from AWS, with enough memory, enough disk, and either one or two > CPUs, using a reduced chroot with only build-essential packages. I'm not able to reproduce this locally, and the only potentially relevant difference I see between the AWS testbed and my local environment is that I am running Intel and the AWS system is AMD. > If you could not reproduce the bug please contact me privately, as I > am willing to provide ssh access to a virtual machine where the bug is > fully reproducible. Will do, as time permits. This package has a low popcon, and is a build-dependency of libcallstats-java, which also has a low popcon, and has no reverse dependencies. I believe both are part of an effort to get Jitsi back into Debian. If that's not likely to happen, an alternative is to file RM bugs for both of them. (I am adding the Uploaders to the cc:) Thanks, tony
signature.asc
Description: PGP signature
