pingcap / pingcap/failpoint

Does upstream want to have Debian packaging?

Open
#89 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
895
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Hi,

I've packaged this for Debian and got it included in Debian officially, and by extension also Ubuntu:

https://tracker.debian.org/pkg/golang-github-pingcap-failpoint

https://launchpad.net/ubuntu/+source/golang-github-pingcap-failpoint

Are you here at upstream interested in having this debian/ subdirectory and the packaging? If yes, I can file a PR to submit it.

You can use it to generate .deb packages directly at upstream, or for example include the .deb generation it in the CI to be able to detect if any changes in upstream failpoint are incompatible with Debian and breaks the package.

CC: @dveeden

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the linked Debian Tracker and Launchpad package pages, then inspect the proposed debian/ subdirectory scope. First confirm that upstream wants to carry Debian packaging and whether CI integration is included; done means the maintainer-approved packaging and any requested compatibility check are defined and accepted.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, go
Domain
build-system, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.