Skip to content

Workflow choice for novice user

Let me summarize high level questions.

WORKFLOW

Is this right order of steps?

FOCUS

  • basic workflow without git
  • basic workflow with patch-unapplied git
  • gbp/debsign/dput workflow with patch-unapplied git
  • sbuild/dgit workflow with patch-applied+auto-commit

NON-FOCUS

  • dgit-maint-debrebase exposure should be limited

GPG key

  • Correct key usage is ~/.devscripts configuration issue (not debsign usage issue)
    • I used to worry to use my old RSA1024-key over Debian keyring registered one.
    • I am now worried not to use my newer Ed25519-key prematurely

My question is: Should we need to address this is README? Maybe main text is the right place.

salsa-ci

Q1: Which is the best generic template content?

---
include:
 - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml`

or

---
include:
  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml

Q2: how to deal salsa-ci for (quasi-)native package like this debmake-doc without separate upstream?

Q3: What kind of exra comment to be added in template salsa-ci.yml generated by debmake?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information