Description
I have been unable to successfully reproduce the build of v1.10.3 in the releases section on two different machines, running fresh installs of Fedora 43 and Debian 13. My upgrade message and unsigned binary hash on both machines also match the values recorded on WalletScrutiny.com's Specter page, which currently lists the build as not reproducible from source.
Steps to reproduce
- In a new copy of Fedora 43 or Debian 13, install Docker Engine using the instructions found in the official Docker documentation
- Clone the repository, then fetch and cleanly checkout tags/v1.10.3
- Follow the instructions found in docs/reproducible-build.md
Expected behavior
Upgrade message of:
b1.0.2-1.10.3-1zucdggdy53lf3uzhdn7l8wetyn0a5l3zmfynqcgswszdmm2g2upqwg9f3u
Unsigned binary hash of:
9e5383fb527d9c40fbb6dcbdc49ce66118c7c374c2fd79cb7413220ec443dda0
Actual Behavior
Upgrade message of:
b1.0.2-1.10.3-1f5vpx7ry9zm8lp7vemjl82rdlq9xzcjypr6jnajp44ulcl7ps7mqzvx7lg
Unsigned binary hash of:
a6d231e5f4d793d9dd18001a55cc944147c60aad63a0e2735e262d4186e7f98b
Please let me know if I can provide extra context, logs, etc. to see why this might be happening. I'm also happy to run any additional tests/diagnostics on my end if that's helpful.
Description
I have been unable to successfully reproduce the build of v1.10.3 in the releases section on two different machines, running fresh installs of Fedora 43 and Debian 13. My upgrade message and unsigned binary hash on both machines also match the values recorded on WalletScrutiny.com's Specter page, which currently lists the build as not reproducible from source.
Steps to reproduce
Expected behavior
Upgrade message of:
b1.0.2-1.10.3-1zucdggdy53lf3uzhdn7l8wetyn0a5l3zmfynqcgswszdmm2g2upqwg9f3u
Unsigned binary hash of:
9e5383fb527d9c40fbb6dcbdc49ce66118c7c374c2fd79cb7413220ec443dda0
Actual Behavior
Upgrade message of:
b1.0.2-1.10.3-1f5vpx7ry9zm8lp7vemjl82rdlq9xzcjypr6jnajp44ulcl7ps7mqzvx7lg
Unsigned binary hash of:
a6d231e5f4d793d9dd18001a55cc944147c60aad63a0e2735e262d4186e7f98b
Please let me know if I can provide extra context, logs, etc. to see why this might be happening. I'm also happy to run any additional tests/diagnostics on my end if that's helpful.