public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] runscript is deprecated; please use openrc-run instead
Date: Wed, 26 Aug 2015 06:30:48 -0400	[thread overview]
Message-ID: <CAGfcS_kn0Peyz5aAeM+8zu4XXyNPs4LGt-edS1HmJuk_-a+yJQ@mail.gmail.com> (raw)
In-Reply-To: <CAG6MAzTYsdxNtJB5oYVF1Ba9x9pdgnAJVX+SmtCXF0PwR=EG7Q@mail.gmail.com>

On Wed, Aug 26, 2015 at 5:39 AM, hydra <hydrapolic@gmail.com> wrote:
>
> The init script must be changed to use openrc-run, your action will be to
> update dbus as usual. Or better, open a bug report so that the init script
> will be updated.
>

A bit more background.  These messages are really targeted more at
package maintainers, but they're made user-visible because not all
packages are well-maintained.  Also, since openrc is no longer used by
all Gentoo users there may be package maintainers that simply don't
ever see the message.

When you see a new message like this I'd suggest doing the following:
1.  Give it a few days, just to let maintainers fix things on their
own without being hassled.
2.  Check to see if it is fixed in a more recent package version.  If
it is, most likely the maintainer just doesn't want to make everybody
rebuild things and they plan for you to get the fix whenever the next
version is deployed.
3.  Check to see if a bug is already open for your package.  If not,
go ahead and create one.  Anytime you check for an existing bug, look
for recently-closed ones too.

Usually these errors are put in place many months before anything is
expected to break, and then before actually breaking anything there is
a discussion on -dev, tracker bugs, and so on.  So, don't panic, but
it never hurts to log a bug if the issue isn't already resolved.

-- 
Rich


  reply	other threads:[~2015-08-26 10:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26  9:30 [gentoo-user] runscript is deprecated; please use openrc-run instead Mick
2015-08-26  9:39 ` hydra
2015-08-26 10:30   ` Rich Freeman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-12 10:48 Gevisz
2015-04-12 11:04 ` Alan McKinnon
2015-04-12 11:27   ` Gevisz
2015-04-12 12:52     ` Mick
2015-04-12 16:30       ` Gevisz
2015-04-12 15:13     ` Neil Bothwick
2015-04-12 16:40       ` Gevisz
2015-04-12 17:22     ` Alan McKinnon

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=CAGfcS_kn0Peyz5aAeM+8zu4XXyNPs4LGt-edS1HmJuk_-a+yJQ@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@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