On 2021-03-02, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0] we noticed that > python-scrapy could not be built reproducibly. > > This is because it uses the current build year when building the > documentation which, of course, changes depending which year you > build the software. > > Patch attached that uses SOURCE_DATE_EPOCH [1] instead.
In the upstream pull request: https://github.com/scrapy/scrapy/pull/5019 It was suggested drop the practice of using the build year at all and manually updating the year... though upstream did not go so far as to actually do that as far as I can tell. Perhaps a really simple patch with the most recent copyright year hard-coded that needs to be updated alongside debian/copyright would be acceptible? It could also check to make sure the most recent year mentioned in debian/copyright matches the patch year, if you really wanted to make sure they stayed in sync. Alternately, going with the SOURCE_DATE_EPOCH patch for now until upstream decides how to fix it? live well, vagrant
signature.asc
Description: PGP signature
