Comment: Add some troubleshooting.
apt install is more modern
|Deletions are marked like this.||Additions are marked like this.|
|Line 5:||Line 5:|
|sudo apt-get install debhelper dh-make git git-buildpackage lintian||sudo apt install debhelper dh-make git git-buildpackage lintian|
|Line 44:||Line 44:|
|sudo dpkg --install ../hello_1.2.3-1_all.deb||sudo apt install ../hello_1.2.3-1_all.deb|
This small tutorial shows steps I would take to prepare packaging for most of the source packages. For the example hypothetical source package hello of version 1.2.3 is used.
sudo apt install debhelper dh-make git git-buildpackage lintian
Ensure the source package is DFSG-compatible (free software). Non-free source and binary packages will not enter Debian main.
- Create a packaging Git repository named after the source package:
git init hello cd hello
- Import the source package from URL:
gbp import-orig --pristine-tar https://example.org/hello.tar.gz
gbp will ask some questions, but these are trivial to answer.
Use dh_make to prepare packaging scaffold under debian/ directory. Source package name and its version has to be provided via --packagename option:
dh_make --packagename hello_1.2.3
Remove unneeded files from under debian/. Most of the files ending in .ex are not mandatory and could be added later if needed. Add debian/ and commit:
git add debian git commit
- Build the package:
gbp buildpackage -uc -us
- If the build fails, inspect the reasons of failure. Sometimes turning on the verbose mode in debian/rules helps. Repeat the build-fix-build cycle until successful build is achieved.
- Inspect the built binary packages. Check the contents, ensure everything is installed into the expected locations:
dpkg --contents ../hello_1.2.3-1_all.debCheck the dependencies and other relationships with other packages:
dpkg --info ../hello_1.2.3-1_all.debInstall the package and try using it:
sudo apt install ../hello_1.2.3-1_all.deb
Inspect lintian messages. gbp buildpackage runs lintian after successful builds (if lintian is installed). Make sure the package is clean of both errors and warnings, although some warnings may be justified.
To make sure the package will build on buildds, build it for clean Debian Unstable with only the essential packages, possibly by using sbuild.
(Optional) Add autopkgtest.
- Upload/ask for sponsorship.
Some dependencies are not in Debian yet: Package them or ask someone to do so. All build dependencies have to be packaged.
Non-essential files in the source package are not DFSG-compatible: Repack the source to exclude them.
Package build downloads files from the network: This must not be done.