I am currently using subversion to track changes in /etc. etc-update can sometimes break this when replacing old configuration files with new ones because moving untracked files to replace tracked files will result in subversion not realizing a change has occured in the destination file (cp apparently does not have this problem). I reported this problem to the subversion mailing list and was told this occurs because the timestamp is not updated when using mv. I was told that touching the file after moving it can solve this problem. I haven't been able to reproduce the problem, which apparently only occurs if the mtime is wacked out on the temporary configuration file. So the question is, should etc-update touch the configuration file after replacing it? Reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3.
Created attachment 65379 [details, diff] touches the resulting configuration file This touches the replaced configuration file to update the mtime. I caught the mv after replacing with the new config and replacing with the merged config. I don't know if there are any others.
in r3932
This has been released in 2.1.1_pre3-r2.
