Unable to sign Ubuntu Code of Conduct

Asked by Andrew Davison

I'm attempting to sign the Ubuntu code of conduct, but repeatedly receive the error:

(7, 9, u'No public key')

The signed copy is copied below.

Having read previous answers I have compared the original file to the signed copy, and other than the header and signature, there are no differences reported. My key appears on keyserver.ubuntu.com and has been there for around 24 hours at this point.

Does anybody have any clues as to why I still cannot sign the code of conduct?

Thanks,

    Andy.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

= Ubuntu Code of Conduct v1.1 =

This Code of Conduct covers our behaviour as members of the Ubuntu
Community, in any forum, mailing list, wiki, web site, IRC channel,
install-fest, public meeting or private correspondence. Ubuntu
governance bodies are ultimately accountable to the Ubuntu Community
Council and will arbitrate in any dispute over the conduct of a member
of the community.

      '''Be considerate.''' Our work will be used by other people, and
      we in turn will depend on the work of others. Any decision we take
      will affect users and colleagues, and we should take those
      consequences into account when making decisions. Ubuntu has
      millions of users and thousands of contributors. Even if it's not
      obvious at the time, our contributions to Ubuntu will impact the
      work of others. For example, changes to code, infrastructure,
      policy, documentation, and translations during a release may
      negatively impact others' work.

      '''Be respectful.''' The Ubuntu community and its members treat
      one another with respect. Everyone can make a valuable
      contribution to Ubuntu. We may not always agree, but disagreement
      is no excuse for poor behaviour and poor manners. We might all
      experience some frustration now and then, but we cannot allow that
      frustration to turn into a personal attack. It's important to
      remember that a community where people feel uncomfortable or
      threatened is not a productive one. We expect members of the
      Ubuntu community to be respectful when dealing with other
      contributors as well as with people outside the Ubuntu project and
      with users of Ubuntu.

      '''Be collaborative.''' Collaboration is central to Ubuntu and to
      the larger free software community. This collaboration involves
      individuals working with others in teams within Ubuntu, teams
      working with each other within Ubuntu, and individuals and teams
      within Ubuntu working with other projects outside. This
      collaboration reduces redundancy, and improves the quality of our
      work. Internally and externally, we should always be open to
      collaboration. Wherever possible, we should work closely with
      upstream projects and others in the free software community to
      coordinate our technical, advocacy, documentation, and other work.
      Our work should be done transparently and we should involve as
      many interested parties as early as possible. If we decide to
      take a different approach than others, we will let them know early,
      document our work and inform others regularly of our progress.

      '''When we disagree, we consult others.''' Disagreements, both
      social and technical, happen all the time and the Ubuntu
      community is no exception. It is important that we resolve
      disagreements and differing views constructively and with the help
      of the community and community processes. We have the Technical
      Board, the Community Council, and a series of other governance
      bodies which help to decide the right course for Ubuntu. There are
      also several Project Teams and Team Leaders, who may be able to
      help us figure out the best direction for Ubuntu. When our goals
      differ dramatically, we encourage the creation of alternative sets of
      packages, or derivative distributions, using the Ubuntu Package
      Management framework, so that the community can test new ideas and
      contribute to the discussion.

      '''When we are unsure, we ask for help.''' Nobody knows
      everything, and nobody is expected to be perfect in the Ubuntu
      community. Asking questions avoids many problems down the road,
      and so questions are encouraged. Those who are asked questions should
      be responsive and helpful. However, when asking a question, care must
      be taken to do so in an appropriate forum.

      '''Step down considerately.''' Members of every project come and
      go and Ubuntu is no different. When somebody leaves or disengages
      from the project, in whole or in part, we ask that they do so in a
      way that minimises disruption to the project. This means they
      should tell people they are leaving and take the proper steps to
      ensure that others can pick up where they left off.

We pride ourselves on building a productive, happy and agile community
that can welcome new ideas in a complex field, and foster collaboration
between groups with very different needs, interests and goals. We hold
our leaders to an even higher standard, in the Leadership Code of
Conduct, and arrange the governance of the community to ensure that
issues can be raised with leaders who are engaged, interested and
competent to help resolve them.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJQdVqrAAoJEEdvuNiOqYviCNMP/jsnkD8p5iQ8JIOS00YUnPqV
W/szkxKImj+ni4O2/AsxUzNdZiwD2bRyR3dji/YYhosdYz1c556dTzE1re7b6D7T
KcqBOhP9B7m/6ajY6zjC8+08EKSNsrZUJXZXOIMjvq0NfZDIgon62s7Mxxs8GyRQ
0aLsC48djAWgoXu5Lk8sn3LYYH9fonBcsjCLiw0GKlZPB5Nbq8xvySIHHgxia+RU
o1QBslGxMNVE+MMwD+RPXaFq8zUhSL64ACCphjUJByxUIJpwb4kC4vDoG7r3FZ5Q
D0o1KpjE+mpFzUA0MOMvYyHgSl2SF6mc+WZ6vw7A65+9tTdpqzbn45EqFYiijklK
w6CfXJPhjneLGJwTS8zK2fEZ91PsZNc+Gp7hOqeOIOSSqKlKMxxe8KeYCOqAJGiu
sscwnUCTQqSv2rqnIJxMQ3JPGAW1uW4A+bJ8PcHZ4ZDGLhSlHoxSfFls6pWaGl6H
ZcbviuykId3tKLPsvv75GBnyzPLKH5jQkYyhSHbOvo/MiqMr398TghEAFax8QpQq
Gfg9GxWXXTj0nDUZfcdArG6XGkh9dLUWVRQTy0QS7+XyBNSFW4XbVVX4JdONa0Xn
WSMKyqLLV1qtT9B31BMPiJCtKwpUI4W740AR1bD6i2Qu9/RIOAqESS+IVHAtKV8t
YowOH7WVbhHB/kA6awl2
=Oe31
-----END PGP SIGNATURE-----

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Andrew Davison
Solved:
Last query:
Last reply:
Revision history for this message
Laura Czajkowski (czajkowski) said :
#1

You have only one key:
http://keyserver.ubuntu.com:11371/pks/lookup?op=vindex&search=0xD543BD02B52EF7A5

You may want to be certain you are signing with the one key that Lp knows about
If you have more than one key in your keyring, your need to sign using this command that selects the same key that Lp knows about:
 gpg -u B52EF7A5 --clearsign

Revision history for this message
Andrew Davison (andydvsn) said :
#2

Thanks for your reply, Laura - I was sure I tried this earlier, but have just given it another shot. Signed the file again, compared it just in case, copy-n-pasted back into Launchpad. Same error, I'm afraid. :(

Revision history for this message
Nicolas Martignoni (nicolas-martignoni) said :
#3

