unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 27264@debbugs.gnu.org
Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Date: Thu, 08 Jun 2017 22:47:08 +0200	[thread overview]
Message-ID: <87lgp2p5pv.fsf@gnu.org> (raw)
In-Reply-To: <87vao6poh7.fsf@netris.org> (Mark H. Weaver's message of "Thu, 08 Jun 2017 10:01:56 -0400")

Hello Mark,

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hi Mark,
>>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> 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 think many of us use GTK+/GNOME applications, but fewer use GNOME, so
>> I suppose we just didn’t test a full GNOME setup.
>>
>> Next time we should probably do that or, even better, have an automated
>> test that logs in, takes a screenshot, and does some OCR to check
>> whether we got something that looks like a GNOME screen.
>
> I think this is unacceptable.  The test you propose above is no where
> near adequate to assure that the updated desktop environment is usable
> for real work.
>
> I'm annoyed that I've been forced to either use a different desktop
> environment in the meantime or else sacrifice security updates.  I would
> never consider pushing such a major update to master without testing it
> first.  I'm astonished that anyone thinks that this is acceptable
> behavior.

I sympathize, and I agree that it sucks.

Now, I think we are all guilty.  Rather than trying to find someone to
blame, I’m more interested in seeing why we got there and what we can do
to avoid it in the future.  Of course we can call for GNOME users to
test it, and we’ll surely do that explicitly in the future.  But IMO we
should be thankful to those who worked on this upgrade branch, and I
feel it would be unwise to sit back and add more on their shoulders.

> While it's true that users can boot into an older generation of their
> system in an emergency, and that's a *great* comfort, in general it's
> not an acceptable fallback because it entails sacrificing security
> updates.  I'm concerned that our fallback feature has caused people to
> become quite careless with breaking things on our master branch.

This is wrong.  None of us is careless, and suggesting that this is the
case is really unpleasant.

Thanks to Marius, Kei, and Roel for working on the fix.

Ludo’.

  parent reply	other threads:[~2017-06-08 20:48 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
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 [this message]
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=87lgp2p5pv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27264@debbugs.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).