[MacPorts] #49350: py27-ptyprocess "no destroot found at..." when trying to install or upgrade

[MacPorts]

#49350: py27-ptyprocess "no destroot found at..." when trying to install or upgrade
-------------------------------------------------+-------------------------
 Reporter:  esbailey@…                           |      Owner:  macports-
     Type:  defect                               |  tickets@…
 Priority:  Normal                               |     Status:  new
Component:  ports                                |  Milestone:
 Keywords:  py27-ptyprocess, destroot, upgrade,  |    Version:  2.3.4
  install                                        |       Port:
                                                 |  py27-ptyprocess
-------------------------------------------------+-------------------------
 When attempting an upgrade of outdated packages, py27-ptyprocess fails
 with the following log:

 {{{
 :debug:install Executing org.macports.install (py27-ptyprocess)
 :debug:install Using /usr/bin/tar
 :debug:install Using /usr/bin/gzip
 :error:install org.macports.install for port py27-ptyprocess returned: no
 destroot found at:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_python_py-ptyprocess/py27-ptyprocess/work/destroot
 :debug:install Error code: NONE
 :debug:install Backtrace: no destroot found at:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_python_py-ptyprocess/py27-ptyprocess/work/destroot
     while executing
 "create_archive $location $portarchivetype"
     (procedure "portinstall::install_main" line 22)
     invoked from within
 "portinstall::install_main org.macports.install"
     ("eval" body line 1)
     invoked from within
 "eval $procedure $targetname"
 :info:install Warning: targets not executed for py27-ptyprocess:
 org.macports.activate org.macports.install
 :notice:install Please see the log file for port py27-ptyprocess for
 details:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_python_py-ptyprocess/py27-ptyprocess/main.log
 }}}

 I attempted the following with no success:

 {{{
 port clean installed
 port upgrade outdated
 }}}

 Same error.

 {{{
 port uninstall py27-ptyprocess
 port clean py27-ptyprocess
 port upgrade outdated
 }}}

 produced this message:

 {{{
 --->  Activating py27-ptyprocess @0.5_0
 Error: org.macports.activate for port py27-ptyprocess returned: Image
 error:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess-0.5-py2.7.egg-info already exists and does not
 belong to a registered port.  Unable to activate port py27-ptyprocess. Use
 'port -f activate py27-ptyprocess' to force the activation.
 Please see the log file for port py27-ptyprocess for details:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
 .org_release_ports_python_py-ptyprocess/py27-ptyprocess/main.log
 Error: Problem while installing py27-ptyprocess
 To report a bug, follow the instructions in the guide:
     http://guide.macports.org/#project.tickets
 }}}

 to which I did:

 {{{
 port -f activate py27-ptyprocess
 }}}

 which then gave me:

 {{{
 --->  Computing dependencies for py27-ptyprocess
 --->  Activating py27-ptyprocess @0.5_0
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess-0.5-py2.7.egg-info already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess-0.5-py2.7.egg-info.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/__init__.py already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/__init__.py.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/__init__.pyc already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/__init__.pyc.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/_fork_pty.py already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/_fork_pty.py.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/_fork_pty.pyc already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/_fork_pty.pyc.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/ptyprocess.py already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/ptyprocess.py.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/ptyprocess.pyc already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/ptyprocess.pyc.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/util.py already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/util.py.mp_1445185992.
 Warning: File
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/util.pyc already exists.  Moving to:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/ptyprocess/util.pyc.mp_1445185992.
 --->  Cleaning py27-ptyprocess
 }}}

 after which I did:

 {{{
 port upgrade outdated
 }}}

 and things seem to have proceeded as expected from that point forward.

 HOWEVER:  it seems to me like there might be a bug in the activation
 process or an issue with destroot.  This is why I'm filing the ticket for
 someone to check.

 Thank you.

 -Erik

-- 
Ticket URL: <https://trac.macports.org/ticket/49350>
MacPorts <https://www.macports.org/>
Ports system for OS X