public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] net-dns/dnssec-root: Blind stable on arm, critical bug 667774
Date: Fri, 12 Oct 2018 08:50:55 -0400	[thread overview]
Message-ID: <CAGfcS_kBe-ZUMOsEwe-92gmVCReyY4VDiT0rJ2=TUcht_RK7iw@mail.gmail.com> (raw)
In-Reply-To: <95271f29-6c3c-1b9c-f12b-96c467b8bdec@gentoo.org>

On Thu, Oct 11, 2018 at 1:14 PM Thomas Deutschmann <whissi@gentoo.org> wrote:
>
> But that's not the point here. The point was to get some attention that
> again we have a lacking architecture (net-dns/dnssec-root is not the
> only package where ARM arch team is lacking behind) which affects anyone
> "trusting" somehow in STABLE keywords.

ARM is not a Gentoo security supported arch.

If the ARM maintainers feel that stable keywords make the lives of
their users better, and it isn't causing problems for anybody else,
I'm not sure why we should be interfering with this.

>
> If everyone is using ~ARCH and don't care about STABLE keywords, well,
> we could save a bunch of time, energy...
>

Is this costing YOU any time/energy?  If not, why do you care?

This thread seems to be devolving into another debate about the
purpose of stable, and I'm mainly seeing arguments that have come up
countless times already.

Most of these arguments tend to point out things that are perceived as
being wrong with stable as it currently exists.  Most of these
arguments are probably posted by people who don't even run stable, let
alone maintain it.

If somebody wants to actually "fix" stable IMO the best way to go
about that is to create a proposal for something new that people will
get behind.  Gentoo tends to move forward by creating new things, not
by arguing about what is broken with old things.

What solution is even being proposed?  Tell devs they're not allowed
to work on stable?  That doesn't mean that their next thoughts will be
"wow, since I'm not allowed to spend 10 hours per week working on
something I cared about, I guess I'll spend those 10 hours per week
working on something that somebody else cares about."  If it makes
Gentoo less useful to them personally, they're just as likely to just
drop other contributions they make on the side as they look for better
solutions.

IMO when stable teams create issues for maintainers by not being
responsive to bugs then this needs to be dealt with.  However, the
Council has already allowed maintainers to drop stable keywords when
this happens, and I imagine they'd be responsive to dealing with
issues that are more sustained.

-- 
Rich


  parent reply	other threads:[~2018-10-12 12:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 15:10 [gentoo-dev] net-dns/dnssec-root: Blind stable on arm, critical bug 667774 Thomas Deutschmann
2018-10-11 15:45 ` Corentin “Nado” Pazdera
2018-10-11 17:04   ` Thomas Deutschmann
2018-10-11 17:07     ` Alec Warner
2018-10-11 18:07     ` Marc Schiffbauer
2018-10-11 15:48 ` Alec Warner
2018-10-11 17:14   ` Thomas Deutschmann
2018-10-12 10:07     ` Jeroen Roovers
2018-10-12 12:50     ` Rich Freeman [this message]
2018-10-20 12:19       ` Andreas Sturmlechner
2018-10-20 12:22         ` Mikle Kolyada
2018-10-20 12:26           ` Andreas Sturmlechner
2018-10-20 12:56             ` Mikle Kolyada
2018-10-20 13:29         ` Rich Freeman
2018-10-11 23:38 ` Sergei Trofimovich
2018-10-12  0:40   ` Thomas Deutschmann
2018-10-12  7:28     ` Sergei Trofimovich
2018-10-12  2:12   ` Matt Turner
2018-10-12 13:47 ` [gentoo-dev] " Mikle Kolyada

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='CAGfcS_kBe-ZUMOsEwe-92gmVCReyY4VDiT0rJ2=TUcht_RK7iw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox