[developers-reference] 01/01: Update section about package tracker
This is an automated email from the git hooks/post-receive script.
hertzog pushed a commit to branch master
in repository developers-reference.
commit 9a9bdb951bfca5fbeec5ed6eaceced04ffe336b1
Author: Raphaël Hertzog <hertzog@debian.org>
Date: Thu Mar 15 00:51:07 2018 +0100
Update section about package tracker
Document that it recognizes git commit notices generated by GitLab.
---
debian/changelog | 7 +++++++
resources.dbk | 14 ++++++++------
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 20b0760..40ab06d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+developers-reference (3.4.20) UNRELEASED; urgency=medium
+
+ * Update section about package tracker to document that it recognizes
+ git commit notices generated by GitLab.
+
+ -- Raphaël Hertzog <hertzog@debian.org> Thu, 15 Mar 2018 00:49:09 +0100
+
developers-reference (3.4.19) unstable; urgency=medium
[ Hideki Yamane ]
diff --git a/resources.dbk b/resources.dbk
index 448bf38..1fd808e 100644
--- a/resources.dbk
+++ b/resources.dbk
@@ -1298,12 +1298,14 @@ Once you set up the VCS repository to generate commit notifications, you just
have to make sure it sends a copy of those mails to the package tracker at
<literal>dispatch@&tracker-host;</literal> or at
<literal>dispatch+<replaceable>sourcepackage</replaceable>_vcs@&tracker-host;</literal>.
-In the former case, you must make sure that the package tracker is able to identify
-the source package and the appropriate keyword... either by adding the headers
-<literal>X-Distro-Tracker-Package: <replaceable>sourcepackage</replaceable></literal> and
-<literal>X-Distro-Tracker-Keyword: vcs</literal> or by relying on the
-fact that the package tracker will detect the <literal>X-Git-Repo</literal> header
-and assume that the name of the git repository matches a source package.
+The latter is only needed when the package tracker doesn't know how to
+identify the source package name or when the repository is not
+named after the source package name. GitLab commit notices
+are identified with their <literal>X-GitLab-Project</literal> field, other
+common git notification mails are identified with their <literal>X-Git-Repo</literal>
+field. In both cases, it extracts the basename, drops the <literal>.git</literal>
+suffix and it assumes that the resulting string is the name of the source
+package.
</para>
<para>
For Subversion repositories, the usage of svnmailer is recommended.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/collab-maint/developers-reference.git
Reply to: