-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan wrote:
> The patch looks more like Morse code than a unified diff (it's
> quite corrupted). Use the one I posted earlier today.
Heh...you're right. That patch was corrupt.
Anyway, it patches fine now, but now I get an error on make
No need to CC me; I'm subscribed to the list.
Mike Loiterman wrote:
> Kris Deugau wrote:
> > The patch was created by someone else. I didn't apply it directly,
> > as I wanted a patch to apply during a .rpm build, so I rebuilt it
> > as a "whole-source-tree" patch. I've just pushed it out to
>
"Mike Loiterman" <[EMAIL PROTECTED]> writes:
> Is this the patch you posted:
>
> - - - --- Client/Core.pm~ 2002-11-25 19:07:38.0 +0100
> +++ Client/Core.pm2002-11-25 18:55:35.0 +0100
> @@ -216,8 +216,10 @@
> foreach $rr ($query->answer) {
> my $pushe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kris Deugau wrote:
> Mike Loiterman wrote:
>> I followed the instuructions below to patch Razor2's taint
>> problem. The Config.pm patch worked perfectly, but the Core.pm
>> patch failed at hunk 1. Is this an SA issue, or a Razor
>> issue..(i.e. pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I posted my latest patches for razor 2.34 here a few days ago. I
Is this the patch you posted:
- - - --- Client/Core.pm~ 2002-11-25 19:07:38.0 +0100
+++ Client/Core.pm 2002-11-25 18:55:35.0 +0100
@@ -216,8 +216,10 @@
> "ML" == Mike Loiterman <[EMAIL PROTECTED]> writes:
ML> I followed the instuructions below to patch Razor2's taint problem.
ML> The Config.pm patch worked perfectly, but the Core.pm patch failed at
ML> hunk 1. Is this an SA issue, or a Razor issue..(i.e. patch created
ML> by Razor folks or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I followed the instuructions below to patch Razor2's taint problem.
The Config.pm patch worked perfectly, but the Core.pm patch failed at
hunk 1. Is this an SA issue, or a Razor issue..(i.e. patch created
by Razor folks or SA folks)?
- --- sta
