From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kei Kebreau Subject: Re: [PATCH] gnu: maxima: Update to 5.39.0. Date: Sun, 18 Dec 2016 12:59:33 -0500 Message-ID: <87shpl2k56.fsf@openmailbox.org> References: <871sx64614.fsf@openmailbox.org> <87k2axnt21.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIfkS-0003t8-MN for guix-devel@gnu.org; Sun, 18 Dec 2016 12:59:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cIfkO-0006Kq-Mf for guix-devel@gnu.org; Sun, 18 Dec 2016 12:59:48 -0500 Received: from smtp22.openmailbox.org ([62.4.1.56]:48066 helo=smtp7.openmailbox.org) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cIfkO-0006JM-CW for guix-devel@gnu.org; Sun, 18 Dec 2016 12:59:44 -0500 In-Reply-To: <87k2axnt21.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Sun, 18 Dec 2016 16:41:26 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Marius Bakke writes: > Kei Kebreau writes: > >> This was supposed to be a simple version bump for Maxima, but it has >> come to my attention that Maxima hasn't built reproducibily for quite a >> while now (since version 5.36.1 according to my tests, possibly >> further). Is there any particular reason why? I can't seem to pinpoint >> the cause. > > The patch looks good. Are you sure it was reproducible before? > That's the thing; I'm not sure! I'll being investigating, though. > I've found 'diffoscope' to be useful when troubleshooting > reproducibility problems. E.g. by running it on two cancelled builds, or > by installing to different output paths with a superficial change to the > expression. It will show sections that differs which may aid locating > the offending code. > Yes. I see that diffoscope complains about missing 'xxd'. That may be useful to package (unless we already have it and I'm just oblivious). > For C family programs, a "hail mary" grep for __DATE__ or __TIME__ can > be enough. Tobias suggested making those return a fixed value, which I > think could be worthwhile, at least for the build environment. Cool. I'll remember this tip. Patch pushed as 4a652c78d425bfd76c2baba510ecd255b22b4714. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEg7ZwOtzKO2lLzi2m5qXuPBlGeg0FAlhWzoYACgkQ5qXuPBlG eg3gOQ//ZZ7tpFFTrMeTeJP6otJBJaBtyUVYh6o8ZByVlXoMEEDwgy72NI9pfnVY VawDpKfV3jTWnkis+An/2NxjjxTnZ/eIowGKt4ENKYTazZLwjW4oarSsgwPK9F8i +86yvmmAkD9EcSyqu4YgcwY71fwZ1GBnetivpFfgiFsJU4iJdFlbEsxF6pPvSpzE vZqyzHfjXxkPVfqzi7UDTgz+FU9k3+to9JXpDfCkWjoDFK/cQqLFDo2eHBjkrLt3 r++fe67wz/RwPolquUajlLx2br7LIQnm0OZG0+AlvvzV4jb/NjOwq2e+UXQhzCzw F4aacLl9IoA44DFQU/ovW7E9QEMEZpbhEiOA1aEa6CLkfdOaIp8rty9AC8krRvjb 9p5YPEEslJKJtJWgAeHBtmMCf+V9xEq0haWvGRwQI637C039Ok4yVwUnNIiyMkn0 RDGfKsSOeIRHmRlzhSvzXsdPeSz4XxeL4vu/lqnu48FIQSskrhbbU0E1/c7CjQhn jQLKPwB7C4bAUHOxoOWo4bVykvYVLGAQIFt51kA7HoUuoEUK/pkULfsNt4kUKY2r GPb+Ubwqzd8+srDUQx6sIRc3QK9vG6Q3fc3+4d545ATm5FEJRm5I/OKJsnTCqY9K WkUZkHusLO2UAX1gsrpdsNxZHKUXVMhAzr001ayu7wpVY111zAU= =gDAX -----END PGP SIGNATURE----- --=-=-=--