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.
Binary package hint: bzr-builddeb
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.
ProblemType: Bug ture: all ature: Ubuntu 2.6.32- 11.15-generic
Architecture: amd64
Date: Mon Feb 1 10:25:34 2010
DistroRelease: Ubuntu 10.04
Package: bzr-builddeb 2.2~ubuntu4
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: bzr-builddeb
Uname: Linux 2.6.32-11-generic x86_64