|
Hi,tony:
Infact,my local build command is as follows:
sudo sbuild --source --force-orig-source --arch=amd64 -c sid-amd64-sbuild
I tried similar command with yours locally, it does always fail:
sudo sbuild --source --force-orig-source --dist=sid --arch-any --no-arch-all -c sid-amd64-sbuild
The above build command can pass if I patch the debian/patches/modify_pom.patch based on the Error infomation.
--- a/debian/patches/modify_pom.patch
+++ b/debian/patches/modify_pom.patch
@@ -1,7 +1,7 @@
Description: Modify upstream pom to allow Debian build
Author: Olek Wojnar <olek@debian.org>
Forwarded: not-needed
-Last-Update: 2022-10-20
+Last-Update: 2023-03-27
--- a/pom.xml
+++ b/pom.xml
@@ -28,7 +28,7 @@ Last-Update: 2022-10-20
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
-+ <version>3.8.1</version>
++ <version>3.10.1</version>
+ <configuration>
+ <source>1.8</source>
+ <target>1.8</target>
@@ -46,7 +46,7 @@ Last-Update: 2022-10-20
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-resources-plugin</artifactId>
-+ <version>3.1.0</version>
++ <version>3.3.0</version>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
I guess we can't get the exact build command of official build and how can we address this kind of bug ?
From: tony mancill on behalf of tony mancill Sent: Friday, March 24, 2023 13:47 To: sun min Cc: debian-java@lists.debian.org Subject: Re: RFS: zstd-jni-java/1.5.4-2+ds-1 [Team] -- JNI bindings for Zstd (Architecture-specific files) 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 |