>> For me it is pretty strange that TSL team does not want to do anything >> about such obvious bug of fcron 2.9.5. I don't see too much changes >> between 2.9.5 and the latest versions... AVT> There is no way of making sure fcron works for everybody after such an AVT> upgrade, because some people might have changed their config file, and AVT> it will thus not be upgraded to the working one. AVT> There are quite a few noticeable changes. Some settings have to be added AVT> into the crontab if 2.2 fcron is upgraded to later versions which may AVT> prove a little of hassle for some.
That's exactly why I suggest to make upgrading to fcron3 optional and require manual "swup --install" to do such step. If there really are significant differences, users who decided to jump to fcron3 will surely know they need to examine config files after upgrading. And those who just have "swup --upgrade" in their crontabs and let swup do all the job will not have any troubles (except, yes, 2.9.5's bugs :)). Well, seems I'll have to "swup --remove fcron" and install fcron3 manually from sources. It is not the TSL way, I believe! :) Denis Solovyov _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
