Hi,

It's my NMU that is involved, but I'm curious - why is this:
a) causing the build to halt
b) happening at all?

The error, if one actually exists, is not in the section you quoted,
but higher up:

...
tar: rivet-0.5.0/debian/control:
time stamp 2006-11-28 10:20:04 is 1088 s in the future
tar: rivet-0.5.0/debian/rules:
time stamp 2006-11-28 10:20:04 is 1088 s in the future
tar: rivet-0.5.0/debian/patches/05-configure.dpatch:
time stamp 2006-11-28 10:20:04 is 1088 s in the future
tar: rivet-0.5.0/debian/patches/10-tclconfig.dpatch:
time stamp 2006-11-28 10:20:04 is 1088 s in the future
tar: rivet-0.5.0/debian/patches/15-invalidlvalue.dpatch:
time stamp 2006-11-28 10:20:04 is 1088 s in the future
...
and so on.

Is the clock out on the hppa buildd?

Will a rebuild be attempted?

It's not an issue on any other builds (and my clock is fine at this
end).

What's actually happening here?

--


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

Attachment: pgpSCRKxCo119.pgp
Description: PGP signature

Reply via email to