-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[WIP] fail2ban: update to 1.1.0. #48297
Open
AnInternetTroll
wants to merge
1
commit into
void-linux:master
Choose a base branch
from
AnInternetTroll:user/luca/fail2ban-man
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[WIP] fail2ban: update to 1.1.0. #48297
AnInternetTroll
wants to merge
1
commit into
void-linux:master
from
AnInternetTroll:user/luca/fail2ban-man
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
This badly needs a release upstream, but for now this passes tests for me (mostly taken from Fedora). cc @ahesford
|
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
from
January 20, 2024 21:44
d154622
to
9945768
Compare
Thanks for taking a look at this :D
I've applied your suggestion and it builds locally for me as expected!
|
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
from
January 26, 2024 19:08
9945768
to
e9d0b79
Compare
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
from
February 7, 2024 21:20
e9d0b79
to
f9c3686
Compare
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
3 times, most recently
from
March 21, 2024 21:13
5a3d468
to
ae6df7d
Compare
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
3 times, most recently
from
May 31, 2024 21:58
9ba3957
to
85ff366
Compare
Thanks @classabbyamp!. I've added the change but tests started to fail.
At a first look it seems like a package bump might fix it. I'll
investigate this further, but for the moment I'm marking this PR as a
WIP.
|
AnInternetTroll
changed the title
fail2ban: add man pages
[WIP] fail2ban: update to 1.1.0.
May 31, 2024
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
from
May 31, 2024 22:03
85ff366
to
12e0db0
Compare
I would appreciate some testing here, as I lack the knowledge to do it myself |
Please also backport fail2ban/fail2ban#3782 |
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
from
July 20, 2024 11:21
12e0db0
to
71af982
Compare
is this still WIP? please rebase |
AnInternetTroll
force-pushed
the
user/luca/fail2ban-man
branch
from
September 26, 2024 18:43
71af982
to
0ad5b0f
Compare
The only issue with this PR is that it is not tested (outside of the original man page change) |
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.
Testing the changes
Local build testing