Hello
> Hello> I dont think to request a user action is a fair way to solve the issue.
> Update of anacron package should leave the fonctionnality as it is before the > update , that is
running
> Please consider to solve the upgrade of anacron really.
> Best Regards
It is running and fixed. This only impacted a small number of testing users who upgraded to -33
where symlinks were removed.
Anyone who did not update to this version (-33) would not have these issues. Trying to override dh
functionality is what caused this problem.
I don't think there needs to be more work done.
Lance Lin <lqi...@protonmail.com>
I do not think it is a good idea to leave the package as is for users who were affected without a
postinst script that makes sure the service is enabled, if upgraded from versions -33 to -35.
I had to specifically look for this bug reports for anacron to make sure the system behaviour is "by
design" and anacron service is disabled for some specific purpose.
I know where to look for these bug reports and how to fix it, but many people do not and leaving
them like that without working cron subsystem is not fair.
Thank you
Tim
