Am 12.01.2021 um 15:36 schrieb Baptiste Daroussin :
> Note that I have fixed it in r561337 (with some cleanup)
Merci.
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure
Kaiserallee 13a
76133 Karlsruhe
Tel. +49 721 9109500
https://infrastructure.punkt.de
i...@punkt.de
AG Mannheim
On Tue, Jan 12, 2021 at 03:20:36PM +0100, Patrick M. Hausen wrote:
> Dear ports gurus,
>
> what am I doing wrong that makes me still receive this message every couple
> of days?
>
> > Von: pkg-fall...@freebsd.org
> > Betreff: [package - main-i386-default][sysutils/env4801] Failed for
> >
Hi!
> Am 12.01.2021 um 15:23 schrieb Kyle Evans :
> This failure in particular stems from line 5 of the Makefile inside the dist:
>
> NO_MAN= sorry
Thanks! I completely missed that I was pulling a Makefile from phk.
> The MK_MAN in the port makefile should probably go away entirely, and
> this
On Tue, Jan 12, 2021 at 8:20 AM Patrick M. Hausen wrote:
>
> Dear ports gurus,
>
> what am I doing wrong that makes me still receive this message every couple
> of days?
>
> > Von: pkg-fall...@freebsd.org
> > Betreff: [package - main-i386-default][sysutils/env4801] Failed for
> > env4801-0.3_1
Dear ports gurus,
what am I doing wrong that makes me still receive this message every couple of
days?
> Von: pkg-fall...@freebsd.org
> Betreff: [package - main-i386-default][sysutils/env4801] Failed for
> env4801-0.3_1 in build
> Datum: 12. Januar 2021 um 15:05:07 MEZ
> An: p...@hausen.com
>
On 12/01/2021 11:42, DutchDaemon - FreeBSD Forums Administrator wrote:
On 11/01/2021 22:39, Greg Rivers via freebsd-ports wrote:
since the update from 4.6.2 to 4.6.3 today. It starts, but as soon as
the MTA writes to the listening socket, it aborts, e.g.:
pid 54733 (milter-greylist), jid
On 11/01/2021 22:39, Greg Rivers via freebsd-ports wrote:
since the update from 4.6.2 to 4.6.3 today. It starts, but as soon as the MTA
writes to the listening socket, it aborts, e.g.:
pid 54733 (milter-greylist), jid 0, uid 26: exited on signal 6
resulting in:
sm-mta[54648]:
Hello.
I've got several services authenticating against a Samba AD DC via
"saslauthd -a ldap"
This works perfectly from the users' point of view.
However I often find failures in the logs:
saslauthd[89676]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
saslauthd[89676]: Retrying
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
