[Pkg-clamav-devel] Bug#1006179: ClamAV 1.0.0 release candidate now available

[Andrew C Aitchison]

On Thu, 22 Dec 2022, Scott Kitterman wrote:

> On Monday, December 12, 2022 10:45:57 PM EST Scott Kitterman wrote:
>> On Saturday, December 10, 2022 11:14:14 AM EST Sebastian Andrzej Siewior
>>
>> wrote:
>>> On 2022-12-07 12:51:30 [-0500], Scott Kitterman wrote:
>>>> OK.  I'm back to having some time for Debian again, so let me know how I
>>>> can help.
>>>
>>> I pushed something to the experimental branch. It ain't much…
>>> This updates the build dependencies and you still need download the
>>> upstream .tar.gz yourself for 1.0.0. uscan is a bit of help. The split
>>> script isn't working anymore.
>>
>> Looks like it needs an some rewrite.  I guess we are in the land of CMake
>> now as the configure.ac files it expects to find don't exist now.
>>
>>> The llvm code is gone from the archive. This is the only good new. We
>>> probably need to patch clamav to take the tfm library instead the one
>>> they ship. The only change is probably that one you pointed out (with
>>> the larger bit size).
>>> I also found the 7z folder and I *think* that it can be
>>> substituted by lzma-dev.
>>> The result builds and the testsuite passes.
>>> Besides we need to split out unrar.
>>>
>>>> Scott K
>>>
>>> Sebastian
>>
>> That doesn't sound too bad.  I'll see if I can find some time to work on the
>> split, but probably not until Wednesday or Friday.
>
> I did, eventually, look at this some.  This is both easier and harder is some
> ways.
>
> First, the CMake build system supports not building libclamavunrar, so we
> don't need to monkey with the build system to get clamav built with it
> removed.  I think split script is a do-over.  Only the most trivial parts of
> it are still useful.
>
> My suggested path forward is to manually create a DFSG tarball (and clean up
> the win32 bits we don't need) by removing the relevant directories:
>
> libclamunrar
> win32
>
> Then, at least in theory we can build a DFSG free package by passing
> ENABLE_UNRAR_DEFAULT=OFF in the configure parameters.
>
> 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 tarball and update git
> (including the pristine-tar branch so we can work with the same tarball)?

How will that affect the non-free unrar package that Ubuntu ships ?

-- 
Andrew C. Aitchison                      Kendal, UK
                    andrew at aitchison.me.uk