On 2018, നവംബർ 24 3:02:56 AM IST, "David López Zajara"
wrote:
>The problem is still present on Gitlab 11.3.10
>
One possibility I can think of is ruby-gpgme version. Upstream has 2.0.13 and
we have 2.0.16. Ideally it should not be a problem, but may be some deprecated
api was removed. Try a
The problem is still present on Gitlab 11.3.10
https://maqui.darkbolt.net/
Linux registered user ~#363219
PGP keys avaiables at KeyServ. ID: 0x4233E9F2
Los hombres somos esclavos de la historia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After upgrade to 11.2, gitlab is not giving a 500 internal server error
when configuring GPG key.
But, is only getting one email identity from the key, and it isn't the
identity registered in the user.
On gitlab 10.5, configuring GPG key gives all em
3 matches
Mail list logo
