Hi Mattia, > wait, but why is the checksum of the .dsc in the .buildinfo wrong? > `debsign` takes care of updating the checksums in the .buildinfo when > you sign a .changes (or a .buildinfo). And of course if you sign
oh, that must be new then. I have a specific setup that copies the .dsc and .changes from the remote (Debian) system to the local (BSD) system that contains my PGP secret key, signs them with a only slightly patched version of debsign (to work on BSD, not GNU coreutils and such), and copies them back. It is semantically interesting, because the build was not actually done with the signed .dsc, but I guess that’s irrelevant. Meh, so I guess I have to port the newer debsign to BSD and then change the wrapper copying script to handle the added complexity… bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C"
