Followup-For: Bug #859572
X-Debbugs-Cc: solo-debianb...@goeswhere.com,
bugs-debian-20170...@james-ross.co.uk
Control: reassign -1 libxml2
Control: affects -1 libxslt1.1 xsltproc
Control: forwarded -1 https://gitlab.gnome.org/GNOME/libxslt/-/issues/37
Control: tags -1 fixed-upstream
Control: fixed
A correction for a mistake in my previous message:
> Because Debian builds packages from a fixed build path, neither the
> 'reprotest'
> utility in Salsa-CI, nor the Reproducible Builds team's package test
> infrastructure for Debian[1] currently check for equivalent binary package
> output from
Control: severity -1 wishlist
Dear Maintainer,
Because Debian builds packages from a fixed build path, neither the 'reprotest'
utility in Salsa-CI, nor the Reproducible Builds team's package test
infrastructure for Debian[1] currently check for equivalent binary package
output from differing
Control: severity -1 wishlist
Dear Maintainer,
Because Debian builds packages from a fixed build path, neither the 'reprotest'
utility in Salsa-CI, nor the Reproducible Builds team's package test
infrastructure for Debian[1] currently check for equivalent binary package
output from differing
Control: severity -1 wishlist
Dear Maintainer,
Because Debian builds packages from a fixed build path, neither the 'reprotest'
utility in Salsa-CI, nor the Reproducible Builds team's package test
infrastructure for Debian[1] currently check for equivalent binary package
output from differing
Control: severity -1 wishlist
Dear Maintainer,
Currently, Debian's buildd and also the Reproducible Builds team's testing
infrastructure[1] both use a fixed build path when building binary packages.
This means that your package will pass current reproducibility tests; however
we believe that
6 matches
Mail list logo
