https://bugzilla.redhat.com/show_bug.cgi?id=1020292 --- Comment #33 from Warren Togami <wtogami@xxxxxxxxx> --- >> the binary output packaged must be identical when built by anyone. > Are we having Fedora-level problems where this isn't always true? When using mock to build a clean buildroot, given a set of N-V-R's the binary output must be identical as the same package built in an identical buildroot. This would require build-time hacks beyond the usual >> There are other challenges in the build that will require discussion with FESCo. > can you outline those here? A few examples: * The official file format of the wallet.dat is BDB4. For this reason it MUST build against libdb4-devel. It appears this is fine in Fedora, but RHEL7 ships only libdb4 without the -devel package, so we'd need an exception for EPEL. * The leveldb/ directory of the source is a Bitcoin-specific fork of leveldb. Upstream leveldb is abandoned as a project, and leveldb is consensus critical so it is unsafe to link it to an general distribution library maintained in a separate package that could differ from leveldb used by non-Fedora Bitcoin nodes. FESCo would need to approve Bitcoin shipping its own fork of leveldb that is static linked in Bitcoin itself. * libsecp256k1/ directory of the source is another consensus critical library static linked in Bitcoin. FESCo must just allow Bitcoin to maintain and ship its own internal components, especially these components that are shipped in the Bitcoin source itself because they are consensus critical. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review