This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Stephen, The GitHub repository is for development: releases are *not* made there. I'm working on the "version.texi" thing. > I have a script i've used for many years to automatically grab, build, and > deploy LDM. > > the meat is: > > ldm_base_url="ftp://ftp.unidata.ucar.edu/pub/ldm/" > ... > if [ -n "${ldm_ver}" ] && curl -s "${ldm_base_url}/versions" | sed -e > 's/\.tar.*$//' | grep -q "^${ldm_ver}$"; then > : # user specified a version of LDM that exists on servers > else > echo "You must specify a version of LDM that exists. Valid LDM versions are:" > curl -s "${ldm_base_url}/versions" | sed -e 's/\.tar.*$//' -e 's/^/ /' || > { rc=$? ; echo "Curl to get LDM versions failed, aborting..."; exit ${rc} ;} > exit 1 > fi > > i.e it tries to grab 'ftp://ftp.unidata.ucar.edu/pub/ldm/versions' to figure > out if a specified version is valid, or to find the latest release. > > That file is no longer present. > > Is this an oversight or a permanent change? Regards, Steve Emmerson Ticket Details =================== Ticket ID: KJF-988774 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.