[gentoo-user] runscript is deprecated; please use openrc-run instead

[Mick]

I've noticed this during booting:

* runscript is deprecated; please use openrc-run instead.
* Starting D-BUS system messagebus ...
* start-stop-daemon: fopen `/var/run/dbus.pid': No such file or directory
* Detaching to start `/usr/bin/dbus-daemon' ...
[ ok ]
* runscript is deprecated; please use openrc-run instead.


Is this a warning of things to come, or should I change my settings somewhere?

[hydra]

Post by Mick
* runscript is deprecated; please use openrc-run instead.
* Starting D-BUS system messagebus ...
* start-stop-daemon: fopen `/var/run/dbus.pid': No such file or directory
* Detaching to start `/usr/bin/dbus-daemon' ...
[ ok ]
* runscript is deprecated; please use openrc-run instead.
Is this a warning of things to come, or should I change my settings somewhere?
--
Regards,
Mick

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.

[Rich Freeman]

Post by hydra
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.