Re: mail/rspamd: committer needed for a tiny modification after maintainer timeout

Älven wrote: > > Michael Grimm writes: >> -# REQUIRE: LOGIN redis >> +# REQUIRE: LOGIN redis keydb valkey […] >> Could someone be so kind and commit 287828 (and close both 287828 and >> 282443)? > Would be glad to help with this simple task. :) > Already t

Re: sysutils/logwatch: Need to patch very first line of a script fails, dunno why

Miroslav Lachman <000.f...@quip.cz> wrote: > > On 18/07/2025 20:48, Michael Grimm wrote: >> But: If I do apply that very same patch by 'patch < >> files/patch-scripts_logwatch.pl' at the appropriate location, all 18 hunks >> are applied successfully.

Re: sysutils/logwatch: Need to patch very first line of a script fails, dunno why

Edward Sanford Sutton, III wrote: > On 7/18/25 11:48, Michael Grimm wrote: >> Hi, >> I am preparing for the upcoming logwatch-7.13 release, and ran into an issue >> I can't understand. >> I do want to patch the logwatch.pl script by providing a >> 'fi

Re: sysutils/logwatch: Need to patch very first line of a script fails, dunno why

Michael Grimm wrote: > But: If I do apply that very same patch by 'patch < > files/patch-scripts_logwatch.pl' at the appropriate location, all 18 hunks > are applied successfully. I forgot to mention, that when removing the very first hunk starting at line 1, all o

Committer needed for a simple sysutils/logwatch bugfix

I do need a committer to apply a simple bugfix for sysutils/logwatch (add missing files to pkg-plist and files/Makefile): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285078 Thanks in advance, Michael

Re: New maintainer: would that be a no-go?

Daniel Engberg wrote: > On 2025-02-28 22:32, Michael Grimm wrote: > Upstream is releasing new versions twice a year, January and July. I made > some contributions to logwatch which have been accepted immediately after the > last release in January in order to give some time for te

New maintainer: would that be a no-go?

Hi, I am the new maintainer of sysutils/logwatch and I never have been a maintainer of any port before. Thus a newbie ;-) Upstream is releasing new versions twice a year, January and July. I made some contributions to logwatch which have been accepted immediately after the last release in Janu

Re: mail/postfix: making postscreen blacklistd aware, interested?

Michael Grimm wrote: > But before bothering the maintainer with a PR of my private interest I want > to ask here: > > Anyone else interested? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=28 Nice PR number ;-) HTH, Michael

mail/postfix: making postscreen blacklistd aware, interested?

Hi, I am running DNSBLs out of postscreen: postscreen_dnsbl_sites = .zen.dq.spamhaus.net=127.0.0.[2..11] .combined.mail.abusix.zone Until recently those detected bots tried it a couple of times and gave up. Now, there are a significant number of bots trying every couple of minutes over

Re: FreeBSD Port: mariadb106-server-10.6.18

Chris Kiakas wrote: > I updated a MariaDB 10.6.17 server to 10.6.18 from ports and I am no longer > able to stop or restart. > > 'service mysql-server stop’ just sits there with > > Stopping mysql. > Waiting for PIDS: 71178 > > This is on a 13.3-RELEASE system. I also tried updating another j

Alternative to SpamAssassin's sa-update tool?

Hi, I am running rspamd and do not intend to use SpamAssassin's ruleset, but I do use rulesets provided and maintained by others [1]. I am using 'sa-update' for updating both frequently adapted rulsets. Working fine. But, in order to be able to use that tool, I do have to install 'mail/spamass

Re: SO_PASSCRED and SCM_CREDENTIALS | error: use of undeclared identifier

Gleb Popov wrote: > > On Wed, Mar 20, 2024 at 11:16 PM Michael Grimm wrote: >> Compilation fails: >> >> cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG >> -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC >&g

SO_PASSCRED and SCM_CREDENTIALS | error: use of undeclared identifier

Hi Disclaimer: I am trying to create a new port (knot-resolver-current) developed under Linux upstream. A so-called manager functionality is brand new in comparison to the previous knot-resolver. The corresponding git repository is leading edge development. My main motivation is: learning how

Re: dns/knot3 and dns/knot-resolver do not get along with

Mark Millard wrote: > On Feb 26, 2024, at 01:06, Michael Grimm wrote: >> Possible solutions: >> >> 1) dns/knot3-lib should store its libraries and includes into a different >> location as dns/knot3 does > > A variation of that is that dns/knot-resolv

Re: dns/knot3 and dns/knot-resolver do not get along with

Mark Millard wrote: > Michael Grimm wrote on > Date: Sun, 25 Feb 2024 19:46:22 UTC : >> I am trying to install dns/knot3 and dns/knot-resolver simultaneously. >> >> Compilation is achieved with the help of poudriere which complains about >> dns/knot-resolver: &

