Re: Bug#402179: tar: FTBFS: race condition in test-suite
severity 402179 important
usertag 402179 rc-m68k
On Mon, Jan 08, 2007 at 07:39:46PM +0100, Andreas Barth wrote:
> * Kurt Roeckx (email@example.com) [070108 19:35]:
> > Anyway, the only reason I see that we want to fix it in etch now is that
> > in case we later want a new version of tar in etch we don't get hit by
> > the problem.
> If I look at the stats, it doesn't seem too probably to be hit by it,
> and a simple retry would resolve it.
I think we've been fence-sitting on this long enough.
Most of the time, timestamp race condition bugs will affect certain kernels
or architectures with a high probability because the filesystem's timestamp
resolution is high enough that a clock cycle is a significant fraction of
it. That doesn't seem to be the case here, with the /possible/ exception of
m68k; on all other archs, the probability of hitting the race is low enough
that working around it by retrying the package is trivial.
So I think downgrading the bug is ok here, with an "rc-m68k" usertag because
of the uncertainty on that arch.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.