package source for Debian 11 ("Bullseye") not working
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
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 .
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with packager/setup.deb.sh and reproduce the apt update failure using the Bullseye source entries shown in the issue. Check how the Debian 11 repository is published and how the script handles apt errors; done means Bullseye has a usable Release file and setup failures are reported instead of hidden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, shell
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100