Community Packages

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#21799 - [fcron] needs user and group cron

Attached to Project: Community Packages
Opened by Andrej Gelenberg (nikel) - Tuesday, 23 November 2010, 11:25 GMT
Last edited by Thorsten Töpper (Atsutane) - Wednesday, 24 November 2010, 06:33 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thorsten Töpper (Atsutane)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

fcron fail to start if cron user and group are missing. Plead add user cron in install script for the package if missing.
This task depends upon

Closed by  Thorsten Töpper (Atsutane)
Wednesday, 24 November 2010, 06:33 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See my comment below.
Comment by Ionut Biru (wonder) - Tuesday, 23 November 2010, 11:34 GMT Comment by Andrej Gelenberg (nikel) - Tuesday, 23 November 2010, 12:20 GMT
i have utmp group with gid 22. It no really reliable to hard code gid. Install script seems to fail for me.
Comment by Ionut Biru (wonder) - Tuesday, 23 November 2010, 12:27 GMT Comment by Andrej Gelenberg (nikel) - Tuesday, 23 November 2010, 13:07 GMT
And so? IMHO, if you assume cron to be gid 22, because it in that list, then it should be in filesystem package already. Otherwise it lead to problems, when some other package wont to have the same gid, or what ever. Better use groupadd -r cron. At least, when gid 22 not available.
Comment by Thorsten Töpper (Atsutane) - Tuesday, 23 November 2010, 19:45 GMT
Edit 2010-11-14 7:30 UTC+01: Now that I'm awake and read the comments again: No won't implement that.
The feature is provided, we have a table with specifications one can lookup when creating a custom group/user.
A quick fix that comes to mind before I drink my coffee: Add a new group, get the files to this, remove the group, reinstall fcron so cron is done as 22 and recreate your group and reassign the files to the recreated one, remove the temprary one, make sure there are no problems with specified IDs.

Just because someone has problems with a specified GID I don't mess up with a clean working and simple .install file, that is not the philosophy of this operating system.

Loading...