Tom H <tomh0...@gmail.com> writes: > On Sun, Mar 22, 2015 at 7:31 AM, Alan McKinnon <alan.mckin...@gmail.com> > wrote: >> >> It looks to me like sysvinit-2.88-r7 was stabilized and the maintainer >> of apcupsd didn't notice. From the ebuild for apcupsd-3.14.8-r2: >> >> DEPEND=" >> || ( >=sys-apps/util-linux-2.23[tty-helpers] >> <=sys-apps/sysvinit-2.88-r4 >> sys-freebsd/freebsd-ubin >> ) >> >> What I suggest is copy that ebuild to your local overlay and update the >> DEPEND to <=sys-apps/sysvinit-2.88-r7 and redigest >> >> If that gives a correct update path for world, then file a bug against >> apcupsd. > > Some commands were moved from sysvinit to util-linux, and these > commands are required by apcupsd and are included in util-linux if > it's compiled with the "tty-helpers" use flag.
Is this somehow reflected in the dependencies? And how could I deal with the multiple versions of util-linux that seem to be required? Perhaps I should forcefully update util-linux and use tty-helpers so that apcupsd still works in case I reboot. But what other problems might that cause? What am I supposed to think? Should we not update unless no problems are listed and just wait in case there are some, potentially having to wait indefinitely? How about security updates then? -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
