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

[Sebastian Andrzej Siewior]

On 2014-07-03 21:26:49 [+0200], Andreas Cadhalpun wrote:
> 
> >>I see you backported a patch to expose cl_initialize_crypto in clamav.h.
> >>Have you already tested/patched the reverse dependencies?
> 
> 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.

This has any meaning?


Regarding the bugs here. I might have talked upstream into moving
cl_initialize_crypto() into the other init function. Lets see how that
goes. If it works, we are done :)

> >- havp: #753530
> >   doesn't look very well maintained. For that reason we might want to
> >   bump the so number of the version to make sure the "old" version works
> >   even if nobody updates the packages.
> >   Besides that, it is only on unstable so we don't have to worry about
> >   stable :)
> 
> 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.

Well, if it wouldn't be for havp we wouldn't know it by now I think :)
But you made a fair point.

> >- dansguardian: #753533
> >   I opened that bug against stable. Which remainds, shouldn't oldstable
> >   be gone by now?
> 
> It has the same version in stable and unstable, so the stable update is just
> the same as the update in unstable.
> 
> >- c-icap-modules: started yesterday, should be finished by tonight :)
> 
> OK.

Patch ready but posponed due to what I just wrote about moving
cl_initialize_crypto().

> >- 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?
> 
> 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.
> 
> Best regards,
> Andreas

Sebastian