Differences between revisions 13 and 14
Revision 13 as of 2015-08-22 00:23:02
Size: 2122
Editor: ?Tzafrir
Comment: Correct order of operations
Revision 14 as of 2015-08-22 10:11:01
Size: 3596
Editor: ?Tzafrir
Comment: Making a release. A r/w clone URL
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
gbp clone git://anonscm.debian.org/pkg-voip/PACKAGE gbp clone ssh://anonscm.debian.org/git/pkg-voip/PACKAGE
Line 35: Line 35:
If you don't have a write-access to the repository, use the following instead:
{{{
gbp clone git://anonscm.debian.org/pkg-voip/PACKAGE
}}}
If you want to push later, set the url or pushurl for the remote "origin" later to the above ssh URL.
Line 59: Line 64:
=== New Release ===
Note: do this after checking that the build works well. The following steps need to be done by the DD / DM uploading the package.

Update the changelog. Normally just use:
{{{
gbp dch -caR
}}}
This creates an extra commit with the up-to-date changelog.

Build and tag (please sign tags):
{{{
gbp buildpackage --git-pbuilder --git-tag --git-sign-tags
}}}

Alternatively, build and tag later when you're happy with the result:
{{{
gbp buildpackage --git-pbuilder
gbp buildpackage --git-tag-only --git-sign-tags
}}}

This produces an unsigned changes file. Now you need to sign it. Copy the path to the path to the changes file file from the output of {{{gbp buildpackage}}} for the next command.
{{{
debsign ../PACKAGE_VERSION-REV_ARCH.changes
}}}
And upload it:
{{{
dput ../PACKAGE_VERSION-REV_ARCH.changes
}}}

Now wait. Don't push your changes yet. Wait for the confirmation that the package has been accepted to Unstable, New queue, or whereever you upoaded it to. Only then push your changes.

If you have no new upstream, no need to push upstream and pristine-tar (but it's probably harmless).

{{{
git push --follow-tags origin master upstream pristine-tar
}}}

PKG VoIP Team

Infrastructure

Interacting with the team

Task description

We package VoIP software for Debian

For packaging

  • TODO: fill in interesting ITPs and such

HOWTO

Packages are maintained in Git using simple quilt patches.

Build

First, check out:

gbp clone ssh://anonscm.debian.org/git/pkg-voip/PACKAGE
cd PACKAGE
git branch pristine-tar origin/pristine-tar

If you don't have a write-access to the repository, use the following instead:

gbp clone git://anonscm.debian.org/pkg-voip/PACKAGE

If you want to push later, set the url or pushurl for the remote "origin" later to the above ssh URL.

Next build it. You should probably use git-buildpackage (gbp):

gbp buildpackage

TODO: complete instructions

New Version

Instructions here are for packages where upstream is in the form of a tarball.

You should start by getting a tarball. This is best done using uscan (TODO: document? link?). Make sure it is not in the current directory. Make sure that the working copy is clean: no uncommitted changes.

gbp import-orig --pristine-tar ../path/to/tarball.orig.tar.gz

New Package

Again, instructions for a repository base on tarballs.

mkdir PACKAGE
cd PACKAGE
git init
gbp import-orig --pristine-tar ../path/to/tarball.orig.tar.gz

New Release

Note: do this after checking that the build works well. The following steps need to be done by the DD / DM uploading the package.

Update the changelog. Normally just use:

gbp dch -caR

This creates an extra commit with the up-to-date changelog.

Build and tag (please sign tags):

gbp buildpackage --git-pbuilder --git-tag --git-sign-tags

Alternatively, build and tag later when you're happy with the result:

gbp buildpackage --git-pbuilder
gbp buildpackage --git-tag-only --git-sign-tags

This produces an unsigned changes file. Now you need to sign it. Copy the path to the path to the changes file file from the output of gbp buildpackage for the next command.

debsign ../PACKAGE_VERSION-REV_ARCH.changes

And upload it:

dput ../PACKAGE_VERSION-REV_ARCH.changes

Now wait. Don't push your changes yet. Wait for the confirmation that the package has been accepted to Unstable, New queue, or whereever you upoaded it to. Only then push your changes.

If you have no new upstream, no need to push upstream and pristine-tar (but it's probably harmless).

git push --follow-tags origin master upstream pristine-tar

Add new repository on git.debian.org

log into git.debian.org an execute the script on pkg-voip home dir

/srv/home/groups/pkg-voip/scripts/$ ./create_pkg-voip_git.sh NEWREPO

VoIP/Extremadura2007