LIRC update overwrites config file

When the latest version of lirc applies it doesn't check for an existing lircd.conf and replaces it when you select a remote, it should be known to the user that it is doing this.

I experienced this too. What is the point of overwriting working configs without informing the user? Is the old config incompatible with the new binary? Doesn't seem to be that way as the new config files did not work for me AT ALL. When i replaced with old config everything works as before.

What's the reasoning for this?

If config files absolutely need to be updated, AT LEAST the user must be informed of this.

Also using iMON receiver but with Logitech Harmony 525 remote.

mvisa wrote:
> I experienced this too. What is the point of overwriting working configs
> without informing the user? Is the old config incompatible with the new
> binary? Doesn't seem to be that way as the new config files did not work
> for me AT ALL. When i replaced with old config everything works as
> before.
>
> What's the reasoning for this?
>
> If config files absolutely need to be updated, AT LEAST the user must be
> informed of this.
>
> Also using iMON receiver but with Logitech Harmony 525 remote.
>
This boils down to a lot of confusion with the way the config files get handled.
 Choosing "Custom" avoids overwriting the remote. It was supposed to "help"
upgrade scenarios, but appears to have done more damage than harm.

--
Mario Limonciello
<email address hidden>

I ran the config 2x, so now I don't have the "backup" to revert to.

As had been predicted in https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/239938 - warning months ago that

> the automatic replacement of /etc/lirc/lircd.conf without warning might lead to final loss of one's configuration

(see also the comment there) - this should be fixed to avoid deleting what can amount to hours of work for some remotes.

this is fixed in bzr #30

Sponsors, please pull the latest copy of the bzr branch linked on this bug for sponsorship.

This bug was fixed in the package lirc - 0.8.3-0ubuntu2

---------------
lirc (0.8.3-0ubuntu2) intrepid; urgency=low

  * debian/patches/25_upstream_2.6.26.patch:
    - Fix lirc-modules-source compilation on 2.6.26 by pulling some
      patches from CVS (LP: #247233)
  * debian/rules:
    - Install original modules back into proper location for
      intrepid kernel (LP: #242216)
  * debian/patches/37_msi_tv_anywhere.dpatch:
    - Create patch for supporting MSI TV @anywhere remote. (LP: #241830)
  * debian/lirc.postinst:
    - Correct path to look for module in Intrepid.
    - Ask for a path when using dvico remotes. (LP: #238032)
    - Don't accidentally overwrite lircd.conf and hardware.conf
      when things haven't really changed at all. (LP: #206609)
  * debian/lirc.init.d:
    - Don't allow udev to put us into endless spinning loops. Instead
      pray that module hotplugging worked for all things USB. (LP: #269743)
  * debian/lirc.fdi:
    - Include this FDI file to prevent in kernel support for the
      saa7134 when LIRC is installed. (LP: #204960, #164627)
  * debian/rules:
    - Install FDI file.
  * debian/lirc.install:
    - List FDI file.
  * debian/patches/22_hauppauge_novat_500.dpatch:
    - Adapt to include alternative numeric keys. (LP: #224080)
  * debian/patches/25_upstream_2.6.27.dpatch:
    - Update to content that is currently sitting in Ubuntu GIT
      tree.

 -- Mario Limonciello <email address hidden> Wed, 24 Sep 2008 12:02:17 -0500