On jeudi 12 juillet 2018 18:28:21 BST Sune Vuorela wrote:
> On Wednesday, July 11, 2018 10:08:23 PM CEST Vagrant Cascadian wrote:
> > Ideally QT_RCC_SOURCE_DATE_OVERRIDE would get set based on
> > SOURCE_DATE_EPOCH, otherwise build tools have an arbitrary growing
>
> No. As explained, we need to l
On Wednesday, July 11, 2018 10:08:23 PM CEST Vagrant Cascadian wrote:
> Ideally QT_RCC_SOURCE_DATE_OVERRIDE would get set based on
> SOURCE_DATE_EPOCH, otherwise build tools have an arbitrary growing
No. As explained, we need to look at each individual package to check if the
timestamp is actual
> 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
El mié., 11 de jul. de 2018 17:12, Vagrant Cascadian
escribió:
> On 2018-07-11, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Version: 5.11.1+dfsg-1
> >
> > The bug upstream has been closed as invalid (see
> https://bugreports.qt.io/
> > browse/QTBUG-62511) Non the less a workaround has been inc
On 2018-07-11, Lisandro Damián Nicanor Pérez Meyer wrote:
> Version: 5.11.1+dfsg-1
>
> The bug upstream has been closed as invalid (see https://bugreports.qt.io/
> browse/QTBUG-62511) Non the less a workaround has been included in Qt 5.11,
> already in experimental. Setting QT_RCC_SOURCE_DATE_OVER
5 matches
Mail list logo