[ 
https://issues.apache.org/jira/browse/BEAM-8787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224865#comment-17224865
 ] 

Elliotte Rusty Harold edited comment on BEAM-8787 at 11/2/20, 6:20 PM:
-----------------------------------------------------------------------

Verified that current instructions are still inaccurate in at least some ways:

 

sudo] password for elharo: 
 Reading package lists... Done
 Building dependency tree 
 Reading state information... Done
 Package python-pip is not available, but is referred to by another package.
 This may mean that the package is missing, has been obsoleted, or
 is only available from another source
 However the following packages replace it:
 python3-pip


was (Author: elharo):
Veirifed that current instructions are still inaccurate in at least some ways:

 

sudo] password for elharo: 
Reading package lists... Done
Building dependency tree 
Reading state information... Done
Package python-pip is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
 python3-pip

> Python setup issues
> -------------------
>
>                 Key: BEAM-8787
>                 URL: https://issues.apache.org/jira/browse/BEAM-8787
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>    Affects Versions: 2.16.0
>         Environment: debian x86 (gLinux)
>            Reporter: Elliotte Rusty Harold
>            Priority: P1
>
> This could be an issue with incomplete or inaccurate contributing docs. tldr; 
> `./gradlew check` fails on Debian after initial checkout.
> The docs say that one should first run:
> sudo apt-get install \
>     openjdk-8-jdk \
>     python-setuptools \
>     python-pip \
>     virtualenv
> but even after running this pieces are missing. I'm still debugging exactly 
> what's missing but the symptoms look like this:
> > Task :sdks:python:test-suites:tox:py35:setupVirtualenv FAILED
> The path python3.5 (from --python=python3.5) does not exist
> > Task :sdks:python:test-suites:tox:py36:setupVirtualenv FAILED
> [ant:fmpp] Traceback (most recent call last):
> [ant:fmpp]   File "/usr/lib/python3/dist-packages/virtualenv.py", line 25, in 
> <module>
> [ant:fmpp]     import distutils.sysconfig
> [ant:fmpp] ModuleNotFoundError: No module named 'distutils.sysconfig'
> ...
> FAILURE: Build completed with 2 failures.
> 1: Task failed with an exception.
> -----------
> * What went wrong:
> Execution failed for task ':sdks:python:test-suites:tox:py35:setupVirtualenv'.
> > Process 'command 'virtualenv'' finished with non-zero exit value 3
> Indeed there is no Python 3.5 on this system:
> gnome-user-share                      python2.6
> gnome-vfs-2.0                         python2.7
> gnupg                                 python3
> gnupg2                                python3.6
> gold-ld                               python3.7
> goobuntu-config-tools                 python3.8
> But nowhere in the setup docs do we say that Python 3.5 is required to build 
> this. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to