Debian Packaging Workflow - Revision history

Markusblatt: /* Building the package */

2022-03-30T19:42:00Z

Building the package

2022-03-30T19:32:20Z

Performing builds using locally built packages

2022-03-30T19:31:53Z

Additional setup instructions

2022-03-30T19:31:38Z

Additional setup instructions

2022-03-30T19:31:00Z

Import a pre-release version using an upstream git commit or tag

2022-03-30T19:29:31Z

Import a pre-release version using an upstream git commit

2022-03-30T19:29:06Z

Import a prerelease version using an upstream git commit

2022-03-30T19:28:49Z

repository management with git-buildpackage

2022-03-30T19:28:25Z

Repositories on Salsa

2022-03-30T15:31:28Z

Notes on Maintaining the Debian Packages

← Older revision		Revision as of 19:42, 30 March 2022
Line 108:		Line 108:
	DEPS=opm-sid gbp buildpackage --git-ignore-new \		DEPS=opm-sid gbp buildpackage --git-ignore-new \
	--git-export-dir=../build-area-pbuilder-sid --git-pbuilder		--git-export-dir=../build-area-pbuilder-sid --git-pbuilder
		+
		+	=== Finishing touches and uploading of the release ===
		+
		+	* Update debian/changelog: <code>gbp dch</code>
		+	* Polish debian/changelog.
		+	* push changes, e.g. by <code>gbp push</code>
		+	* Ask Markus (he is a Debian Maintainer) to upload the release
		+
		+	The uploader should:
		+	* Test the package build
		+	* Release debian/changelog: <code>dch -r</code>
		+	* Tag the release: <code>gbp tag --sign-tags</code>
		+	* Push the changes: <code>gbp push</code>

@@ Line 97: / Line 97: @@
       export DEPSBASE=/var/cache/pbuilder/deps
       BINDMOUNTS=$DEPSBASE
-      BUILDRESULT=$DEPSbase/$DEPS
+      #BUILDRESULT=$DEPSbase/$DEPS
   else
-      BUILDRESULT=/var/cache/pbuilder/result
+      #BUILDRESULT=/var/cache/pbuilder/result
   fi

@@ Line 66: / Line 66: @@
   # the hook dir may already be set/populated!
   HOOKDIR="$HOME/.pbuilder/hooks/"
-and create that dorectory if it is not present
+and create that directory if it is not present
 ==== Running autopkgtest ====

@@ Line 66: / Line 66: @@
   # the hook dir may already be set/populated!
   HOOKDIR="$HOME/.pbuilder/hooks/"
 ==== Running autopkgtest ====

@@ Line 55: / Line 55: @@
   dch --newversion $VERSION
-Doing it this way will make sure that branch upstream contains the complete upstream git history. Note that one could also use a git tag instead of a git commit hash instead.
+Doing it this way will make sure that the branch upstream contains the complete upstream git history. Note that one could also use a git tag instead of a git commit hash instead. Note. that the version includes the date of the commit to make the order of the releases sensible.
 == Building the packages in a chroot using cowbuilder ==

@@ Line 40: / Line 40: @@
 * Do further work on the package.
-==== Import a pre-release version using an upstream git commit ====
+==== Import a pre-release version using an upstream git commit or tag ====
 Instead of importing the new version using uscan as above, you manually create a tarball based on a git checkout of upstream.

@@ Line 19: / Line 19: @@
 ==== repository management with git-buildpackage ====
-* To clone a repository please use gbp use e.g.: <code>gbp clone https://salsa.debian.org/science-team/opm-common</code>
+* To clone a repository please use gbp use e.g.: <code>gbp clone https://salsa.debian.org/science-team/opm-common</code>. This  will clone the repository with the three banches master (Where the debian packaging effort is), upstream (The upstream repository as of the last release that was imported), and pristine-tar (The branch holding the deltas for reconstructing the original tarball).
 * To download the recent changes to the packaging effort from other do <code>gbp pull</code>
 * To upload your recent changes (to all relevant branches) use <code>gbp push</code>

@@ Line 5: / Line 5: @@
 === Repositories on Salsa ===
-For each module there is a corresponding repository on sala. These are:
+For each module there is a corresponding repository on [https://salsa.debian.org salsa]. These are:
 * [https://salsa.debian.org/science-team/opm-common https://salsa.debian.org/science-team/opm-common]
 * [https://salsa.debian.org/science-team/opm-material https://salsa.debian.org/science-team/opm-material]
@@ Line 14: / Line 14: @@
 The packaging effort uses [https://honk.sigxcpu.org/piki/projects/git-buildpackage/ git-buildpackage] as the main tool and bases the packaging on release tarballs and quilt for patching the upstream versions found in OPM's git repositories.
 === git-buildpackage instruction ===

@@ Line 33: / Line 33: @@
 * make sure the patch-queue branch is up to date
 * update upstream: <code>git fetch upstream</code>
-* update necessary branches from debian repo (in case of changes from others): gbp pull
+* update necessary branches from debian repo (in case of changes from others): <code>gbp pull</code>
 * import new version: <code>gbp import-orig --uscan</code>
 * rebase patch queue: <code>gbp pq rebase</code>
 * resolve conflicts, etc.
 * export the patch queue: <code>gbp pq export --commit</code>
 * change the commit message to something more meaningful
 ==== Import a prerelease version using an upstream git commit ====
@@ Line 53: / Line 55: @@
   git checkout master # branch with the debian packaging
   gbp import-orig --upstream-vcs-tag=$TAG ../$PREFIX.orig.tar.gz
 Doing it this way will make sure that branch upstream contains the complete upstream git history. Note that one could also use a git tag instead of a git commit hash instead.