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 Mon, 25 Jun 2007 14:17:26 GMT

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

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

I agree, we should state that GNU tar (or compatible) is required.

> I thought of doing a manual step of untar-ring with a non gnu-tar, then tarring back
up with a non-tar utility, or tar with --format=ustar, and using that, but then the md5 checksum
will fail...Is that acceptable?

No, that's not acceptable. The md5 checksums would have to be recreated too, otherwise they
are useless. But I'm not sure we want too many manual steps in the release process, so stating
that GNU tar is required is probably sufficient. Most platforms come with unzip or GNU tar
installed by default, so it shouldn't be a big problem as long as the requirements are clearly
stated.

There was a similar discussion on the Ivy list a couple of months ago.
<URL:http://mail-archives.apache.org/mod_mbox/incubator-ivy-dev/200704.mbox/%3C20070402183548.GA25940@petunia.outback.escape.de%3E>

I think they ended up with a disclaimer on the download page. One of the messages in the thread
said:

> Ant and many other projects include a disclaimer about requiring GNU
> tar on the download page.  I'd suggest to do the same for Ivy as well.

A good idea for Derby too, I think.

> 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