Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #12617
| From | tony mancill <tmancill@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.java |
| Subject | Re: RFS: zstd-jni-java/1.5.4-2+ds-1 [Team] -- JNI bindings for Zstd (Architecture-specific files) |
| Date | 2023-03-24 06:50 +0100 |
| Message-ID | <GcItj-eGtf-3@gated-at.bofh.it> (permalink) |
| References | <GcItj-eGtf-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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
Back to linux.debian.maint.java | Previous | Next | Find similar
Re: RFS: zstd-jni-java/1.5.4-2+ds-1 [Team] -- JNI bindings for Zstd (Architecture-specific files) tony mancill <tmancill@debian.org> - 2023-03-24 06:50 +0100
csiph-web