[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted chrony 3.5-7 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 17 Mar 2020 15:21:53 +0100
Source: chrony
Architecture: source
Version: 3.5-7
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut <vincent.debian@free.fr>
Changed-By: Vincent Blut <vincent.debian@free.fr>
Changes:
 chrony (3.5-7) unstable; urgency=medium
 .
   * debian/chrony.maintscript:
     - Remove the /etc/NetworkManager/dispatcher.d/20-chrony conffile.
 .
   * debian/control:
     - Support seccomp facility on riscv64. It should be noted that the system
     call filter will stay disabled by default on this architecture until
     Linux >= 5.5 hits unstable.
     - Bump libseccomp-dev build-dep to 2.4.3-1~ to provide seccomp facility on
     riscv64.
     - Break network-manager (<< 1.20.0-1~). Prior to this version,
     NetworkManager would not look for dispatcher scripts into
     /usr/lib/NetworkManager/dispatcher.d/.
 .
   * debian/dirs:
     - Create the usr/lib/NetworkManager/dispatcher.d subdirectories.
 .
   * debian/links:
     - Change the location of the NetworkManager dispatcher script.
 .
   * debian/patches/:
     - Add allow-renameat2-in-seccomp-filter.patch. Required as the riscv64
     architecture does not support the rename() and renameat() system calls.
 .
   * debian/rules:
     - Move the NetworkManager dispatcher script in
      /usr/lib/NetworkManager/dispatcher.d/.
Checksums-Sha1:
 54df16a5e03e2e0feb743de0d64fce81446428e5 2338 chrony_3.5-7.dsc
 5f213d41764ce6d59139edd60e3a528b6036d5f8 36332 chrony_3.5-7.debian.tar.xz
Checksums-Sha256:
 822c7aed1a36a2a70456ecbe0d8acafe88dd28594a7acff9f1d916e5dd9739e5 2338 chrony_3.5-7.dsc
 413bf5aa9ff97afea5a86899685fd5a239866b287df723ba77cb1df113400543 36332 chrony_3.5-7.debian.tar.xz
Files:
 9d04884a5c71dafe3ece02a03b8ebc3a 2338 net optional chrony_3.5-7.dsc
 f43c486be49d225a943efcf0422263d5 36332 net optional chrony_3.5-7.debian.tar.xz

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

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5xRXkACgkQnFyZ6wW9
dQocxQf/SOVfI71XhfY0S6fC7ca1XZkFlefVFoPRtiLHgdsJDQoSlKXre9fsqduB
nTKOmMOZcc5D6AzYnQrO1uZyAlmVMhtuNoLuXGNS3eYLwwYCOekBhI1sa8zkEow3
5X2aaw3i2biczb/IEAuF1Fi7D2A146lX0hdr+YbSxhYLx2TGSkbUxJ84MY6t1L89
j/WPPpl1g5PM6p/hYK947EhpJqASGp570aO8I6XqemQiHrqmfzAU58LR3iLiGNTS
7CMpeboktOtd2E9SNQOoB0E11zltQK6xFyAIYY65y1LZ3GepNHdPqnGWzIAPNJhd
nqg2AKPY6mfBTkufVgKDL45Z029l/A==
=Qpr+
-----END PGP SIGNATURE-----


Reply to: