| 1 |
On Wed, Aug 26, 2015 at 5:39 AM, hydra <hydrapolic@×××××.com> wrote: |
| 2 |
> |
| 3 |
> The init script must be changed to use openrc-run, your action will be to |
| 4 |
> update dbus as usual. Or better, open a bug report so that the init script |
| 5 |
> will be updated. |
| 6 |
> |
| 7 |
|
| 8 |
A bit more background. These messages are really targeted more at |
| 9 |
package maintainers, but they're made user-visible because not all |
| 10 |
packages are well-maintained. Also, since openrc is no longer used by |
| 11 |
all Gentoo users there may be package maintainers that simply don't |
| 12 |
ever see the message. |
| 13 |
|
| 14 |
When you see a new message like this I'd suggest doing the following: |
| 15 |
1. Give it a few days, just to let maintainers fix things on their |
| 16 |
own without being hassled. |
| 17 |
2. Check to see if it is fixed in a more recent package version. If |
| 18 |
it is, most likely the maintainer just doesn't want to make everybody |
| 19 |
rebuild things and they plan for you to get the fix whenever the next |
| 20 |
version is deployed. |
| 21 |
3. Check to see if a bug is already open for your package. If not, |
| 22 |
go ahead and create one. Anytime you check for an existing bug, look |
| 23 |
for recently-closed ones too. |
| 24 |
|
| 25 |
Usually these errors are put in place many months before anything is |
| 26 |
expected to break, and then before actually breaking anything there is |
| 27 |
a discussion on -dev, tracker bugs, and so on. So, don't panic, but |
| 28 |
it never hurts to log a bug if the issue isn't already resolved. |
| 29 |
|
| 30 |
-- |
| 31 |
Rich |
Archives