Closed sblaisot closed 9 months ago
cc @gilacost
Working on it, there is an issue on the github runner and not reading the GPG Keys correctly.
Hi @dalbarado any news?
Continue troubleshooting, I already changed PGP, but aptly over github runner didn't work as expected, because it didn't take pgp anymore. Investigating the issue.
On Mon, 18 Sept 2023 at 03:20, Sebastien BLAISOT @.***> wrote:
Hi @dalbarado https://github.com/dalbarado any news?
— Reply to this email directly, view it on GitHub https://github.com/esl/packages/issues/71#issuecomment-1722812672, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGRO4LHEECJLWDSULSGTTZLX27R3NANCNFSM6AAAAAA4THQGM4 . You are receiving this because you were mentioned.Message ID: @.***>
-- Our upcoming conferences: Code BEAM Europe https://codebeameurope.com: 19-20 October 2023 RabbitMQ Summit https://rabbitmqsummit.com: 20 October 2023
Erlang Solutions cares about your data and privacy; please find all details about the basis for communicating with you and the way we process your data in our Privacy Policy https://www.erlang-solutions.com/privacy-policy.html. You can update your email preferences or opt-out from receiving Marketing emails here. https://forms.erlangsolutions.com/email-preference?epc_hash=JtO6C7Q2rJwCdZxBx3Ad8jI2D4TJum7XcUWcgfjZ8YY
any news? this is still a problem.
Problem is fixed now, I have to regenerate the entire repo using a new pgp which is published.
Following instruction
Installation using repository
on https://www.erlang-solutions.com/downloads/ result in a unusable repo, the GPG signature used to sign repo is not the one downloadable at repo root.Can you please publish the missing signing public key?