fail2ban: update to 1.0.2

[MeganerdNL]

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for my native architecture, (x86_64-glibc)
• I built this PR locally for these architectures (if supported. mark crossbuilds):
  • armv6l-glibc

Why this was necessary

There are many changes in fail2ban recently, especially for Python 3.11 - which is standard Python 3 in Void Linux now. Solves some compile errors in often used jail configs.

[necrophcodr]

@MeganerdNL You may want to read https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#committing-your-changes on how to format commits.

[necrophcodr]

Be aware that this may drop any errors or logging output happening from the server.

[triallax]

What's the point of this change?

[MeganerdNL]

What's the point of this change?

It prevents the spamming the local login with messages every time you change something (Server OK and so on). I can remove it so users can add it themselves if it has other unwanted effects I'm not aware of.

[MeganerdNL]

@MeganerdNL You may want to read https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#committing-your-changes on how to format commits.

Thanks. Sorry, I did read it, but thought using git only was ok too.
If it's a requirement I will use it from now on.

[Bnyro]

Following the proper commit message style is a requirement for the PR to become merged.
You can run git commit --amend -m "fail2ban: update to 1.0.2. and git push -f to fix the commit message.

[MeganerdNL]

• I removed ">/dev/null 2>&1" in the run command as it could indeed prevent important messages per @necrophcodr / @mhmdanas
• I corrected the commit message style as required per @Bnyro.

[Bnyro]

Please run git rebase -i master instead of merging the changes.

[MeganerdNL]

Please run git rebase -i master instead of merging the changes.

Yes I will in the future. Relatively new to git and github. Quick learner. Let me know if I have to change anything now - it seems not,. Cheers.

[Bnyro]

Yes, you should fix that now because your PR now contains 2 useless commits where you merged with the latest master changes. Otherwise your PR can't be merged because it destroys the commit history.

[MeganerdNL]

Yes, you should fix that now because your PR now contains 2 useless commits where you merged with the latest master changes. Otherwise your PR can't be merged because it destroys the commit history.

I did what you said. But it complained. Then I forced pushed it. Is it oke now? Only 1 commit... so it seems. Really sorry for the trouble. Thanks for the help.

[Bnyro]

Yes, the changes in the PR looks good to me now!
Didn't test the package though.

[MeganerdNL]

Ok. last force-push unnecessary. Nothing happened. Learned something.