On Tue, Mar 21, 2023 at 01:13:35AM +0000, sun min wrote:

Package: sponsorship-requests

zstd-jni-java (1.5.4-2+ds-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
* Update debian/libzstd-jni1.symbols.

Hello sun min,

Should this upload target unstable or experimental? (Unless you plan to
file an unblock request with the release team for bookworm, I think it
should experimental.)

If that's okay with you, I will update the changelog before sponsoring
the upload.

Cheers,
tony

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmQaf6IACgkQIdIFiZdL PpYauhAAs9wvXimxEb1OyGDMJidZfWfauC7gxAbPDDPrO37/h43d2hqQ3vY2UkJ4 RRbqRpaCCzHsRQT5k2gPiAipdL1GvSc6O6nmyzCBqoxYACzD5ZDU6vkDBI2+ht3Q ZDuOkTB/2MWhH7LTD8hW06NPsVuhq2BGWjDfFbPNgslbEnGKmOMn9wE4iLKtn3Dr cKTUcotU5SL/lXvhvxP3MyZkMAly+LKA43BDKt1eSEstqpDDLXdkBX80oV4x9Sdn 47Qs7Gdd+QSk8ifHUoUPQQp6hzmvAPc+J7GbwrCeFSTpju5XMhovTx6TmaDDB2M8 m3WgCig0y4BD+2a4a+bUWYm3RAwij/llhB02+TcPY/kA4+dphqh7LG3tltE2Iaam F4EJPddrX5D6TrEsPdwOvDi1UwKG3ZGC4oUvqsVbLh0WatkpopNlS9IYhkRYcr+f /4t6QEnxzQYp/4hBrxpCLuuMzra1jtuAJEx3BwCG8JfSCN+tpl6Ap6U7rmX2gRVl PjLbgyBrIxRWuqn74SE2VSn5k0g59smc6ZSJwpenXTvPgeke4Kbrgt4NboX/E8I5 OwoyLBPT1JI9RqObvBWUAJPmmrymykMVVSmKHGIav6x71Zi4NIqc1YDWfvmn36mg riJKUwgedkst9KgNczxdG6rrBu8gZ7A/VA+gwtsP0BYtnPcCT90=
=jXUw
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi sun min,

On Fri, Mar 24, 2023 at 03:01:00AM +0000, sun min wrote:

Hi, all

Could someone have a look at the build status of zstd-jni-java[1] ?

It seems that the official build was failed while my local build is okay.

Yes, I will take a look. I also built the package successfully before sponsoring the upload. However, I didn't build it in the exact way that
the autobuilders do.

This patch "debian/patches/modify_pom.patch" defines maven-resources-plugin use version 3.1.0, which is not the latest versin(3.3.0).

Should this be the problem to cause the build failure ?

I am able to reproduce the build failure when I force a build of
--arch-any in combination with --no-arch-all. For example, this build consistently fails:

sbuild --chroot=unstable --dist=unstable --arch-any --no-arch-all

This build is always successful:

sbuild --chroot=unstable --dist=unstable --arch-any --arch-all

And this build is also successful:

sbuild --chroot=unstable --dist=unstable --no-arch-any --arch-all

Let me know if you have any problems reproducing this locally. It might
be helpful to invoke the build with DH_VERBOSE=1.

Cheers,
tony

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmQdOYcACgkQIdIFiZdL Ppba7RAAnn/1XMcbuCSNWyHn3TcPFahtcPOpMGcnEk+QJq19UKySZwqknweRSkeb x2u613tl8JFVCwngFsfDBXF8XofoAOPoCiyVRM34VxKBxARRK3Jw/7ZdWNQfJGCo G8OhhWsCGtYxI05uLDvIt00FjL2GpDRmmXI/VjNyjhfDwoNZ8riIU7zhyMAxnloK /qrOca6PYPjQnIvFvP9jWzU0CqqsM9QK7Bx1FhZPES/p9l/s0AodUb7TXVQgI3ow xFNk/Keo9Ze0MRVKfTOjfGibXcqXpa2FyvExVwYBBv/gCCvgXYK3lqFwQlFRZamC hSudsHryeYhubpOXRcSD2fBYPW6iPvv31Lt36qAd1xbAbGXXT8/dt+ox67F6oUzF cZWltZ1O4Q/f6+WB6L6N4VnDdF5LDefrY9wJqNipaunxq1M7EjLxVS0uBovyzCaC 62UPBqSbHJcz4dRQZwm4aXI2QfUNkxLPNzDeo3obB/7+jUdy4pGoB3ZuGEoU1+Zr BrJzLoeZlu6z8wtM1hy2ApDVqBYyXSCtebUJThdM95PWYJoHacm3xnPN45HYGMiy 67B290KR5Skzsd8cwtiYoCFzyzHu+dDHES3D+0DWyFBRiY293xxvhyk2K5E2va/O M9cwNZnN/7HBWJ0ww5UWbjyEOIJAaJp6ExLXzKkagl0fEXXkq/w=
=ld+W
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)