El vie, 17-02-2006 a las 17:13 +0100, Stephan Kramer escribió: > Sorry to attach to resolved bug, but I'm not really content with the way this > transition is done. I'm assuming most people when asked whether they want to > replace a fetchmail configuration file, would respond No as they don't want to > break their mail configuration (the difference with fetchmailrc is not that > obvious). This is at least what I did and after that it took a while to > realize > that I wasn't getting emails anymore, and that fetchmail hadn't started up at > the last reboot. > Well, if you say no and your init.d/fetchmail file is not upgrade the START_DAEMON flag would not affect you. Actually it will only ask you if your init.d/fetchmail was changed by hand.
If you talk about the /etc/default/fetchmail file the only problem I can think about is if you are updating from a 6.3.x version from unstable. There was a bug on the first versions that we uploaded, but since they didn't made it into testing we'll not provide an upgrade path to fix that unexpected bug, is unstable after all. > No I don't know how to better do this (maybe a more urgent message somewhere > in > the upgrade), so maybe you just have to ignore this. > It is defined no the NEWS file as stated by policy, and as I told I should have created the correct /etc/default/fetchmail file if you are upgrading from 6.2.x If I'm missing something, please let me know. Regards, Héctor
