Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 May 2019 18:35:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 238267] sysutils/py-google-compute-engine not correctly defaulting to using python 2.7.
Message-ID:  <bug-238267-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238267

            Bug ID: 238267
           Summary: sysutils/py-google-compute-engine not correctly
                    defaulting to using python 2.7.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: gjb@FreeBSD.org
                CC: ler@FreeBSD.org, lucas.kanashiro@collabora.com
             Flags: maintainer-feedback?(lucas.kanashiro@collabora.com)

There seems to be an incompatibility with the sysutils/py-google-compute-en=
gine
port and the default lang/python (python3.6) that causes GCE-specific start=
up
scripts to fail to run.

Investigating further after applying a fix to the GCE image build files whi=
ch
added DEFAULT_VERSIONS=3Dpython=3D2.7 to the environment, the port continue=
d to be
built using python3.6 as the default version.

While chroot(8)ed to the resulting image to inspect further, I found this:

 root@:/usr/local/etc/rc.d # grep ^command_interpreter google_*
 google_accounts_daemon:command_interpreter=3D"/usr/local/bin/python2.7"
 google_clock_skew_daemon:command_interpreter=3D"/usr/local/bin/python2.7"
 google_instance_setup:command_interpreter=3D"/usr/local/bin/python2.7"
 google_network_daemon:command_interpreter=3D"/usr/local/bin/python2.7"
 google_startup:command_interpreter=3D"/usr/local/bin/python2.7"

However, the environment suggests python3.6 is being used for compiled
binaries.

 root@:/# file /usr/local/bin/launch_instance
 /usr/local/bin/launch_instance: symbolic link to launch_instance-3.6

 root@:/usr/ports/sysutils/py-google-compute-engine # make \
    __MAKE_CONF=3D/dev/null -V PYTHON_VER
 3.6

 root@:/usr/ports/sysutils/py-google-compute-engine # make \
    __MAKE_CONF=3D/dev/null -V SUB_LIST

 PYTHON_CMD=3D"/usr/local/bin/python3.6"  \
 PYTHON_VER=3D"3.6" PREFIX=3D/usr/local LOCALBASE=3D/usr/local  \
 DATADIR=3D/usr/local/share/py36-google-compute-engine \
 DOCSDIR=3D/usr/local/share/doc/py36-google-compute-engine \
 EXAMPLESDIR=3D/usr/local/share/examples/py36-google-compute-engine  \
 WWWDIR=3D/usr/local/www/py36-google-compute-engine \
 ETCDIR=3D/usr/local/etc/py36-google-compute-engine

 root@:/usr/ports/sysutils/py-google-compute-engine # make \
 __MAKE_CONF=3D/dev/null -V FLAVOR
 py36

I believe DEFAULT_VERSIONS=3Dpython=3D2.7 needs to be added to the port Mak=
efile to
fix this until these scripts work properly with python3.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238267-7788>