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
分支
250
平均合併
3 天 55 分鐘
30 天內合併 PR
2

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

jamulussoftware/jamulus 的其他 Issue

查看 jamulussoftware/jamulus 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。