ere.
>
> Anyway, I will keep updating this branch until it's ready for a pull-up
> request, very likely with force-pushes in order to polish the commits
> before submission.
>
> Let me know how it goes!
>
> Cheers,
> -- Pierre
>
> On 6/29/23 23:56, Dustin
Am Thu, 29 Jun 2023 16:41:51 +0200
Guido Falsi schrieb:
> On 29/06/23 16:35, FreeBSD User wrote:
> > Hello,
> >
> > running a recent CURRENT, 14.0-CURRENT #10 main-n263871-fd774e065c5d: Thu
> > Jun 29 05:26:55
> > CEST 2023 amd64, xfreerdp (net/freerdp) d
Hello,
running a recent CURRENT, 14.0-CURRENT #10 main-n263871-fd774e065c5d: Thu Jun
29 05:26:55 CEST
2023 amd64, xfreerdp (net/freerdp) doesn't working anymore on Windows 10 guest
in bhyve. It
seems OpenSSL 3 is the culprit (see the error message from xfreerdp below). I
opened already a
PR (se
On Mon, 28 Feb 2022 17:11:27 +0100
Michael Gmelin wrote:
[...]
schnipp
[...]
> >
> > poudriere jail -l:
> >
> > # poudriere jail -l
> > JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
> > 123-amd64 12.3-RELEASE amd64
> > url=https://download.freebsd.org/releases/a ... 3-RELEASE/ 2022-02-24
> > 14:1
Hello folks,
we run at least two poudriere build systems on recent CURRENT boxes and one of
these
poudriere build systems is working within a jail - setup via FreeBSD's
/etc/jail.conf and
by misusing the port ezjail for copying/deploying our self-compiled jail
binary. The
poudriere jail uses ZF
