Dear Daniel, thank you for your feedback. On 22.10.2022 14:48, Daniel Swarbrick wrote:
I guess if you want the _Debian_ package release date, you can read that into a variable with something like $(shell dpkg-parsechangelog -S date) in debian/rules, and then do whatever is necessary to poke that into the source that it's building.
That's not the issue, I can access the debian package release just fine via SOURCE_DATE_EPOCH.
Getting the release date of the upstream tag should be feasible too, using something like `git log -1 --format=%ai <upstream_tag>`.
Thank you very much, this brings me in the right direction, I prefer `git log -1 --format=%as` but I get an issue during build:
fatal: not a git repository (or any parent up to mount point /)Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Setting GIT_DISCOVERY_ACROSS_FILESYSTEM to `1` unfortunately doesn't help. Do you have any idea how to make this work in the build system?
Best regards, Martin
Attachment:
signature.asc
Description: PGP signature