On Sun, Jan 07, 2007 at 02:46:42PM -0700, Bdale Garbee wrote: > > 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.
I agree for the most part. But if you think this bug shouldn't be fixed for etch, I think it either needs to be marked as non release critical or it should be tagged etch-ignore. I've CC'd the release team, to get their input on it. 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. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]