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.

Sign up for GitHub

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

Jump to bottom

Automated survey of latest available externals versions #410

Open
jcfreeman2 opened this issue Nov 12, 2024 · 0 comments
Open

Automated survey of latest available externals versions #410

jcfreeman2 opened this issue Nov 12, 2024 · 0 comments

Comments

@jcfreeman2
Copy link
Collaborator

At this week's Coordination Team meeting, Roland brought up - and Alessandro enthusiastically seconded - the idea of performing a survey of the current versions of the externals which we use as we wrap up v5.2 and move on to v5.3 development. He added that this is something which could be partially automated via a script which determines what the current version of each external in use is, and what the latest version available in Spack is. We can then use the results as a guide to look into situations where we're using old externals, want to see what the latest-greatest version of an external package is, etc.
jcfreeman2 pushed a commit that referenced this issue Nov 15, 2024
JCF: Issue #410: extend list_packages.py to be able to list primary e…
a909496 
…xternals for a given release
jcfreeman2 pushed a commit that referenced this issue Nov 15, 2024
JCF: Issue #410: add a rough draft of a script designed to core dump …
94f15c7 
…a bunch of survey info about the externals used
jcfreeman2 pushed a commit that referenced this issue Nov 18, 2024
JCF: Issue #410: add logic whereby for each Spack external package, t…
d4960e6 
…he currently used version, the official "Preferred Version", and the latest version obtainable by spack checksum is listed, with date info where possible
jcfreeman2 added a commit that referenced this issue Nov 26, 2024
@jcfreeman2
JCF: Issue #410: create a self-contained script which installs the po…
e53e2eb 
…etry Python package and uses it to automagically find the latest compatible Python packages for DUNE DAQ
jcfreeman2 pushed a commit that referenced this issue Nov 26, 2024
JCF: Issue #410: remove superfluous call to poetry shell since we alr…
39ba296 
…eady have freshenv set up in python_package.sh
jcfreeman2 pushed a commit that referenced this issue Nov 27, 2024
JCF: Issue #410: add packages which were missing from the original py…
6694684 
…project.toml and which I know were needed
jcfreeman2 pushed a commit that referenced this issue Nov 28, 2024
JCF: Issue #410: change the Python package releases to what poetry is…
dd2ec56 
… giving me + tweak the externals to reflect the stripped down/updated scenario in my ongoing externals v2.2 work
jcfreeman2 pushed a commit that referenced this issue Nov 28, 2024
JCF: Issue #410: change the Python package releases to what poetry is…
14c01e5 
… giving me + tweak the externals to reflect the stripped down/updated scenario in my ongoing externals v2.2 work
jcfreeman2 pushed a commit that referenced this issue Dec 2, 2024
JCF: Issue #410: on second thought, this last commit, involving the
2c34697 
actual changing of the package versions used in the nightly, is more
appropriate for johnfreeman/update_externals.

Having said that, I'll want to retain the bugfix to pyproject.toml, so
I'll introduce that in the next commit.

Revert "JCF: Issue #410: change the Python package releases to what
poetry is giving me + tweak the externals to reflect the stripped
down/updated scenario in my ongoing externals v2.2 work"

This reverts commit dd2ec56.
jcfreeman2 pushed a commit that referenced this issue Dec 2, 2024
JCF: Issue #410: as foreshadowed in the previous commit, reintroduce …
1476c81 
…the bugfix to pyproject.toml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcfreeman2