dunetna

Recipe under construction

monica@undisclosed.example.com (monica) — Sun, 11 Jun 2017 22:57:58 +0000

Creating a new package with git

Description: Basic steps to create a new package with git. This page does not pretend to b a packging tutorial.

Language(s): English

Download the upstream package. Repack it if it is needed. Suppose you have a file with format package_name-version.tar.gz. Let's create our git repo:

PKGNAME=package_name
VERSION=version  
mkdir $PKGNAME; cd $PKGNAME
git init

Check that user.name and user-email have the right values:

git config user.name '<Your name>'
git config user.email '<Your email>'

Import upstream sources to your repository:

gbp import-orig -u $VERSION --pristine-tar ../$PKGNAME-$VERSION.tar.gz

If you miss to add –pristine-tar option, you can generate it later wit the following command:

pristine-tar commit ../$PKGNAME_-$VERSION.orig.tar.gz

In the parent folder you have a link named PKGNAME_VERSION.orig.tar.gz to your original .tar.gz upstream file. Let's create the debian directory:

# license can be gpl, gpl2, gpl3, lgpl, lgpl2, lgpl3, artistic, apache, bsd or mit. 
# See man dh_make, option -c
LICENSE=license 
dh_make -c LICENSE -f ../PKGNAME_VERSION.orig.tar.gz -p PKGNAME_VERSION
git add debian/
git commit -m "Create debian directory via dh_make"

Remove all unneeded files in debian directory (it depends on your package):

git rm debian/README.Debian debian/README.source ...
git commit -m "Remove all unneeded dh_make templates"

Stuff that always must be done:

Close the ITP bug
Add building dependencies (almost always)
Add runtime dependencies (not so frequently)

If you're impatient, you can try to build it now… In fact, after each change you do, you can try to build the package. See how to build the package below. More change you will do:

Update Section, Priority, Homepage and Description fields.
Update debhelper compatibility
Update copyright
Update menu file, adding an icon if it is necessary
Update watch file
Install files that are not installed automatically: icons, man pages,…
Adapt debian/rules to your needs
Unapply patches after building

If you have to change the source code, you should use quilt. First, add .pc directory (and optionally .gitignore) to .gitignore:

echo -e ".gitignore\n.pc" > .gitignore

Now you can change the code with:

quilt new new-patch-name.patch
quilt edit files-to-change
quilt refresh

To build the package you can use git-buildpackage:

git buildpackage

or better (but slower):

git buildpackage --git-pbuilder

To check that every thing is ok:

lintian -i -I --show-overrides --pedantic ../$PKGNAME_$VERSION-1_i386.changes

Sign the package:

debsign $PKGNAME*.changes

Upload the package

dput $PKG_NAME*changes

Remember to tag your last commit:

git-buildpackage --git-tag-only

And push if you haven't done it before:

git push alioth
git push alioth --tags

Set up a remote repository in collab-maint in allioth (or inthe corresponding team):

ssh git.debian.org
umask 002
cd /git/collab-maint/
./setup-repository $PKGNAME '$PKGNAME Debian packaging'
exit

git config gitweb.owner '<Your name>'

git remote add alioth ssh://git.debian.org/git/collab-maint/$PKGNAME.git
git push alioth master 
git push alioth upstream
git push alioth pristine-tar

More info: https://wiki.debian.org/Alioth/Git

Building a backport

monica@undisclosed.example.com (monica) — Thu, 12 Jan 2017 22:44:20 +0000

Description: Building a backport in the proper way. The goal is to upload the backport to the official backports repository.

Language(s): English

These notes are based on https://wiki.debian.org/BuildingFormalBackports

Create a cowbuilder image. If you are already using cowbuilder for other stuff, you must specify where the base will be and the distribiution where you want to backport:

$ sudo cowbuilder --create --basepath /var/cache/pbuilder/base-jessie.cow --distribution jessie

Add an entry to changelog

$ dch --bpo

Build the backport:

$ gbp buildpackage --git-pbuilder --git-ignore-new --git-dist='jessie' -d -vSTABLE_VERSION

where STABLE_VERSION is the stable version or the last backport.

Upload the package

$ dput PKG_NAME*changes

Recipe under construction

monica@undisclosed.example.com (monica) — Sat, 27 Feb 2016 22:04:24 +0000

QA upload work flow

Description: Orphaned packages are responsability of QA team and any DD can make an upload to have these packages well maintained. Here you have a workflow to do this kind of uploads. It is assumed that the package is not using any version control system. If it uses one, take a look at Packaging a new upstream version and Packaging a new Debian release

Language(s): English

Download the package and try to build it:

