Latest upstream release: 0.18.0
Current version/release in rawhide: 0.17.0-1.fc34
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://fedoraproject.org/wiki/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/12803/
One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.
Created attachment 1744587 [details]
[patch] Update to 0.18.0 (#1912875)
the-new-hotness/release-monitoring.org's scratch build of bcc-0.18.0-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=58973111
FEDORA-2021-5f441e4a53 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f441e4a53
FEDORA-2021-5f441e4a53 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5f441e4a53`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f441e4a53
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-5f441e4a53 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.