Element-web: Riot-web installation error; repository does not have a stable release
Description
When I try to install riot-web in Ubuntu 18.04, using bionic distribution,
it gives the following error
E: The repository 'https://riot.im/packages/debian bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
Sumaid
All 10 comments
Following the instructions on https://riot.im/desktop.html on a fresh bionic install worked for me - @dbkr do you have any thoughts as to what might be going wrong?
lampholder
on 11 Jan 2019
@tejasvi Since you are seeing this as well, did you follow the instructions on https://riot.im/desktop.html?
jryans
on 11 Mar 2019
@jryans Yeah, I surely did.
tejasvi
on 12 Mar 2019
The package repository and https://riot.im/desktop.html seem to be 404 now. What's up with that?
lammas
on 13 Apr 2019
@lammas That would be because of https://matrix.org/blog/2019/04/11/security-incident/
turt2live
on 13 Apr 2019
Any update about this issue? I saw today a new version was released but i cannot install it because that
'E: The repository 'https://riot.im/packages/debian bionic Release' does not have a Release file.'
thanks
ecofintech
on 16 May 2019
@ecofintech the repository isn't riot.im/packages anymore, it is packages.riot.im,
https://packages.riot.im/debian/dists/bionic/Release
so you'd want
https://packages.riot.im/debian bionic Release
t3chguy
on 16 May 2019
I don't know if this helps some others having this issue, but I'm running Linux Mint 19 (Tara) and ran into the same error. I was using the exact commands on the site for desktop. However, because I'm using Mint instead of straight up Ubuntu or Debian the lsb_release -cs command returned tara instead of bionic which messed up the link to the repo. I replaced the $(lsb_release -cs) in the echo command with bionic and it worked.
So for those having the same problem and come across this issue, you may want to run lsb_release -cs in your terminal and make sure that the distro coming out matches one of the ones here. If it doesn't match, then manually replace it in the echo command.
This might be something to be noted on the desktop download instructions page.
gen1e
on 21 May 2019
This might be something to be noted on the desktop download instructions page.
Definitely. It would not take that long to make that change and it would save every Mint user time.
LinuxOnTheDesktop
on 31 Mar 2020
The original issue likely caused by a 32 bit system where 32 bit Electron is no longer supported. https://www.electronjs.org/blog/linux-32bit-support
The mint issues will be solved by https://github.com/vector-im/riot-web/issues/13367
t3chguy
on 24 Apr 2020
Related issues
lukebarnard1
·
3Comments
t3chguy
·
3Comments
anoadragon453
·
3Comments
turt2live
·
3Comments
richvdh
·
3Comments
Most helpful comment
I don't know if this helps some others having this issue, but I'm running Linux Mint 19 (Tara) and ran into the same error. I was using the exact commands on the site for desktop. However, because I'm using Mint instead of straight up Ubuntu or Debian the
lsb_release -cscommand returnedtarainstead ofbionicwhich messed up the link to the repo. I replaced the$(lsb_release -cs)in the echo command withbionicand it worked.So for those having the same problem and come across this issue, you may want to run
lsb_release -csin your terminal and make sure that the distro coming out matches one of the ones here. If it doesn't match, then manually replace it in the echo command.This might be something to be noted on the desktop download instructions page.