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

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Thu Jul 3 15:37:58 UTC 2014


Hi,

On 03.07.2014 08:54, Sebastian Andrzej Siewior wrote:
> On 2014-07-02 23:12:01 [+0200], Andreas Cadhalpun wrote:
>> Now uscan removes both contrib and win32 directories, so that's not the
>> problem. It's rather that the originally downloaded tarball is now nearly 40
>> MB instead of the 15 MB tarball from sourceforge.
>> There are also various .gitignore files, which would interfere with our own
>> usage of git, so I added them to Files-Excluded as well.
>
> I wouldn't mind the initial download.

It's just a minor annoyance.

>> I don't know why they modify their release tarball in this way, but I don't
>> think it makes much difference for us.
>
> Ah. One reason might be that they do "make dist" and autoconf creates
> the tarball. If the extra files (say fp_gcd.c) is not refrenced in
> Makefile then it won't be added to the final tarball.

Yes, that's a likely reason, meaning it really doesn't hurt if these 
files are present, because they are not used.

>>> Maybe they can manage to sign their tags.
>>
>> That would be good, although I don't know if uscan can verify signed tags.
>> Or would there be detached signatures on the download page?
>
> Argh, right. No, it would be part of the tag. So it wouldn't be of any
> use for use then :P

Except if uscan can be thought to verify signed tags...

I see you backported a patch to expose cl_initialize_crypto in clamav.h.
Have you already tested/patched the reverse dependencies?

Best regards,
Andreas



More information about the Pkg-clamav-devel mailing list