On Thu, Mar 16, 2017 at 06:32:07PM +0000, Simon McVittie wrote:
> I'm using a build tool (vectis, #843486) that outputs all built files into a
> newly created directory. I used to be able to use a command like:
>
> debsign whatever_directory/*_source.changes
>
> but this no longer works:
>
> $ debsign ostree_2017.3-1_20170316t070324/ostree_2017.3-1_source.changes
> debsign: Can't find or can't read buildinfo file
> ostree_2017.3-1_20170316t070324/!
> $ debsign
> $(pwd)/ostree_2017.3-1_20170316t070324/ostree_2017.3-1_source.changes
> debsign: Can't find or can't read buildinfo file
> /home/smcv/tmp/build-area/ostree_2017.3-1_20170316t070324/!
Are you sure that was with 2.17.3? That was something I specifically
addressed with in 2.17.3 to fix #857716.
$ debsign serf/serf_1.3.9-1_amd64.changes
The .changes file is already signed.
Would you like to use the current signature? [Yn]n
unsignfile serf/serf_1.3.9-1_amd64.changes
The .buildinfo file is already signed.
Would you like to use the current signature? [Yn]n
unsignfile serf/serf_1.3.9-1_amd64.buildinfo
The .dsc file is already signed.
Would you like to use the current signature? [Yn]n
unsignfile serf/serf_1.3.9-1.dsc
signfile dsc serf/serf_1.3.9-1.dsc James McCoy <[email protected]>
fixup_buildinfo serf/serf_1.3.9-1.dsc serf/serf_1.3.9-1_amd64.buildinfo
signfile buildinfo serf/serf_1.3.9-1_amd64.buildinfo James McCoy
<[email protected]>
fixup_changes dsc serf/serf_1.3.9-1.dsc serf/serf_1.3.9-1_amd64.changes
fixup_changes buildinfo serf/serf_1.3.9-1_amd64.buildinfo
serf/serf_1.3.9-1_amd64.changes
signfile changes serf/serf_1.3.9-1_amd64.changes James McCoy
<[email protected]>
Successfully signed dsc, buildinfo, changes files
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
_______________________________________________
devscripts-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
