Err:10 http://packages.prosody.im/debian aramo Release
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
I am trying to update Aramo on a shared server (a.k.a. "VPS") running an instance of Jitsi-meet, so with Prosody installed[1], but I am having an issue:
root@redacted_name:~# apt update
Hit:1 http://archive.trisquel.info/trisquel aramo InRelease
Get:2 http://archive.trisquel.info/trisquel aramo-updates InRelease [13.9 kB]
Get:3 http://archive.trisquel.info/trisquel aramo-security InRelease [13.8 kB]
Get:4 http://archive.trisquel.info/trisquel aramo-updates/main Sources [729 kB]
Get:5 http://archive.trisquel.info/trisquel aramo-updates/main amd64 Packages [1,902 kB]
Get:6 http://archive.trisquel.info/trisquel aramo-security/main Sources [307 kB]
Get:7 https://download.jitsi.org stable/ InRelease [1,682 B]
Get:8 http://archive.trisquel.info/trisquel aramo-security/main amd64 Packages [1,168 kB]
Ign:9 http://packages.prosody.im/debian aramo InRelease
Err:10 http://packages.prosody.im/debian aramo Release
404 Not Found [IP: 46.43.15.35 80]
Get:11 https://download.jitsi.org stable/ Packages [86.0 kB]
Reading package lists... Done
E: The repository 'http://packages.prosody.im/debian aramo Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I first opened an issue on the repository of Prosody[1] and a contributor suggested I add the line: deb https://packages.prosody.im/debian jammy main to "apt source config" which I understand is this file: /etc/apt/sources.list
However, as I am now about to add 'deb https://packages.prosody.im/debian jammy main' to /etc/apt/sources.list, I am wondering whether it's wise to ask Trisquel to fetch a package from jammy (if that's what this line does - I am not sure.)
Does someone have an idea of what this error is about?
[1] https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart#add-the-prosody-package-repository
[2] https://issues.prosody.im/1829
To get any package from https://packages.prosody.im/debian/ you have to trust whoever administrates that repository to not host (or add in the future) proprietary software or even malware (possibly hidden in the precompiled prosody package). Here it apparently means trusting the Prosody project itself, the repository bearing its domain name.
The repository has no section tailored to Trisquel, i.e., using its version names, such as "aramo". That is the reason for the error. Trisquel 11 Aramo is based on Ubuntu 22.04 Jammy Jellyfish. That is why you were suggested to replace "aramo" with "jammy": the packages built for Ubuntu 22.04 should perfectly work on Trisquel 11.
Notice that the Trisquel project does not modify the prosody source package it fetches from Ubuntu, hence an indication that there is no freedom issue with it. At least in the version Trisquel 11 currently ships. But there is little reason to fear that freedom issues have been introduced since then.
Thank you for taking the time to write up this train of thought. That's helpful. I added the line mentioned above in the apt source config file, which helped move on. However, '$ sudo apt update' still produced an error which I was able to fix and finally update Trisquel by editing a config file ; see: https://community.jitsi.org/t/unable-to-load-module-roster-command-usr-lib-prosody-modules-share-lua-5-2-mod-roster-command-mod-roster-command-lua-no-such-file-or-directory.... Now, I still have an issue. After the update, Jitsi no longer runs. There is an 'host-unknown' xmpp error in one of the log. Anyway. I am carrying on the conversation there https://community.jitsi.org/t/error-xmpp-host-unknown-after-distribution-update/128341/1 - if someone ever has the same issue while updating an instance of Jitsi.
Thanks again, Magic Banana.
I am a translator!
I installed Jitsi on aramo following the instructions at https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart, it worked fine and it does not use any repository from prosody.
I locked the creation of rooms and created an xmpp account to be used to create a room.
I cannot check or test something now though, because my desktop is currently out-of-order (need to replace cooling).
Did you install Jitsi following the "manual installation" guide?
> Did you install Jitsi following the "manual installation" guide?
Yes, I did and the instance was working fine *before* I updated the Aramo.
Updating messed up Jitsi-meet.
That said: the instance of Jitsi-meet I run is working again now. It seems that
all I did was to add 'Include "conf.d/*.cfg.lua"' at the end of
/etc/prosody/prosody.cfg.lua (but that did not help immediately, maybe I had
omitted to run systemctl restart prosody).
> I locked the creation of rooms and created an xmpp account to be used to
> create a room.
I am not sure I understand that bit. Does that mean that rooms cannot be created
freely on the instance you set up but that one needs xmpp credentials to
create a room ?
If that is it, I think I am okay with mine being freely available, a bunch of
people use it and I don't mind if others do. That's why I also thought I might
not need prosody since I don't think I use the "lobby feature" nor restrict
access/nor create users.
> it worked fine and it does not use any repository from prosody.
Next time I will skip adding the prosody repository. Thank you for mentioning
this.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires