Am Thu, 9 Sep 2021 22:12:09 +0200
Philipp Ost schrieb:
> On 9/9/21 9:15 PM, FreeBSD User wrote:
> [...]
> > What has changed in the recent 14-CURRENT OpenSSH update that dramatically
> > that working
> > schematics do not work any more?
>
> OpenSSH has been updated to v8.7p1:
>
>
On Thu, 9 Sept 2021 at 15:18, FreeBSD User wrote:
>
> /etc/ssh/sshd_config line 89: Unsupported option UsePAM
Sorry, it turns out I had the wrong version of config.h in my commit.
I'm running a build now and will commit it once a test with that
change passes. I will look into all of the
On Wed, Sep 08, 2021 at 02:10:47AM +0100, Jamie Landeg-Jones wrote:
> Steve Kargl wrote:
>
> > Yes, that's likely. So, it could be a change in behavior
> > for ImageMagick. Your suggested ps command doesn't provide
>
> I don't know when the change was made, but the pkg for ImageMagik
On 9/9/21 9:15 PM, FreeBSD User wrote:
[...]
What has changed in the recent 14-CURRENT OpenSSH update that dramatically that
working
schematics do not work any more?
OpenSSH has been updated to v8.7p1:
https://cgit.freebsd.org/src/commit/?id=19261079b74319502c6ffa1249920079f0f69a72
One of
Hello,
after upgrading 14-CURRENT to recent sources September, the 8th 2021, we
realizes today a
strange non-standard behaviour when connecting attempts from several clients to
14-CURRENT
based machines were made involving sshd.
First discovered on 13-STABLE clients (NanoBSD, router/fw
Hi, Not sure where I should go to suggest a bug fix about a weird apache24
reload issue.
On FreeBSD 12.2 servers that run apache24, we recently noticed apache24 kept
crashing when we tried to do a "service apache24 reload". It would core dump
and the only thing you could do is to restart it,
Am Wed, 11 Aug 2021 15:03:54 -0400
Ed Maste schrieb:
> On Wed, 11 Aug 2021 at 05:41, FreeBSD User wrote:
> >
> > Hallo,
> >
> > latest upgrade of CURRENT sources renders buildworld into failure, box is
> > running
> > FreeBSD 14.0-CURRENT #1 main-n248614-67f508db84b: Wed Aug 11 07:29:11 CEST
On Thu, Sep 9, 2021, 10:03 AM Gary Jennejohn wrote:
> On Thu, 9 Sep 2021 09:07:08 -0600
> Warner Losh wrote:
>
> > On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn
> wrote:
> >
> > > I got a very strange error while trying to make installworld on HEAD:
> > >
> > > stand/i386/loader_4th (install)
>
On Thu, 9 Sep 2021 09:07:08 -0600
Warner Losh wrote:
> On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn wrote:
>
> > I got a very strange error while trying to make installworld on HEAD:
> >
> > stand/i386/loader_4th (install)
> > /tmp/install.rIhHqnPC/sh: cc not found
> > *** Error code 127
> >
>
On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn wrote:
> I got a very strange error while trying to make installworld on HEAD:
>
> stand/i386/loader_4th (install)
> /tmp/install.rIhHqnPC/sh: cc not found
> *** Error code 127
>
> This from a tree which I updated at 08:37 UTC. According to uname -a
>
On Thu, Sep 09, 2021 at 04:00:39PM +0200, Stefan Esser wrote:
> I have just opened PR 258387 for this issue, which occurred during testing
> of a port with invalid MASTER_SITE.
>
> The error output of "fetch -v" should be server messages, but it appears that
> the buffer gets overwritten with
I have just opened PR 258387 for this issue, which occurred during testing
of a port with invalid MASTER_SITE.
The error output of "fetch -v" should be server messages, but it appears that
the buffer gets overwritten with data of unknown origin (mostly NUL bytes),
e.g.:
$ fetch -v
I got a very strange error while trying to make installworld on HEAD:
stand/i386/loader_4th (install)
/tmp/install.rIhHqnPC/sh: cc not found
*** Error code 127
This from a tree which I updated at 08:37 UTC. According to uname -a
the tree is at commit main-n249276-fc29a8b9d95.
I booted the new
On 09/09/2021 00:04, Tomoaki AOKI wrote:
devel/ninja/Makefile has USES= python in it, so it maybe require python
to run or at least build.
You could probably remove that line without anyone noticing. Ninja uses
Python for precisely one thing (or, at least, did last time I looked):
There is
14 matches
Mail list logo
