From: Marius Bakke <mbakke@fastmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux.
Date: Sat, 14 Oct 2017 12:30:23 +0200 [thread overview]
Message-ID: <87o9pa6myo.fsf@fastmail.com> (raw)
In-Reply-To: <87y3oeh8cq.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Marius Bakke <mbakke@fastmail.com> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-10-14 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171012173828.26257.23460@vcs0.savannah.gnu.org>
[not found] ` <20171012173830.72AE320339@vcs0.savannah.gnu.org>
2017-10-13 1:06 ` 01/04: gnu: mesa: Disable imx driver for armhf-linux Mark H Weaver
2017-10-13 14:58 ` Marius Bakke
2017-10-13 16:57 ` Mark H Weaver
2017-10-14 0:38 ` Mark H Weaver
2017-10-14 10:30 ` Marius Bakke [this message]
2017-10-16 12:56 ` Ludovic Courtès
2017-10-16 21:52 ` Leo Famulari
2017-10-17 16:08 ` Cuirass HTTP API Ludovic Courtès
2017-10-17 19:49 ` Ricardo Wurmus
2017-10-14 17:51 ` 01/04: gnu: mesa: Disable imx driver for armhf-linux Leo Famulari
2017-10-18 13:53 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9pa6myo.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).