[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #OYI-925913]: LDM 6.13.17 build failure

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.

  • Subject: [LDM #OYI-925913]: LDM 6.13.17 build failure
  • Date: Mon, 31 Oct 2022 11:50:50 -0600
Hi Ryan,

re:
> Such an update to bird01.allisonhouse.com would require physical presence.
> Unfortunately at this time it's not likely that I will be able to visit the
> dish in OKC this year and therefore won't be able to migrate to a newer OS.
> Barring me getting someone else to do it, there won't be any movement on
> this front until early next year.

OK, thanks for the update.

FYI: the additions made in the current release are NOT crucial for the
continued use of the software for NOAAPort ingest, so continuing to use a
previous version should have no detrimental/unexpected effects.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: OYI-925913
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.