| 2008-07-03 11:44:51 |
Nosto Raksi |
bug |
|
|
added bug |
| 2008-11-03 21:15:13 |
Neal McBurnett |
bzr: status |
New |
Confirmed |
|
| 2008-11-03 21:15:13 |
Neal McBurnett |
bzr: statusexplanation |
|
I can confirm this on ubuntu linux hardy, bzr 1.3.1 using the bzr branch command.
It is a problem for the project I'm developing, because I want to deliver test files to the end user, and the file modification times of the test files are important to the functioning of the program - it processes them chronologically.
Everything else in my development and packaging toolchain seems to preserve file modification times (setuptools, tar, dpkg, etc), so bzr is the weak link in the chain, when I or others build a distribution from a branch other than my original trunk directory.
I guess I have to either always distribute from the original directory (not great for distributed development, and more risk of including unwanted files or changes) or deliver the files inside a zip archive or the like, and unpack them at install time.
Support for preserving file metadata like create and modification times would be useful in
many circumstances.
Modification times are far more portable and far less problematic than the permission and ownership metadata discussed in https://bugs.edge.launchpad.net/bzr/+bug/67589
|
|
| 2008-11-03 21:19:19 |
Martin Pool |
bzr: importance |
Undecided |
Wishlist |
|
| 2008-11-03 21:19:19 |
Martin Pool |
bzr: statusexplanation |
I can confirm this on ubuntu linux hardy, bzr 1.3.1 using the bzr branch command.
It is a problem for the project I'm developing, because I want to deliver test files to the end user, and the file modification times of the test files are important to the functioning of the program - it processes them chronologically.
Everything else in my development and packaging toolchain seems to preserve file modification times (setuptools, tar, dpkg, etc), so bzr is the weak link in the chain, when I or others build a distribution from a branch other than my original trunk directory.
I guess I have to either always distribute from the original directory (not great for distributed development, and more risk of including unwanted files or changes) or deliver the files inside a zip archive or the like, and unpack them at install time.
Support for preserving file metadata like create and modification times would be useful in
many circumstances.
Modification times are far more portable and far less problematic than the permission and ownership metadata discussed in https://bugs.edge.launchpad.net/bzr/+bug/67589
|
|
|
| 2010-03-21 23:47:42 |
Martin Pool |
summary |
file modification time not preserved by checkout |
want to store file's modification time during commit |
|
| 2010-11-23 17:32:37 |
Levi Purvis |
bug |
|
|
added subscriber Levi Purvis |
| 2011-01-31 15:52:59 |
Tim Halvorsen |
bug |
|
|
added subscriber Tim Halvorsen |
| 2017-06-23 00:49:34 |
Jelmer Vernooij |
tags |
|
new-format |
|
| 2017-06-23 00:49:40 |
Jelmer Vernooij |
bug task added |
|
brz |
|
| 2017-06-23 00:50:57 |
Jelmer Vernooij |
brz: status |
New |
Triaged |
|
| 2017-06-23 00:51:01 |
Jelmer Vernooij |
brz: importance |
Undecided |
Wishlist |
|
