commands updating working tree should provide the same modification time for all modified files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
John A Meinel |
Bug Description
Many package sources includes files generated from other
files which are also included in the tree.
There are cases where bzr produce inconsistent time stamps
(the generated file is modified before its source file).
This occurs rarely but kind of makes it worse. It's true that the
packages have build dependencies so the needed tools are known,
but in some circumstances, the upstream packager may have use a
different version of a tool and produced a file that the Ubuntu packager
cannot reproduce exactly (we encounter a variation of
that problem on the bzr project when people use different pyrex
versions).
Ideally, all files modified by a given command (branch, checkout, update, pull, etc) should receive
the exact same timestamp.
Using futimes() should help address the problem on Linux.
I don't know if that's available on Windows though (it is on OSX and FreeBSD)
Related branches
- Vincent Ladeuil: Approve
- Martin Packman (community): Approve
-
Diff: 108 lines (+43/-1)3 files modifiedNEWS (+6/-0)
bzrlib/tests/test_transform.py (+25/-1)
bzrlib/transform.py (+12/-0)
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: udd |
Changed in bzr: | |
milestone: | 2.1.0 → 2.1.0rc1 |
status: | Fix Committed → Fix Released |
Thanks for filing this Vincent. Uhm, Its a dup :).
-Rob