Describe the issue:
Hello,
it appears the process to build the release tarballs (what im referring to is the file named [numpy-1.26.3.tar.gz](https://github.com/numpy/numpy/releases/download/v1.26.3/numpy-1.26.3.tar.gz) in the asset section of https://github.com/numpy/numpy/releases/tag/v1.26.3, not the source code lnks) have all files with timestamp epoch = 0, aka Jan 1970, small example:
$ wget --quiet https://github.com/numpy/numpy/releases/download/v1.26.3/numpy-1.26.3.tar.gz
$ TZ=UTC tar tzf numpy-1.26.3.tar.gz --full-time -v | head
-rw-r--r-- 0/0 5495 1970-01-01 00:00:00 numpy-1.26.3/.circleci/config.yml
-rw-r--r-- 0/0 1842 1970-01-01 00:00:00 numpy-1.26.3/.cirrus.star
-rw-r--r-- 0/0 1133 1970-01-01 00:00:00 numpy-1.26.3/.clang-format
-rw-r--r-- 0/0 230 1970-01-01 00:00:00 numpy-1.26.3/.codecov.yml
-rw-r--r-- 0/0 75 1970-01-01 00:00:00 numpy-1.26.3/.coveragerc
-rw-r--r-- 0/0 19 1970-01-01 00:00:00 numpy-1.26.3/.ctags.d
-rw-r--r-- 0/0 322 1970-01-01 00:00:00 numpy-1.26.3/.devcontainer/devcontainer.json
-rwxr-xr-x 0/0 485 1970-01-01 00:00:00 numpy-1.26.3/.devcontainer/setup.sh
-rw-r--r-- 0/0 2593 1970-01-01 00:00:00 numpy-1.26.3/.gitattributes
-rw-r--r-- 0/0 1660 1970-01-01 00:00:00 numpy-1.26.3/.github/CONTRIBUTING.md
this has started with 1.26.0, and it continues with the latest release 1.26.3, while 1.25.2 is not showing this issue.
has something changed in how the assets are generated for a release? could you look into restoring a more "modern" timestamps for release files? this is causing issues downstream in debian, where we have checks in place to make sure nothing "unusual" happens, and files being dated 1970 got flagged
thanks!
Reproduce the code example:
Error message:
No response
Python and NumPy Versions:
n/a
Runtime Environment:
No response
Context for the issue:
No response
Describe the issue:
Hello,
it appears the process to build the release tarballs (what im referring to is the file named
[numpy-1.26.3.tar.gz](https://github.com/numpy/numpy/releases/download/v1.26.3/numpy-1.26.3.tar.gz)in the asset section of https://github.com/numpy/numpy/releases/tag/v1.26.3, not thesource codelnks) have all files with timestamp epoch = 0, aka Jan 1970, small example:$ wget --quiet https://github.com/numpy/numpy/releases/download/v1.26.3/numpy-1.26.3.tar.gz $ TZ=UTC tar tzf numpy-1.26.3.tar.gz --full-time -v | head -rw-r--r-- 0/0 5495 1970-01-01 00:00:00 numpy-1.26.3/.circleci/config.yml -rw-r--r-- 0/0 1842 1970-01-01 00:00:00 numpy-1.26.3/.cirrus.star -rw-r--r-- 0/0 1133 1970-01-01 00:00:00 numpy-1.26.3/.clang-format -rw-r--r-- 0/0 230 1970-01-01 00:00:00 numpy-1.26.3/.codecov.yml -rw-r--r-- 0/0 75 1970-01-01 00:00:00 numpy-1.26.3/.coveragerc -rw-r--r-- 0/0 19 1970-01-01 00:00:00 numpy-1.26.3/.ctags.d -rw-r--r-- 0/0 322 1970-01-01 00:00:00 numpy-1.26.3/.devcontainer/devcontainer.json -rwxr-xr-x 0/0 485 1970-01-01 00:00:00 numpy-1.26.3/.devcontainer/setup.sh -rw-r--r-- 0/0 2593 1970-01-01 00:00:00 numpy-1.26.3/.gitattributes -rw-r--r-- 0/0 1660 1970-01-01 00:00:00 numpy-1.26.3/.github/CONTRIBUTING.mdthis has started with 1.26.0, and it continues with the latest release 1.26.3, while 1.25.2 is not showing this issue.
has something changed in how the assets are generated for a release? could you look into restoring a more "modern" timestamps for release files? this is causing issues downstream in debian, where we have checks in place to make sure nothing "unusual" happens, and files being dated 1970 got flagged
thanks!
Reproduce the code example:
Error message:
No response
Python and NumPy Versions:
n/a
Runtime Environment:
No response
Context for the issue:
No response