[MacPorts] #35332: py-keyring will not install

[MacPorts]

#35332: py-keyring will not install
---------------------------------------+------------------------------------
 Reporter:  pavel.hlavnicka@…          |       Owner:  and.damore@…           
     Type:  defect                     |      Status:  assigned               
 Priority:  Normal                     |   Milestone:                         
Component:  ports                      |     Version:  2.1.2                  
 Keywords:                             |        Port:  py-keyring             
---------------------------------------+------------------------------------

Comment(by pavel.hlavnicka@…):

 not sure if this is anyhow helpful... but if I run {{{sudo port -d install
 py-keyring}}} I got the well known error

 {{{
 DEBUG: Executing command line:  cd
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_release_tarballs_ports_python_py-
 keyring/py27-keyring/work/keyring-0.6.2" &&
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
 setup.py --no-user-cfg build
 Traceback (most recent call last):
   File "setup.py", line 24, in <module>
     version = runcmd(['/usr/bin/xcodebuild', '-version'],
 {})[0].splitlines()[0]
 IndexError: list index out of range
 }}}

 but then if I did {{{cd /opt/local....}}} from the failed command and then
 {{{sudo
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
 setup.py --no-user-cfg build}}} from the command line, I got this

 {{{
 running build
 running build_py
 creating build
 creating build/lib.macosx-10.8-x86_64-2.7
 creating build/lib.macosx-10.8-x86_64-2.7/keyring
 copying keyring/__init__.py -> build/lib.macosx-10.8-x86_64-2.7/keyring
 copying keyring/backend.py -> build/lib.macosx-10.8-x86_64-2.7/keyring
 copying keyring/cli.py -> build/lib.macosx-10.8-x86_64-2.7/keyring
 copying keyring/core.py -> build/lib.macosx-10.8-x86_64-2.7/keyring
 copying keyring/getpassbackend.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring
 copying keyring/http.py -> build/lib.macosx-10.8-x86_64-2.7/keyring
 creating build/lib.macosx-10.8-x86_64-2.7/keyring/tests
 copying keyring/tests/__init__.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/tests
 copying keyring/tests/test_backend.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/tests
 copying keyring/tests/test_cli.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/tests
 copying keyring/tests/test_core.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/tests
 copying keyring/tests/test_util.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/tests
 creating build/lib.macosx-10.8-x86_64-2.7/keyring/util
 copying keyring/util/__init__.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/util
 copying keyring/util/escape.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/util
 creating build/lib.macosx-10.8-x86_64-2.7/keyring/backends
 copying keyring/backends/__init__.py ->
 build/lib.macosx-10.8-x86_64-2.7/keyring/backends
 running build_ext
 building 'osx_keychain' extension
 creating build/temp.macosx-10.8-x86_64-2.7
 creating build/temp.macosx-10.8-x86_64-2.7/keyring
 creating build/temp.macosx-10.8-x86_64-2.7/keyring/backends
 /usr/bin/clang -fno-strict-aliasing -fno-common -dynamic -pipe -O2 -fwrapv
 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
 -c keyring/backends/osx_keychain.c -o
 build/temp.macosx-10.8-x86_64-2.7/keyring/backends/osx_keychain.o
 /usr/bin/clang -bundle -undefined dynamic_lookup -L/opt/local/lib
 build/temp.macosx-10.8-x86_64-2.7/keyring/backends/osx_keychain.o
 -L/System/Library/Frameworks/ -o
 build/lib.macosx-10.8-x86_64-2.7/osx_keychain.so -framework Security
 -framework CoreFoundation -framework CoreServices
 }}}

 I'm not familiar with macports build process - so this observation can be
 meaning less - or it shows that the environment is somehow modified by
 invoking {{{port install...}}} compared to a vanilla command line.
 environment.

 Can this help somehow?

-- 
Ticket URL: <https://trac.macports.org/ticket/35332#comment:14>
MacPorts <http://www.macports.org/>
Ports system for Mac OS