Skip to content

nilrt-snac: upgrade to v3.1.1#980

Open
amstewart wants to merge 1 commit intoni:nilrt/master/nextfrom
amstewart:dev/next/nilrt-snac
Open

nilrt-snac: upgrade to v3.1.1#980
amstewart wants to merge 1 commit intoni:nilrt/master/nextfrom
amstewart:dev/next/nilrt-snac

Conversation

@amstewart
Copy link
Copy Markdown
Contributor

Summary of Changes

Release corresponding to the LV 2026Q2 / NILRT 11.5 release.

Justification

Regular currency upgrade.

Testing

  • This is what the recipe has already been building. This PR just updates the package version.

Procedure

## [3.1.1] - 2025-03-27

Release corresponding to the LV 2026Q2 / NILRT 11.5 release.

Includes github changes through PR ni#87.

# Added

* Added more helpful failure messages when common OS issues occur during file operations. (ni#86)

### Changed

* The nilrt-snac tool will now attempt to create an execution log, to help mitigate timestamp collisions in the file name. (ni#86)
* Syslog will now switch to the uid/gid of ``root:adm`` when performing log operations. This also fixes a warning about insecure log directory permissions issued during boot. (ni#87)

### Fixed

* Fixed a duplicate quote issue in some SNAC configuration settings which caused ``nirtcfg`` errors when parsing the ``ni-rt.ini`` file. (ni#85)

Signed-off-by: Alex Stewart <alex.stewart@emerson.com>
@chaitu236
Copy link
Copy Markdown
Contributor

Is this meant to be targeted to nilrt/master/scarthgap (and cherry-picked to -next, but not cherry-picked to nilrt/26.3/scarthgap)?

@amstewart
Copy link
Copy Markdown
Contributor Author

It's targetted to -next and expected to be cherry-picked to scarthgap, but not 26.3.

@chaitu236
Copy link
Copy Markdown
Contributor

It's targetted to -next and expected to be cherry-picked to scarthgap, but not 26.3.

Can we do the opposite i.e., target to scarthgap and cherry-pick to -next. This is what we usually do and also, we'd like to avoid submitting anything to -next this late in release to avoid build time increases due to having to build -next components and also to avoid potential build failures in -next.

@chaitu236
Copy link
Copy Markdown
Contributor

chaitu236 commented Mar 26, 2026

Offline discussion: We'll merge this PR after release is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants