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!
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!
FS#40636 - [fcron] 3.1.3-1 update overwrites systab
Attached to Project:
Community Packages
Opened by Martin Nyolt (PapaNappa) - Sunday, 01 June 2014, 20:04 GMT
Last edited by Thorsten Töpper (Atsutane) - Saturday, 14 June 2014, 11:13 GMT
Opened by Martin Nyolt (PapaNappa) - Sunday, 01 June 2014, 20:04 GMT
Last edited by Thorsten Töpper (Atsutane) - Saturday, 14 June 2014, 11:13 GMT
|
DetailsDescription:
When fcron gets updated, it replaces the current systab with the default one. All changes are lost. This applies for instance to fcron version 3.1.3-1, where it hit me last. Other user-specific crontabs are not affected. The package ships a default systab.orig file, which is overwritten on each update. The .orig file is the user-friendly version, which is compiled into binary format by fcrontab. This is also forced for the systab on each install/update by the fcron.install script. I suppose adding var/spool/fcron/systab.orig to the backup array in the PKGBUILD solves the problem. Steps to reproduce: 1. Modify the systab, e.g. # fcrontab -e -u systab 2. Update fcron 3. Modify the systab again, notice the changes are reverted. |
This task depends upon
Closed by Thorsten Töpper (Atsutane)
Saturday, 14 June 2014, 11:13 GMT
Reason for closing: Implemented
Additional comments about closing: 3.1.3-2
Saturday, 14 June 2014, 11:13 GMT
Reason for closing: Implemented
Additional comments about closing: 3.1.3-2
Upstream provides this functionality of having a "system crontab", and the current package breaks this.
Furthermore, if I would like to change the interval or dates when the scripts in /etc/cron.*/ are executed, I would have to modify the systab nonetheless.
This is because these are the default entries in the systab.
Having them in the root crontab would make them execute twice after updates.
Best regards,
Martin