Debian packaging - Revision history

Ardumont: Install redirection to the docs page

2021-10-27T07:55:09Z

Install redirection to the docs page

NicolasDandrimont: Drop the dirty chroot suggestion

2021-09-01T12:21:11Z

Drop the dirty chroot suggestion

← Older revision		Revision as of 12:21, 1 September 2021
Line 342:		Line 342:

	tmpfs /var/lib/schroot/union/overlay tmpfs uid=root,gid=root,mode=0750,nr_inodes=0 0 0		tmpfs /var/lib/schroot/union/overlay tmpfs uid=root,gid=root,mode=0750,nr_inodes=0 0 0

	~~=== Base packages ===~~

	~~In order not to reinstall the same packages every time, it is also reasonable to install debhelper, python3 and python3-all in the chroot.~~

	~~'''If you do so, do not use these chroots to upload to Debian itself!'''~~


	[[Category:Software development]]		[[Category:Software development]]
	[[Category:System administration]]		[[Category:System administration]]

Ardumont: Replace stretch reference to buster where it makes sense

2021-03-15T14:11:39Z

Replace stretch reference to buster where it makes sense

← Older revision		Revision as of 14:11, 15 March 2021
Line 39:		Line 39:
	Our debian packaging Jenkins jobs expect the following branches, which are pretty close to what https://dep-team.pages.debian.net/deps/dep14/ mandates:		Our debian packaging Jenkins jobs expect the following branches, which are pretty close to what https://dep-team.pages.debian.net/deps/dep14/ mandates:
	* debian/upstream (history of unpacked upstream releases)		* debian/upstream (history of unpacked upstream releases)
	* debian/<suite> (history of the packaging of the given suite, e.g. unstable-swh, ~~stretch~~-swh)		* debian/<suite> (history of the packaging of the given suite, e.g. unstable-swh, buster-swh)
	* pristine-tar (data to regenerate upstream tarballs from a git export)		* pristine-tar (data to regenerate upstream tarballs from a git export)

Line 121:		Line 121:
	Checkout the new branch		Checkout the new branch
	git checkout debian/<version number>		git checkout debian/<version number>
	git checkout -b debian/~~stretch~~-swh		git checkout -b debian/buster-swh

	Update the gbp config to match the branch		Update the gbp config to match the branch
	sed -i s/unstable-swh/~~stretch~~-swh/ debian/gbp.conf		sed -i s/unstable-swh/buster-swh/ debian/gbp.conf

	Generate the initial backports entry. Use the current Debian version number (9 for stretch, 10 for buster, ...)		Generate the initial backports entry. Use the current Debian version number (9 for stretch, 10 for buster, ...)
	dch -l "~~~bpo9~~" -D ~~stretch~~-swh --force-distribution 'Rebuild for ~~stretch~~-swh'		dch -l "~bpo10" -D buster-swh --force-distribution 'Rebuild for buster-swh'

	You should then be able to try a local package build, and if that succeeds, to push the tag for Jenkins to autobuild.		You should then be able to try a local package build, and if that succeeds, to push the tag for Jenkins to autobuild.
Line 285:		Line 285:
	sudo sbuild-createchroot --include apt-transport-https,ca-certificates sid /srv/chroots/sid http://deb.debian.org/debian/		sudo sbuild-createchroot --include apt-transport-https,ca-certificates sid /srv/chroots/sid http://deb.debian.org/debian/

	# Create ~~stretch~~ chroot		# Create buster chroot
	sudo sbuild-createchroot --include apt-transport-https,ca-certificates ~~stretch~~ /srv/chroots/~~stretch~~ http://deb.debian.org/debian/		sudo sbuild-createchroot --include apt-transport-https,ca-certificates buster /srv/chroots/buster http://deb.debian.org/debian/


Line 309:		Line 309:
	aliases=unstable-amd64-sbuild,UNRELEASED-amd64-sbuild,unstable-swh-amd64-sbuild		aliases=unstable-amd64-sbuild,UNRELEASED-amd64-sbuild,unstable-swh-amd64-sbuild

	For ~~stretch~~:		For buster:
	aliases=~~stretch~~-swh-amd64-sbuild,~~stretch~~-backports-amd64-sbuild,~~stretch~~-backports-swh-amd64-sbuild		aliases=buster-swh-amd64-sbuild,buster-backports-amd64-sbuild,buster-backports-swh-amd64-sbuild

	==== dependencies cache ====		==== dependencies cache ====
Line 325:		Line 325:
	You should update your chroot environments once in a while (to avoid repeating over and over the same step during your package build):		You should update your chroot environments once in a while (to avoid repeating over and over the same step during your package build):

	sudo sbuild-update -udcar sid; sudo sbuild-update -udcar ~~stretch; sudo sbuild-update -ud jessie~~		sudo sbuild-update -udcar sid; sudo sbuild-update -udcar buster

	=== environment setup ===		=== environment setup ===

Ardumont: /* Bootstrapping a dependency packaging repository */

2021-03-10T11:22:51Z

Bootstrapping a dependency packaging repository

← Older revision		Revision as of 11:22, 10 March 2021
Line 104:		Line 104:

	You can then go on to try building the package.		You can then go on to try building the package.
			gbp buildpackage --git-builder='sbuild -As'
	gbp buildpackage --git-builder='sbuild -As'

	Once the package builds, if you want to check your package's conformance to Debian policy, you can run <tt>lintian</tt> on the changes:		Once the package builds, if you want to check your package's conformance to Debian policy, you can run <tt>lintian</tt> on the changes:

