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 摘要。