[Qa-jenkins-scm] [jenkins.debian.net] 01/01: reproducible: better explain maintainer notifications

Holger Levsen holger at moszumanska.debian.org
Fri Oct 2 09:21:06 UTC 2015


This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit 7490f3aa22fc8987c7a7cbff75a4c888b50e1495
Author: Holger Levsen <holger at layer-acht.org>
Date:   Fri Oct 2 11:20:35 2015 +0200

    reproducible: better explain maintainer notifications
---
 bin/reproducible_html_indexes.py             |  2 +-
 hosts/bpi0-armhf-rb/etc/rc.local             |  6 +++---
 hosts/hb0-armhf-rb/etc/rc.local              |  6 +++---
 hosts/profitbricks-build2-amd64/etc/rc.local |  4 ++--
 hosts/profitbricks-build3-amd64/etc/rc.local | 14 +++++++-------
 5 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/bin/reproducible_html_indexes.py b/bin/reproducible_html_indexes.py
index ec8ce29..3b5f66d 100755
--- a/bin/reproducible_html_indexes.py
+++ b/bin/reproducible_html_indexes.py
@@ -374,7 +374,7 @@ pages = {
         'notes': True,
         'nosuite': True,
         'title': 'Packages with notification enabled',
-        'header': '<p>The following {tot} packages in {suite}/{arch} have notifications enabled. On status changes (e.g. reproducible → unreproducible) the system sends an email to $srcpackage at packages.debian.org, notifying the maintainer and relevant parties.  (You can subscribe through the PTS or Tracker if you are interested in such emails).<br />Please ask us to enable notifications for your package(s) in our IRC channel #debian-reproducible or via <a href="mailto:reproducible-builds [...]
+        'header': '<p>The following {tot} packages have notifications enabled. (This page only shows packages in {suite}/{arch} though notifications are send for these packages in unstable and experimental in any tested arch.) On status changes (e.g. reproducible → unreproducible) the system sends an email to $srcpackage at packages.debian.org, notifying the maintainer and relevant parties.  You can subscribe through the PTS or Tracker if you are interested in such emails.<br />Please ask u [...]
         'header_query': 'SELECT COUNT(*) FROM sources WHERE suite="{suite}" AND architecture="{arch}" AND notify_maintainer = 1',
         'body': [
             {
diff --git a/hosts/bpi0-armhf-rb/etc/rc.local b/hosts/bpi0-armhf-rb/etc/rc.local
index f11b6b5..7940adf 100755
--- a/hosts/bpi0-armhf-rb/etc/rc.local
+++ b/hosts/bpi0-armhf-rb/etc/rc.local
@@ -15,9 +15,9 @@ systemctl disable systemd-timesyncd
 systemctl disable systemd-timedated
 systemctl stop systemd-timesyncd
 systemctl stop systemd-timedated
-ntpdate -b us.pool.ntp.org
+ntpdate -b de.pool.ntp.org
 echo "$(date) - system was rebooted" | mail -s "$(hostname -f) rebooted" root
-date --set="-400 days"
-echo "$(date) - system is running in the past now" | mail -s "$(hostname -f) in the past" root
+date --set="+400 days"
+echo "$(date) - system is running in the future now" | mail -s "$(hostname -f) in the future" root
 
 exit 0
diff --git a/hosts/hb0-armhf-rb/etc/rc.local b/hosts/hb0-armhf-rb/etc/rc.local
index f11b6b5..7940adf 100755
--- a/hosts/hb0-armhf-rb/etc/rc.local
+++ b/hosts/hb0-armhf-rb/etc/rc.local
@@ -15,9 +15,9 @@ systemctl disable systemd-timesyncd
 systemctl disable systemd-timedated
 systemctl stop systemd-timesyncd
 systemctl stop systemd-timedated
-ntpdate -b us.pool.ntp.org
+ntpdate -b de.pool.ntp.org
 echo "$(date) - system was rebooted" | mail -s "$(hostname -f) rebooted" root
-date --set="-400 days"
-echo "$(date) - system is running in the past now" | mail -s "$(hostname -f) in the past" root
+date --set="+400 days"
+echo "$(date) - system is running in the future now" | mail -s "$(hostname -f) in the future" root
 
 exit 0
diff --git a/hosts/profitbricks-build2-amd64/etc/rc.local b/hosts/profitbricks-build2-amd64/etc/rc.local
index 9f9cb35..7940adf 100755
--- a/hosts/profitbricks-build2-amd64/etc/rc.local
+++ b/hosts/profitbricks-build2-amd64/etc/rc.local
@@ -17,7 +17,7 @@ systemctl stop systemd-timesyncd
 systemctl stop systemd-timedated
 ntpdate -b de.pool.ntp.org
 echo "$(date) - system was rebooted" | mail -s "$(hostname -f) rebooted" root
-date --set="-400 days"
-echo "$(date) - system is running in the past now" | mail -s "$(hostname -f) in the past" root
+date --set="+400 days"
+echo "$(date) - system is running in the future now" | mail -s "$(hostname -f) in the future" root
 
 exit 0
diff --git a/hosts/profitbricks-build3-amd64/etc/rc.local b/hosts/profitbricks-build3-amd64/etc/rc.local
index 7f05066..7940adf 100755
--- a/hosts/profitbricks-build3-amd64/etc/rc.local
+++ b/hosts/profitbricks-build3-amd64/etc/rc.local
@@ -11,13 +11,13 @@
 #
 # By default this script does nothing.
 
-#systemctl disable systemd-timesyncd
-#systemctl disable systemd-timedated
-#systemctl stop systemd-timesyncd
-#systemctl stop systemd-timedated
-#ntpdate -b de.pool.ntp.org
+systemctl disable systemd-timesyncd
+systemctl disable systemd-timedated
+systemctl stop systemd-timesyncd
+systemctl stop systemd-timedated
+ntpdate -b de.pool.ntp.org
 echo "$(date) - system was rebooted" | mail -s "$(hostname -f) rebooted" root
-#date --set="-400 days"
-#echo "$(date) - system is running in the past now" | mail -s "$(hostname -f) in the past" root
+date --set="+400 days"
+echo "$(date) - system is running in the future now" | mail -s "$(hostname -f) in the future" root
 
 exit 0

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git



More information about the Qa-jenkins-scm mailing list