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#2869 - lirc overwrites /etc/lircd.conf

Attached to Project: Arch Linux
Opened by Sasha (kleptophobiac) - Friday, 24 June 2005, 16:31 GMT
Last edited by Dale Blount (dale) - Saturday, 25 June 2005, 13:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Paul Mattal (paul)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The lircd.conf file stores all the remote codes for a remote control. Whenever upgrading or installing lirc, it automatically overwrites this file. The file should be added to the backup line.

It really ought to be extracted as /etc/lircd.conf.pacnew, as the old file is far more likely to be correct.

I assign this as a high level severity because it overwrites user settings irrevocably.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 23 October 2005, 12:41 GMT
Reason for closing:  Fixed
Comment by Paul Mattal (paul) - Thursday, 07 July 2005, 01:07 GMT
Thanks for reporting this bug. I'm going to fix this in the next release, which I plan to make soon. Also planning to include the kernel modules in this upcoming release.

Looking for a clever install script way to save the existing configurations BEFORE the upgrade. I think I can pull that off using pre_upgrade and triggering off the new version. Look for action on this soon.

- P
Comment by arjan timmerman (blaasvis) - Tuesday, 26 July 2005, 14:38 GMT
status ?
Comment by Paul Mattal (paul) - Tuesday, 26 July 2005, 14:45 GMT
I haven't done the clever thing yet. Otherwise I have the new package. I expect to kick this out around bug squashing day.
Comment by Paul Mattal (paul) - Saturday, 06 August 2005, 03:24 GMT
I'm confused about this bug somehow. The lirc package doesn't contain /etc/lircd.conf or /etc/lircmd.conf files. It tells you to copy them in from the /usr/share directory.

So how is this happening? Have you got a particular version of the lirc package you can reference so I can be sure we've got this handled?
Comment by Sasha (kleptophobiac) - Saturday, 06 August 2005, 04:15 GMT
It happened on both the 0.7.0 and 0.7.1 versions for me... my lircd.conf became the stock lircd.conf that is more example than directly useful. When I simply extract the built package with tar in a sandbox directory, there is definitely a lircd.conf there.

[root@mythbe01 sandbox]# tar -xzf lirc-0.7.1-1.pkg.tar.gz
[root@mythbe01 sandbox]# ls
etc lib lirc-0.7.1-1.pkg.tar.gz usr
[root@mythbe01 sandbox]# cd etc
[root@mythbe01 etc]# ls
lircd.conf rc.d
[root@mythbe01 etc]#
Comment by Paul Mattal (paul) - Saturday, 06 August 2005, 04:50 GMT
Strange. Do we have the same versions of this package tar?

My md5sum is 688f3d85d8569d7638c0bdd70c254a4d

I have no /etc/lirc.conf.

I verified that the md5sum above matches the (lingering) one on the main download site, too. Is it possible this was a customized version of the package?

If still puzzled, can you attach it to this bug?

I hope this bug doesn't get any weirder before we figure it out. ;)
Comment by Sasha (kleptophobiac) - Saturday, 06 August 2005, 04:56 GMT
I used the 0.7.0 package from the server, and the 0.7.1 by making the PKGBUILD. my md5sum for the package should be different, but I used the official pkgbuild with no modifications.

I'll rerun abs and try again when I can get to my box again (I think my web access at home is down, so I can't ssh in).
Comment by Paul Mattal (paul) - Wednesday, 21 September 2005, 03:22 GMT
Any discoveries on this one?

Meanwhile, I'm working on getting the new version to compile, but it's been more than a little bit tricky, so it's slow in coming. But hopefully I'll get it done soon.

Loading...