Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42098 - [lirc-utils] irexec.service: Unknown lvalue 'Wants' in section 'Install'

Attached to Project: Arch Linux
Opened by Ole Ernst (olebowle) - Wednesday, 24 September 2014, 12:24 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 20 January 2015, 22:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Basically upstream irexec.service needs to be updated (see http://sourceforge.net/p/lirc/tickets/29/).

May I however suggest to remove the Wants line altogether, as there are several other packages (such as eventlircd and inputlirc) which works nicely together with irexec.
Adding dependencies with drop-in files (/etc/systemd/system/irexec.service.d/*.conf) is easy, removing them on the other hand is not.[1]

This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Tuesday, 20 January 2015, 22:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1:0.9.2-1.
Comment by Ole Ernst (olebowle) - Wednesday, 24 September 2014, 12:25 GMT
[1] (https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg18541.html)
Comment by Dave Reisner (falconindy) - Wednesday, 24 September 2014, 12:39 GMT
Wants is fine to leave in. A failure (including non-existence) of a wanted dependency doesn't result in any service-level failure. The thread you reference talks about BindsTo, which is a stronger type of dependency, similar to Requires. A failure here from a dependent service *will* cause a service-level failure.
Comment by Ole Ernst (olebowle) - Wednesday, 24 September 2014, 12:49 GMT
Because both lircd.service and irexec.service are in the same package (lirc-utils) it will always be existent, hence lircd will be started if irexec is started.
Splitting the package might be a solution?
Comment by Dave Reisner (falconindy) - Wednesday, 24 September 2014, 12:51 GMT
Right, that sounds *much* better than the alternative of starting irexec.service out of the box and having it fail. If you want to switch lircd providers, then just mask lircd.service and add your own Wants.
Comment by Ole Ernst (olebowle) - Wednesday, 24 September 2014, 12:55 GMT
Oh masking, right totaly forgot about that possibility. Thanks!

Loading...