Accepted chrony 3.5-5 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 22 Dec 2019 17:30:40 +0100
Source: chrony
Architecture: source
Version: 3.5-5
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut <vincent.debian@free.fr>
Changed-By: Vincent Blut <vincent.debian@free.fr>
Changes:
chrony (3.5-5) unstable; urgency=medium
.
* debian/control:
- Bump standard-version to 4.4.1 (no change required).
.
* debian/install:
- Install 50-chrony.list in /usr/lib/systemd/ntp-units.d.
.
* debian/ntp-units.d/50-chrony.list:
- Allow timedated to interact with chronyd.
.
* debian/patches/*:
- Cherry-pick upstream commits to better manage RTCs that don't support
interrupts. This fixes an issue exhibited when a specific upstream system
test is run on the Ubuntu CI. Thank to Christian Ehrhardt for working
with Miroslav Lichvar to address this problem.
.
* debian/tests/control:
- Use @builddeps@ as a test dependency for upstream_system_tests.
.
[ Christian Ehrhardt ]
* debian/tests/upstream-simulation-test-suite:
- Redirect stderr on make call to stdout. On some architectures (e.g. armhf)
the clksim tests compile but throw some warnings. (MR: !2)
Checksums-Sha1:
b33c81543d668323e57fc3f7f1f761c04e8b7d25 2330 chrony_3.5-5.dsc
94f33d96769ae822f3c4de82e5a8e1700ff8228d 35096 chrony_3.5-5.debian.tar.xz
Checksums-Sha256:
6b6dc0474036a23cfa905554c63964dd41c964166d22ba59753ec7e368520662 2330 chrony_3.5-5.dsc
af12b9b5b8aa9e334c3cdbba39ba5bb1c95db34593f160bbbfce99b775db45ef 35096 chrony_3.5-5.debian.tar.xz
Files:
b6bff0f5f25f1da36f86d4d0ccfbf2d4 2330 net optional chrony_3.5-5.dsc
18878982ce23a599fb6b099a774c51f7 35096 net optional chrony_3.5-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl4BJFwACgkQnFyZ6wW9
dQqo5Af+PX1pKodsAn1Kvclj4I4JxSsV3WW7g6S7rICgwU9eI4C1OZUt6zu60qSE
PwMVaSQ9tft4RhthjeevJdO0eNrOZ+RKEv3OXmFr5MnlOdQBK5O33Z1m3ByOmJDf
CJCUoMb8COwUQzTjjlPj41dYGnDTQ0ole9bSwQbhXw1Pp9mftneIdGIgU800Y5Pu
TacHhb3fKrtlBBU+BVVoqqPPg0oHdN9Ea07aGzjEdBgtJzjQXvp8LEO++sOpoBEb
XFjG9LpetEO5zB8WBx8g56pLxZs6n3HaUuxxmPQlLwCQTdgqaowezQ1V9IZXyDU8
JsHl6t0/AMvqbZc0ZTFs0ENmB1e2Eg==
=Grb1
-----END PGP SIGNATURE-----
Reply to: