texml: error renaming texml to texml file already exists

[novak.sje@…]

Hi all,

I'm trying to install texml and have encountered the following error:

From: /opt/local/var/macport/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texml/texml/main.log

:debug:destroot Executing proc-post-org.macports.destroot-destroot-0
:error:destroot org.macports.destroot for port texml returned: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texml/texml/work/destroot/opt/local/bin/texml" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texml/texml/work/destroot/opt/local/bin/texml": file already exists
:debug:destroot Error code: NONE
:debug:destroot Backtrace: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texml/texml/work/destroot/opt/local/bin/texml" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texml/texml/work/destroot/opt/local/bin/texml": file already exists
    while executing
"proc-post-org.macports.destroot-destroot-0 org.macports.destroot"
    ("eval" body line 1)
    invoked from within
"eval $post $targetname"
:info:destroot Warning: targets not executed for texml: org.macports.activate org.macports.destroot org.macports.install

Mac ports appears to be trying to move a file to itself, which unsurprisingly doesn't work. I get the same error whether I install from binary or source. I have uninstalled and cleaned this port and updated etc my ports installation prior to reinstalling this port.

I've attached the main.log file for reference. cheers, Novak.

[novak.sje@…]

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texml/texml/main.log

[ryandesign (Ryan Carsten Schmidt)]

The port should be updated to python 2.7, since that's what we're doing with other ports, and that might fix this problem, since python 2.5 and earlier are handled somewhat differently in the python portgroup than later versions.