Bug 1206734 - build-compare is not installed on Fedora
Summary: build-compare is not installed on Fedora
Status: NEW
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: All Fedora
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Adrian Schröter
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-28 20:10 UTC by Bruno Pitrus
Modified: 2024-03-16 12:58 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Pitrus 2022-12-28 20:10:01 UTC
The Fedora:{36,37,Rawhide} projects do not support build-compare (the OBS reproducible builds checker which skips publishing a rebuilt package if it is identical to the previous one)

This results in unnecessary rebuilds when any dependency gets updated, which then get pushed to the published repository, wasting bandwidth and end-user time.

Please consider supporting build-compare when building for Fedora.
Comment 1 Olaf Hering 2024-03-15 11:37:41 UTC
Each private project has to enable (and include a copy of "the latest" build-compare) this on its own.
Comment 2 Jan Zerebecki 2024-03-15 14:34:41 UTC
Just guessing, as I have not tried none of this:

If someone submits a build-compare package and gets it included and maintains it in Fedora, then it could be enabled by default for the Fedora OBS projects that have the package.

As an intermediate step you could create a home:you:FedoraWBc:39 project that inherits from Fedora:39 . Then add a build-compare package to it. And in its prjconf add the line: Support: build-compare

My guess is that then every project that inherits from that would have it enabled.
Comment 3 Olaf Hering 2024-03-16 12:58:12 UTC
A slightly better idea would be to rename prj home:olh:build-compare to
openSUSE:Tools:build-compare (or whatever), and then include this prj/repository first in the <repository> section. It is supposed to have no side effects, beside pulling in build-compare.rpm.