Description of problem: Sometimes when I open files with kdevelop it changes the modification timestamps of the files in the project. Sometimes it's one of the files which have been opened and sometimes it's some other files in the project from a directory containing header files included by the files which have been opened. Example: two directories with source files - a and b. *.cpp files in a include headers from b. When I open all files from a in kdevelop sometimes modification timestamps of some files in a change and sometimes in b. From what I've seen the nanoseconds part of the timestamp gets reset to 0. For example, before: 2012-01-04 21:21:02.866618267 after: 2012-01-04 21:21:02.000000000 So far I haven't seen a case where the timestamp got increased. Some build tools trigger a rebuild when they detect this change of the modification timestamp. Version-Release number of selected component (if applicable): kdevelop-4.2.3-3.fc15.i686 How reproducible: About 30% of the time. Steps to Reproduce: 1. ls --full-time 2. Open multiple files in kdevelop 3. ls --full-time and compare with results from step 1 Actual results: modification timestamps are changed for some files Expected results: modification timestamps are unchanged for all files Additional info:
The same files also have their ctime increased to the current time.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping