[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How does one include the original upstream signature?

On Fri, Aug 04, 2017 at 09:27:14AM -0400, Theodore Ts'o wrote:
> I'm getting the following lintian error message:
> E: e2fsprogs changes: orig-tarball-missing-upstream-signature e2fsprogs_1.43.5.orig.tar.gz
> N:
> N:    The packaging includes an upstream signing key but the corresponding
> N:    .asc signature for one or more source tarballs are not included in your
> N:    .changes file.
> N:
> N:    Severity: important, Certainty: certain
> N:
> N:    Check: changes-file, Type: changes
> N:
> ... but I can't figure out how to get the changes file to include the
> original upstream signature file.  I've tried naming the upstream
> signature file e2fsprogs_1.43.5.orig.tar.gz.asc; I've tried naming it
> e2fsprogs-1.43.5.tar.gz.  Neither cause dpkg-buildpackage to include
> the signature file.
Are you using a recent enough dpkg version?
"Optionally  each  original  tarball  can  be  accompanied  by  a
detached upstream  signature (.orig.tar.ext.asc and
.orig-component.tar.ext.asc), extraction supported since dpkg 1.17.20,
building supported since dpkg 1.18.5."
(from dpkg-source(1))


Attachment: signature.asc
Description: PGP signature

Reply to: