[Rpm-maint] [rpm-software-management/rpm] Make rpm builds more reproducible (Issue #2590)

[Simon J Mudd]

To your comment:

>  in some workflows people receive an srpm from somewhere and build that. 

my answer is precisely that. **When I try to rebuild the single package the process fails at the end of a 3-hour build run with an extremely obscure error message.**  Yet somehow it seems to work with the upstream packager as the rpms are built and shared publicly. The upstream packager's build environment is not public and I've seen in some cases that to make the build work in some cases some "munging" of the build environment is needed. That's very messy.

However, I think you understand my point of view. The intent of me creating this issue was to bring it up. It seems you're aware of the problem space and have shared that others also experience similar issues.

Is there anything that can be done now? What should happen next? I do not think I can do anything right now and clearly any changes would be a long term effort. Can any further progress be made?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2590#issuecomment-1667726799
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2590/1667726799 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230807/ffbfc581/attachment.html>