Adding a GPG key does not recognize all idents

changed the description

added Create [DEPRECATED] devopscreate gpg typebug labels

Checking other issues, I've found related omnibus-gitlab!2747 (merged) and omnibus-gitlab#3821 (closed).

I'm referencing it, because as I've commented, my installation are Debian non-omnibus and ruby-gpgme gem are 2.0.16 / libgpgme 1.12 version. But this does not explain why adding the signature on gitlab.com does the same result.

Thanks for reporting @Er_Maqui!

I wonder if this is another manifestation of the problem in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23492/diffs

Can you confirm the public key you're trying to add, and perhaps add it as an attachment to this issue? http://pgp.mit.edu/pks/lookup?op=vindex&search=0x7C58C0E04233E9F2 ? I'm having some trouble downloading that one...

added needs investigation label

added priority3 severity3 labels

The key is the one pointed by you. But for simplicity I'll post it here.

If you need any information / try on my side please let me know it.

Thanks,

Hi,

There's any new data about this? Can I help with something on this bug?

Thanks,

There's new data about this bug?

added SLOMissed label

removed SLOMissed label

added [deprecated] Accepting merge requests label

removed [deprecated] Accepting merge requests label

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

Adding a GPG key does not recognize all idents

Summary

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Designs

Child items ...

Activity

Frequently Asked Questions