PKG_NAME="package_name"; PKG_VERSION="version_number"; PKG_REVISION="revision_number"
mkdir ${PKG_NAME}; cd ${PKG_NAME}
apt-get source ${PKG_NAME}
sudo cowbuilder --build ${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc

Now we have two possibilities: fix bugs and tidy up the package to have a new Debian release or package a new upstream version.

New Debian release

cd ${PKG_NAME}-${PKG_VERSION}
dch -q

New upstream version

uscan  
PKG_QA_VERSION="qa_version_number"; PKG_QA_REVISION="1"
cd ${PKG_NAME}-${PKG_VERSION}
uupdate -v $PKG_QA_VERSION ../${PKG_NAME}-${PKG_QA_VERSION}.tar.xz
cd ../${PKG_NAME}-${PKG_QA_VERSION}
dch -a

Add a first entry in the new chagelog blck with the text “QA upload”.

Both cases

Fix all you want to fix.

cd ..
dpkg-source -b ${PKG_NAME}-${PKG_QA_VERSION}
sudo cowbuilder --build ${PKG_NAME}_${PKG_QA_VERSION}-${PKG_QA_REVISION}.dsc

Check if new package works as expected. If it doesn't work, fix it, recreate the source package and rebuild it again until it works properly.

Run lintian:

lintian -i -I --show-overrides --pedantic /var/cache/pbuilder/result/${PKG_NAME}_${PKG_QA_VERSION}-1_${ARCH}.changes

Try to make the package lintian free, do all needed changes/commits and build as many times as you need to make the package ready to upload.

Install and test the package:

sudo dpkg -i /var/cache/pbuilder/result/${PKG_NAME}_${PKG_QA_VERSION}-1_${ARCH}.deb

Check that there are not weird changes comparing the new package with the old one:

debdiff /var/cache/pbuilder/result/${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc /var/cache/pbuilder/result/${PKG_NAME}_${PKG_QA_VERSION}-1.dsc

Prepare the package to upload:

cd ${PKG_NAME}-${PKG_QA_VERSION}
dch -r

Built it again:

cd ..
dpkg-source -b ${PKG_NAME}-${PKG_QA_VERSION}
sudo cowbuilder --build ${PKG_NAME}_${PKG_QA_VERSION}-${PKG_QA_REVISION}.dsc

Sign the package (if it has not been done during the last command):

debsign /var/cache/pbuilder/result/${PKG_NAME}*changes

Upload the package:

dput /var/cache/pbuilder/result/${PKG_NAME}*changes

Debian Developer recipes

monica@undisclosed.example.com (monica) — Thu, 21 Jan 2016 08:59:29 +0000

Description: Here you will find some recipes I use for some Debian tasks

Language(s): English

NMUs

RCBW (Release Critical Bugs of the Week) work flow
Check and upload a NMU of someone else

QA Uploads

QA Upload work flow

Packaging

Creating a new package with git
Packaging a new upstream version
Packaging a new Debian release
Packaging with git
cowbuilder: Creating a proper image to build a package
pbuilder: tips
Building a backport

wnpp packages

Fix wnpp inconsistencies

Misc

Non-DD to DD steps
Managing GPG keys
Useful links

cowbuilder: Creating a proper image to build a package

monica@undisclosed.example.com (monica) — Sat, 28 Nov 2015 15:45:14 +0000

Description: When packaging with cowbuilder, each time you want to build, all needed packages have to been configured. This recipe shows how to prepare a cowbuilder base to do all this configurations only once.

Language(s): english

Copy a basic image (or create it with sudo cowbuilder –create):

$ sudo cp -a /var/cache/pbuilder/base.cow /var/cache/pbuilder/base-PKGNAME.cow

Start a session within this image telling cowbuilder that all changes will be saved:

$ sudo cowbuilder --login --basepath /var/cache/pbuilder/base-PKGNAME.cow --save-after-login

Once inside the image, enable package sources:

# sed -i 's/#\(deb-src .*\)/\1/g' /etc/apt/sources.list
# aptitude update

Install build dependencies of the package:

# aptitude build-dep PKGNAME

Logout:

# exit

Now, to use this image for building:

$ sudo cowbuilder --build PKGNAME_VERSION.dsc --basepath /var/cache/pbuilder/PKGNAME.cow

If you use git-buildackage:

$ gbp buildpackage --git-pbuilder --git-dist='PKGNAME'

If you want to use this last command, your image must have the prefix 'base-' (see #721444)

monica@undisclosed.example.com (monica) — Tue, 14 May 2013 09:50:43 +0000

monica@undisclosed.example.com (monica) — Tue, 14 May 2013 09:50:05 +0000

monica@undisclosed.example.com (monica) — Sun, 05 May 2013 17:18:21 +0000

monica@undisclosed.example.com (monica) — Sun, 05 May 2013 17:18:09 +0000

monica@undisclosed.example.com (monica) — Sun, 05 May 2013 17:17:50 +0000

monica@undisclosed.example.com (monica) — Fri, 29 Mar 2013 20:26:36 +0000

monica@undisclosed.example.com (monica) — Fri, 29 Mar 2013 20:25:49 +0000

monica@undisclosed.example.com (monica) — Fri, 19 Oct 2012 10:06:10 +0000

monica@undisclosed.example.com (monica) — Thu, 18 Oct 2012 00:23:34 +0000

monica@undisclosed.example.com (monica) — Sun, 08 Jul 2012 02:12:07 +0000

monica@undisclosed.example.com (monica) — Sun, 22 Apr 2012 19:57:55 +0000

monica@undisclosed.example.com (monica) — Sun, 22 Apr 2012 19:22:35 +0000

monica@undisclosed.example.com (monica) — Wed, 04 Apr 2012 11:42:16 +0000

monica@undisclosed.example.com (monica) — Wed, 04 Apr 2012 01:20:06 +0000

monica@undisclosed.example.com (monica) — Tue, 03 Apr 2012 23:34:09 +0000