[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#894476: marked as done (rcc: please honour SOURCE_DATE_EPOCH)

Your message dated Wed, 11 Jul 2018 16:21:49 -0300
with message-id <56728171.BAyLc9RQiM@tonks>
and subject line Solved from the Qt side.
has caused the Debian Bug report #894476,
regarding rcc: please honour SOURCE_DATE_EPOCH
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
894476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894476
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qtbase5-dev-tools
Version: 5.9.2+dfsg-12
Severity: wishlist
Tags: upstream
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps toolchain

Hi,

While investigating ultracopier's lack of build reproducibility, I found
out that rcc encodes the timestamp of the files the QRC file being
compiled references (see end of RCCFileInfo::writeDataInfo()). This
becomes a problem for generated files because the output of rcc is then
different in 2 different builds. It would be nice if rcc had an option
to encode a stable timestamp, eg. EPOCH.

Best regards,

Thomas

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qtbase5-dev-tools depends on:
ii  libc6                            2.27-2
ii  libgcc1                          1:8-20180321-1
ii  libqt5core5a [qtbase-abi-5-9-2]  5.9.2+dfsg-12
ii  libqt5dbus5                      5.9.2+dfsg-12
ii  libstdc++6                       8-20180321-1
ii  perl                             5.26.1-5
ii  qtchooser                        64-ga1b6736-5
ii  zlib1g                           1:1.2.8.dfsg-5

qtbase5-dev-tools recommends no packages.

qtbase5-dev-tools suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
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_OVERRIDE should be enough 
to solve this issue.

Now the point is: where should this variable be set?

I guess dh's cmake and qmake helpers might be a good place to start with, but 
I think you might have a bteer undesrtanding of this.

After all forcing the variable will mean also already reproducible builds will 
get modified.

Cheers!

-- 
18: Como se pueden evitar los problemas de alimentacion electrica
    * No coma cerca de un enchufe
    Damian Nadales
    http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: