Hello. 

(one of) the Fedora spamassassin maintainers here. I thought I'd chime
in with some information...

On Tue, Dec 20, 2022 at 08:48:13AM -0800, Kenneth Porter wrote:
> On 12/19/2022 7:59 PM, Kenneth Porter wrote:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=2154501
> > 
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-e341ba52a1
> > 
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=2102188
> > 
> > It looks like the packaging fails before building anything because the
> > filename in the spec file for the rules tarball doesn't match the
> > version of rules actually included in the srpm.

The bug is filed by an automated process that basically just says "hey,
there's a new version". It also tries a dirt simple rebuild, by just
updating the version. Thats what you see failing there (for a number of
reasons). I'll see if I can just supress that test build, it seems to be
confusing people. 

> The srpm at the Koji link seems to build fine on my Rocky 8 (RHEL 8 respin)
> x86_64 system. The error reported in the Bugzilla entry must be from an
> initial test build as the rules tarball in the Koji srpm matches the
> filename in its spec file.
> 
> Here's a direct link to the test srpm, copied from the Koji link above:
> 
> https://kojipkgs.fedoraproject.org//packages/spamassassin/4.0.0/1.fc38/src/spamassassin-4.0.0-1.fc38.src.rpm
> 
> The rule tarball is indeed included in the generated RPM as an initial rule
> set under /usr/share/spamassassin.
> 
> The packaging script:
> 
> https://src.fedoraproject.org/rpms/spamassassin/blob/rawhide/f/spamassassin.spec
> 
> The README which includes justification for including the rules:
> 
> https://src.fedoraproject.org/rpms/spamassassin/blob/rawhide/f/README.RHEL.Fedora

Right. 

Do note that this was an initial version I was pushing to Fedora
rawhide. It already had an issue causing spamd to not start with default
options (fixed in 4.0.0-2). 

Everyone is of course welcome to rebuild and use this, but keep in mind
it's still in testing and if it breaks you should let us know (file a
bug). 

Thanks, 

kevin

Attachment: signature.asc
Description: PGP signature

Reply via email to