Skip to content

Update development.seneca to compile MET after upgrading seneca to Debian Bookworm #2761

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Task

On Friday, 12/8/23, RAL-IT upgraded the RAL/JNT METplus development machine to Debian Bookworm. This issue is to update the contents of development.seneca as needed to enable MET to compile in new operating system. Note that changes should be made to both the develop, main_v11.1, and main_v11.0 branches since nightly build regression tests are run for all three versions on seneca.

Note, as part of this issue, please also recompile earlier MET releases in seneca:/d1/projects/MET/MET_releases. For releases already compiled in /nrit/ral, just provide a soft-link to them in that directory.

Time Estimate

1 day.

Sub-Issues

Consider breaking the task down into sub-issues.
None needed

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as the next official version or Backlog of Development Ideas
  • For the next official version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

Task Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issue
    Select: Milestone as the next official version
    Select: MET-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions