Produce .deb packages

Offen
#268 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@kpanuragh arbeitet bereits daran.

Seit 13.11.2026.

  • #272 von @kpanuragh — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
debian, rust, ubuntu

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Rust
Sterne
310
Forks
22
Ø Merge
1 T. 15 Std.
Gemergte PRs (30 T.)
13

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus linux-credentials/credentialsd

Alle Issues in linux-credentials/credentialsd

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.