[Pkg-clamav-devel] Processing of clamav_0.98.4+dfsg-1_i386.changes

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Thu Jul 3 20:45:11 UTC 2014


Hi,

On 03.07.2014 22:13, Scott Kitterman wrote:
> On July 3, 2014 3:26:49 PM EDT, Andreas Cadhalpun <andreas.cadhalpun at googlemail.com> wrote:
>> Looking closer, I think now that cl_initialize_crypto and
>> cl_cleanup_crypto are in clamav.h, they should be moved from
>> CLAMAV_PRIVATE to CLAMAV_PUBLIC in libclamav/libclamav.map.
>
> Should discuss with upstream.

Sure, but I postpone this now, to see, if Sebastian managed to convince 
upstream to call cl_initialize_crypto inside of cl_init.
That would make such a discussion void.

>> Not very well maintained means in this case completely unmaintained
>> since three years. Given that it has now 5 RC bugs, it's probably best
>> to remove it from the archive.
>
> Upstream havp offered to do a new release to fix this issue, so depending on how hard the RC bugs are to fix, it might be worth an NMU.

Apart from the clamav API change, there are:

#689892: This has a patch.
#689778: is a duplicate of #689892.
#582306: This is a pseudo-bug from a time, where clamav itself was
          perceived as to volatile for stable. (Could just be closed.)
#640601: This claims the installation fails, but I can't reproduce that.
          Instead the init script fails:
          Mounting /var/lib/havp/havp.loop under /var/spool/havp ...
          mount: Could not find any loop device.

>>> - python-pyclamav: haven't look at it yet.
>>
>> I just looked into this one and the attached patch should be enough,
>> but
>> I'm not sure how to test that.
>>
>> Scott, since you are the only uploader of python-pyclamav, can you
>> verify that this patch is good?
>
> I can try it.

OK, but you can wait until we know definitely what upstream will do.

>> By the way, python-pyclamav seems to be dead upstream since 2008 and
>> superseeded by python-pyclamd, which seems to be unmaintained in Debian
>>
>> since 2011, while the last upstream version is from 2014-06-23.
>>
>> You might want to consider to take over python-pyclamd and remove
>> python-clamav from unstable.
>
> Python-pyclamd doesn't fully replace python-clamav.  It requires little enough maintenance that I think it's worth keeping.
>
> I'll look into the patch and pyclamd.

I see.

Best regards,
Andreas




More information about the Pkg-clamav-devel mailing list