Bug#379418: dpkg-buildpackage: signing .dsc and .changes fails with UTF-8 encoded uid

2007-09-27 Thread Frank Lichtenheld
On Thu, Sep 27, 2007 at 11:55:56PM +0200, Székelyi Szabolcs wrote: > Frank Lichtenheld wrote: > > On Sun, Jul 23, 2006 at 02:46:26PM +0200, Székelyi Szabolcs wrote: > >> Lintian (and Policy?) requires the Debian changelog to be UTF-8 > >> encoded. But if -- for example, -- the maintainer name is en

Bug#379418: dpkg-buildpackage: signing .dsc and .changes fails with UTF-8 encoded uid

2007-09-27 Thread Székelyi Szabolcs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frank Lichtenheld wrote: > On Sun, Jul 23, 2006 at 02:46:26PM +0200, Székelyi Szabolcs wrote: >> Lintian (and Policy?) requires the Debian changelog to be UTF-8 >> encoded. But if -- for example, -- the maintainer name is encoded this >> way, then gpg

Bug#379418: dpkg-buildpackage: signing .dsc and .changes fails with UTF-8 encoded uid

2007-07-10 Thread Frank Lichtenheld
On Sun, Jul 23, 2006 at 02:46:26PM +0200, Székelyi Szabolcs wrote: > Lintian (and Policy?) requires the Debian changelog to be UTF-8 > encoded. But if -- for example, -- the maintainer name is encoded this > way, then gpg fails to find the secret key because assumes by default > that the command li

Bug#379418: dpkg-buildpackage: signing .dsc and .changes fails with UTF-8 encoded uid

2006-07-23 Thread Székelyi Szabolcs
Package: dpkg-dev Version: 1.13.22 Severity: normal Tags: patch l10n -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Lintian (and Policy?) requires the Debian changelog to be UTF-8 encoded. But if -- for example, -- the maintainer name is encoded this way, then gpg fails to find the secret key