On Friday, December 23, 2022 5:15:35 AM EST Sebastian Andrzej Siewior wrote:
> On 2022-12-22 18:31:37 [-0500], Scott Kitterman wrote:
> > I think we should focus on getting clamav up to 1.0.0 before the freeze
> > and
> > deal with the unrar bits later (should be easy enough to get a freeze
> > exc
On Friday, December 23, 2022 5:15:35 AM EST Sebastian Andrzej Siewior wrote:
> On 2022-12-22 18:31:37 [-0500], Scott Kitterman wrote:
> > I think we should focus on getting clamav up to 1.0.0 before the freeze
> > and
> > deal with the unrar bits later (should be easy enough to get a freeze
> > exc
On December 23, 2022 11:47:53 AM UTC, Andrew C Aitchison
wrote:
>On Fri, 23 Dec 2022, Sebastian Andrzej Siewior wrote:
>
>> Then we need to decide what we do about the
>> rust bits. I'm currently unsure if we can use the in-source bits or must
>> use packages.
>
>From https://blog.clamav.net/2
On Fri, 23 Dec 2022, Sebastian Andrzej Siewior wrote:
Then we need to decide what we do about the
rust bits. I'm currently unsure if we can use the in-source bits or must
use packages.
From https://blog.clamav.net/2022/10/
Starting with ClamAV 0.105.1, some of the ClamAV project is written
On 2022-12-22 18:31:37 [-0500], Scott Kitterman wrote:
> I think we should focus on getting clamav up to 1.0.0 before the freeze and
> deal with the unrar bits later (should be easy enough to get a freeze
> exception for if we need it).
>
> If you think tha'ts reasonable, I'll manually make the
5 matches
Mail list logo