What type of hardware are you using : VPS bought online
What YunoHost version are you running : current
What app is this about : sharkey
Describe your issue
I reset the vps, reinstalled debian 12 and reinstalled yunohost, now I can’t install sharkey without issue, tried resetting again and it didn’t help.
Share relevant logs or error messages
https://paste.yunohost.org/raw/abepokemun
Tried the test branch from github too, still doesn’t work.
emo
February 6, 2025, 12:17pm
3
hi, the underlying problem imho is a problem in yarn, matching the lately problems in linkwarden and joplin too.
here is the diskussion:
opened 07:27AM - 03 Feb 25 UTC
## Issue
New releases of [pnpm](https://github.com/pnpm/pnpm/releases) and [npm… ](https://github.com/npm/cli/releases) signed with the new npm `"keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"` published to https://registry.npmjs.org/-/npm/v1/keys cannot be installed with the version of Corepack currently distributed with Node.js LTS versions without using workarounds.
For instance,
```shell
corepack install -g pnpm@9
```
executed using Node.js [22.13.1](https://github.com/nodejs/node/releases/tag/v22.13.1) Active LTS (with bundled [corepack@0.30.0](https://github.com/nodejs/corepack/releases/tag/v0.30.0)) on Ubuntu `24.04.1` LTS results in the error "Cannot find matching keyid":
```text
$ corepack install -g pnpm@9
Installing pnpm@9.15.5...
Internal Error: Cannot find matching keyid: {"signatures":[{"sig":"MEQCIHGqHbvc2zImUPEPFpT4grh6rMYslel+lAjFArx8+RUdAiBfnJA+bgmUvO5Lctfkq+46KKDQdx/8RhLPge3pA+EdHA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"keys":[{"expires":null,"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg=="}]}
```
The same problem can be expected to affect any new releases of [Yarn Modern aka berry](https://github.com/yarnpkg/berry/releases). [Yarn v1 Classic](https://github.com/yarnpkg/yarn) is frozen, but could also be affected if security fixes are released.
## Request
Please clarify if minimum [corepack@0.31.0](https://github.com/nodejs/corepack/releases/tag/v0.31.0) will be rolled out to Node.js Maintenance and Active LTS status versions `18.x`, `20.x` and `22.x`.
*Note: [corepack@0.31.0](https://github.com/nodejs/corepack/releases/tag/v0.31.0) is already rolled out in the Current [Node.js 23.7.0](https://github.com/nodejs/node/releases/tag/v23.7.0) version.*
## Related
- #612
- #616
## Workaround
In some situations it is possible to follow the [README > Manual Installs](https://github.com/nodejs/corepack/blob/main/README.md#manual-installs) section and execute the following to pull in a corrected version of Corepack with updated keys from https://registry.npmjs.org/-/npm/v1/keys:
```shell
npm install -g corepack@0.31.0
```
there is a workaround, i did not test (I don’t want to break anything that I don’t understand enough about) but i hope a ynh dev will know what to do.
1 Like
Has anyone been able to install it? I tried to start a new thread to ask but it gets moved to invalid, this one was apparently fine. Workaround either doesn’t work, or I did it wrong.
wbk
February 10, 2025, 8:45pm
5
Hi dilroopgill,
I saw your post before it got moved, and noticed it was thin on details, although, in your defence, you didn’t ask for help but only asked if anyone was able to install it.
A while back I looked into the *key-versions, they all seem quite demanding apps under heavy development, which may explain difficulties creating an installer that works all the time.
Late last year there was another thread regarding Sharkey that got solved. That won’t help you with the yarn
-error, but maybe it is helpful once you tried the workaround for that.
brooksl
February 10, 2025, 10:07pm
6
Same error here, install fails
Internal Error: Cannot find matching keyid: {"signatures"
https://paste.yunohost.org/raw/bipumexeka
That error seems unrelated, someone somewhere is likely working on a fix lol, I just was hoping someone more technically inclined here knew of any info