public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] newsitem: OpenRC runscript transition
Date: Mon, 22 Aug 2016 21:47:21 +0200	[thread overview]
Message-ID: <1471895241.31785.118.camel@gentoo.org> (raw)
In-Reply-To: <20160822172016.GA17457@linux1>

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

El lun, 22-08-2016 a las 12:20 -0500, William Hubbs escribió:
> Title: OpenRC runscript transition
> Author: William Hubbs <williamh@gentoo.org>
> Content-Type: text/plain
> Posted: 2016-08-25
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: <sys-apps/openrc-0.22

Maybe it's a bit late as 0.21.3 is already stable and, then, people
won't get the news item if they already updated :/

> 
> Starting with OpenRC 0.21.3, service script authors should use
> #!/sbin/openrc-run instead of #!/sbin/runscript to start their
> scripts.
> The following message will be displayed for each service on your
> system
> which is not updated:
> 
>  * <scriptpath> uses runscript, please convert to openrc-run.
> 
> This message is not fatal; your system will boot normally.
> 
> To silence most of the messages, you can run the following command as
> root:
> 
> # emerge /etc/init.d

Probably "oneshot" emerge would be preferred and, then, "emerge -1
/etc/init.d" would be better I think

> 
> The remaining packages (netifrc and udev-init-scripts as of this
> writing) have newer versions in the unstable tree with the fix, and
> are
> in the process of being stabilized.

Cannot that packages being stabilized then instead of "suggesting"
implicitly to the people to manually keyword "random" newer versions
and, also, accepting that were are too slow stabilizing that things? (I
would try to stabilize it at least for amd64... in my case I cannot
test as I run systemd... but it shouldn't be too hard to find some dev
or user able to test in that arch at least)

Also, if the downside of not re-emerging the packages is only a
warning, I would note that people can avoid (if they can live with the
message) the re-emerge (and wait for normal updates) for the case they
want to avoid re-emerging so many packages just now :/

Thanks :)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2016-08-22 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 17:20 [gentoo-dev] newsitem: OpenRC runscript transition William Hubbs
2016-08-22 19:47 ` Pacho Ramos [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=1471895241.31785.118.camel@gentoo.org \
    --to=pacho@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