Kelly.Ohair at Sun.COM
Wed Sep 17 09:29:35 PDT 2008
This binary file has a %[A-Z]% byte pattern in it, and when it gets
processed by sccs, those bytes get turned into an SCCS keyword value.
This problem was found when I did the Mercurial conversion, which gets
the SCCS 'pre-keyword' file contents.
I'd ignore this one, except for the fact that is is a binary file. :^(
Joseph D. Darcy wrote:
> Mark Wielaard wrote:
>> Hi Joe,
>> On Sun, 2008-09-14 at 23:31 -0700, Joseph D. Darcy wrote:
>>> Hmm. That is strange; the file doesn't have any delta's on it after
>>> its creation so it should be the same for each build; these are the
>>> hashes I get on the file in my workspace:
>>> md5 (test.txt) = 85833c4399256ea461d68601fc8c146c
>>> sha1 (test.txt) = 317740eed4a0e3d13887dead3507c7d9e6442edb
>> So the md5 sum from the b11 tar.gz is:
>> And for the b12 tar.gz:
>> The one from jdk7 mercurial is also different btw:
>> Converting with hexdump and creating a diff gives:
>> --- jdk6-b11.text.txt.hex
>> +++ jdk6-b12.text.txt.hex
>> @@ -13798,7 +13798,7 @@
>> 0035e50 745b 3159 6d55 1768 2b2b 104c 5120 3960
>> 0035e60 2a37 5a21 1d4e 562e 6521 6c0e 3245 306e
>> 0035e70 6061 5b16 1412 1549 5145 3c6e 305b 2f38
>> -0035e80 3730 312f 4330 4954 4556 600e 260f 5522
>> +0035e80 3830 322f 4338 4954 4556 600e 260f 5522
>> 0035e90 4923 3b68 3a74 4b59 4420 6b17 5c15 3026
>> 0035ea0 1d42 6b4b 5351 3d5c 2e12 1f59 6861 1b32
>> 0035eb0 6e1c 555a 3124 541f 2d2f 1352 4b1b 6958
>> So somewhere between your and mine machine this one byte gets changed.
>> Maybe in the packing or unpacking of the tar.gz file?
> I'm looking into what might be going on.
More information about the jdk6-dev