From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gEKY2-0006Ak-B7 for guix-patches@gnu.org; Sun, 21 Oct 2018 16:42:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gEKU6-0007ol-7l for guix-patches@gnu.org; Sun, 21 Oct 2018 16:38:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58580) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gEKU6-0007oh-3N for guix-patches@gnu.org; Sun, 21 Oct 2018 16:38:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gEKU5-000653-V3 for guix-patches@gnu.org; Sun, 21 Oct 2018 16:38:02 -0400 Subject: [bug#33038] [PATCH 3/6] bootstrap: Add %bootstrap-mes. Resent-Message-ID: From: Marius Bakke In-Reply-To: <875zxxax4f.fsf@gnu.org> References: <20181014085857.3863-1-janneke@gnu.org> <20181014085857.3863-3-janneke@gnu.org> <87r2gld3nt.fsf@gnu.org> <875zxxax4f.fsf@gnu.org> Date: Sun, 21 Oct 2018 22:37:43 +0200 Message-ID: <87sh0z8294.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; 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: Jan Nieuwenhuizen , Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 33038@debbugs.gnu.org --=-=-= Content-Type: text/plain Jan Nieuwenhuizen writes: >> It would be nice to maybe make this a separate commit (following the >> make-bootstrap.scm changes) so that you can state in the commit log >> which commit was used to build this binary. > > Ah yes, that's nice. Hmm, there's a slight complication because for the > i686-linux version I cheated; icu4c, python-more-itertools and swig fail > to build on core-updates-next. I added a hack and reverted that... > which is probably less than great. So I cleaned it up a bit and just > added it. FYI the issues mentioned here have been fixed in the 'core-updates' branch. I suppose you can still rebase on it, or just merge it. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlvM45cACgkQoqBt8qM6 VPq2wQf/Z/bTSXqKGM1DBriAwxe8CMhs3mwIdVkOhBSCVEcjb6zgGFG0MpajHwL0 fsNi3KUhJ+D3wgMLlhtkVJidv4ERis0TNkURmu6f80ZDesYL3V3IJzf8gcvQnDZ/ X2nxJQM/Ief0flYlXdwxN+/kt6uu+TXvUX54GSHlyCQHZLDEojsQY5USfYbP8O6h iA+I3IoYS8LuQcLqgvVRHo0uz1mcs0FhZ3Js0zGO9znjiPGIqzpPNCGCyIAItzaB FHU/0G1yCaZkx1KPi3NKz5dK4AW267zfrNgOon5nOuyghGTuV2zGpixOOfZD/9ad XlIFxqE6mikHnpyFBgg/Id4MqwDq6A== =5Jed -----END PGP SIGNATURE----- --=-=-=--