public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: arm@gentoo.org
Subject: Re: [gentoo-dev] net-dns/dnssec-root: Blind stable on arm, critical bug 667774
Date: Fri, 12 Oct 2018 00:38:01 +0100	[thread overview]
Message-ID: <20181012003801.61bae709@sf> (raw)
In-Reply-To: <673fa7bc-c3f6-9c76-5675-783754ce3e9a@gentoo.org>

On Thu, 11 Oct 2018 17:10:10 +0200
Thomas Deutschmann <whissi@gentoo.org> wrote:

> Let me quote https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6f6bb91b7f134a121ef9fa1dd504b9ca52c5aa8:
> 
> > 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. ;]
> 
> Maybe it is time to destabilize ARM on Gentoo to stop the impression
> that we really support ARM.

[ CC: arm@ ]

A few points to think about:

1. I have read this as a direct statement that ARM is not maintained.
   I don't think it is a fair (or constructive) assessment of team's work
   on ARM front.

2. The bug was created less than a week ago and was not communicated
   explicitly as urgent on #gentoo-arm. I see failure to handle the bug
   as a communication failure and not a team's death signal.

   Were there any attempts to reach out to the teams or just arm users?

3. I do not believe arm boxes (or most of users' boxes) update @world weekly
   and restart unbound automatically. Deadline of a few days is not feasible
   to propagate to users quickly. There is frequently no order-of-days response
   from arch teams. It would be nice to have but it's not realistic (IMO).

4. net-dns/dnssec-root is used by a single(ish) package in tree: net-dns/unbound

   Which is: not a system package, not a default package, not suggested by handbook
   package, can operate without DNSSEC enabled.

   While annoying it's not going to lock users out or corrupt their data. I don't
   think state of this package is characteristic of ARM support in Gentoo.

5. net-dns/dnssec-root is a plain-text file package. It should have been ALLARCHES
   stablewithout involvement of arm@.

6. If this package is so important it needs to be stable months before keys expire.
   Then users would have a chance to get the update during casual update. Or
   net-dns/unbound DNSSEC functionality should not be marked stable anywhere
   if package requires periodic manual intervention to just keep working.

-- 

  Sergei


  parent reply	other threads:[~2018-10-11 23:38 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
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 [this message]
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=20181012003801.61bae709@sf \
    --to=slyfox@gentoo.org \
    --cc=arm@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