desktop-packages team mailing list archive

[Till Kamppeter <1479431@xxxxxxxxxxxxxxxxxx>]

Seb, this is still an upstream issue as it is reported by a Red Hat
developer and worked on by the upstream developers at HP. So do not
replace the upstream task by a task for the Ubuntu package, but if you
want to make me as the Ubuntu maintainer of HPLIP aware of the bug,
simply add the Ubuntu package task.

Re-added upstream task.

Seb, did you perceive any breaking effect by this in Wily? Is the
problem release-critical? Or can we simply wait for the upstream
developers to fix it (and then have the fix in 16.04)?

** Also affects: hplip
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1479431

Title:
  move systemd bits from 56-hpmud_sysfs.rules to 56-hpmud.rules

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  Prior to 3.15.6 both 56-hpmud_sysfs.rules & 56-hpmud.rules contained
  if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@$env{BUSNUM}:$env{DEVNUM}.service

  With 3.15.6 this has been removed from 56-hpmud.rules, but still remains in 56-hpmud_sysfs.rules.
  AFAICT 56-hpmud_sysfs.rules, which uses deprecated SYSFS instread of ATTR, exists only for older distributions like RHEL5, where there's no systemd. So IMHO it should have been removed from 56-hpmud_sysfs.rules, not from 56-hpmud.rules.

  Related:
  You might also consider using "TAG+="systemd", ENV{SYSTEMD_WANTS}=..." instread of RUN+=""
  see:
  http://jasonwryan.com/blog/2014/01/20/udev/
  http://blog.fraggod.net/2012/06/16/proper-ish-way-to-start-long-running-systemd-service-on-udev-event-device-hotplug.html
  man systemd.device

  With regards,
  --
  Jiri

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1479431/+subscriptions