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
* Kurt Roeckx ([EMAIL PROTECTED]) [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
severity 402179 important
user debian-release@lists.debian.org
usertag 402179 rc-m68k
thanks
On Mon, Jan 08, 2007 at 07:39:46PM +0100, Andreas Barth wrote:
* Kurt Roeckx ([EMAIL PROTECTED]) [070108 19:35]:
Anyway, the only reason I see that we want to fix it in etch now is that
in case we
On Sat, 2007-01-06 at 17:26 +0100, Kurt Roeckx wrote:
Hi,
What's the status of this bug? There's a patch available form upstream
for some time now.
Would you mind I did an NMU for this?
I'm working on 1.16.1 for unstable. Are you contemplating an NMU for
unstable or etch?
Bdale
--
On Sun, Jan 07, 2007 at 11:06:33AM -0700, Bdale Garbee wrote:
On Sat, 2007-01-06 at 17:26 +0100, Kurt Roeckx wrote:
Hi,
What's the status of this bug? There's a patch available form upstream
for some time now.
Would you mind I did an NMU for this?
I'm working on 1.16.1 for
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
Hi,
What's the status of this bug? There's a patch available form upstream
for some time now.
Would you mind I did an NMU for this?
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
This bug seems to only occur for the posix format tar archives. It's
repeatable outside the tar test suite by doing:
#!/bin/sh
export TAR_OPTIONS=-H posix --pax-option=exthdr.name=%d/PaxHeaders/%f
echo hello file1
echo goodbye file2
while :; do
tar cf archive.1 file1 file2
tar cfT
Package: tar
Version: 1.16-2
Severity: serious
Hello Bdale,
tar test-suite tests/append02.at has a race condition which cause
the test to fail sometimes, and thus the package to FTBFS.
echo Creating archive.1
tar cf archive.1 file1 file2
here
echo Creating archive.2
tar cfT archive.2
9 matches
Mail list logo
