[Bug 237872] sysutils/py-google-compute-engine: fix daemons in python 2.7 case

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237872

            Bug ID: 237872
           Summary: sysutils/py-google-compute-engine: fix daemons in
                    python 2.7 case
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: swills at FreeBSD.org
                CC: lucas.kanashiro at collabora.com
                CC: lucas.kanashiro at collabora.com
             Flags: maintainer-feedback?(lucas.kanashiro at collabora.com)

Created attachment 204351
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=204351&action=edit
add PYTHON_VER to py-google-compute-engine rc scripts rev0

The python 2.7 version of these packages fail like this on startup:

Starting google_network_daemon.                                                 
daemon: /usr/local/bin/google_network_daemon: No such file or directory         
Starting google_accounts_daemon.                                                
daemon: /usr/local/bin/google_accounts_daemon: No such file or directory        
Starting google_clock_skew_daemon.                                              
daemon: /usr/local/bin/google_clock_skew_daemon: No such file or directory      
eval: /usr/local/bin/google_metadata_script_runner: not found                   

The attached patch should fix it. Patch also includes some formatting changes.


This still leaves the question of why the python 2.7 version is being used in
the currently generated GCE images, given the release script doesn't specify
2.7:

https://svnweb.freebsd.org/base/head/release/tools/gce.conf?annotate=347056#l11

But that may be related to the fact that google-cloud-sdk is still marked
Python 2.7. Anyway, this patch should avoid the worst issue at the moment.


And also, I'm not sure whether py-google-compute-engine can really work with
python 3, since it uses py-boto which, doesn't seem to support Python 3:

https://github.com/boto/boto#introduction

although it was explicitly marked as USE_PYTHON=concurrent in ports r433425.
Maybe it doesn't matter or py-google-compute-engine should switch to boto3, but
that's an upstream issue.

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