lkml.org 
[lkml]   [1998]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Broken patch-2.1.106 on linux-kernel-patch, do not apply
Date
On Sat, 13 Jun 1998 20:41:28 -0400 (EDT), 
George <greerga@nidhogg.ham.muohio.edu> wrote:
>On Sun, 14 Jun 1998, Keith Owens wrote:
>>The uuencoded version of patch-2.1.106.gz on the linux-kernel-patch
>>mailing list is broken and should not be applied. gunzip complains
>>about premature end of file.
>
>I don't have a problem with premature end of file.
>
>nidhogg:~$ uudecode 2.1.106;gunzip patch-2.1.106.gz

That is seriously wierd. I definitely have a broken patch after
uudecode.

cmp -l mailed/patch-2.1.106.gz kernel.org/patch-2.1.106.gz

317746 72 244
317747 221 147
317748 235 101
317749 6 232
317750 153 375
317751 365 177
317752 377 311
317753 46 206
317754 30 32
317755 152 256
317756 272 266
317757 331 130
317758 140 23
317759 114 0

Getting a clean patch-2.1.106.gz from ftp.kernel.org, uuencoding it and
comparing with the mailed patch, there is a difference in the last
line.

..I&=!FOU_R88:KK98$P`` mailed uuencode
.I&=!FOU_R88:KK98$P`` ftp.kernel.org patch-2.1.106.gz, uuencoded
`
end

So either the mail was corrupted in transit or there are differences in
uuencode/uudecode. My version is sharutil-4.2-8 (rpm), I get the same
effect with sharutils-4.2-5. Which version of uudecode do you have?
What does the last line of your version of the mailed patch say?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.205 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site