Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
From: Tim Dudgeon <tdudgeon@informaticsmatters.com>
Subject: Re: [jira] Resolved: (DERBY-1489) Provide ALTER TABLE DROP COLUMN
       functionality
Date: Sat, 07 Oct 2006 19:18:56 +0100
Lines: 46
Message-ID: <eg8r2g$77v$1@sea.gmane.org>
References: <21326448.1152375449855.JavaMail.jira@brutus>
 <2300554.1160090241912.JavaMail.root@brutus> <eg7lnu$2l1$1@sea.gmane.org>
 <4527DE4D.6040102@amberpoint.com> <eg8p4f$1qv$1@sea.gmane.org>
 <4527EE5F.8030607@amberpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.4 (X11/20060614)
In-Reply-To: <4527EE5F.8030607@amberpoint.com>
Sender: news <news@sea.gmane.org>

That could be it - I'm on Linux.
I'll try build from svn first.


Tim

Bryan Pendleton wrote:
>> I downloaded the 10.2.1.6 sources, and tried to apply the path to those.
>> patch -p0 < drop_column_v8_restored_tests.diff
> 
> That seems like a reasonable technique. I tried a similar, but not 
> identical,
> experiment: I took my 10.2 svn sandbox, and I ran patch -p0 <drop_...diff
> and it seemed to work fine, although I got a few "offset 10 lines" 
> messages.
> 
> I just tried some experiments with the sources from the download zip site
> http://db.apache.org/derby/releases/release-10.2.1.6.cgi
> and I think the problem may have to do with line-end characters.
> 
> Are you working on a Windows system or on a Unix system?
> 
> The files in the source release appear to have DOS line end characters and
> that seems to confuse the patch program.
> 
> Here's three suggestions:
> 1) Pull a svn client of the 10.2 branch and apply the patches to that. I've
> done it and I believe it works. Plus, that will make it easier for you to
> manage the patch process down the road with subsequent releases of the 
> 10.2 branch
> 2) If you're on a Unix system, try grabbing the sources and patching them
> on a Windows system. The line end characters may not be a problem then.
> 3) Use a tool to convert the line end characters of the files needing to be
> patched from DOS format to Unix format, then try applying the patch.
> 
> Meanwhile, I'll ask separately on the developer's list about line end 
> characters
> in the source distributions.
> 
> thanks,
> 
> bryan
> 
> 
> 
>