On Thu, 16 Mar 2017 18:14:42 -0400, James McCoy wrote:

> > Same here (well, not vectis :)). I guess having the build results in
> > ../build-area or somewhere else (e.g. /var/cache/pbuilder/result) is
> > quite common, so Simon and me are probably not the only ones whose
> > packaging workflow is broken -- which would warrent a severity >
> > normal and a fix for stretch IMO.
> Ah, now I can reproduce.  The problem happens when the changes is in a
> different directory and there's no buildinfo in the referenced changes
> file.

Oh, right, the .buildinfo is missing in the .changes files I tried to
sign.
(Interesting, it used to be there before in my case [0], I think …)
 
> Will work on this soon.

Thanks!


Cheers,
gregor


[0]
https://anonscm.debian.org/cgit/pkg-perl/packages/pkg-perl-tools.git/tree/examples/check-build#n167
ff.

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: R.E.M.: Everybody Hurts

Attachment: signature.asc
Description: Digital Signature

_______________________________________________
devscripts-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel

Reply via email to