update-notifier-hp-firmware upstart job doesn't make sense in update-notifier; port to systemd

[Sebastien Bacher]

update-notifier ships a debian/update-notifier-hp-firmware.conf upstart job. Ideally a such job should be included in the package it's interacting with, hplip in this case.

We are also converting the user session to be using systemd so basically it means hplip should be including an systemd user job (if that's still something needed)

Doing that under systemd is probably best done using a udev rules triggering a systemd service

[Sebastien Bacher (seb128)]

Till, could you have a look to this one? Check if we still need that hp firmware script and if we do see if we can include a systemd job in hplip that does the same thing?

[Martin Pitt (pitti)]

Untested sketch: Add an udev rule like
    ACTION=="add", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="XXXX", ENV{ID_MODEL_ID}=="YYYY", ENV{SYSTEMD_USER_WANTS}+="hp-firmware.service"

and add a /usr/lib/systemd/user/hp-firmware.service whose ExecStart= calls
/usr/bin/hp-plugin-ubuntu if necessary. Note that you probably need some shell commands there, use

  ExecStart=/bin/sh -ec 'shell code here; \
      more shell code there'

for that.

[Bryan Quigley (bryanquigley)]

Some (hopefully helpful) notes when I was looking at this before:
Best summary of why it was added - https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/734822
The printer appears to be from 2005.