Bug 2170297

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-5udq654q/clamav.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./clamav-1.0.1-norar.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

I've started the build for 1.0.1 in rawhide and f38.  But we'll need to update to 0.103.8 in the stable releases.  Hopefully Sérgio can get to that soon.

Thank you for updating the stable releases to 0.103.8.  As upstream ClamAV lists the 0.103.x LTS reaching EoL in Sept 2023, is there a plan to update the stable releases to 1.0.x LTS?

(In reply to Scott Kile from comment #3)
> Thank you for updating the stable releases to 0.103.8.  As upstream ClamAV
> lists the 0.103.x LTS reaching EoL in Sept 2023, is there a plan to update
> the stable releases to 1.0.x LTS?

Good question - I've started a discussion here: https://lists.clamav.net/pipermail/clamav-users/2023-February/013283.html

https://docs.clamav.net/faq/faq-rust.html

"I've heard that Rust requires an internet connection to work. Will I need the internet to compile ClamAV?
Yes and no.

If you're using the release tarball from clamav.net/downloads then the third-party libraries from the Rust ecosystem will be vendored into the tarball and an internet connection will not be required for the build.

If you're using some other means to obtain the ClamAV source code, such as Git or the release artifacts provided automatically by GitHub, then an internet connection will be required in order to build ClamAV."

So can't this be built for EPEL?

https://www.clamav.net/downloads/production/clamav-1.0.1.tar.gz
https://www.clamav.net/downloads/production/clamav-1.0.1.tar.gz.sig

(In reply to bunkobugsy from comment #5)
> So can't this be built for EPEL?

Bundled libraries are forbidden in Fedora/EPEL. See:

https://fedoraproject.org/wiki/Bundled_Libraries
https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling

May be it's possible with exception, but not sure.

It's possible to add new libraries in EPEL, but it's a lot of work.

(In reply to Jan ONDREJ from comment #6)
> Bundled libraries are forbidden in Fedora/EPEL. See:

As per https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling this is not forbidden, but it should be avoided.

And for Rust on EPEL 7 and 8, there might be no other choice than bundling (other than no ClamAV in EPEL).

Yes, it looks like we will be using the bundled rust source for EPEL 7/8 if/when we update to 1.X in EPEL.

It seems to me that it's possible to have clamav 1.0.0 on EPEL 7 with devtools (rust-toolset-7).

Having to use the devtoolset is a constraint?

https://www.softwarecollections.org/en/scls/rhscl/rust-toolset-7/

There is a rust package in EPEL 7 that is newer.  I've filed https://src.fedoraproject.org/rpms/rust/pull-request/19 to help with that, though it's not strictly necessary.  The main blocker at this point is a test failure reported here: https://github.com/Cisco-Talos/clamav/issues/842

Releases retrieved: 1.1.0-rc
Upstream release that is considered latest: 1.1.0-rc
Current version/release in rawhide: 1.0.1-4.fc39
URL: http://www.clamav.net/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/291/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/clamav

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-enldntjz/clamav.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./clamav-1.1.0-norar.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Releases retrieved: 1.1.0
Upstream release that is considered latest: 1.1.0
Current version/release in rawhide: 1.0.1-4.fc39
URL: http://www.clamav.net/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/291/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/clamav

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-2kd6ubsc/clamav.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./clamav-1.1.0-norar.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 225, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1961559 [details]
Update to 1.1.0 (#2170297)

So, what are people's thoughts about tracking the latest (non-LTS) clamav releases in Fedora?  I think it would be a good thing to do.

yes, I think we should update clamav on Fedora releases with 1.1

Releases retrieved: 1.2.0-rc
Upstream release that is considered latest: 1.2.0-rc
Current version/release in rawhide: 1.0.1-5.fc39
URL: http://www.clamav.net/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/291/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/clamav

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-vozfvemn/clamav.spec']' returned non-zero exit status 1.

StdOut:
warning: %patchN is deprecated (7 usages found), use %patch N (or %patch -P N)
setting SOURCE_DATE_EPOCH=1691107200
error: Bad file: ./clamav-1.2.0-norar.tar.xz: No such file or directory

RPM build warnings:
    %patchN is deprecated (7 usages found), use %patch N (or %patch -P N)

RPM build errors:
    Bad file: ./clamav-1.2.0-norar.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1981601 [details]
Update to 1.2.0-rc (#2170297)

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-gzmg3dmu/clamav.spec']' returned non-zero exit status 1.

StdOut:
warning: %patchN is deprecated (7 usages found), use %patch N (or %patch -P N)
setting SOURCE_DATE_EPOCH=1692144000
error: Bad file: ./clamav-1.2.0-norar.tar.xz: No such file or directory

RPM build warnings:
    %patchN is deprecated (7 usages found), use %patch N (or %patch -P N)

RPM build errors:
    Bad file: ./clamav-1.2.0-norar.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1983642 [details]
Update to 1.2.0-rc (#2170297)