On 7. Aug 2019, at 04:02, Kubilay Kocak wrote:
>
> On 7/08/2019 7:57 am, The Doctor via freebsd-ports wrote:
>> Wehen Will clamav be updated?
>> I understand there is a security issue?
>
> The best / most effective method to report/request security releases or
> updates is in Bugzilla, I've
On 14.01.19 10:09, Jochen Neumeister wrote:
>
> On 14.01.19 09:56, Gregory Byshenk wrote:
>> On Sun, Jan 13, 2019 at 08:39:12PM -0500, Charles Sprickman via
>> freebsd-stable wrote:
On Jan 13, 2019, at 3:19 PM, Randy Bush wrote:
> I have a mission critical app server running an old
On 20.10.18 22:22, Alexander Zagrebin wrote:
> В Thu, 18 Oct 2018 09:50:31 +0200
> Florian Smeets via freebsd-ports пишет:
>
>> does 5.2.20 break VNC remote console to VBoxHeadless VMs for anyone
>> else? I can still connect to the console with VNC but all I get is a
>&g
Hi,
does 5.2.20 break VNC remote console to VBoxHeadless VMs for anyone else? I can
still
connect to the console with VNC but all I get is a black screen. Going back to
5.2.18
restores VNC functionality.
I do have to mention that I have the patch from PR: 230460 applied to both
versions,
as
On 12.10.18 21:00, @lbutlr wrote:
> On 09 Oct 2018, at 11:53, Mark Martinec wrote:
>> A release 2.11.1 of amavisd-new now is available at:
>>
>> https://amavis.org/amavisd-new-2.11.1.tar.bz2
>>
>> Release notes are at:
>>
>> https://amavis.org/release-notes.txt
>
> Does this still have a
On 04.10.18 11:32, Miroslav Lachman wrote:
> Miroslav Lachman wrote on 2018/10/04 11:12:
>> I upgraded mailserver from 10.4 to 11.2 (it is amd64 with GENERIC
>> kernel).
>> All packages were reinstalled from repository built in our poudriere
>> for 11.2. Everything works except amavisd-new.
IIRC
On 22.05.18 23:58, Miroslav Lachman wrote:
> Am I the only one seeing occasional unreliable pkg upgrades?
No.
>
> I think changes in package name or ports origin should be better handled
> by pkg tools.
> For example, we have php-composer installed on many of our machines. The
> ports was
On 04/11/2016 15:40, Marko Cupać wrote:
> I guess I came to positive conclusion too early. Everything did
> compile, install and start without problems. But so far I had problems
> with amavisd-new which would die with the following message:
>
> Nov 4 15:20:52 mx1 amavis[38170]: (!)_DIE: Suicide
