dgatwood: Perhaps it would be better to file a new bug with full
details. Just "broken" on its own doesn't offer much to go on, and a
new report would be better anyway in case it turns out not to be caused
by the same thing as the original bug.
** Changed in: lirc (Ubuntu)
Assignee: Colin Wa
This bug seems to have regressed to being broken again in 10.04.
--
lirc overwrote my lircd.conf
https://bugs.launchpad.net/bugs/129038
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
lirc (0.8.2-0ubuntu4) gutsy; urgency=low
* Clarify the intentions of choosing a remote (LP: #129038)
* Add 17_devinput.dpatch to show correct DEVICE
in doc/lirc.hwdb. (LP: #129689)
* Write out REMOTE="" to lircd.conf as well to allow
external apps to parse this information.
-- Mar
I am uploading a newer debdiff to cover the typo in the template, as
well as to solve another open lirc bug, 129689
** Attachment added: "debdiff"
http://launchpadlibrarian.net/8767416/lirc.debdiff
** Attachment removed: "better explanation debdiff"
http://launchpadlibrarian.net/8598494/li
** Changed in: lirc (Ubuntu)
Assignee: (unassigned) => Colin Watson
--
lirc overwrote my lircd.conf
https://bugs.launchpad.net/bugs/129038
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Ok. I don't know if the packaging guidelines allow this, but maybe it
should abort if there ist already a lircd.conf.dpkg-old. In the
meantime, I recreated my lircd.conf with irrecord, and my remote works
again like a charm. By the way: in the .debdiff file, there seems to be
a typo, theres "lirc.c
The behavior of the postinst script will simple rename your existing config to
/etc/lirc/lircd.dpkg-old. Your old configuration should be present there,
unless you reconfigured lirc multiple times to choose different remotes.
Here is the snippet of what the postinst script does:
