Hi,
Was just noticing that the 2020Q1 port for OpenSSL was still showing up
with 11 different CVE's, yet I noticed that the commit [1] in r511808 says
it fixed 9e0c6f7a-d46d-11e9-a1c7-b499baebfeaf, yet it still shows up in pkg
audit for CVE-2019-1549 and CVE-2019-1547.
Any idea what the story is
Hi,
Just a bit of a heads up that poudriere will require you to be on the new
version of FreeBSD before you can build for it on the current system. For
example, if you are running 12.1, and you upgrade poudriere's jail to 13.0,
it will complain that you have to be running that version on the host
ng buildworld and building ports by hand
has made me start to look at more practical approaches, such as pkg's and
freebsd-update. Unless you have trust issues with upstream binaries, or
require unusual build options, I think it may not be worth using poudriere,
and pe
, tex and
llvm, wtf is with those build times?! heh
Anyway, thanks for clarifying!
Cheers,
Dan McGrath
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Hi,
Just a heads up that I also had bug report #243609 [1] open on this that I
guess can/should be closed now.
Dan
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243609
On Mon, Mar 16, 2020 at 3:57 AM Guido Falsi via freebsd-ports <
freebsd-ports@freebsd.org> wrote:
> On 15/03/20 18:09,
On Sat, Apr 4, 2020 at 7:43 PM Robert Huff wrote:
> I understand there are folks for whom poudriere or synth are The
> Right Tool(tm). But I am one of a number of folks for whom it is like
> carpet-bombing the neighborhood to get rid of one miscreant squirrel.
>
I swear, you find that s
Hi,
On Wed, Apr 29, 2020 at 11:20 AM Bob Eager wrote:
> The port doesn't get updated every time there is a new drive database;
> that would be unworkable.
>
Just a thought, but perhaps something similar to what ntp does with:
service ntpd fetch
But of course using smartd, so that it can fet
