Python update #31
Merged
Python update #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
December 19, 2023 06:40
…with older python packages
- removed some older intel based python recipes to deprecated - updated the requirements files of some python recipes - updated recipes to be able to handle newer os base images
|
I'd vigorously mark anything we don't actively maintain and patch as
deprecated or unmaintained - that way anyone else using them should realise
the risks they're taking
…On Wed, 24 Jan 2024 at 17:43, Cristian Di Pietrantonio < ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
On python/hpc-python-hdf5mpi/Dockerfile
<#31 (comment)>
:
I wonder whether we should mark Intel containers as deprecated (we do not
want to maintain containers users can't use on our systems). I am wondering
the same for CUDA, even though we might get NVIDIA nodes in the near future.
—
Reply to this email directly, view it on GitHub
<#31 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTBU5NA4ORMUO3LXTVLFLYQCUS5AVCNFSM6AAAAABBK33K56VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQNBQGUZDAOJVG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
@dipietrantonio sorry for reply to this comment so late but I don't understand your comment. The recipes are marked as deprecated. The containers I just removed as they have critical security holes. What else would you like to happen? |
|
@pelahi what I meant is that we should remove them not only because of security, but also because we do not have an intel (user facing) machine anymore. Maybe let's create a tag for future reference. In other words, I worried that we would fix security holes and maintain the containers that won't be used on Setonix. |
|
Hi @dipietrantonio I did move the intel recipes to deprecated. I deleted the containers but let the repositories as empty. Did you want me to remove the repos entirely? |
dipietrantonio
approved these changes
Mar 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These updates were driven by the fact that the recipes for hpc-python were quite old and had a number of security holes.
The updates are to remove some critical sercurity holes and the related docker images on quay.io have been removed.