-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.3.1 debbuild failures on 22.04 arm* #484
Comments
Uh. This is what I think is happening:
Why the hashes of both packages that are purely transitional do not match is the key point here. Need to make some changes to get the packages out of the build and compare with the ones in the repo. As a workaround, we can use a branch to skip the autopkgtest. |
Umm, binary diff of the .debs. First one is from the build in Jenkins and the second one from the repository: /tmp ❯ diffoscope libignition-common5-av_5.3.1-1~jammy_all.deb ~/Downloads/libignition-common5-av_5.3.1-1~jammy_all.deb
--- libignition-common5-av_5.3.1-1~jammy_all.deb
+++ /home/jrivero/Downloads/libignition-common5-av_5.3.1-1~jammy_all.deb
├── file list
│ @@ -1,3 +1,3 @@
│ -rw-r--r-- 0 0 0 4 2022-11-18 05:41:44.000000 debian-binary
│ --rw-r--r-- 0 0 0 572 2022-11-18 05:41:44.000000 control.tar.xz
│ --rw-r--r-- 0 0 0 8072 2022-11-18 05:41:44.000000 data.tar.xz
│ +-rw-r--r-- 0 0 0 568 2022-11-18 05:41:44.000000 control.tar.xz
│ +-rw-r--r-- 0 0 0 8076 2022-11-18 05:41:44.000000 data.tar.xz
├── control.tar.xz
│ ├── control.tar
│ │ ├── file list
│ │ │ @@ -1,3 +1,3 @@
│ │ │ -drwxr-xr-x 0 root (0) root (0) 0 2022-11-17 22:21:12.000000 ./
│ │ │ --rw-r--r-- 0 root (0) root (0) 355 2022-11-17 22:21:11.000000 ./control
│ │ │ --rw-r--r-- 0 root (0) root (0) 172 2022-11-17 22:21:12.000000 ./md5sums
│ │ │ +drwxr-xr-x 0 root (0) root (0) 0 2022-11-18 05:41:44.000000 ./
│ │ │ +-rw-r--r-- 0 root (0) root (0) 355 2022-11-18 05:41:44.000000 ./control
│ │ │ +-rw-r--r-- 0 root (0) root (0) 172 2022-11-18 05:41:44.000000 ./md5sums
├── data.tar.xz
│ ├── data.tar
│ │ ├── file list
│ │ │ @@ -1,7 +1,7 @@
│ │ │ -drwxr-xr-x 0 root (0) root (0) 0 2022-11-17 22:21:10.000000 ./
│ │ │ -drwxr-xr-x 0 root (0) root (0) 0 2022-11-17 22:21:01.000000 ./usr/
│ │ │ -drwxr-xr-x 0 root (0) root (0) 0 2022-11-17 22:21:01.000000 ./usr/share/
│ │ │ -drwxr-xr-x 0 root (0) root (0) 0 2022-11-17 22:21:01.000000 ./usr/share/doc/
│ │ │ -drwxr-xr-x 0 root (0) root (0) 0 2022-11-17 22:21:03.000000 ./usr/share/doc/libignition-common5-av/
│ │ │ --rw-r--r-- 0 root (0) root (0) 475 2022-11-17 22:14:08.000000 ./usr/share/doc/libignition-common5-av/changelog.Debian.gz
│ │ │ --rw-r--r-- 0 root (0) root (0) 24723 2022-11-17 22:14:08.000000 ./usr/share/doc/libignition-common5-av/copyright
│ │ │ +drwxr-xr-x 0 root (0) root (0) 0 2022-11-18 05:41:44.000000 ./
│ │ │ +drwxr-xr-x 0 root (0) root (0) 0 2022-11-18 05:41:44.000000 ./usr/
│ │ │ +drwxr-xr-x 0 root (0) root (0) 0 2022-11-18 05:41:44.000000 ./usr/share/
│ │ │ +drwxr-xr-x 0 root (0) root (0) 0 2022-11-18 05:41:44.000000 ./usr/share/doc/
│ │ │ +drwxr-xr-x 0 root (0) root (0) 0 2022-11-18 05:41:44.000000 ./usr/share/doc/libignition-common5-av/
│ │ │ +-rw-r--r-- 0 root (0) root (0) 475 2022-11-18 05:41:44.000000 ./usr/share/doc/libignition-common5-av/changelog.Debian.gz
│ │ │ +-rw-r--r-- 0 root (0) root (0) 24723 2022-11-18 05:41:44.000000 ./usr/share/doc/libignition-common5-av/copyright There are four bytes of difference between control.tar.xz files although the contain the exactly the same files with the same size. |
I've been looking into this trying to find a workaround for keeping autotestpkg running on ARM but avoiding to fail on problems with the hash sum check but I'm pretty sure that it is impossible to pass an option to apt to ignore that error. We can manually filter the log and make if fail if there are errors that are not the one we expect but probably does not worth the effort. I'm going to disable autopkgtest on ARM, we can rely on the amd64 check. |
Environment
Description
libignition-common5*
packagesSteps to reproduce
Output
The text was updated successfully, but these errors were encountered: