Control: tag -1 + moreinfo

Hi dkg,

On Mon, 26 Jun 2017 14:31:04 -0400 Daniel Kahn Gillmor <d...@fifthhorseman.net> 
wrote:
> I got a report on IRC that sbuild was failing during its signing phase with
> the error message:
> 
>     gpg: signing failed: A locale function failed
> 
> but normal gpg signing was working fine.
> 
> I tracked this down to what appears to be an upstream bug with
> pinentry when trying to sign in LC_ALL=C when the User ID for the
> signing key has a non-ASCII character in it:
> 
>     https://dev.gnupg.org/T3222
> 
> However, sbuild shouldn't be enforcing a C (or any other non-UTF-8)
> locale during the signing phase, so there's something wrong with
> sbuild too.
> 
> Looking in the source for sbuild, i think it looks like it's setting
> C.UTF-8 which shouldn't have this problem.  But the problem happens
> anyway, and i haven't been able to track it down further.
> 
> My attempt at building that let me replicate this error was:
> 
>     sbuild -d sid-amd64-sbuild -k $KEYID $DSCNAME
> 
> (where $KEYID refered to a secret key i have access to with only one
> User ID.  That User ID was 'Test Usér <tes...@example.net>')

thanks a lot for your report and your investigation!

Unfortunately, I'm not able to reproduce your findings. :(

    Build needed 00:00:22, no disk space
    Signature with key '96758709F780776A746BB14CCC1BF96161B0F46B' requested:
     signfile buildinfo 
/home/josch/git/dpkg-tests/t-source-minimal/pkg-minimal_1.0_amd64.buildinfo 
96758709F780776A746BB14CCC1BF96161B0F46B
    
     fixup_changes buildinfo 
/home/josch/git/dpkg-tests/t-source-minimal/pkg-minimal_1.0_amd64.buildinfo 
/home/josch/git/dpkg-tests/t-source-minimal/pkg-minimal_1.0_amd64.changes
     signfile changes 
/home/josch/git/dpkg-tests/t-source-minimal/pkg-minimal_1.0_amd64.changes 
96758709F780776A746BB14CCC1BF96161B0F46B
    
    Successfully signed buildinfo, changes files

This is a key I just created for testing purposes. As you can see, there are
definitely non-ASCII characters in its user id:

    gpg: checking the trustdb
    gpg: marginals needed: 3  completes needed: 1  trust model: pgp
    gpg: depth: 0  valid:   4  signed:   1  trust: 0-, 0q, 0n, 0m, 0f, 4u
    gpg: depth: 1  valid:   1  signed:   0  trust: 1-, 0q, 0n, 0m, 0f, 0u
    pub   rsa1024/CC1BF96161B0F46B 2018-07-01 [SC]
          96758709F780776A746BB14CCC1BF96161B0F46B
    uid                 [ultimate] Pokémon ポケモン <poke@me>

Any idea what I could do to see the issue you are having?

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to