Hi!
> > > > man.cgi has provisions for most of this already, it's only missing
> > > > some job to regulary extract the latest
> > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/13.0-CURRENT/ports.txz
> > > > for the current tree of the manuals.
> > > How does it actually create the
On 2020-08-31 16:30, Kurt Jaeger wrote:
Hi!
I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
everyone updates, as it fixes "serious" security issues.
I don't see it coming in the port tree and neither in the pkg audit
vulnerability database.
On Mon, Aug 31, 2020 at 01:51:35AM +0200, Jan Beich wrote:
>
> The actual error appears to have been elided. Paste full output when
> restarting build (as text/plain) or upload poudriere log.
>
> www/firefox used to build fine on aarch64, see
>
> On 31. Aug 2020, at 16:31, Kurt Jaeger wrote:
>
> Hi!
>
>> I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
>> everyone updates, as it fixes "serious" security issues.
>>
>> I don't see it coming in the port tree and neither in the pkg audit
>> vulnerability database.
>
Hi!
> I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
> everyone updates, as it fixes "serious" security issues.
>
> I don't see it coming in the port tree and neither in the pkg audit
> vulnerability database.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248856
has a
Hello.
I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
everyone updates, as it fixes "serious" security issues.
I don't see it coming in the port tree and neither in the pkg audit
vulnerability database.
If you already knew, please disregard and forgive.
bye
On 30.08.2020 11:28, Niclas Zeising wrote:
>> Exactly. Another case in point: x11/xtset. Maintenance stopped in
>> 1993, 11 days after the FreeBSD project came into existence. It works
>> fine, and I find it very useful. If at some time in the future it
>> should no longer work with the
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,
We have been seing this behaviour of poudriere with other Ports as well
(tomcat, jni). If it runs out of memory, e.g. swap limits of the jail
we're running poudriere in are too small, then it just fails silently.
We have been able to prevent this by increasing the limits, to twice the
memory
