[slf4j-dev] lone zero block in slf4j-1.0-beta4.tar.gz

[Curt Arnold]

Untarring slf4j-1.0-beta4.tar.gz will (at least on my system) display  
a warning (tar: a lone zero block at 1361) that suggests it was  
prepared with an non-current version of ant (1.6.2 or earlier).  Ant  
1.6.3 or later (1.6.5 is current) should have the fix and produce  
tarballs that do not result in the warning.  The warning appears to  
be strictly cosmetic.  The issue popped up in the one of the release  
candidates for log4j 1.2.11 and was discussed in the following thread.

Begin forwarded message:

> From: Simon Kitching <skitching at apache.org>
> Date: May 22, 2005 11:37:52 PM CDT
> To: Log4J Developers List <log4j-dev at logging.apache.org>
> Subject: Re: 1.2.11rc1 Build
> Reply-To: Log4J Developers List <log4j-dev at logging.apache.org>
> Reply-To: skitching at apache.org
>
>
> <release-notes>
> Changes from Ant 1.6.2 to Ant 1.6.3
> ===================================
>
> Changes that could break older environments:
> --------------------------------------------
>
> * The subant task used the canonical version of a file path. This
>   has been changed to use the absolute path. Bugzilla 30438.
>
> * Tar now writes two EOF blocks rather than one.
>   Bugzilla report 28776
>
> ...
> </release-notes>
>
> Regards, Simon
> -- 
> A. Because it breaks the logical sequence of discussion
> Q. Why is top posting bad?
>
> On Sun, 2005-05-22 at 21:23 -0700, Mark Womack wrote:
>
>> Hm.  I am using Ant 1.6.2, which should have the fix?
>>
>> -Mark
>>
>> ----- Original Message -----
>> From: "Simon Kitching" <skitching at apache.org>
>> To: "Log4J Developers List" <log4j-dev at logging.apache.org>
>> Sent: Sunday, May 22, 2005 9:02 PM
>> Subject: Re: 1.2.11rc1 Build
>>
>>
>>
>>> On Mon, 2005-05-23 at 13:48 +1000, Paul Smith wrote:
>>>
>>>> yep, that tar's downloading ok.
>>>>
>>>> The tar has an error when unpacking though, or maybe it's just a
>>>> warning.  When I do
>>>>
>>>> tar xfz logg*.tar.gz
>>>>
>>>> I get:
>>>>
>>>> tar: A lone zero block at 18809
>>>>
>>>
>>> That's a known bug in the Ant tar task: see
>>>  http://issues.apache.org/bugzilla/show_bug.cgi?id=28776
>>>
>>> You should use a fixed version of Ant to build the release.
>>>
>>> Most versions of tar just ignore this problem anyway. However one
>>> particular release of gnu tar tightened up checks and turned this  
>>> into a
>>> warning. Later versions of gnu tar dropped the warning message  
>>> for this
>>> problem as it was causing so many reports if I remember correctly...
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe at logging.apache.org
> For additional commands, e-mail: log4j-dev-help at logging.apache.org
>
>