Produce .deb packages

Aberta
#268 2 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

@kpanuragh já está trabalhando nisso.

Desde 13/11/2026.

  • #272 de @kpanuragh — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
38/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
debian, rust, ubuntu
Domínio
build-system, release

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Rust
Estrelas
310
Forks
22
Merge médio
1d 15h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de linux-credentials/credentialsd

Todas as issues de linux-credentials/credentialsd

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.