Produce .deb packages

未關閉
#268 2 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

@kpanuragh 已經在處理了。

開始於 2026年11月13日。

  • #272 來自 @kpanuragh —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
debian, rust, ubuntu

研究方向

The payload names no source files. Start from the existing RPM spec files for Fedora and openSUSE and the AUR packaging, which the issue cites as references for what a Debian package definition should cover. Done means a debian/ packaging directory whose build produces a .deb with vendored Rust dependencies, which the maintainers have confirmed works. The open questions about Debian and Ubuntu repository rules need an answer from a maintainer before the work is finished.

由索引模型根據 Issue 內容生成。

描述

We have spec files written for RPM packages for Fedora and openSUSE, and there's community support for Arch in AUR, but we don't have anything for the .deb ecosystem for Debian/Ubuntu

It would be great if we could get this working for that ecosystem. We need to get it done before the Ubuntu feature freeze in February if we want to make it into the next release.

The released packages would probably wind up being built in openSUSE Build Service next to our other packages, but creating the package definition would be very helpful as starting point.

Some open questions:

  • We will need the build to support vendoring. Our build system does that already, but I don't know how different build systems integrate that for deb files.
  • I also don't know if there's any other rules we need to follow to get into the Debian or Ubuntu repositories.
主要語言
Rust
星號
310
分支
22
平均合併
1 天 15 小時
30 天內合併 PR
13

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

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

linux-credentials/credentialsd 的其他 Issue

查看 linux-credentials/credentialsd 的全部 Issue

相似的 Issue

更多 Rust Issue

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

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