Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #12791
| From | Mechtilde <ooo@mechtilde.de> |
|---|---|
| Newsgroups | linux.debian.maint.java |
| Subject | Re: (java) Builds not reproducible on armhf |
| Date | 2024-08-24 21:40 +0200 |
| Message-ID | <Jf4M9-7mFv-13@gated-at.bofh.it> (permalink) |
| References | <IG6pr-eAHn-3@gated-at.bofh.it> <IGBCV-eTt4-1@gated-at.bofh.it> <Jf3ZL-7mas-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hello, now I'm able to test it at amdahl.debian.org There I get te same timestanp I get at my amd64 maschine and at my pbuilder ARCH=armhf chroot. So I have no idea to reproduce and to fix it. Kind regards Am 24.08.24 um 20:30 schrieb Mechtilde Stehmann: > Hello, > > in the meantime I did some more tests to find the reason for it. > > I build it again with pbuilder specifying ARCH=armhf and get the right > date for the pom file (same date as the amd64 build) > > Now I think I need access to an armhf box to test it natively. > > What should I do to get temporary. > > Kind regards > > Mechtilde > > Am 21.05.24 um 19:20 schrieb Vagrant Cascadian: >> On 2024-05-20, Mechtilde Stehmann wrote: >>> I want to clean up my Java packages. >>> >>> There are several with FTBR. I found that the day of the *.poms s a date >>> from 1970. >>> >>> for example they are the packages >>> >>> vinnie >> >> Looking at the history for vinnie: >> >> https://tests.reproducible-builds.org/debian/history/armhf/vinnie.html >> >> It is only very recently that this started happening (2024-05-04) >> without source changes in vinnie itself, so I would suspect some change >> in the toolchain used to produce the .pom files? >> >> commons-email is similar, although starting 2024-04-04: >> >> >> https://tests.reproducible-builds.org/debian/history/armhf/commons-email.html >> >> ez-vcard is similar too, starting 2024-04-20: >> >> >> https://tests.reproducible-builds.org/debian/rb-pkg/trixie/armhf/diffoscope-results/ez-vcard.html >> >> Although some of those builds also have differences in some xz >> contents... might just be related to the timestamp differences. >> >> >> Wild hunch is one build is run on a 64-bit kernel (without a linux32 >> personality) and one build on a 32-bit kernel... that is one of the main >> differences between these armhf test builds and builds on other >> architectures, where this does not seem to happen... >> >> >> live well, >> vagrant > -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Back to linux.debian.maint.java | Previous | Next — Previous in thread | Find similar
Builds not reproducible on armhf Mechtilde Stehmann <mechtilde@debian.org> - 2024-05-20 10:20 +0200
Re: Builds not reproducible on armhf Thorsten Glaser <t.glaser@qvest-digital.com> - 2024-05-20 18:20 +0200
Re: (java) Builds not reproducible on armhf Vagrant Cascadian <vagrant@reproducible-builds.org> - 2024-05-21 19:40 +0200
Re: (java) Builds not reproducible on armhf Mechtilde Stehmann <mechtilde@debian.org> - 2024-08-24 21:00 +0200
Re: (java) Builds not reproducible on armhf Mechtilde <ooo@mechtilde.de> - 2024-08-24 21:40 +0200
csiph-web