Bug#1050944: jtreg6: please make the build reproducible

2023-09-01 Thread Chris Lamb
Hey tony & Vagrant, > > Maybe this should be restricted to only make it writeable to the > > user ... e.g. chmod u+w or similar? Ah, I mistakenly confused "+w" as a synonym for "u+w". (I used to know all the octal codes like the back of my hand, but there seems to be little call to use them in

Bug#1050944: jtreg6: please make the build reproducible

2023-08-31 Thread tony mancill
On Thu, Aug 31, 2023 at 02:58:47PM -0700, Vagrant Cascadian wrote: > On 2023-08-31, Chris Lamb wrote: > > 2. The jtreg.jar file was being generated with 444 (read-only) > > permissions. This meant that strip-determinism could not fixup the > > file modification times of the files within that

Bug#1050944: jtreg6: please make the build reproducible

2023-08-31 Thread Vagrant Cascadian
On 2023-08-31, Chris Lamb wrote: > 2. The jtreg.jar file was being generated with 444 (read-only) > permissions. This meant that strip-determinism could not fixup the > file modification times of the files within that archive. It was > actually printing: "dh_strip_nondeterminism: warning: Ignoring

Bug#1050944: jtreg6: please make the build reproducible

2023-08-31 Thread Chris Lamb
Source: jtreg6 Version: 6.2+1-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that jtreg6 could not be built