Hello.
I see Clamav 0.105.0, 0.104.3 and 0.103.6 were released on May 5th, the
latter two closing "several CVE fixes".
However, the port was not updated and not even portaudit entries were added.
Was this overlooked?
Are the FreeBSD ports somehow not affected?
Thanks in advance.
bye
Hi!
> I see Clamav 0.105.0, 0.104.3 and 0.103.6 were released on May 5th, the
> latter two closing "several CVE fixes".
>
> However, the port was not updated and not even portaudit entries were added.
>
> Was this overlooked?
There's a PR waiting:
https://bugs.freebsd.org/bugzilla/show_bug.cgi
On 5/19/22 09:38, Kurt Jaeger wrote:
There's a PR waiting:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263944
Sorry, I missed that.
Hi all,
i created 2 new issues on April 30th. One was a maintainer update
for an existing port which was committed instantly.
The new port I submitted has not been touched by anyone since then.
Did I do anything wrong in the issue?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263675
Thank
Hi ports@
Tip to avoid 12.3-STABLE taking ages for enormous
cd /usr/ports/www/chromium ; make
after failing to find a package
pkg install chromium
pkg search chromium
vi -c/url: /etc/pkg/FreeBSD.conf
:s/latest/quarterly/
Caution: A subsequent `pkg upgrade` will caus
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, you
On 19.05.22 09:30, Andrea Venturoli wrote:
Hello.
I see Clamav 0.105.0, 0.104.3 and 0.103.6 were released on May 5th, the
latter two closing "several CVE fixes".
However, the port was not updated and not even portaudit entries were
added.
Was this overlooked?
Are the FreeBSD ports somehow
