While using etc-update, I selected option for interactive merge of a config file (option 3). This worked quite well When the same invocation of etc-update progressed to subsequent configs, I did not need interactivity so selected option 1, replace file with update. This "worked" but did not prompt me about removing the ._ file. It simply removed it. Please note that this is *not* the config for which I did an interactive merge Reproducible: Always Steps to Reproduce: 1. Run etc-update with >1 pending update 2. Use interactive merge (option 3) for first update 3. Use non-interactive merge (option 1) for subsequent update Actual Results: As mentioned in description above Expected Results: Subsequent, non-interactive, merges should give the warning (like rm -i) of before removing the config file.
I don't see how the exact sequence of events that you describe could happen. Here is the code for option 1: case ${my_input} in 1) echo "Replacing ${ofile} with ${mfile}" chmod --reference=${ofile} ${mfile} mv ${mv_opts} ${mfile} ${ofile} rm ${rm_opts} ${file} return 255 The values of mv_opts and rm_opts are never modified while etc-update is running unless, unless the user selects -5 or -7 from the main menu.
