Accepted chrony 3.3-3 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 18 Aug 2018 16:23:19 +0200
Source: chrony
Binary: chrony
Architecture: source
Version: 3.3-3
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut <vincent.debian@free.fr>
Changed-By: Vincent Blut <vincent.debian@free.fr>
Description:
chrony - Versatile implementation of the Network Time Protocol
Closes: 906276
Changes:
chrony (3.3-3) unstable; urgency=medium
.
* debian/:
- Normalize packaging with “wrap-and-sort -ab”.
.
* debian/control:
- Bump standard-version to 4.2.0:
↳ Install upstream release notes as “/usr/share/doc/chrony/NEWS.gz”.
Installing these as “/usr/share/doc/package/changelog.gz” is now
deprecated.
.
* debian/patches/:
- Cherry-pick upstream patch to avoid hangs when starting
chronyd on newer kernels by falling back to urandom.
Thanks to Gustavo Scalet <gustavo.scalet@collabora.com> for the report and
the initial patch. (LP: #1787366, Closes: #906276)
.
* debian/upstream/metadata:
- Add DEP12 upstream metadata file.
Checksums-Sha1:
b40c9bd62b6aa9f2cfb5362be291121d351445e3 2150 chrony_3.3-3.dsc
ecea12a6d123fee66988db4f08acc99d71328c0e 32296 chrony_3.3-3.debian.tar.xz
Checksums-Sha256:
7f3235f55fb6e99a36e730958b7f03f1559feff1c7feae99400fd4ac4f451b8b 2150 chrony_3.3-3.dsc
90541e441782194ba6e58f2b88d2c3e98d64d9b40a0b4d6c4a8e5011be9e40ca 32296 chrony_3.3-3.debian.tar.xz
Files:
db7c0efef509657d3f26b7938a7354d7 2150 net optional chrony_3.3-3.dsc
9c56910adf5a272eee3a5ca446fe88f7 32296 net optional chrony_3.3-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlt5B00ACgkQnFyZ6wW9
dQrTHAf+KuscS9aZzkDpMCBlxVfeFWylyOpFiqnErEG/B0TAdGCeR+RoOT2H9eRK
C/TsRCwap9iFDoOgB8U558B//sm8VCENTY+UBjD0aYD9MkG4L1C9mleJRrqO8Wpf
J9Hhkai1jjeVwM/xDVqLRroUCKLdO/5uCrpHxEGx31jKcfVcwJjf2j/U+Ne774dq
g7QYjyoJPXBPQBEIG0Zf2Q9wSPTHFr84IwRWo5NEp85/hyd3sbyJZDK+4DiySnOc
4LGBnZQ4ahYhDaRkZX6qCmqbOMqXKMtx+rCOTq26jZ9IyvW5iR5J5pphB+czYVQd
1Z0umwCspodEM6/2Bq23HkuDHrlUcw==
=VduO
-----END PGP SIGNATURE-----
Reply to: