Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian....@packages.debian.org
Usertags: pu

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,

I’d like to fix #868491 in Stretch to prevent the “if-up” script from 
failing in certain situations (usually at boot when chronyd isn’t fully 
ready) which impede ifupdown from correctly registering the concerned 
network interface in /run/network/ifstate.

Cheers,
Vincent

- -- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----

iQJLBAEBCgA1FiEE/VQBlxWoTJPh4vI5ipzudlpxp4AFAll0k80XHHZpbmNlbnQu
ZGViaWFuQGZyZWUuZnIACgkQipzudlpxp4AcuRAA2n+jALgsb71pdnKK/QoTikpG
HpOJ7x+wdtgP0t4hr/CEu3pNONfq/HZQ+dJCkoKT+Z/pMcSzhVe7A7CQv8HfeDbx
kdNZRxPqbEr8PTlm3T9ZGJbTTpGbY6JiOEsPdiOmpwxJCrb7fuF9gN20Yyerd67+
S3Fh9BFKINSbLl8oxz/WIap1TKAUmEN2yt9eeWTMmOHgPXwIsKczN8KC5EU0TTj7
zf5hX9tAPhD8oxAQir7SDIad6sWZ656UHpMVRT947M2TB7QynMZI6xuCl2uOCQEk
bssbt1kzQUFFwXEXl5KbPnsRyHnwgr1C1jj+QIBuonyegcamHqCP87gquFV9Dww+
iuZ7atbCX9qQqgSeJb5F7bffKc4GxnBmLuV+9VRxlWHpNSeOupEAq3qEZjDa9ZWe
IEzYEtgnSxTGcn437VDXRyh5a6NQMXecD6b16pCfG6LXDOu7jT5NSCAX7sjYO4ak
uTEa4aKfzSkmVlliDPR5oUjqgHPgeQNMZz3dgKStCfKrHSwilnzwMRAevGXFfASC
pNA8g+KCqxwU4UVCzpaXPmm0u6v5lB8Qh8RswcbRTDZC/E5nVtbwoBx1sHc/ilEV
hhGJGendYWZDnC4+QfZvuwyerUkS9RjpCq4364ZVnI4+SC0DXlCsD8VtyX/bXhYa
/K42g7nXGKvV8Mpf8Ns=
=5MtQ
-----END PGP SIGNATURE-----
diffstat for chrony-3.0 chrony-3.0

 changelog        |   15 +++++++++++++++
 chrony.if-up     |    2 +-
 chrony.ppp.ip-up |    2 +-
 3 files changed, 17 insertions(+), 2 deletions(-)

diff -Nru chrony-3.0/debian/changelog chrony-3.0/debian/changelog
--- chrony-3.0/debian/changelog 2017-04-26 17:39:44.000000000 +0200
+++ chrony-3.0/debian/changelog 2017-07-22 17:24:44.000000000 +0200
@@ -1,3 +1,18 @@
+chrony (3.0-4+deb9u1) stretch; urgency=medium
+
+  * debian/chrony.if-up:
+    - Do not pass the “burst” command to chronyc as the script could return an
+    error in certain situations. As a consequence, that would prevent ifupdown
+    from writing the current state of the interfaces in /run/network/ifstate.
+    Thanks to John Eikenberry <j...@zhar.net> for reporting that issue.
+    (Closes: #868491)
+
+  * debian/chrony.ppp.ip-up:
+    - Take the same action as for the “chrony.if-up” script as a precautionary
+    measure.
+
+ -- Vincent Blut <vincent.deb...@free.fr>  Sat, 22 Jul 2017 17:24:44 +0200
+
 chrony (3.0-4) unstable; urgency=medium
 
   * debian/patches/*:
diff -Nru chrony-3.0/debian/chrony.if-up chrony-3.0/debian/chrony.if-up
--- chrony-3.0/debian/chrony.if-up      2017-01-16 17:33:37.000000000 +0100
+++ chrony-3.0/debian/chrony.if-up      2017-07-22 17:23:39.000000000 +0200
@@ -6,7 +6,7 @@
 
 if [ -e /run/chronyd.pid ] &&
     ip r list dev $IFACE 2> /dev/null | grep -q '^default'; then
-    chronyc -m online 'burst 4/10' > /dev/null 2>&1
+    chronyc online > /dev/null 2>&1
 else
     exit 0
 fi
diff -Nru chrony-3.0/debian/chrony.ppp.ip-up chrony-3.0/debian/chrony.ppp.ip-up
--- chrony-3.0/debian/chrony.ppp.ip-up  2017-01-16 17:33:37.000000000 +0100
+++ chrony-3.0/debian/chrony.ppp.ip-up  2017-07-22 17:23:39.000000000 +0200
@@ -6,6 +6,6 @@
 # Modified by Vincent Blut <vincent.deb...@free.fr>
 
 /bin/pidof chronyd > /dev/null || exit 0
-/usr/bin/chronyc -m online 'burst 4/4' > /dev/null 2>&1
+/usr/bin/chronyc online > /dev/null 2>&1
 touch /var/run/chrony-ppp-up
 exit 0

Reply via email to