[lintian] 01/01: releases.md: Document how to update lintian.d.o
This is an automated email from the git hooks/post-receive script.
nthykier pushed a commit to branch master
in repository lintian.
commit 9ed7913082e75c26ec5abe6105d920d3b7d67b3c
Author: Niels Thykier <niels@thykier.net>
Date: Sun Jan 7 20:55:52 2018 +0000
releases.md: Document how to update lintian.d.o
Signed-off-by: Niels Thykier <niels@thykier.net>
---
doc/releases.md | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 88 insertions(+)
diff --git a/doc/releases.md b/doc/releases.md
index a879b57..a7e1edc 100644
--- a/doc/releases.md
+++ b/doc/releases.md
@@ -47,3 +47,91 @@ To update lintian on lintian.debian.org, please see the README in
obtained any new dependencies, these must be installed by DSA before
updating lintian.debian.org (send a patch to DSA for their metapackage
for lintian.debian.org).
+
+
+Updating lintian.debian.org
+===========================
+
+Once a new release is done and tagged, we can update the installation
+on archive-wide processing server that generates "lintian.debian.org".
+Historically, this server was the same as "lintian.debian.org".
+However, these days the archive-wide processing happens on a separate
+server called:
+
+ lindsay.debian.org
+ (DD-accessible)
+
+In the rest of the this document, we will refer to this as the lintian-host.
+
+
+The update is done in the following steps:
+
+Step 1
+------
+
+Ensure that any new dependencies are installed. These must be
+installed by DSA before updating lintian.debian.org (send a patch to
+DSA for their metapackage for lintian.debian.org).
+
+Often there are no new dependencies meaning that this step can be
+omitted. Please remember that you can request the dependencies before
+the lintian release.
+
+Step 2
+------
+
+Login to the lintian-host and ensure that lintian is not currectly
+performing an archive-wide run and that you have "plenty" of time to
+complete the upgrade. The entire upgrade can be done in less than 5
+minutes (but you may want to have a "slightly" larger window the first
+few times).
+
+You can find lintian's crontab via either:
+
+ sudo -ulintian crontab -l
+
+OR
+
+ less /srv/lintian.debian.org/etc/crontab
+
+If the archive-wide run is currently active, check the harness log
+(`tail -f /srv/lintian.debian.org/logs/harness.log`).
+
+ 1. If lintian is processing packages, then send a SIGTERM to the
+ "reporting-lintian-harness" process and it will gracefully
+ terminate lintian and commit the latest changes. A few seconds
+ after the signal has been sent, reporting-lintian-harness should
+ emit something like:
+
+ [2018-01-07T14:26:25]: Signal SIGTERM acknowledged[...]
+
+ 1. If "reporting-sync-state" is running then either kill it and
+ "harness" (if you do not mind triggering an error and possible
+ cron-noise). Alternatively, wait for "reporting-lintian-harness"
+ to start and kill it once lintian starts processing packages.
+
+ 1. If "reporting-html-reports" is running, then just wait the 5-10
+ minutes it takes for the entire run to complete. Otherwise, we
+ might end up with a broken report.
+
+
+
+Now that we are sure the lintian is not running and will not start in
+the middle of the upgrade, we can perform the actual upgrade.
+
+ cd /srv/lintian.debian.org/lintian
+ # Reset the directory in case there are out of band patches
+ # - alternative being "sudo -ulintian git stash" as long as you clean it up
+ sudo -ulintian git reset --hard
+ sudo -ulintian git fetch
+ # e.g. sudo -ulintian git checkout 2.5.67
+ sudo -ulintian git checkout $LINTIAN_RELEASE_TAG
+
+ # Update the manual + manpages
+ sudo -ulintian debian/rules clean
+ sudo -ulintian debian/rules rebuild-lintian.debian.org
+
+With this, the upgrade is complete. If the reporting framework needs
+additional configuration, please remember to update
+`/srv/lintian.debian.org/config.yaml` (Note it is *not* the one in the
+reporting directory).
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/lintian/lintian.git
Reply to: