[Bug 1636355] Re: In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-11-01 Thread Launchpad Bug Tracker
This bug was fixed in the package lirc - 0.9.4c-4 --- lirc (0.9.4c-4) unstable; urgency=low * Team upload. * Upload to unstable. * Resolves (new bugs) LP: #1636355, LP: #1636353 * Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570, LP: #1393056, LP: #1310508,

[Bug 1636355] Re: In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-10-31 Thread Alec Leamas
** Changed in: lirc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636355 Title: In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-

[Bug 1636355] Re: In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-10-29 Thread Alec Leamas
I have rebuilt the source package 0.9.4c-3 on an updated zesty host, and it builds and installs /usr/sbin/lircd-uinput as expected. This bug is possibly related to bug #1636353. The cause can be found in the build log at https://launchpadlibrarian.net/290954740/buildlog_ubuntu-zesty-

[Bug 1636355] Re: In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-10-28 Thread Alec Leamas
Sorry, my bad. The file list for zesty does indeed not include lircd- uinput. Stay tuned -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636355 Title: In lirc 0.9.4, lircd-uinput.service fails to

[Bug 1636355] Re: In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-10-28 Thread Alec Leamas
Hm... when I list the contents of the lirc package, I see can see it in place: $ dpkg -L lirc | grep lircd-uinput | grep bin /usr/sbin/lircd-uinput $ So, this looks strange. Thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to