Pymol plugin cannot be installed

Issue #18 resolved
Ben Hanson created an issue

We've had this problem before, but I don't know the fix. When the following command is run from cmake:

     cmake -E tar cvf ${FFEA_TAR_DIR}/FFEAplugin.tar.gz ${FFEA_TAR_DIR}/FFEAplugin

The resulting .tar.gz file cannot be installed with Pymol. Untaring shows the following

py09bh@Carrie:/localhome/Software/ffea/current/share/ffea/plugins/pymol-> tar -xvf FFEAplugin.tar.gz tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' tar: Removing leading../' from member names ../FFEAplugin/ tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_kinetic_states.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/system_names_pokemon.txt tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_pin.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_trajectory.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_kinetic_rates.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_material.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_universe.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/Blob.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_measurement.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_springs.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_frame.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_binding_sites.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_surface.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_topology.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_node.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_stokes.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/FFEA_script.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_kinetic_map.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/system_names_greekletters.txt tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_pdb.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword SCHILY.nlink' ../FFEAplugin/__init__.py tar: Ignoring unknown extended header keywordSCHILY.dev' tar: Ignoring unknown extended header keyword SCHILY.ino' tar: Ignoring unknown extended header keywordSCHILY.nlink' ../FFEAplugin/FFEA_vdw.py tar: Ignoring unknown extended header keyword SCHILY.dev' tar: Ignoring unknown extended header keywordSCHILY.ino' tar: Ignoring unknown extended header keyword `SCHILY.nlink' ../FFEAplugin/system_names_dbzcharacters.txt

Internet says it's the wrong format of tar file (cmake has tar 'bundled' with it, it doesn't use a local one), but I've no idea how we can get around this using cmake to tar the thing. Any ideas would be appreciated. I think Albert fixed it last time so I'm assigning this to him

Comments (2)

  1. Albert Solernou Crusat

    I just sorted that out, the plugin can be installed again. The reason of the bug was that CMake has to compress the folder one folder above of FFEAplugin. If one un-tars the resulting tar ball manually using CentOS 6 it will still print "tar: Ignoring unknown extended header keyword `SCHILY.dev'". It does not happen when compressing using LinuxMint17, and it is not harmful anyway.

    Thus I am closing that issue :)

  2. Log in to comment