On 2023-04-17, Aurelien Jarno wrote: > On 2023-04-16 15:16, Vagrant Cascadian wrote: >> On 2023-04-16, Aurelien Jarno wrote: >> > I have tried adding a simple .sbuildrc defining $build_path to '/build' >> > to zandonai.d.o. Unfortunately while it more or less does what you want >> > for the build path, it completely clutter the logs, as any text matching >> > "build" is now replaced by "<<BUILDDIR>>": >> > >> > https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring&arch=s390x&ver=42.1-1%2Bb2&stamp=1681671508&raw=0 >> >> > >> > I guess one option is to use a build path unlikely to match any string >> > from a build log, like with the randomized directory. Something like >> > "/build/reproducible-path/"? >> >> Just for clarity, then the the PKGBUILDIR would end up being >> /build/reproducible-path/PACKAGE-VERSION ? That works! Or something even >> shorter ... e.g. /build/path/PACKAGE-VERSION or >> /build/debian/PACKAGE-VERSION ? Really, the 2nd directory matters >> little, as long as it is predictible. :) > > Yes, setting $build_path to '/build/debian' indeed means that > PKGBUILDDIR is /build/debian/PACKAGE-VERSION. > > Unfortunately the string 'build/debian' appears in a few build logs: > 0ad ... > xtables-addons > > Do you have other short suggestions? Do we want to show it has been > built on a debian buildd? In that case /build/debian-buildd might do it.
Well, then a verification build using reproducible builds will be "lying" that it is built on a buildd. :) Hrm. "DeBiAn" ? Kind of hard on the eyes. Less ugly, "/build/Debian"? Still somewhat likely to to have inappropriate matches? "fixedpath"? Or just go with "reproducible-path" as it is not tragically long if it seems unlikely to match inappropriately. :) Is sbuild replacing the string mandatory; could we do without that feature? What would we loose? Might require patching sbuild... live well, vagrant
signature.asc
Description: PGP signature
