> That's sadly something we can only "fix" by making packages have the right
> value set. As per Qt policy the environment variable needs to be prefixed
> with QT, so no chance of directly using SOURCE_DATE_EPOCH.
I added a downstream patch to a test-version [1] in openSUSE with
+static c
Is this the same as this upstream bug?
https://bugreports.qt.io/browse/QTBUG-62511
that had this patch merged
https://codereview.qt-project.org/#/c/202999/5/src/tools/rcc/rcc.cpp
with a renamed SOURCE_DATE_EPOCH env var
2 matches
Mail list logo