package source for Debian 11 ("Bullseye") not working

[stefanux]

There is no working repository for Debian 11 ("Bullseye"), error is:

E: The repository 'https://packagecloud.io/Keymetrics/pm2/debian bullseye Release' does not have a Release file.

source.file:

deb [signed-by=/etc/apt/keyrings/Keymetrics_pm2-archive-keyring.gpg] https://packagecloud.io/Keymetrics/pm2/debian/ bullseye main
deb-src [signed-by=/etc/apt/keyrings/Keymetrics_pm2-archive-keyring.gpg] https://packagecloud.io/Keymetrics/pm2/debian/ bullseye main

created from shellscript:

apt update && apt install sudo curl && curl -sL https://raw.githubusercontent.com/Unitech/pm2/master/packager/setup.deb.sh | sudo -E bash -

BTW: the shellscript does not handle errors (apt-get update) with set -eo pipefail so it show no errors because output (AND error output) is sent to /dev/null .

[robiXxu]

Hello. I get the same thing

Ign:7 https://packagecloud.io/Keymetrics/pm2/debian bullseye InRelease
Err:8 https://packagecloud.io/Keymetrics/pm2/debian bullseye Release
  404  Not Found [IP: 54.193.48.245 443]
Reading package lists... Done
E: The repository 'https://packagecloud.io/Keymetrics/pm2/debian bullseye Release' does not have a Release file.

I ended up installing it with npm

[kabili207]

It doesn't look like the debian packages in packagecloud have been updated for the past four years

[kiritokatklian]

Tried updating packages today and got the same error

[9021007]

issue still occurring

[SannanOfficial]

Can confirm that I have the same error but on Debian 12:

E: The repository 'https://packagecloud.io/Keymetrics/pm2/debian bookworm 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. W: http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

Any idea on how to fix?

[SannanOfficial]

Ignore the ubuntu stuff in the error message. That is because I accidentally added a few ubuntu keys, will be removing them, but they aren't relevant to this particular error.

[SannanOfficial]

For now, I just removed the repo altogether by doing: sudo rm -rf /etc/apt/sources.list.d/Keymetrics_pm2.list And then did my pm2 install with npm. But of course, this isn't really an ideal solution.