dns/knot3 and dns/knot-resolver do not get along with

Hi, I am trying to install dns/knot3 and dns/knot-resolver simultaneously. Compilation is achieved with the help of poudriere which complains about dns/knot-resolver: ===> Installing existing package /packages/All/knot-resolver-5.7.0_2.pkg [stable-default-job-02] Installing knot-resolver-5.7.

Re: dns/knot-resolver security update to 5.7.1

Moin Rahman wrote: >> On Feb 25, 2024, at 6:15 PM, Michael Grimm wrote: >> P.S. Please forgive my lack in experience with PRs ;-) >>Please let me know, what to correct if neccessary > > Well as a starter: > 1. You do not need PORTREVISION when you alr

dns/knot-resolver security update to 5.7.1 (was: dns/knot3 update to 3.3.4)

Moin Rahman wrote: >> On Feb 25, 2024, at 5:04 PM, Michael Grimm wrote: >> >> a new version of this port has been released two month ago. >> >> The maintainer normally updates knot3 shortly after the release of a new >> version. He didn't react on a

dns/knot3 update to 3.3.4

Hi, a new version of this port has been released two month ago. The maintainer normally updates knot3 shortly after the release of a new version. He didn't react on a mail of mine. No pun intended, there are numerous reasons for that. I do have a git-diff patch at hand, successfully compiling

Re: dns/libidn2-2.3.4_1

Michael Grimm wrote: > I do not understand why the recent fix > https://cgit.freebsd.org/ports/commit/?id=9eb1bbbe39f24802e8dbd45074b4c2f319d4d2c0 > might have broken that port. After recompilation of all ports and subsequent reinstallation of all of them, this issue doesn't

dns/libidn2-2.3.4_1

Hi dns/libidn2-2.3.4_1 is broken: ld-elf.so.1: /usr/local/lib/libidn2.so.0: version IDN2_0.0.0 required by /usr/local/bin/host not defined ... I do not understand why the recent fix https://cgit.freebsd.org/ports/commit/?id=9eb1bbbe39f24802e8dbd45074b4c2f319d4d2c0 might have broken t

Re: misc/freebsd-release-manifests need fixing

Moin Rahman wrote: >> On Dec 20, 2023, at 4:06 PM, Michael Grimm wrote: >> >> Hi, >> >> today's commit broke misc/freebsd-release-manifests need fixing. There are >> no longer 12.3 versions available. >> > [snip] > Thanks for the he

misc/freebsd-release-manifests need fixing

Hi, today's commit broke misc/freebsd-release-manifests need fixing. There are no longer 12.3 versions available. ===> Building package for freebsd-release-manifests-20231220 pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd

Re: Setting of DEFAULT_VERSIONS of php and poudriere's ports compilation woes in my setup

Guido Falsi wrote: > On 02/12/23 21:37, Michael Grimm wrote: >> Hi, >> I am following the git repository for ports and using poudriere to compile >> those. >> Today I stumbled over: >> 20231125: >> AFFECTS: users of lang/php81 >> AUTHOR: b...@f

Setting of DEFAULT_VERSIONS of php and poudriere's ports compilation woes in my setup

Hi, I am following the git repository for ports and using poudriere to compile those. Today I stumbled over: 20231125: AFFECTS: users of lang/php81 AUTHOR: b...@freebsd.org The default version of PHP has been switched from 8.1 to 8.2. […] I had h

Re: misc/freebsd-release-manifests is broken

Colin Percival wrote > On 11/20/23 14:05, Michael Grimm wrote: >> after the 14.0 release announcement, port misc/freebsd-release-manifests is >> broken, due to legacy 'RC4' references: > > Thanks, I forgot to update the plist when I updated the MANIFEST files. &g

misc/freebsd-release-manifests is broken

Hi, after the 14.0 release announcement, port misc/freebsd-release-manifests is broken, due to legacy 'RC4' references: ===> Building package for freebsd-release-manifests-20231120 pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/fr

Re: PYTHON_DEFAULT needs to be bumped to at least 3.10, or to the latest 3.12

Charlie Li wrote: > The next bump will be to 3.11, in keeping with the n-1 cadence. 3.12 is not > ready yet, not without the setuptools overhaul amongst other things. Just out of curiosity: does a time schedule exist, yet? Regards, Michael

Re: net/openntpd with constraint stops working after recent security/ca_root_nss upgrade

Herbert J. Skuhra wrote: > > > On Sat, Oct 07, 2023 at 04:59:31PM +0200, Michael Grimm wrote: >> Hi >> >> I am running net/openntpd with a constraint: >> >> … >> constraint from "9.9.9.9" >> >> After the recent upgrade of sec

