On Sun, 2007-01-07 at 19:13 +0100, Kurt Roeckx wrote: > I was planning on getting it into etch.
As I've stated before, I'm not sure that fixing this bug for etch is really useful. Of course, if there's a reason to update the tar in etch for a security bug or something similar, fixing this too would make good sense. But since it's only a race condition in the regression suite and makes no difference to the tar binary itself, and the tar package in etch is already built for all relevant release architectures, taking the risk of changing the tar package just to fix this isn't obviously worthwhile to me. The right fix for unstable is 1.16.1 plus patches from upstream. While I think this version is generally better than 1.16, enough has changed that I would *not* expect the release team to want this version for etch at this late date. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
