cronie, as shipped with RHEL 10, has a new feature to keep backups of previous crontabs under ~/.cache/crontab/. The `crontab` binary does this automatically.

However, if ~/.cache does not exist, any user editing their own crontab (after it was created previously, so the backup mechanism kicks in) will get the following error printed in the console:

$ crontab -e
crontab: installing new crontab
/home/user/.cache/crontab: mkdir: No such file or directory

Note that if ~/.cache/crontab does not exist, the crontab binary creates it, but if ~/.cache does not exist, it does not and errors out. This affects all users, provided ~/.cache does not exist when editing an already-existing crontab.

As a workaround, ~/.cache can be manually created. However, `crontab` should create ~/.cache if needed and it does not exist, to avoid the unnecessary error.