Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Date: Thu, 16 Jul 2009 09:11:58 +0200
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: tar issue in ant snapshot target
In-reply-to: <4A5E675C.6030509@sbcglobal.net>
Sender: Kristian.Waagan@Sun.COM
To: derby-dev@db.apache.org
Message-id: <4A5ED2BE.7030504@Sun.COM>
Organization: Sun Microsystems Inc.
References: <4A5E5E96.5030302@sbcglobal.net> <4A5E6465.3060209@sbcglobal.net>
 <4A5E675C.6030509@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)

Kathey Marsden wrote:
> Kathey Marsden wrote:
>> Kathey Marsden wrote:
>>> I am getting lots of warnings like the one below with the
>>> ant snapshot target when trying to make the release.
>>>
>>>   [tar] Entry: 
>>> db-derby-snapshot-debug-10.5.2.0-794445/javadoc/publishedapi/jdbc4/org/apache/derby/vti/package-tree. 
>>>
>>> html longer than 100 characters.
>>>
>>> Is this an issue?
>>>
>>> Thanks
>>>
>>> Kathey
>>>
>>>
>> I guess this is an issue: If I go ahead and do ant release and then try
>> [C:/tmp] tar tvf db-derby-10.5.2.0-bin.tar | grep vti | grep package
>>
>> I see the files there, but also @LongLink messages.  It's been a 
>> while since I made a release candidate but don't remember this problem.
>>
>> tar: blocksize = 20
>> USTAR Version
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> ././@LongLink: Unknown file type field value `L'
>> -rw-r--r--   1 0        0           1076  Jul 15 15:55 
>> db-derby-10.5.2.0-bin/javadoc/jdbc3/org/apache/derby/vti/package-
>> frame.html
>> -rw-r--r--   1 0        0          10032  Jul 15 15:55 
>> db-derby-10.5.2.0-bin/javadoc/jdbc3/org/apache/derby/vti/package-
>> summary.html
>> -rw-r--r--   1 0        0           6563  Jul 15 15:55 
>> db-derby-10.5.2.0-bin/javadoc/jdbc3/org/apache/derby/vti/package-
>> tree.html
>> -rw-r--r--   1 0        0           1076  Jul 15 15:55 
>> db-derby-10.5.2.0-bin/javadoc/jdbc4/org/apache/derby/vti/package-
>> frame.html
>> -rw-r--r--   1 0        0          10032  Jul 15 15:55 
>> db-derby-10.5.2.0-bin/javadoc/jdbc4/org/apache/derby/vti/package-
>> summary.html
>> -rw-r--r--   1 0        0           6563  Jul 15 15:55 
>> db-derby-10.5.2.0-bin/javadoc/jdbc4/org/apache/derby/vti/package-
>> tree.html
>>
>>
> The @LongLink messages  were with mks tar. With cygwin tar I don't see 
> the errors with tar tvf.  Based on the discussion in DERBY-2839 this 
> is to be expected with the src tarball but not the bin distribution.  
> Advice welcome.

Hi Kathey,

At this point, my only advice would be to use GNU tar.
What have the previous release managers done?


-- 
Kristian

>
>
> Kathey
>
>