[08:26:25]
<yalh76> > <@rodinux07:matrix.org> hello, I had found an issue with the smtp on mobilizon and resolve it, did you seen it yalh76 ? https://github.com/YunoHost-Apps/mobilizon_ynh/pull/153
Nope, I wasn't very available lately, I will look at that this week-end
[14:07:26]
<Rosbeef Andino 🐧> i tried with other users on my selfhoster server and it does not work too. maybe i should ask directly on matrix forum.
[15:21:00]
<tituspijean> Rosbeef Andino 🐧: you should check the logs of your server, they should contain information on what happens here
[17:31:58]
<Memo> I tried to upgrade some changes with dependencies with Misskey on a local test installation, but got an access error:
2022-12-08 16:23:11,514: DEBUG - + sudo -u misskey env PATH=/opt/node_n/n/versions/node/18.0.0/bin:/opt/node_n/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin corepack enable
2022-12-08 16:23:11,615: DEBUG - Internal Error: EACCES: permission denied, symlink '../lib/node_modules/corepack/dist/pnpm.js' -> '/opt/node_n/n/versions/node/18.0.0/bin/pnpm'
2022-12-08 16:23:11,615: DEBUG - Error: EACCES: permission denied, symlink '../lib/node_modules/corepack/dist/pnpm.js' -> '/opt/node_n/n/versions/node/18.0.0/bin/pnpm'
https://paste.yunohost.org/raw/fovojowoga
Any help is appreciated.
[17:32:02]
<Aleks (he/him/il/lui)> but that's a relative path and dunno what's the cwd in that context
[17:32:02]
<Aleks (he/him/il/lui)> sounds like a permission issue
[17:32:02]
<Memo> I did only some small changes in scripts to prepare for the next update with node.js 18 and yarn berry:
https://github.com/YunoHost-Apps/misskey_ynh/pull/135
[17:32:02]
<Aleks (he/him/il/lui)> naively I would say that `misskey` cant write /opt/node_n/n/versions/node/18.0.0/bin/pnpm ... or is it the other way around, it tries to create the symlink as '../lib/node_modules/corepack/dist/pnpm.js?
[17:32:06]
<Aleks (he/him/il/lui)> and what makes me say this is that apparently it tries to install pnpm inside nvm ...
[17:32:06]
<Aleks (he/him/il/lui)> i dunno what `corepack enable` does because i have little clue about all the whole npm stories, but sounds too me like it's yet another stuff of bloated web technologies where tools are piled-up on top of each other each time to supposedly "help" while at the same time adding yet another layer of complexity ...
[17:32:06]
<Memo> Can this be because both are not backwards compatible and therefore do not work with the current version of Misskey?
[17:32:06]
<Aleks (he/him/il/lui)> adding 3 new npm/yarn/whatever call sounds like not-that-small-changes territory ;P
[17:32:10]
<Aleks (he/him/il/lui)> honestly if the current (or rather previous) way of installing yarn is not broken, I would stick with it
[17:32:10]
<Aleks (he/him/il/lui)> yeah i know
[17:32:10]
<Memo> I just tried to integrate the instructions in the changelog for the next version:
https://github.com/misskey-dev/misskey/blob/develop/CHANGELOG.md
[17:32:10]
<Aleks (he/him/il/lui)> i'm so tired of that nodejs crap
[17:32:10]
<Aleks (he/him/il/lui)> « Corepack is an experimental tool to help with managing versions of your package managers. »
[17:32:10]
<Aleks (he/him/il/lui)> oh god
[17:32:10]
<Aleks (he/him/il/lui)> ah so like it's supposed to install yarn
[17:32:10]
<Aleks (he/him/il/lui)> djeezus fukin christ
[17:32:14]
<Memo> I guess the new update will be out this weekend, so I'll try it that way first - Thanks Aleks
[17:32:14]
<Aleks (he/him/il/lui)> hmmm yup
[17:32:14]
<Memo> ok, so just node.js 18 ?
[19:40:53]
<Memo> BTW: it IS a permission issue, because `'corepack enable'` has to be run with `'sudo'` and not as `misskey` user.
However, I don't know how to call this in the upgrade / install script `¯\_(ツ)_/¯`
[19:42:26]
<Memo> As you can see, this gives me no rest 😉
[19:43:18]
<Aleks (he/him/il/lui)> but again do we really need it ...
[19:47:23]
<Memo> That's something I don't really know at all.
I'm not a developer either, and I can't judge whether this is necessary to run the app or not.
[19:49:23]
<Memo> I also wonder if it's not necessary why the devs put it in the changelog.
[19:51:44]
<Aleks (he/him/il/lui)> because maybe that's the recommendation for easier development/deployment because supposedly this tool takes care of installing yarn for you independently of which distro you're on
[19:52:04]
<Aleks (he/him/il/lui)> but we already know which distro we're on and installing yarn with apt does work and is already implemented
[19:52:32]
<Aleks (he/him/il/lui)> at least that's my rough guess, maybe it does important stuff and doesn't just install yarn
[19:57:58]
<Memo> Yes, may be, but this is unfortunately far beyond my knowledge.
[19:59:03]
<Memo> how ever - I won't worry about it for now