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, zerochaos@gentoo.org, blueness@gentoo.org,
	dilfridge@gentoo.org, dlan@gentoo.org, maekke@gentoo.org,
	nerdboy@gentoo.org, vapier@gentoo.org, xmw@gentoo.org,
	zlogene@gentoo.org
Subject: Re: [gentoo-dev] net-dns/dnssec-root: Blind stable on arm, critical bug 667774
Date: Fri, 12 Oct 2018 08:28:28 +0100	[thread overview]
Message-ID: <20181012082828.7fba265c@sf> (raw)
In-Reply-To: <dffe3470-aa3c-0107-8fd8-4f0fc41c6dbe@gentoo.org>

On Fri, 12 Oct 2018 02:40:38 +0200
Thomas Deutschmann <whissi@gentoo.org> wrote:

> On 2018-10-12 01:38, Sergei Trofimovich wrote:
> >> 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.  
> 
> See the ARM bug queue for stable requests. ARM is always last and behind
> since we dropped HPPA.

I agree it lags. I disagree it's not maintained (I disagree HPPA is not
maintained either but let's leave it for another day). Let's wait for arm@ input.

I'm CCing all members as listed in https://wiki.gentoo.org/wiki/Project:ARM directly:
  zerochaos@
  [skip alicef@ (kernel stabilization)]
  blueness@
  dilfridge@
  dlan@
  maekke@
  nerdboy@
  vapier@
  xmw@
  zlogene@

And asking a few the questions directly (zerochaos@ as a lead and the arm@ team):

a) If you are not planning to do any arm@ work in short term can you remove
   yourself from project's wiki page?

b) Can you update your status in arm project to mention if you are
   doing any stabilization work so people could contact you occasionally?

c) Is it in your opinion worth keeping arm@ stable? (Do you use stable, do you
   expect people to use stable, etc.)

Thanks!

> > 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?  
> 
> Bug was assigned highest priority in bugzilla. But it looks like ARM arch
> team is ignoring set priority.

I personally don't filter emails by priority either. I guess I should now :)

> *I* didn't asked in #gentoo-arm but I pinged project several times in
> #gentoo-dev channel.

https://wiki.gentoo.org/wiki/Project:ARM explicitly lists #gentoo-arm.
In my experience there are quite a few active users of arm.

> Disclaimer: I am not the maintainer of unbound nor dnssec-root package. I took
> action last week after I noticed that there was a time bomb ticking and
> nobody cared. I fully agree that an updated dnssec-root package could have been
> made available one year ago giving everyone enough time...

Do we do anything about it? Post GLSA, news item, gento-users@, anything to get
users notified? Or just leave them uninformed?

> > 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.  
> 
> Unbound is a popular resolver and many Gentoo users are operating ARM-based
> routers. I don't get your point. Of course you could disable DNSSEC and DNS
> will resume working. But is this really your point?
> 
> >    While annoying it's not going to lock users out or corrupt their data.  
> 
> Right, it doesn't cause data corruption. But when your Gentoo-based router
> will stop working this can be a problem. Don't forget about remote systems.
> Again, people who know how to deal with problems like that aren't the
> problem. But why do we care about stable packages if we assume that everyone
> knows what to do when experiencing problems?

My point that this bug is not critical. Broken software happens all the time.
I can understand why you think otherwise.

> > 5. net-dns/dnssec-root is a plain-text file package. It should have been ALLARCHES
> >    stablewithout involvement of arm@.  
> 
> It wasn't about dnssec-root package. Of course this could have been stabilized
> under ALLARCHES policy. It wasn't because package has a new dependency
> (>=dev-perl/XML-XPath-1.420.0 + deps) which was lacking stable keywords, too.  

Thank you! That was not clear from the bug.

> If ARM can keep up I am quiet. But please, be honest. We don't need another
> HPPA. Nobody will win something if we tell world "ARM is a first class citizen
> in Gentoo" when it isn't (anymore). But if people would know it is ~ARCH, we
> would not disappoint expectations.

I think arm@ is the best decider here.

-- 

  Sergei


  reply	other threads:[~2018-10-12  7:28 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
2018-10-12  0:40   ` Thomas Deutschmann
2018-10-12  7:28     ` Sergei Trofimovich [this message]
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=20181012082828.7fba265c@sf \
    --to=slyfox@gentoo.org \
    --cc=arm@gentoo.org \
    --cc=blueness@gentoo.org \
    --cc=dilfridge@gentoo.org \
    --cc=dlan@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=maekke@gentoo.org \
    --cc=nerdboy@gentoo.org \
    --cc=vapier@gentoo.org \
    --cc=xmw@gentoo.org \
    --cc=zerochaos@gentoo.org \
    --cc=zlogene@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