Open ktdreyer opened 9 years ago
TODO: check out https://github.com/mkouhei/pydebsign . It is a Python re-implementation of debsign, and it might suit our goals.
Any .changes
files that reference .dsc
files need to be rewritten as well. They typically contain checksums of the .dsc
files.
It is typical for Debian/Ubuntu to sign all
.dsc
files. This ticket explores the possibility of having merfi handle this.An example of an inline-signed
.dsc
file (the curl package for trusty): http://us.archive.ubuntu.com/ubuntu/pool/main/c/curl/curl_7.19.7-1ubuntu1.dscThe problem is that this affects the reprepro metadata, because the .dsc file's overall checksum changes after it gets signed.
An example of a metadata file that contains a checksum of a
.dsc
file is http://us.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Sources.bz2The workflow would have to look something like this:
.dsc
file (conventionally Debian developers usedebsign
for this, but technically it could be done withgpg
orrpm-sign
).dsc
file usingreprepro
Release
files (as merfi already does).Alternatively, if we wanted to do the signing without interleaving
reprepro
, another workflow might be:.dsc
file to the repo, usingreprepro
.dsc
file.dsc
file within theSources
file(s)Sources
within theRelease
fileRelease
file (as merfi already does).This is more complex, more tightly coupled with the behavior of reprepro, and more prone to possible errors. On the other hand, the advantage is that
reprepro
can be run only once at the beginning, before anything has to be signed.Maybe it would be easier to package and build reprepro for Red Hat rel-eng's platform (ie RHEL 6) than it would be to implement this "fiddle with the checksums" workflow in merfi.