jool: update to 4.1.15 #28542
Draft
jool: update to 4.1.15 #28542
+4
−41
Conversation
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
Contributor
|
Yet again, thank you for your work. FYI, I have some plans to add some UCI, namespace, and firewall integration. |
Changelog: https://github.com/NICMx/Jool/releases/tag/v4.1.15 - Add support for kernels 6.15-6.18 - Add support for RHEL 9.6, 9.7 Drops 200-fix-compilation-in-v6.18.patch as upstream accepted Signed-off-by: Goetz Goerisch <ggoerisch@gmail.com>
GoetzGoerisch
force-pushed
the
jool-4.1.15
branch
from
bc76585 to
fcf896c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
📦 Package Details
Maintainer: @GoetzGoerisch @tiagogaspar8
(You can find this by checking the history of the package
Makefile.)Description:
Changelog: https://github.com/NICMx/Jool/releases/tag/v4.1.15
Drops 200-fix-compilation-in-v6.18.patch as upstream accepted
🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
git am(e.g., subject line, commit description, etc.)
We must try to upstream patches to reduce maintenance burden.