public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Joshua Kinard <kumba@gentoo.org>
Subject: Re: [gentoo-dev] is this newsitem worthy?
Date: Mon, 22 Aug 2016 12:13:19 -0500	[thread overview]
Message-ID: <20160822171319.GB16554@whubbs1.gaikai.biz> (raw)
In-Reply-To: <c4584fb5-f24f-f379-8579-246ed23ccafd@gentoo.org>

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

On Sun, Aug 21, 2016 at 11:36:07PM -0400, Joshua Kinard wrote:
> On 08/21/2016 15:31, William Hubbs wrote:
> > All,
> > 
> > take a look at the discussion on
> > https://bugs.gentoo.org/show_bug.cgi?id=591414, in particular the last
> > few comments.
> > 
> > My question is, is the emerge action newsitem worthy as Mark suggests?
> > 
> > Thanks,
> > 
> > William
> 
> I think it is.  I was scratching my head over some of these warnings, wondering
> why no one has fixed some of them yet.  For the less-used packages, such as
> sys-apps/timer_entropyd, without a revbump, I'd not have thought that simply
> re-merging the package on all of my systems would update the init script and
> make the warning go away.
 
 The news item is being written and will be posted here soon.

> IMHO, such a change *should* have been a revbump, and, if that was the only
> change to that package, that revbump should have gone straight to stable since
> it doesn't really represent a significant change (and issues regarding such a
> change should have already been worked out).  OTOH, if there were other things
> that could be fixed in a package, then pack this change into the rest and
> follow the normal stabilization process.
 
Here is the thread where this was announced; The revbump and
stabilization was left to the individual package maintainers and no one
said otherwise should be done including myself.

 https://archives.gentoo.org/gentoo-dev/message/b2b147b1860a9eb938ff5e4eec3dd014

> As for the "--quiet --quiet" bit...that's a bit obtuse.  The message being
> output is only using an "ewarn", so it's not a critical error and should have
> been squelched with the first --quiet.  I'd either update the message to an
> "eerror" to get attention or add a note about the double-quiets somewhere (or
> add a new switch, --stfu, to do the job </smirk>).

heh, the discussion on the bug has shown that there is an issue here
which I am going to look into.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2016-08-22 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 19:31 [gentoo-dev] is this newsitem worthy? William Hubbs
2016-08-22  3:36 ` Joshua Kinard
2016-08-22 17:13   ` William Hubbs [this message]

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=20160822171319.GB16554@whubbs1.gaikai.biz \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kumba@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