Re: postfix' blacklistd patch

Juraj Lutter wrote: >> On 16 Jan 2023, at 16:49, Michael Grimm wrote: >> I wonder if the following condition for triggering blacklistd is appropriate: >> >> >> /* notify blacklistd of SASL authentication failure */ >> pfilter_no

postfix' blacklistd patch

Hi, I wonder if the following condition for triggering blacklistd is appropriate: if (status != XSASL_AUTH_DONE) { msg_warn("%s: SASL %s authentication failed: %s", state->namaddr, sasl_method, STR(state->sasl_reply)); /* RFC 4954 Section 6. */

Re: security/py-fail2ban quits working after some hours

I've seen that you upgraded this port already, but may I remind you at the following glitch: Michael Grimm wrote: > BTW: One glitch in fail2ban.conf file: > > # Option: allowipv6 > # Notes.: Allows IPv6 interface: > # Default: auto > #

Re: security/py-fail2ban quits working after some hours

Michael Grimm wrote: > Cy Schubert wrote >> I've been able to reproduce the problem here. Please try the attached patch >> obtained from our upstream. It fixes a dovecot regression that crept into >> the latest release. > > Yes, I am running dovecot jails

Re: security/py-fail2ban quits working after some hours

Cy Schubert wrote > In message , Roger > Marquis w > rites: >> Cy Schubert wrote: >>> Michael Grimm writes: >>>> this is a recent stable/13-n252672-2bd3dbe3dd6 running = >>>> py39-fail2ban-1.0.1_2 and python39-3.9.14 >>>> I hav

security/py-fail2ban quits working after some hours

[cc's to maintainer] Hi, this is a recent stable/13-n252672-2bd3dbe3dd6 running py39-fail2ban-1.0.1_2 and python39-3.9.14 I have been running fail2ban for years now, but immediately after upgrading py39-fail2ban fron 0.11.2 to 1.0.1 the fail2ban-server will end up as a runaway process consumi

Re: git: 34ab3bea8aa2 - main - graphics/gd: update to 2.3.3

Christian Ullrich wrote: > * Dirk Meyer wrote: >> The branch main has been updated by dinoex: >> >> URL: >> https://cgit.FreeBSD.org/ports/commit/?id=34ab3bea8aa25b1e994a7da9a4653d558585e5d2 >> >> commit 34ab3bea8aa25b1e994a7da9a4653d558585e5d2 >> Author: Dirk Meyer >> AuthorDate: 2022-02

mail/postfix and mail/postfix-current missing on www.freebsd.org ports section

Hi, I noticed today that mail/postfix and mail/postfix-current are missing on https://www.freebsd.org/cgi/ports.cgi?query=%5Epostfix+&stype=all&sektion=all (I did reset my browser's caching). Regards, Michael

Re: security/rkhunter without hashes after recent STABLE-13 update

Hi Stefan, Stefan Esser wrote > Am 07.07.21 um 22:24 schrieb Michael Grimm: >> Warner Losh wrote: >>> On Wed, Jul 7, 2021 at 12:47 PM Michael Grimm wrote: >>>> Warner Losh wrote: >>>>> Sorry for any hassle this work is causing. >>>

Re: security/rkhunter without hashes after recent STABLE-13 update

Warner Losh wrote: > > On Wed, Jul 7, 2021 at 12:47 PM Michael Grimm wrote: >> Warner Losh wrote: >>> Sorry for any hassle this work is causing. >> >> No big deal for rkhunter, a workaround exists ;-) > > I think the reason is that it automatically s

Re: security/rkhunter without hashes after recent STABLE-13 update

Warner Losh wrote: > On Wed, Jul 7, 2021 at 9:26 AM Michael Grimm wrote: >> Warner Losh wrote: >>> What's the hash that you have at n246157? I think it should be fd5b08977630. >> >> No, it's stable/13-n246157-fd5b0897763 >> >> I will

Re: security/rkhunter without hashes after recent STABLE-13 update

Warner Losh wrote: > > On Wed, Jul 7, 2021 at 6:19 AM Michael Grimm via freebsd-stable > wrote: >> Can someone point me into the right direction, how to find out if the >> output of /sbin/sha256sum changes between stable/13-n246147 and >> stable/13-n246157? > &g

security/rkhunter without hashes after recent STABLE-13 update

Hi, I noticed that after my last upgrade to stable/13-n246157 (from stable/13-n246147) that /usr/local/var/lib/rkhunter/db/rkhunter.dat started lacking hashes. Regarding rkhunter.conf the default setting is: HASH_CMD=SHA256 and: If just the command name is given, and it is on