From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:38834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gf0s5-00031q-Uz for guix-patches@gnu.org; Thu, 03 Jan 2019 06:09:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gf0s2-0001Lm-Sy for guix-patches@gnu.org; Thu, 03 Jan 2019 06:09:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:34855) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gf0s2-0001LS-Pe for guix-patches@gnu.org; Thu, 03 Jan 2019 06:09:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gf0s2-0004oy-8g for guix-patches@gnu.org; Thu, 03 Jan 2019 06:09:02 -0500 Subject: [bug#33923] [PATCH] gnu: vboot-utils: Fix building on armhf-linux. Resent-Message-ID: Date: Thu, 3 Jan 2019 12:07:46 +0100 From: Danny Milosavljevic Message-ID: <20190103120746.2471a735@scratchpost.org> In-Reply-To: <20181230150459.19028-1-kkebreau@posteo.net> References: <20181230150459.19028-1-kkebreau@posteo.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/3IBOQIsvqK6YhyBRq7a.XbT"; 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: Kei Kebreau Cc: 33923@debbugs.gnu.org --Sig_/3IBOQIsvqK6YhyBRq7a.XbT Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hmm, OK, but why not use the newest release? Apparently, there's release-R72-11316.B already. Although cmd_bdb seems to be still broken in the newer release. And so are the tests. And so is the workbuf test check. So your patch definitely LGTM as is! Additionally, the patches are not in upstream master, so it might make sense to send those to the them, so that we don't have to maintain the extra patches forever. --Sig_/3IBOQIsvqK6YhyBRq7a.XbT Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlwt7QIACgkQ5xo1VCww uqUyMAf+LtTEhTx86UaJ24myRKdL+Ez2f18+Kt0X44TfdawcmrdDmchQZRKBcoxQ v/q/vQ4NENBXJkvPyIN/hAHlBBDRshMhZ0g/aYcAua6vsbZ+3d1yw41b2fgWMwHG y/fF/LQRT7Na2UPcHL5NgQSaHTBDA/u1J8KirwU1/w+jblG5dz7zcBnN5cB/xarm x3fm2dRTeetKpX1/6pBfNIhNQ/7kkQOUEL1jxKYhqhAnCfSfRrZTcwpA5ODYuNoO 2QSa4gGsJqEWg2D17YDJ+/keVvhv+4HPk2DnWPy8sCHoQfiUwr4DWvoQ5xunVONn 2cyEWAwxwDH6g08uPW4Y689tW/trcw== =Mtw4 -----END PGP SIGNATURE----- --Sig_/3IBOQIsvqK6YhyBRq7a.XbT--