I'm experiencing exactly the same problem with following text. I specified explicitly the key with the syntax
gpg -u CC188BF6 --clearsign UbuntuCodeofConduct-1.1.txt
but no joy :-(

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

= Ubuntu Code of Conduct v1.1 =

This Code of Conduct covers our behaviour as members of the Ubuntu
Community, in any forum, mailing list, wiki, web site, IRC channel,
install-fest, public meeting or private correspondence. Ubuntu
governance bodies are ultimately accountable to the Ubuntu Community
Council and will arbitrate in any dispute over the conduct of a member
of the community.

      '''Be considerate.''' Our work will be used by other people, and
      we in turn will depend on the work of others. Any decision we take
      will affect users and colleagues, and we should take those
      consequences into account when making decisions. Ubuntu has
      millions of users and thousands of contributors. Even if it's not
      obvious at the time, our contributions to Ubuntu will impact the
      work of others. For example, changes to code, infrastructure,
      policy, documentation, and translations during a release may
      negatively impact others' work.

      '''Be respectful.''' The Ubuntu community and its members treat
      one another with respect. Everyone can make a valuable
      contribution to Ubuntu. We may not always agree, but disagreement
      is no excuse for poor behaviour and poor manners. We might all
      experience some frustration now and then, but we cannot allow that
      frustration to turn into a personal attack. It's important to
      remember that a community where people feel uncomfortable or
      threatened is not a productive one. We expect members of the
      Ubuntu community to be respectful when dealing with other
      contributors as well as with people outside the Ubuntu project and
      with users of Ubuntu.

      '''Be collaborative.''' Collaboration is central to Ubuntu and to
      the larger free software community. This collaboration involves
      individuals working with others in teams within Ubuntu, teams
      working with each other within Ubuntu, and individuals and teams
      within Ubuntu working with other projects outside. This
      collaboration reduces redundancy, and improves the quality of our
      work. Internally and externally, we should always be open to
      collaboration. Wherever possible, we should work closely with
      upstream projects and others in the free software community to
      coordinate our technical, advocacy, documentation, and other work.
      Our work should be done transparently and we should involve as
      many interested parties as early as possible. If we decide to
      take a different approach than others, we will let them know early,
      document our work and inform others regularly of our progress.

      '''When we disagree, we consult others.''' Disagreements, both
      social and technical, happen all the time and the Ubuntu
      community is no exception. It is important that we resolve
      disagreements and differing views constructively and with the help
      of the community and community processes. We have the Technical
      Board, the Community Council, and a series of other governance
      bodies which help to decide the right course for Ubuntu. There are
      also several Project Teams and Team Leaders, who may be able to
      help us figure out the best direction for Ubuntu. When our goals
      differ dramatically, we encourage the creation of alternative sets of
      packages, or derivative distributions, using the Ubuntu Package
      Management framework, so that the community can test new ideas and
      contribute to the discussion.

      '''When we are unsure, we ask for help.''' Nobody knows
      everything, and nobody is expected to be perfect in the Ubuntu
      community. Asking questions avoids many problems down the road,
      and so questions are encouraged. Those who are asked questions should
      be responsive and helpful. However, when asking a question, care must
      be taken to do so in an appropriate forum.

      '''Step down considerately.''' Members of every project come and
      go and Ubuntu is no different. When somebody leaves or disengages
      from the project, in whole or in part, we ask that they do so in a
      way that minimises disruption to the project. This means they
      should tell people they are leaving and take the proper steps to
      ensure that others can pick up where they left off.

We pride ourselves on building a productive, happy and agile community
that can welcome new ideas in a complex field, and foster collaboration
between groups with very different needs, interests and goals. We hold
our leaders to an even higher standard, in the Leadership Code of
Conduct, and arrange the governance of the community to ensure that
issues can be raised with leaders who are engaged, interested and
competent to help resolve them.

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJQdH+JAAoJEBNI/nIf411Q6igH/A2YU6UIwhBBfyu+WH7eWc0P
T95wPExL8fHNogyOMTLjNn8AXvU3swh3dFaXGo2AUSXzOhr11Sr4A3G5J4cL8/og
ZhbhvxxoVuMZB2IPAonTtmJgWZXSZAhkQjogGwz7qKCm/tvaQwP2CU2kk9MlnTdf
qxGGe9aUBD94gIwW4kaqFa6PK4S00u+Kub+j2gfAWjxBSDL+rPPqg3YlWM8zTm6D
w28OAvrAU1BQiz37KbKAX/eqxrNdK6wdhawLaDTFeccUX3ntYSlm3mA2atA25qHq
O7+I3h0UyVLIW66zpDpCrKR8KZbXd6pdB1yRscH6zv+Irg2PSoaLC5pH5a9tbDY=
=QiLV
-----END PGP SIGNATURE-----

Revision history for this message
Laura Czajkowski (czajkowski) said :
#4

This should be resolved now, sorry for the hassle.

Revision history for this message
Andrew Davison (andydvsn) said :
#5

Hooray! It's good to know it wasn't me for a change. ;)

Revision history for this message
John Bartley K7AAY (jwhn) said :
#6

Same problem. I ran

gpg -u E515D862 --clearsign

which stalled after I entered the appropriate passphrase.

Revision history for this message
Colin Watson (cjwatson) said :
#8

Bob, please can you file a new ticket with full details of what you tried to do? It's not practical to keep track of closed tickets that people jump back into years later like this. Thanks.

  https://answers.launchpad.net/launchpad/+addquestion