From 556c3d13787071c91bc0a9514eee90f2f69eff1d Mon Sep 17 00:00:00 2001 From: "B. Stack" Date: Tue, 20 Feb 2024 21:56:10 -0500 Subject: tmdbv3api: add this package --- tmdbv3api/debian/source/format | 1 + tmdbv3api/debian/source/local-options | 4 ++++ tmdbv3api/debian/source/options | 4 ++++ tmdbv3api/debian/source/patch-header | 22 ++++++++++++++++++++++ 4 files changed, 31 insertions(+) create mode 100644 tmdbv3api/debian/source/format create mode 100644 tmdbv3api/debian/source/local-options create mode 100644 tmdbv3api/debian/source/options create mode 100644 tmdbv3api/debian/source/patch-header (limited to 'tmdbv3api/debian/source') diff --git a/tmdbv3api/debian/source/format b/tmdbv3api/debian/source/format new file mode 100644 index 0000000..163aaf8 --- /dev/null +++ b/tmdbv3api/debian/source/format @@ -0,0 +1 @@ +3.0 (quilt) diff --git a/tmdbv3api/debian/source/local-options b/tmdbv3api/debian/source/local-options new file mode 100644 index 0000000..77effbe --- /dev/null +++ b/tmdbv3api/debian/source/local-options @@ -0,0 +1,4 @@ +# +# ### gbp-buildpackage(1) user may like this. ### +#abort-on-upstream-changes +#unapply-patches diff --git a/tmdbv3api/debian/source/options b/tmdbv3api/debian/source/options new file mode 100644 index 0000000..077de7d --- /dev/null +++ b/tmdbv3api/debian/source/options @@ -0,0 +1,4 @@ +# +# ### dgit-maint-merge(7) workflow user need this ### +# single-debian-patch +# auto-commit diff --git a/tmdbv3api/debian/source/patch-header b/tmdbv3api/debian/source/patch-header new file mode 100644 index 0000000..6ff0a40 --- /dev/null +++ b/tmdbv3api/debian/source/patch-header @@ -0,0 +1,22 @@ +The automatically generated patch puts this free form text on top of it. + +If you are using gbp-buildpackage(1), you probably don't need this file. + +If you are using dgit-maint-merge(7), please consider text as follows. + +The Debian packaging of foo is maintained in git, using the merging workflow +described in dgit-maint-merge(7). There isn't a patch queue that can be +represented as a quilt series. + +A detailed breakdown of the changes is available from their canonical +representation - git commits in the packaging repository. For example, to see +the changes made by the Debian maintainer in the first upload of upstream +version 1.2.3, you could use: + + % git clone https://git.dgit.debian.org/foo + % cd foo + % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' + +(If you have dgit, use `dgit clone foo`, rather than plain `git clone`.) + +A single combined diff, containing all the changes, follows. -- cgit