Ardumont: /* Bootstrapping a dependency packaging repository */

2021-03-10T11:22:12Z

Bootstrapping a dependency packaging repository

← Older revision		Revision as of 11:22, 10 March 2021
Line 103:		Line 103:
	git commit -m "Initial packaging for pytest-postgresql"		git commit -m "Initial packaging for pytest-postgresql"

	You can then go on to try building the package. Once the package builds, if you want to check your package's conformance to Debian policy, you can run <tt>lintian</tt> on the changes:		You can then go on to try building the package.

			gbp buildpackage --git-builder='sbuild -As'

			Once the package builds, if you want to check your package's conformance to Debian policy, you can run <tt>lintian</tt> on the changes:
	lintian -EI ../pytest-postgresql_1.3.4-1+swh1_amd64.changes		lintian -EI ../pytest-postgresql_1.3.4-1+swh1_amd64.changes

Ardumont: Update jenkins job template to match the current reality and add samples

2020-10-22T09:37:38Z

Update jenkins job template to match the current reality and add samples

@@ Line 165: / Line 165: @@
       display-name: <short-name>
       pkg: <source-name>
       jobs:
         - 'dependency-jobs-{name}'
 Use the regular review process to land your changes.

Ardumont: clarify the 2 types of post-receive hooks

2020-10-20T15:03:58Z

clarify the 2 types of post-receive hooks

← Older revision		Revision as of 15:03, 20 October 2020
Line 141:		Line 141:
	* Look up the path to the repository on the storage tab		* Look up the path to the repository on the storage tab

	You need to setup the post-receive hook for Jenkins to be able to trigger on tag pushes.		You need to setup the post-receive hook for Jenkins to be able to trigger on tag pushes
	ssh -p 2222 -t tate.internal.softwareheritage.org phabricator-setup-hook /srv/phabricator/repos/<repo-id> post-receive-~~debian-deps~~		ssh -p 2222 -t tate.internal.softwareheritage.org phabricator-setup-hook /srv/phabricator/repos/<repo-id> <post-receive-hook>

	Note: remember that access to tate is on port 2222.		Note:

			* there exists 2 types of <post-receive-hook>:
			** ''post-receive-swh-modules'' for swh modules developed by the team
			** ''post-receive-debian-deps'' for external modules packaged by the team
			* remember that access to tate is on port 2222.

	The repo ID can be found on the repo's "storage" property page on phabricator, typically		The repo ID can be found on the repo's "storage" property page on phabricator, typically

Douardda: /* Local package building */

2020-09-25T16:45:35Z

Local package building

← Older revision		Revision as of 16:45, 25 September 2020
Line 209:		Line 209:

	for example:		for example:
	gbp buildpackage --git-builder=sbuild -As --force-orig-source --extra-repository='deb [trusted=yes] https://debian.softwareheritage.org/ buster-swh main'		gbp buildpackage --git-builder=sbuild -As --no-clean-source --force-orig-source \
			--extra-repository='deb [trusted=yes] https://debian.softwareheritage.org/ buster-swh main'

	or if you need some third-party repository, say for cassandra:		or if you need some third-party repository, say for cassandra:
	gbp buildpackage --git-builder=sbuild -As --force-orig-source \		gbp buildpackage --git-builder=sbuild -As --no-clean-source --force-orig-source \
	--extra-repository='deb [trusted=yes] https://debian.softwareheritage.org/ buster-swh main' \		--extra-repository='deb [trusted=yes] https://debian.softwareheritage.org/ buster-swh main' \
	--extra-repository='deb [arch=amd64 trusted=yes] https://downloads.apache.org/cassandra/debian 40x main'		--extra-repository='deb [arch=amd64 trusted=yes] https://downloads.apache.org/cassandra/debian 40x main'

Ardumont: mention the port tidbit for tate...

2020-09-23T13:23:29Z

mention the port tidbit for tate...

← Older revision		Revision as of 13:23, 23 September 2020
Line 142:		Line 142:

	You need to setup the post-receive hook for Jenkins to be able to trigger on tag pushes.		You need to setup the post-receive hook for Jenkins to be able to trigger on tag pushes.
	ssh -t tate.internal.softwareheritage.org phabricator-setup-hook /srv/phabricator/repos/<repo-id> post-receive-debian-deps		ssh -p 2222 -t tate.internal.softwareheritage.org phabricator-setup-hook /srv/phabricator/repos/<repo-id> post-receive-debian-deps

	Note: remember that access to tate is on port 2222.		Note: remember that access to tate is on port 2222.

Douardda: /* Setting up the repository on Phabricator */

2020-09-23T13:23:19Z

Setting up the repository on Phabricator

← Older revision		Revision as of 13:23, 23 September 2020
Line 143:		Line 143:
	You need to setup the post-receive hook for Jenkins to be able to trigger on tag pushes.		You need to setup the post-receive hook for Jenkins to be able to trigger on tag pushes.
	ssh -t tate.internal.softwareheritage.org phabricator-setup-hook /srv/phabricator/repos/<repo-id> post-receive-debian-deps		ssh -t tate.internal.softwareheritage.org phabricator-setup-hook /srv/phabricator/repos/<repo-id> post-receive-debian-deps

			Note: remember that access to tate is on port 2222.

	The repo ID can be found on the repo's "storage" property page on phabricator, typically		The repo ID can be found on the repo's "storage" property page on phabricator, typically