From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:54781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4SkX-0002iP-5I for guix-patches@gnu.org; Thu, 14 Mar 2019 11:58:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h4SfH-0005Cb-0Z for guix-patches@gnu.org; Thu, 14 Mar 2019 11:53:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:58589) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h4SfG-0005CI-Dt for guix-patches@gnu.org; Thu, 14 Mar 2019 11:53:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h4SfG-0002EK-8o for guix-patches@gnu.org; Thu, 14 Mar 2019 11:53:02 -0400 Subject: [bug#34845] [PATCH 00/30] Update LXQt to 0.14.1. Resent-Message-ID: Date: Thu, 14 Mar 2019 16:52:48 +0100 From: Danny Milosavljevic Message-ID: <20190314165248.04a42a5f@scratchpost.org> In-Reply-To: <87r2b9r4dc.fsf@riseup.net> References: <20190313125656.2822-1-meiyo@riseup.net> <20190314114729.4678d1e2@scratchpost.org> <87r2b9r4dc.fsf@riseup.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/V2BPw=rbtWKlS=o=kd9jWVg"; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Meiyo Peng Cc: 34845@debbugs.gnu.org --Sig_/V2BPw=rbtWKlS=o=kd9jWVg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, > Thank you for your investigation. Would you please take care of the > problem? I wont be available for god-knows-how-many-days. :-) Sure, no problem. I've pushed your patchset and one reproducibility patch by me to fix (2). > > (1) aboutdialog/lxqtaboutdialog.cpp: QDate::currentDate().toString("yyy= y") > > (2) The environment variable QT_RCC_SOURCE_DATE_OVERRIDE is not set to = 1. (1) is still broken. I'm not sure whether it's possible to find the date of the original tar.gz file on the server or something, in order to find when the release was released, as an approximation of the copyright year. Or fetch it out of the CHANGELOG, hmm. --Sig_/V2BPw=rbtWKlS=o=kd9jWVg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlyKeNAACgkQ5xo1VCww uqUqJAf/UwEpgGzNNGdIwPPnk2UHEafrX7EU+RobZMfpAirqw5Dn7Qy1bczuCtK/ 0v5i3M77zKFy4Vboz5FbO60bPEv77rHlT95CAPekSOZz7UEoOBNXbSUnrG50817Z qBZj+NeAdKIV4XAcOwfb0iGDdZNEcxikLa/Sy3ZdZcnZVa0n5i1ApOVTa5iaNmYt AUa49UiBIXkZV0abSVqOq4fmktM+UBjrXNQ30l4l9qoFM27ywfzio1Jc+eCCVdVf Ry3q0va8Dyz2FG/zKJ3weFY19W+ZyS7aP3R1cZMiqUWnZCB5MlxGK8ZFYh4rzwYr xjre8VVpskFLe7iMOWdyySaogN1Djw== =ul9O -----END PGP SIGNATURE----- --Sig_/V2BPw=rbtWKlS=o=kd9jWVg--