Bug#816876: systemd: bootsched fails after systemd is installed resumes working after systemd is removed

[jda2000]

Source: systemd
Severity: normal

Dear Maintainer,

In the course of an update from Debian 7 to Debian 8 on a color iMac sytemd replaced sysv style init.
Subsequently, bootsched from powerpc-utils stopped working.  It would run and return 0 status but
the system would not power-on at the appointed time.

Following the instructions found here:
  https://ispire.me/downgrade-from-debian-sid-to-stable-from-jessie-to-wheezy/
sysvinit was re-installed and systemd removed:

apt-get install sysvinit-core sysvinit sysvinit-utils
(reboot)
apt-get remove --purge --auto-remove systemd

During this process a message flashed by saying that a supernode(?) had a future date
probably due to an invalid hardware clock setting and the notation "FIXED"

On a hunch, I skipped the rest of the roll-back and retested /sbin/bootshed
That test and a few subsequent all worked. 

and earlier attempt to fix the problem with:

# hwclock --set --date "$(date)"

had not worked.

I'm staying on Debian 8 since /sbin/bootsched is working.

I submit this report to document the work-around in case there are other color iMacs out there still.

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 3.16.0-4-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)