hrsgn opened a new issue #3600:
URL: https://github.com/apache/incubator-heron/issues/3600


   **Describe the bug**
   when i use bazel(bazel build --config=centos heron/...) to buid the heron 
source code from "https://github.com/apache/incubator-heron.git",there is some 
error as below:
   Loading: 
   Loading: 0 packages loaded
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:3:5:
 //external:ant_ant_1_6_5: no such attribute 'netrc' in 'http_file' rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:9:5:
 //external:ant_ant_jar_sources_1_6_5: no such attribute 'netrc' in 'http_file' 
rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:15:5:
 //external:antlr_antlr_2_7_7: no such attribute 'netrc' in 'http_file' rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:21:5:
 //external:aopalliance_aopalliance_1_0: no such attribute 'netrc' in 
'http_file' rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:27:5:
 //external:aopalliance_aopalliance_jar_sources_1_0: no such attribute 'netrc' 
in 'http_file' rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:33:5:
 //external:cglib_cglib_3_1: no such attribute 'netrc' in 'http_file' rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:39:5:
 //external:cglib_cglib_jar_sources_3_1: no such attribute 'netrc' in 
'http_file' rule
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:45:5:
 //external:classworlds_classworlds_1_1_alpha_2: no such attribute 'netrc' in 
'http_file' rule
   ......
   ERROR: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/defs.bzl:2697:5:
 //external:xmlenc_xmlenc_0_52: no such attribute 'netrc' in 'http_file' rule
   ERROR: error loading package '': Encountered error while reading extension 
file 'python/repositories.bzl': no such package '@rules_python//python': error 
loading package 'external': Could not load //external package
   ERROR: error loading package '': Encountered error while reading extension 
file 'python/repositories.bzl': no such package '@rules_python//python': error 
loading package 'external': Could not load //external package
   INFO: Elapsed time: 0.788s
   INFO: 0 processes.
   FAILED: Build did NOT complete successfully (0 packages loaded)
   FAILED: Build did NOT complete successfully (0 packages loaded)
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1.$ git clone https://github.com/apache/incubator-heron.git && cd 
incubator-heron
      $ ./bazel_configure.py
   2. cd ~
      wget -O /tmp/bazel.sh 
https://github.com/bazelbuild/bazel/releases/download/0.26.0/bazel-0.26.0-installer-linux-x86_64.sh
      chmod +x /tmp/bazel.sh
    /tmp/bazel.sh --user
   3. cd   incubator-heron 
    bazel build --config=centos heron/...
   4. See error
   
   
   **Operating System**
    - OS: centOS7
    - python3.8.5
   
   **Additional context**
   [zw@centos01 incubator-heron]$ cd  
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/maven/
   [zw@centos01 maven]$ ll
   总用量 508
   -rw-rw-r--. 1 zw zw  272452  8月   5 17:41 BUILD
   -rw-rw-r--. 1 zw zw   1063     8月   5 17:41 compat_repository.bzl
   -rw-rw-r--. 1 zw zw 234652   8月   5 17:41 defs.bzl
   lrwxrwxrwx. 1 zw zw     43      8月   5 17:40 imported_maven_install.json -> 
/home/zw/incubator-heron/maven_install.json
   -rw-rw-r--. 1 zw zw      0        8月   5 17:41 netrc
   -rw-rw-r--. 1 zw zw    111      8月   5 17:41 WORKSPACE
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to