Gentoo Archives: gentoo-dev

From: William Hubbs <williamh@g.o>
To: gentoo-dev@l.g.o
Cc: Joshua Kinard <kumba@g.o>
Subject: Re: [gentoo-dev] is this newsitem worthy?
Date: Mon, 22 Aug 2016 17:14:03
Message-Id: 20160822171319.GB16554@whubbs1.gaikai.biz
In Reply to: Re: [gentoo-dev] is this newsitem worthy? by Joshua Kinard
1 On Sun, Aug 21, 2016 at 11:36:07PM -0400, Joshua Kinard wrote:
2 > On 08/21/2016 15:31, William Hubbs wrote:
3 > > All,
4 > >
5 > > take a look at the discussion on
6 > > https://bugs.gentoo.org/show_bug.cgi?id=591414, in particular the last
7 > > few comments.
8 > >
9 > > My question is, is the emerge action newsitem worthy as Mark suggests?
10 > >
11 > > Thanks,
12 > >
13 > > William
14 >
15 > I think it is. I was scratching my head over some of these warnings, wondering
16 > why no one has fixed some of them yet. For the less-used packages, such as
17 > sys-apps/timer_entropyd, without a revbump, I'd not have thought that simply
18 > re-merging the package on all of my systems would update the init script and
19 > make the warning go away.
20
21 The news item is being written and will be posted here soon.
22
23 > IMHO, such a change *should* have been a revbump, and, if that was the only
24 > change to that package, that revbump should have gone straight to stable since
25 > it doesn't really represent a significant change (and issues regarding such a
26 > change should have already been worked out). OTOH, if there were other things
27 > that could be fixed in a package, then pack this change into the rest and
28 > follow the normal stabilization process.
29
30 Here is the thread where this was announced; The revbump and
31 stabilization was left to the individual package maintainers and no one
32 said otherwise should be done including myself.
33
34 https://archives.gentoo.org/gentoo-dev/message/b2b147b1860a9eb938ff5e4eec3dd014
35
36 > As for the "--quiet --quiet" bit...that's a bit obtuse. The message being
37 > output is only using an "ewarn", so it's not a critical error and should have
38 > been squelched with the first --quiet. I'd either update the message to an
39 > "eerror" to get attention or add a note about the double-quiets somewhere (or
40 > add a new switch, --stfu, to do the job </smirk>).
41
42 heh, the discussion on the bug has shown that there is an issue here
43 which I am going to look into.
44
45 William

Attachments

File name MIME type
signature.asc application/pgp-signature