From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux. Date: Sat, 14 Oct 2017 12:30:23 +0200 Message-ID: <87o9pa6myo.fsf@fastmail.com> References: <20171012173828.26257.23460@vcs0.savannah.gnu.org> <20171012173830.72AE320339@vcs0.savannah.gnu.org> <87tvz36elv.fsf@netris.org> <87r2u76qnr.fsf@fastmail.com> <87po9rhtpd.fsf@netris.org> <87y3oeh8cq.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33492) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3Ji9-0002aE-Qb for guix-devel@gnu.org; Sat, 14 Oct 2017 06:30:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3Ji6-0007NQ-MN for guix-devel@gnu.org; Sat, 14 Oct 2017 06:30:29 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:43183) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e3Ji6-0007NJ-Ff for guix-devel@gnu.org; Sat, 14 Oct 2017 06:30:26 -0400 In-Reply-To: <87y3oeh8cq.fsf@netris.org> 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: Mark H Weaver Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Mark H Weaver writes: > Mark H Weaver writes: > >> Marius Bakke writes: >> >>> Note that mesa and libdrm did not build any drivers at all on armhf >>> until recent commits on 'staging'. I tried cross-compiling libdrm >>> to update etnaviv symbols instead, but failed some packages before it. >>> >>> So currently it's a trial-and-error process to find flags to make mesa >>> build on armhf. This means armhf users are currently unable to build >>> *any* graphical packages, actually. Given how expensive evaluations >>> are, I figured we might as well deal with it on 'master'. >> >> Thanks for explaining. I think this should have been dealt with on the >> 'staging' branch before merging into 'master'. This is a pretty bad >> situation now for anyone using Guix on armhf. > > Didn't we already talk about this when you merged an earlier 'staging' > branch into 'master' that contained a major GNOME upgrade that was > untested, and broke GNOME desktops for all platforms? > > Do you think it should be acceptable to merge a major branch into > 'master' where *all* graphical packages are broken on armhf? I naively assumed that disabling the etnaviv driver was enough, but concede that it was short-sighted. Unfortunately I did not notice the armhf failures until late in the cycle due to manually restarting all 'gobject-introspection' dependents on i686 and x86_64. And learned that "new job" failures are not listed in the "newly failing" tab. I feel terrible for gambling with armhf users' convenience and security and can only offer a sincere apology. Hopefully the most recent 'mesa' commit solves this issue, and rest assured I won't merge a broken package with ~800 dependents again. Humbly, Marius --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlnh5z8ACgkQoqBt8qM6 VPre3wf/dwkD5hIJUsawfF2+FamTOzpP100wBy/9ZIMxiav5Hyfydk4h/utjV/Vt 7ocXntXROA55MbyPG667PJPujtrsFYNruVegAAqe86kZhWiNfT6lFO0BJ0Na4I2G r6Bd+Q7+6OxyEiUbnUADzmLpSn/WyzaRQbjdKtfNteFSQ3TjvwHj1J7kIHyddTmr IqAPPnwcuv3elFSaGLZM6xb7tGCnFQIiy/uaXZB2DNBXbDNi1OnjhJCRCKvn28LR PvguX2XGL9McfrQaCyaV2qZk0oMRXDHQ7uKUuO8p5L94Xc2I/ADKWP4b8f1+4UD3 kZzHAvTiPtL45QDp/le5G0mg/OALPw== =VpZZ -----END PGP SIGNATURE----- --=-=-=--