Question about build
![](https://seccdn.libravatar.org/avatar/a7bcbbdadbe98519ce41f733dc441577.jpg?s=120&d=mm&r=g)
When I build VirtualBox using osc, I get the following WARNING: [ 15s] WARNING could not set SOURCE_DATE_EPOCH, ensure BUILD_RELEASE is set in /.buildenv I have not found any description of the contents of .buildenv. I do notice that OBS has a file _buildenv, but it does not define BUILD_RELEASE. Is that the same file? Are either file described any place that is accessible? Thanks, Larry
![](https://seccdn.libravatar.org/avatar/86d8a5ad42dcba8dfbc53f0ef3baa365.jpg?s=120&d=mm&r=g)
On 01/05/2024 21.14, Larry Finger wrote:
When I build VirtualBox using osc, I get the following WARNING:
[ 15s] WARNING could not set SOURCE_DATE_EPOCH, ensure BUILD_RELEASE is set in /.buildenv
I have not found any description of the contents of .buildenv. I do notice that OBS has a file _buildenv, but it does not define BUILD_RELEASE. Is that the same file? Are either file described any place that is accessible?
If you are not building for publishing or otherwise real use, then you can ignore this. The downside is that repeated builds will use the same date for mtimes if reproducible builds are on. Which e.g. rsync doesn't expect. But to fix this right now: In osc and obs, .buildenv is prepared by obs-build. To pass in the release with osc, use and replace R with your choice: osc build --release R Long term I want to find a way to improve this, but I'm not sure how yet, besides better wording for the warning. Tracked in https://github.com/openSUSE/post-build-checks/issues/64 . -- Best regards, Jan Zerebecki
participants (2)
-
Jan Zerebecki
-
Larry Finger