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

[Scott Kitterman]

On Friday, December 30, 2022 7:11:45 PM EST Scott Kitterman wrote:
> On December 30, 2022 11:44:39 PM UTC, Sebastian Andrzej Siewior 
<sebastian at breakpoint.cc> wrote:
> >On 2022-12-30 16:22:21 [-0500], Scott Kitterman wrote:
> >> Great.  I finished the changes for the embedded crates (it's not perfect
> >> machine readable copyright format, but it's close and I think it will do
> >> for the moment) and pushed the change.  It should be a fast forward for
> >> you when you pull it.
> >
> >did it.
> >
> >> I think the short d/rules file that I sent you earlier has the ~correct
> >> build options for us, so don't redo that if you don't have to.
> >
> >just updated it with your input.
> >
> >> I'll be around this weekend, so if you upload it, I should be able to
> >> check it through New.  I'll send an email to the release team warning
> >> them about our need for an upcoming transition slot.
> >> 
> >> Anything else I can help with?
> >
> >I got a few steps further instead going to bed. It complains now about
> >missing testfiles because they are no longer shipped. So either we need
> >to tweak it or we just drop that package.
> >Other than that we would need to test or just throw it to exp asap and
> >sort the pieces later. So I think we need to figure out if we keep
> >`clamav-testfiles' and manually move the files or drop it (and maybe
> >introduce it later again if people complain).
> >
> >> Scott K
> >
> >Sebastian
> 
> I think if there's a reasonable way to keep it, we should.  In general
> though, I think uploading to experimental sooner rather than later is the
> right way to go, but if you drop the testfiles package now, it'll end up in
> New again when we put it back (people do use it, so I'm confident we'll get
> complaints if we drop it).

I looked at it some and the testfiles appear to be gone.  Let's drop the binary 
and move on.

I discovered that the experimental (and upstream-experimental) branches still 
have the crates that are now excluded when the tarball is created.  I made a 
new branch called upstream-experimental-fixup and pushed it.  You ought to be 
able to merge that to upstream-experimental and then merge that to 
experimental and get an unpacked directory that dpkg-buildpackage things goes 
with the tarball.  We (I volunteer) will also need to fixup the pristine-tar 
branch, but that can be later.

I pushed some changes to the experimental branch to help it build using dpkg-
buildpackage:

 - added build-depends
 - added my rust compilation requirements patch that I had emailed you (it's 
not applied, just in d/patches and listed in d/patches/series)
 - added the target directory for the unit files in configure in d/rules

With those changes, it gets through to install, where it failes for multiple 
reasons:

1.  There's a typo in the libclamav11.install file (fixed in git).
2.  Missing testfiles (I say nuke the binary and move on, but I didn't do it).
3.  Missing html docs.  This just needs the proper doxygen invocation (but 
it's late and I'm tired here, so I didn't make and changes for this).  I did 
manually build the docs and once those were present it got all the way to 
symbols files.

Back over to you.  I'm going to bed.  Good luck.

Scott K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-clamav-devel/attachments/20221231/35773d00/attachment.sig>