Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain our actual/current software versions over time when Preservation Events are generated #2246

Open
eporter23 opened this issue Feb 9, 2024 · 0 comments
Labels

Comments

@eporter23
Copy link
Contributor

eporter23 commented Feb 9, 2024

Goal: detect and record the currently installed version of software entries stored in Preservation Events so that we aren't recorded an older version of the software that performed the action.

For example, if our version of FITS is upgraded, we should record the version in use at Emory when creating a Characterization event.

This also occurred in 2023 when we had to upgrade to a new minor Fedora patch to address a vulnerability, causing our preservation events to temporarily reflect 4.7.5 instead of 4.7.6.

If we can't dynamically keep the version numbers updated, we should alternatively plan for a maintenance cycle.

@eporter23 eporter23 changed the title Maintain our actual/currrent software versions over time when Preservation Events are generated Maintain our actual/current software versions over time when Preservation Events are generated Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant