From: Catonano <catonano@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 27264@debbugs.gnu.org
Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Date: Thu, 8 Jun 2017 19:29:06 +0200 [thread overview]
Message-ID: <CAJ98PDx7jnf1Wdfst4FqB3zr62GAiNXco_7OBtTHLbapK25EOw@mail.gmail.com> (raw)
In-Reply-To: <20170608170842.GB27164@jasmine>
[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]
2017-06-08 19:08 GMT+02:00 Leo Famulari <leo@famulari.name>:
> On Thu, Jun 08, 2017 at 10:01:56AM -0400, Mark H Weaver wrote:
> > 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'm sorry to be harsh, but I feel justified to air my grievances because
> > I believe this is the kind of event that will cause GNOME users to label
> > GuixSD an experimental distribution that's not suitable for one's
> > primary work machine, but are too polite to complain. Let me be the
> > canary in the coal mine.
>
> I agree with your points. For complex interactive software, someone must
> test it by actually using it. And we should remember that the master
> branch is supposed to always be "deployable", and choose to test
> breaking changes on other branches.
>
> > 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.
>
> It's true, we could not even think of pushing untested or lightly-tested
> changes if we couldn't roll-back.
>
> But, if we want to 1) receive updates to big software suites like GNOME,
> and we want to 2) avoid breakage on the master branch, we *need* more
> testers.
>
> As somebody who has helped with a few of these branches so far, the lack
> of assistance with testing and bug fixes is a major problem. I rarely
> feel as confident as I'd like before pushing the merge. More than once
> I've merged a major branch with the impression that only myself and 1 or
> 2 other people have actually deployed it on their workstation or in a
> staging environment that precedes production.
>
> There is a large number of contributors adding new packages or working
> on features, but almost nobody helps test big changes or other boring
> and tedious maintenance tasks. So, those things suffer, and we end up
> testing on the master branch. I don't have any potential solutions in
> mind. As we are mostly volunteers with limited time and computing
> resources, we can only do so much.
>
I'd love to help with testing the Gnome desktop
The reason why I abstain is because if the desktop environment turns out to
be broken, like in this case, I wouldn't know how to work around that
I'm lost in the command line, I'm not even sure I could manage to access
the so called consoles or that I could open an alternative desktop
environment
If I had a spare computer I would use that.
Unless using a qemu based virtual machine is a good enough solution
If it is, then here I am
Send me an email, indicate me a branch and I'll test it
[-- Attachment #2: Type: text/html, Size: 3756 bytes --]
next prev parent reply other threads:[~2017-06-08 17: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDx7jnf1Wdfst4FqB3zr62GAiNXco_7OBtTHLbapK25EOw@mail.gmail.com \
--to=catonano@gmail.com \
--cc=27264@debbugs.gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.