A core group is still OK from a database point of view, but totally missing from SaaS configuration.

@Sandlayth We still need to check if we can save the permissions for the users not having logged in and modified stuff by recreating a tar archive perhaps.

yeah is ready :) thanks

You've also to probably recompile the eggdrop: the new server is x64, not ARM.

rashk0@eglide:~$

The authenticity of host 'eglide.org (2001:bc8:1200:511a::1)' can't be established.
ECDSA key fingerprint is 8d:5d:04:90:df:e7:2b:56:3b:ac:62:a9:81:58:3f:15.
Are you sure you want to continue connecting (yes/no)?
Host key verification failed.

Expected, as we've changed the server machine, so the keys.

GitHub repository requires authentication, https://verdaccio.org/docs/cli-registry gives solution to prepare a private registry.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ECDSA host key for eglide.org has changed,
and the key for the corresponding IP address 2001:bc8:1200:511a::1
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
8d:5d:04:90:df:e7:2b:56:3b:ac:62:a9:81:58:3f:15.
Please contact your system administrator.
Add correct host key in /home/campari/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/campari/.ssh/known_hosts:19
ECDSA host key for eglide.org has changed and you have requested strict checking.
Host key verification failed.

As a temporary solution to fix Spectacle, I've upgraded the dependencies [1] and published a package to GitHub packages repository [2].

I see 3 entries in the auth log:

Actually, the issue is stranger, there is a mix of user and root files.

I suspect a permission issue when transferring the /home directories from the old machine to the new machine.

Let's track this in T1663.

can you help me ..?

Can't login either. Seems we've an issue with ssh config.

EOF for package.json

Document the change

Chain commands

Rebased

Reverted to requirements.txt only