[MacPorts] #58786: libgpod 0.8.3_1+python27: failed to build: "error renaming "/opt/local/.../libgpod/work/destroot/opt/local/lib/python2.7": no such file or directory"

[MacPorts]

#58786: libgpod 0.8.3_1+python27: failed to build: "error renaming
"/opt/local/.../libgpod/work/destroot/opt/local/lib/python2.7": no such
file or directory"
--------------------------+---------------------
 Reporter:  juliangilbey  |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.5.4
 Keywords:                |       Port:  libgpod
--------------------------+---------------------
 I tried building this port, but I'm getting the error message:

 {{{error renaming
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_libgpod/libgpod/work/destroot/opt/local/lib/python2.7":
 no such file or directory}}}

 This has appeared in previous bug reports, but I do have swig-python
 installed, so that's not the cause.  Hmmm.

 The named directory has the following contents:

 {{{libgpod.4.dylib      libgpod.a       libgpod.dylib   libgpod.la
 pkgconfig}}}

 There ''is'' a python2.7 in destroot, but it's in
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_libgpod/libgpod/work/destroot/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib

 Note that /opt/local/bin/python2.7 symlinks to
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7,
 so this seems eminently reasonable.

 I'm not sure how to solve this strange problem.

-- 
Ticket URL: <https://trac.macports.org/ticket/58786>
MacPorts <https://www.macports.org/>
Ports system for macOS