[MacPorts] #14028: ncbi_tools, 20061015, Checksum failure, then missing getfeat.

[MacPorts]

#14028: ncbi_tools, 20061015, Checksum failure, then missing getfeat.
----------------------------------+-----------------------------------------
 Reporter:  matts at possiamo.com    |       Owner:  macports-tickets at lists.macosforge.org
     Type:  defect                |      Status:  new                                  
 Priority:  Normal                |   Milestone:  Port Bugs                            
Component:  ports                 |     Version:  1.6.0                                
 Keywords:  ncbi_tools, checksum  |  
----------------------------------+-----------------------------------------
 When trying to install ncbi_tools, I get a '''checksum''' error:
 {{{
 % sudo port install ncbi_tools
 --->  Fetching ncbi_tools
 --->  Attempting to fetch ncbi.tar.gz from
 ftp://ftp.ncbi.nlm.nih.gov/toolbox/ncbi_tools/
 --->  Verifying checksum(s) for ncbi_tools
 Error: Checksum (md5) mismatch for ncbi.tar.gz
 Error: Target org.macports.checksum returned: Unable to verify file
 checksums
 Error: Status 1 encountered during processing.
 }}}
 We managed to get the file, md5 it, update the local portfile, and
 start the install, only to find that '''getfeat''' is missing?
 {{{
 % sudo port install ncbi_tools
 Portfile changed since last build; discarding previous state.
 --->  Fetching ncbi_tools
 --->  Verifying checksum(s) for ncbi_tools
 --->  Extracting ncbi_tools
 --->  Configuring ncbi_tools
 --->  Building ncbi_tools
 --->  Staging ncbi_tools into destroot
 Error: Target org.macports.destroot returned: xinstall: Cannot stat:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_ncbi_tools/work/ncbi/bin/getfeat,
 No such file or directory
 Error: Status 1 encountered during processing.
 }}}

 A suggestion:
 A google search shows that the checksum error has occurred before.  In
 other MacPort-like systems, many libraries have started including version
 numbers in their file names to combat similar situations.  This practice
 also ensures that prior versions of the libraries remain available.  I
 have noticed that python, xfce, and a few others are starting to do this
 in MacPorts.

 I was unable to find similar guidelines in the MacPorts wiki. Perhaps
 there are other measures available in MacPorts?

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14028>
MacPorts </projects/macports>
Ports system for Mac OS