Unable to sign Code of Conduct

Bug #359758 reported by Ruben Verweij

This bug report was converted into a question: question #67373: Unable to sign Code of Conduct.

This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

I am unable to sign the Ubuntu Code of Conduct. I downloaded version 1.0.1, added whitespaces as was suggested on the page, signed it with the comment provided on the page and pasted it into the textarea. There was an error stating the text didn't match the Code of Conduct. As I've just followed the steps as indicated on the page, I think this should be considered as a bug. I'd be happy to get a solution from someone.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

This is better handled as a question.

Ruben, can you copy and paste (use http://pastebin.ubuntu.com/) the code of conduct you modified and is trying to sign?


Changed in launchpad:
status: New → Invalid
Revision history for this message
Twisted Lucidity (lucidlytwisted) wrote :

I have this exact same problem, but with code of conduct 1.1. As far as I can tell, I have followed the instructions to the letter. If I copy and past the contents of the ".asc", I get a warning that the contents are not the same as the original text. The signed file begins with:
Hash: SHA1

If I remove that I no longer get the content warning, but now I get a warning about a bad signature.

The only changes I made were adding a couple of few spaces to the title using gedit.
= Ubuntu Code of Con duct v1.1 =
(Full text is here http://pastebin.ubuntu.com/343739/)

I have done a diff -B -b between the unsigned and signed files and the only differences showing are the PGP parts.

As I have just downloaded the 1.1 content, the information in the answer doens't help me.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions