Package: signing-party Version: 2.6-1 Severity: minor Tags: patch Dear Maintainer,
I ran codespell on pgp-tools and found five spelling mistakes. Here is a patch to correct the spelling errors. Best wishes, Edward.
Index: caff/README.many-keys =================================================================== --- caff/README.many-keys (revision 899) +++ caff/README.many-keys (working copy) @@ -18,7 +18,7 @@ For convenience, caff also allows spaces in fingerprints/keyids as output by gpg --fingerprint. -* Use gpgparticipants(1) formated input when possible. +* Use gpgparticipants(1) formatted input when possible. When the KSP organizer provides a gpgparticipants(1) compatible list of all the participants, it can be convenient to transcribe the Index: caff/caff =================================================================== --- caff/caff (revision 899) +++ caff/caff (working copy) @@ -1131,7 +1131,7 @@ my ($message_entity) = @_; if ((scalar @{$CONFIG{'mailer-send'}} > 0) && !$warned_about_broken_mailer_send) { - mywarn("You have set arguments to pass to Mail::Mailer. Better fix your MTA. (Also, Mail::Mailer's error reporting is non existant, so it won't tell you when it doesn't work.)"); + mywarn("You have set arguments to pass to Mail::Mailer. Better fix your MTA. (Also, Mail::Mailer's error reporting is non existent, so it won't tell you when it doesn't work.)"); $warned_about_broken_mailer_send = 1; }; $message_entity->send(@{$CONFIG{'mailer-send'}}); @@ -1870,7 +1870,7 @@ foreach my $u (@signers) { my @signeduids; # uids signed by $u foreach my $uid (@uids) { - # we use UIDs hashes to distinguish and select UIDs; it's the only reliable way to identify them accross keyrings + # we use UIDs hashes to distinguish and select UIDs; it's the only reliable way to identify them across keyrings push @signeduids, $uid if grep { $u eq $_ } (keys %{$uid->{xsigners}}) and !grep { $uid->{hash} eq $_->{hash} } @signeduids; } Index: keyanalyze/pgpring/lib.c =================================================================== --- keyanalyze/pgpring/lib.c (revision 899) +++ keyanalyze/pgpring/lib.c (working copy) @@ -482,7 +482,7 @@ } else { - ungetc (c, fp); /* undo our dammage */ + ungetc (c, fp); /* undo our damage */ /* There wasn't room for the line -- increase ``s'' */ offset = *size - 1; /* overwrite the terminating 0 */ *size += STRING; Index: keyart/doc/druken-bishop.txt =================================================================== --- keyart/doc/druken-bishop.txt (revision 899) +++ keyart/doc/druken-bishop.txt (working copy) @@ -51,7 +51,7 @@ (9,5), which is position 104, the center of the board. Movement is defined by taking the fingerprint, and coverting each -character to its binary value. For exmaple, the fingerprint: +character to its binary value. For example, the fingerprint: E041 3539 273A 6534 A3E1 9259 22EE E048 8086 060F