Update outdated deb installer to deb822

未关闭
#3,975 3 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
57/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
bash, linux, shell, ubuntu
领域
cli, devops

调研方向

The issue does not name the installer script, so first locate the Jamulus Debian repository setup script and read how it currently writes the APT source and installs the signing key. Check the linked Syncthing discussion for the key storage choice before making a change. Done when the installer uses a deb822 .sources file with a matching Signed-By key path and apt update no longer reports the missing-key warning.

由索引模型根据 Issue 内容生成。

描述

good first issue needs documentation tooling

Describe the bug

apt update/upgrade warns
To Reproduce

Expected behavior
clean

Comply with not-so-new apt deb822 format
Screenshots

sudo apt update
...
Tous les paquets sont à jour.
N: Il manque « Signed-By » dans l'entrée sources.list(5) pour « https://github.com/jamulussoftware/jamulus/releases/latest/download »

Operating system

Ubuntu 24.04
Version of Jamulus

3.12.5
Additional context
New value for $REPO_FILE
Decision should be made where to store the key ($KEY_FILE), /etc/apt/trusted.gpg.d/ or /usr/share/keyrings/
Discussion here : https://github.com/syncthing/syncthing/issues/10495

The script should be updated to something like that:

...
REPO_FILE=/etc/apt/sources.list.d/jamulus.sources
KEY_FILE=/etc/apt/trusted.gpg.d/jamulus.asc
GITHUB_REPOSITORY="jamulussoftware/jamulus"

echo "Setting up Jamulus repo at ${REPO_FILE}..."
echo "Types: deb" > ${REPO_FILE}
echo "URIs: https://github.com/${GITHUB_REPOSITORY}/releases/latest/download/" >> ${REPO_FILE}
echo "Suites: ./" >> ${REPO_FILE}
echo "Components: " >> ${REPO_FILE}
echo "Signed-By: " ${KEY_FILE}" >> ${REPO_FILE}
echo "Installing Jamulus GPG key at ${KEY_FILE}..."
curl --fail --show-error -sLo "${KEY_FILE}" https://github.com/${GITHUB_REPOSITORY}/releases/latest/download/key.asc
...
主要语言
C
星标
1.1k
派生
251
平均合并
5 天 1 小时
30 天内合并 PR
1

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

jamulussoftware/jamulus 的其他 Issue

查看 jamulussoftware/jamulus 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。