public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@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: Thu, 11 Oct 2018 11:48:26 -0400	[thread overview]
Message-ID: <CAAr7Pr_RiRWAv=NTOxMSnpiRkWkPqp3c6iWmmNKjxf1xz7BqPg@mail.gmail.com> (raw)
In-Reply-To: <673fa7bc-c3f6-9c76-5675-783754ce3e9a@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

On Thu, Oct 11, 2018 at 11:10 AM Thomas Deutschmann <whissi@gentoo.org>
wrote:

> Let me quote
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6f6bb91b7f134a121ef9fa1dd504b9ca52c5aa8
> :
>

This thread is missing a bunch of context...so I'll try to add it I guess.


>
> > net-dns/dnssec-root: Blind stable on arm, critical bug 667774
> >
> > Note that this is a major fail for a stable architecture.
> > In addition, all arm devboxes are currently offline.
> >
> > Bug: https://bugs.gentoo.org/667774
> > Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
> > Package-Manager: Portage-2.3.49, Repoman-2.3.11
>
> ...and now let's all sit down and enjoy how stable ARM users lose access
> to the Internet and have to figure out how to deactivate DNSSEC to get
> back online. ;]
>

I can't tell if the complaint is that:

1) Someone blind-stabled something on arm and it broke (doesn't build?)
2) The arm team failed to mark a package stable before a hard deadline
(DNSSEC key rotation)

I presume its the latter? Whats the impact? All DNS, or only DNSSEC
validated entries?


> Maybe it is time to destabilize ARM on Gentoo to stop the impression
> that we really support ARM.
>

I'm not really sure I buy this as an argument; but then again I think there
is a general expectation that Gentoo users using 'are paying attention'[0]
so stable arm users would have unmasked the ~arch version of the keys long
before today.

[0] Particularly people using DNSSEC...but maybe I'm just a curmudgeon.


>
>
> --
> Regards,
> Thomas Deutschmann / Gentoo Linux Developer
> C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
>
>

[-- Attachment #2: Type: text/html, Size: 2808 bytes --]

  parent reply	other threads:[~2018-10-11 15:48 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 [this message]
2018-10-11 17:14   ` Thomas Deutschmann
2018-10-12 10:07     ` Jeroen Roovers
2018-10-12 12:50     ` Rich Freeman
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='CAAr7Pr_RiRWAv=NTOxMSnpiRkWkPqp3c6iWmmNKjxf1xz7BqPg@mail.gmail.com' \
    --to=antarus@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