hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis Liu (JIRA)" <>
Subject [jira] [Created] (HIVE-3224) build dependencies download is failing because of sha-1 mismatch
Date Tue, 03 Jul 2012 01:42:58 GMT
Francis Liu created HIVE-3224:

             Summary: build dependencies download is failing because of sha-1 mismatch
                 Key: HIVE-3224
             Project: Hive
          Issue Type: Bug
    Affects Versions: 0.9.1
            Reporter: Francis Liu

Building either trunk or branch-0.9 is failing because of sha-1 dependencies. You'll have
to clear your ivy cache (rm ~/.ivy2) to reproduce it. It seems the sha-1 for hadoop-core and
hadoop-test don't match.  See below.

[ivy:resolve] .. (0kB)
[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve] 		[FAILED     ] org.apache.hadoop#hadoop-core;0.20.2!hadoop-core.jar: invalid
sha1: expected=200f54e0051f3148fae8d8fb66fa3f477e52777f computed=715b8d44fe3d3b692da62d60f0a5e6d8e564e854
[ivy:resolve] 		[FAILED     ] org.apache.hadoop#hadoop-core;0.20.2!hadoop-core.jar:  (0ms)
[ivy:resolve] 	==== local: tried
[ivy:resolve] 	  /Users/fcliu/.ivy2/local/org.apache.hadoop/hadoop-core/0.20.2/jars/hadoop-core.jar
[ivy:resolve] 	==== apache-snapshot: tried
[ivy:resolve] 	==== maven2: tried
[ivy:resolve] 	==== datanucleus-repo: tried
[ivy:resolve] 	==== hadoop-source: tried
[ivy:resolve] 	==== hadoop-source2: tried
[ivy:resolve] 		[FAILED     ] org.apache.hadoop#hadoop-test;0.20.2!hadoop-test.jar: invalid
sha1: expected=0547f30bb192ac86ec30b024cc1c44f5ca7c5029 computed=de3813424008d1193254742e341df193742404a0
[ivy:resolve] 		[FAILED     ] org.apache.hadoop#hadoop-test;0.20.2!hadoop-test.jar:  (0ms)
[ivy:resolve] 	==== local: tried
[ivy:resolve] 	  /Users/fcliu/.ivy2/local/org.apache.hadoop/hadoop-test/0.20.2/jars/hadoop-test.jar
[ivy:resolve] 	==== apache-snapshot: tried

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message