FS#50692 - [lirc] Consider irexec.lircrc as a backup file

Attached to Project: Arch Linux
Opened by Jerome Couradeau (Anakon) - Wednesday, 07 September 2016, 12:01 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No



When upgrading the lirc package, the file /etc/lirc/irexec.lircrc gets overwritten.

As specified in irexec.service, /etc/lirc/irexec.lircrc is the config file for the irexec service. As such, it should be considered as a backup file to not be overwritten during an upgrade.

Additional info:
* package version : lirc 1:0.9.4.b-1
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:15 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/lirc/issues/1
Comment by Bart De Vries (mogw_ai) - Tuesday, 01 May 2018, 11:57 GMT
Same thing happened to me today: /etc/lirc/irexec.lircrc file got overwritten by the update to the latest lirc 1:0.10.1-1.
This is a config file; therefore it should be backed up and not overwritten by a package update.

Additional info: file got overwritten during upgrade:
lirc-1:0.9.4.d-1 --> lirc-1:0.10.1-1
Comment by Jerome Couradeau (Anakon) - Monday, 14 September 2020, 14:22 GMT
13th of September 2020 Bug Day: this bug is still valid.
It's been here for 4 years. One simple add in the PKGBUILD and it could be closed.
Comment by Bart De Vries (mogw_ai) - Tuesday, 15 September 2020, 09:51 GMT
I also second this: I had my config overwritten another three times since replying to this bug report, going from 1:0.10.1-1 through 1:0.10.1-4.
It would indeed be solved by adding just one line to the PKGBUILD.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.
Comment by Jerome Couradeau (Anakon) - Monday, 09 October 2023, 11:48 GMT
Dear bugbot, please don't close this issue as the bug is still here.