bzr should fix timestamps on export

Bug #515631 reported by Steve Langasek on 2010-02-01
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Robert Collins
bzr-builddeb (Ubuntu)

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.

Tags: udd Edit Tag help

Related branches

Steve Langasek (vorlon) wrote :
James Westby (james-w) on 2010-02-01
summary: - bzr-builddeb does not preserve timestamps on export, wants to rebuild
- targets that are current
+ bzr should fix timestamps on export
James Westby (james-w) wrote :

The dir-exporter code should have something similar done as was done for
working tree operations (or perhaps even be ported to TreeTransform?)



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
John A Meinel (jameinel) on 2010-02-02
Changed in bzr:
status: Confirmed → Fix Released
Vincent Ladeuil (vila) on 2010-02-19
Changed in bzr:
milestone: 2.2.0 → 2.2.0b1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers