db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2839) initial problems with the 10.3.1.0 beta candidate
Date Thu, 21 Jun 2007 08:48:26 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506800
] 

Knut Anders Hatlen commented on DERBY-2839:
-------------------------------------------

Re 2)
GNU tar uses a (non-standard) format to store file names longer than 100 characters. For instance,
using Solaris tar to extract the src-tar distribution, I get lots of messages like this

tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
....

and long names get truncated, for instance
db-derby-10.3.1.0-src/java/client/org/apache/derby/client/am/UpdateSensitiveBlobLocatorInputStream.java
-> db-derby-10.3.1.0-src/java/client/org/apache/derby/client/am/UpdateSensitiveBlobLocatorInputStream.j

Extracting the archive with GNU tar does not truncate the names.

If I recreate the archive with GNU tar and tells it to use a standard format with "--format=ustar",
Solaris tar has no problem with the long names. According to the GNU tar manual, --format=ustar
will produce a POSIX.1-1988 compatible archive, which supports file names up to 256 characters.
As far as I can see, 256 characters is sufficient for the source distribution.

Probably not a big problem since GNU tar is available on most platforms, but generally I think
using a standards-compliant format is better.

> initial problems with the 10.3.1.0 beta candidate
> -------------------------------------------------
>
>                 Key: DERBY-2839
>                 URL: https://issues.apache.org/jira/browse/DERBY-2839
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.1.0
>            Reporter: Rick Hillegas
>            Assignee: Myrna van Lunteren
>            Priority: Blocker
>             Fix For: 10.3.1.0
>
>         Attachments: DERBY-2839_3-doc.diff, DERBY-2839_3-src.diff
>
>
> 1) Problem unzipping derby_doc_plugin_1.1.0.zip and derby_ui_plugin_1.1.0.zip:
> rick doc-plugin (1.4) > unzip derby_doc_plugin_1.1.0.zip
> Archive:  derby_doc_plugin_1.1.0.zip
>   End-of-central-directory signature not found.  Either this file is not
>   a zipfile, or it constitutes one disk of a multi-part archive.  In the
>   latter case the central directory and zipfile comment will be found on
>   the last disk(s) of this archive.
> unzip:  cannot find zipfile directory in one of derby_doc_plugin_1.1.0.zip or
>         derby_doc_plugin_1.1.0.zip.zip, and cannot find derby_doc_plugin_1.1.0.zip.ZIP,
period.
> 2) Old problem: Filenames in the src-tar distribution are truncated. What
> is the use of this distribution?
> 3) Broken links in index.html:
>   - Could not find link to pdf for Getting Started. The file is called
>     getstartderby.pdf but the link references getstart.pdf
>   - Could not find link to either of the html files for Working with Derby. The actual
directory
>     is workingwithderbytemp but should be workingwithderby
>   - Could not find the pdf for Working with Derby either. The
>     workingwithderby subdirectory doesn't exist under the pdf branch.
>   - Could not find pdf for Admin Guide. The file is called
>     derbyadmin.pdf but the link specifies adminguide.pdf

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message