Deron Meranda wrote:
> On an unrelated note, I have also tried to compare sources against the
> Savannah Git repository, and I noted that the repository has a couple small
> differences from the FTP files + patches.
>
> The Git repo has a blank file called "-i", probably an accident of some
> comm
On 9/28/14, 12:51 AM, Deron Meranda wrote:
> I was wondering if anybody was going to address the problem with 4.2 patch
> 49 ?
I've attached a corrected version and I will update the FTP sites today.
> Not only is there a critical line of code missing, but the the 'patch'
> command will also fail
Deron Meranda:
> I was wondering if anybody was going to address the problem with 4.2 patch
> 49 ?
>
> It is still corrupted on the FTP server. There are a few lines that appear
> to have been deleted out of the middle of the patch file.
Indeed.
> Not only is there a critical line of code miss
I was wondering if anybody was going to address the problem with 4.2 patch
49 ?
It is still corrupted on the FTP server. There are a few lines that appear
to have been deleted out of the middle of the patch file.
Not only is there a critical line of code missing, but the the 'patch'
command will
I'm trying to patch Bash 4.2 with the latest patch 049. It appears as if
the patch file itself is corrupted. The corresponding patch 026 for Bash
4.3 is fine.
When running patch with mostly default arguments, it seems to work but has
to use merge fuzzing, which it complains about...
$ patch -p0
