= PKG VoIP Team =

== Infrastructure ==

 * '''Salsa team''': ''https://salsa.debian.org/pkg-voip-team''

== Interacting with the team ==

 * '''Documentation''': ''[[https://salsa.debian.org/pkg-voip-team/docs|README]]''
 * '''General discussion mailing list''': <pkg-voip-maintainers@lists.alioth.debian.org> ([[https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-voip-maintainers|mailinglist]])
 * '''Public IRC channel''': ''#debian-voip'' on irc.debian.org (OFTC, bridged from [[https://matrix.to/#/#_oftc_#debian-voip:matrix.org|matrix]]) (see also [[IRC/ElementMatrix|Element]] instructions for Matrix)

== Task description ==

''We package [[https://udd.debian.org/dmd/?email1=pkg-voip-maintainers@lists.alioth.debian.org|VoIP software for Debian]]''

== For packaging ==

 * TODO: fill in interesting ITPs and such

== HOWTO ==
Packages are maintained in Git using git-buildpackage and simple quilt patches.

=== Build ===
First, check out:
{{{
gbp clone git@salsa.debian.org:pkg-voip-team/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 https://salsa.debian.org/pkg-voip-team/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.

Note: This section uses the flag --git-pbuilder which requires you to create an environment first. See [[git-pbuilder]] for more details.

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
}}}


== Links ==
[[VoIP/Extremadura2007]]