Update to Python semver to properly identify kernel versions#8
Open
mmattel wants to merge 6 commits into
Open
Conversation
Closed
Author
|
@Hyphaed ping |
mmattel
force-pushed
the
update_to_semver
branch
from
9d86158 to
a7ab609
Compare
This was referenced Feb 8, 2026
Author
|
Note that I have updated this PR with changes from PR #13 which allows using new kernels. This now makes it much easier to use one branch for local use instead of first merging one into another. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When using Debian Trixie with backports, you get an additional kernel identifyer which breaks version identification.
With the change using Python semver, this is solved automatically 😃
After the changes made, I was able to successfully run the script on my Debian Trixie system using the
6.16.3+deb13-amd64kernel and after rebooting, I had a blazing fastVMware® Workstation 17 Pro 17.6.3 build-24583834up and running !Thanks for the efforts !
One thing to comment: is it possible to disable the automatic conda environment after the script run? Kind of annyoing to disable it on each terminal session manually. (yes, I just could comment out the part in
.bashrc)...NOTE that this PR has been updated for the use with newer kernels, see comment below.