Skip to content
Snippets Groups Projects

doc: git-dpm to gbp

Merged Yao Wei (魏銘廷) requested to merge mwei/python-modules:policy/gbp into master
1 unresolved thread

(Sorry, I found no way to send merge request compared against previous merge request)

Merge request reports

Merged by Dmitry ShachnevDmitry Shachnev 6 years ago (Mar 16, 2019 6:35pm UTC)

Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
127 126 and document them in ``debian/README.source``.
128 127
129 128
130 Tag format
131 ----------
132 129
133 Use the following ``git-dpm`` tag formats for the three branches named above.
134 These lines at the *end* of the ``debian/.git-dpm`` file will ensure the
135 correct tag format for the repository::
130 Configurations
  • I think we need discussion about this. For example in OpenStack team we removed d/gbp.conf file completely.

    please remove it for now, thanks.

  • If we keep the debian/master branch naming convention we need a gbp.conf file. You also need it as soon as you're making a backport on a branch that's anything else than master.

    Finally, if your package uses pristine-tar, you really should have that set in gbp.conf or you'll get some fun results with the default gbp-buildpackage settings recreating the tarball from a git archive, and getting yelled at by the archive for having a different orig tarball. This is all the more so annoying for "drive-by" uploads by team members. I think mandating the use of pristine-tar is a sensible default.

  • Please register or sign in to reply
  • added 1 commit

    • 872355b1 - remove "At the time of writing"

    Compare with previous version

  • Dmitry Shachnev mentioned in commit 7043b5ac

    mentioned in commit 7043b5ac

  • Please register or sign in to reply
    Loading