bzr should fix timestamps on export
Bug #515631 reported by
Steve Langasek
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
High
|
Robert Collins | ||
| bzr-builddeb (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Trying to run 'bzr bd' on pam, I wind up with an export where doc/specs/parse_y.c has a timestamp older than doc/specs/parse_y.y by a few microseconds, so the makefile tries to rebuild it. But the package doesn't build-depend on yacc, because the target *isn't* out of date within the upstream tarball, and the build fails nicely.
If the bzr export doesn't preserve the timestamps from the original tarball or from the working directory, then it should at least make sure they're all set to the same value.
Related branches
lp:~lifeless/bzr/bug-515631
- James Westby: Approve
-
Diff: 120 lines (+41/-11)3 files modifiedNEWS (+4/-0)
bzrlib/export/dir_exporter.py (+8/-9)
bzrlib/tests/test_export.py (+29/-2)
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| summary: |
- bzr-builddeb does not preserve timestamps on export, wants to rebuild - targets that are current + bzr should fix timestamps on export |
Revision history for this message
| James Westby (james-w) wrote | #2 |
| tags: | added: udd |
| Changed in bzr-builddeb (Ubuntu): | |
| status: | New → Invalid |
| Changed in bzr: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| tags: | removed: amd64 apport-bug lucid |
| description: | updated |
| Changed in bzr: | |
| assignee: | nobody → Robert Collins (lifeless) |
| milestone: | none → 2.2.0 |
| Changed in bzr: | |
| status: | Confirmed → Fix Released |
| Changed in bzr: | |
| milestone: | 2.2.0 → 2.2.0b1 |
To post a comment you must log in.
The dir-exporter code should have something similar done as was done for
working tree operations (or perhaps even be ported to TreeTransform?)
Thanks,
James