.buildinfo server
In order to build packages reproducibly, you not only need identical
sources but also some external definition of the environment used for a
particular build. This definition includes the inputs and the outputs
and—in the Debian case—are available in a
$package_$architecture_$version.buildinfo file.
It is not currently clear how these files could or should be handled in practice, hence the creation of this server to investigate.
0xA6B59AB7CD69D4AC
profitbricks-build2-i386 (Automatically generated key for signing .buildinfo files)
0x1310D22166A88B5F
profitbricks-build6-i386 (Automatically generated key for signing .buildinfo files)
0xFD20BBE472905784
0x28F5F5D5FEE63ABA
0x1BD40F376E003684
profitbricks-build5-amd64 (Automatically generated key for signing .buildinfo files)
0x5FA3DA39796FBACF
profitbricks-build1-amd64 (Automatically generated key for signing .buildinfo files)
0x2EB7D8A099C83DD8
0xAEC7FC78A3E8B530
0x4F15D07E60F07CB2
0x2BBA298F216A5729
ff64a (Automatically generated key for signing .buildinfo files)
0x1D3EA4D86F2FB555
codethink-sled15-arm64 (Automatically generated key for signing .buildinfo files)
0xFDD087C6FCA6B1BE
codethink-sled10-arm64 (Automatically generated key for signing .buildinfo files)
0xFD20BBE472905784
0x28F5F5D5FEE63ABA
0x8FCA21099AC7DFA4
0x2EB7D8A099C83DD8
0x2738E803AC4FE478
0xAEC7FC78A3E8B530
0xAEC7FC78A3E8B530
0x2738E803AC4FE478
$ gpg --output=- --clearsign my.buildinfo | curl -X PUT --max-time 30 --data-binary @- https://buildinfo.debian.net/api/submit