unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 27264@debbugs.gnu.org
Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Date: Thu, 08 Jun 2017 02:29:02 -0400	[thread overview]
Message-ID: <878tl3q9g1.fsf@netris.org> (raw)
In-Reply-To: <8760g7nhhx.fsf@fastmail.com> (Marius Bakke's message of "Thu, 08 Jun 2017 08:03:22 +0200")

Marius Bakke <mbakke@fastmail.com> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> I have a question: Does GNOME 3 work for *anyone* in Guix now?  If so,
>> that would be useful information.  If not, I wonder why this got merged
>> into master.
>
> I'm sorry, I don't actually use GNOME and should have tested it before
> pushing. I have been busy lately and didn't want to hold up the branch.

In the future, I think that pushing an updated desktop environment to
master should only be performed by someone who is able and willing to
test it.  Modern desktop environments are quite complex, and many things
can go wrong even if the code compiles.

> It would be good to have a system test for GNOME and other DEs so we can
> catch these problems earlier.

I agree that it would be good to have this, but it would require a
massive effort to produce a sufficiently comprehensive test suite to
render manual testing unnecessary.  In the meantime, automated testing
is not an adequate substitute for user testing.  To my mind, only
someone who actually uses the DE in question to do real work will be
able to meaningfully judge the result as usable.

> I'll try to help fixing this later today, but feel free to revert the
> updates meanwhile.

GNOME contains a great many components, and I don't fully understand
their interdependencies.  It's not something that can be easily
reverted.

      Mark

  reply	other threads:[~2017-06-08  6:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  4:59 bug#27264: gnome-shell-3.24.2 consistently dies during initialization Mark H Weaver
2017-06-07 10:37 ` Ludovic Courtès
2017-06-07 13:15   ` Roel Janssen
2017-06-07 21:58     ` Mark H Weaver
2017-06-08  6:03       ` Marius Bakke
2017-06-08  6:29         ` Mark H Weaver [this message]
2017-06-08 12:35           ` Kei Kebreau
2017-06-08 16:13           ` Marius Bakke
2017-06-08 16:29             ` Marius Bakke
2017-06-09  6:23               ` Chris Marusich
2017-06-09  7:02               ` Mark H Weaver
2017-06-08  7:39         ` Ben Sturmfels
2017-06-08  6:48       ` pelzflorian (Florian Pelz)
2017-06-08 12:01       ` Ludovic Courtès
2017-06-08 12:23         ` Kei Kebreau
2017-06-08 13:09           ` Roel Janssen
2017-06-08 18:08           ` Roel Janssen
2017-06-08 18:34             ` Kei Kebreau
2017-06-08 14:01         ` Mark H Weaver
2017-06-08 14:54           ` Chris Marusich
2017-06-08 17:08           ` Leo Famulari
2017-06-08 17:19             ` Marius Bakke
2017-06-08 17:29             ` Catonano
2017-06-08 17:45               ` Leo Famulari
2017-06-08 18:12             ` Leo Famulari
2017-06-08 20:47           ` Ludovic Courtès
2017-06-11  8:57             ` Mark H Weaver
2017-06-11 13:16               ` Ludovic Courtès
2017-06-08 14:20         ` pelzflorian (Florian Pelz)

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=878tl3q9g1.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=27264@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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).