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

Accepted djbdns 1:1.05-16 (source) into unstable



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

Format: 1.8
Date: Wed, 03 Jul 2024 18:08:00 +0300
Source: djbdns
Architecture: source
Version: 1:1.05-16
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev <roam@debian.org>
Changed-By: Peter Pentchev <roam@debian.org>
Changes:
 djbdns (1:1.05-16) unstable; urgency=medium
 .
   * Acknowledge NMU; thanks, Helmut Grohne and Chris Hofstaedtler!
   * Drop the "type is a bashism" Lintian override, Lintian no longer
     emits this false positive message.
   * Declare compliance with Policy 4.7.0 with no changes.
   * Use debhelper 14:
     - the sysusers sequence is activated by default now
     - let debhelper add some default dependencies automatically
   * Stop overriding the "lines too long" Lintian warning.
   * Use dpkg's default.mk in the rules file.
   * Declare dpkg-build-api v1, drop the implied Rules-Requires-Root: no.
   * Use dh-package-notes to record ELF package metadata.
   * Drop the version of the dh-runit build dependency.
   * Raise the datalimit in the 0011-datalimit patch again to try to fix
     the autopkgtest failures on 32-bit systems.
   * Refresh the Python coding style in the autopkgtest suite.
Checksums-Sha1:
 58c8e937998e20d4f2a00476afc77eef2262a91d 2433 djbdns_1.05-16.dsc
 43e054e8da2a689b3baa1f41151fed12d1d27c93 63088 djbdns_1.05-16.debian.tar.xz
Checksums-Sha256:
 e0583f964291ec8b59fc4c30c8bad9b0d79cfcc7b544f88f70317ec4ca6dde27 2433 djbdns_1.05-16.dsc
 a197983a184d8db4464b9bae45c4b6500c360cbd150e461c569d53fea05e49c5 63088 djbdns_1.05-16.debian.tar.xz
Files:
 228ce0048f588331cb60cdc2ddd3fcca 2433 net optional djbdns_1.05-16.dsc
 0bab93ae24b0aeee3873d222e0e1a88a 63088 net optional djbdns_1.05-16.debian.tar.xz

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

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmaFag4QHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffE0UpEACGATjrcQL8bahma7opWaL1spJq+9hA+epS
c4wJjorSfbAmsT/YpcE41w2f3JL+SeD5CD4i9rDIVKWVov04d6VQml05MTM6+eIW
SKik3bFmMVSastodcpvBM7zNtMSZGWEDGGrBrqkL3QFZjQ4dsCCOkKMTSCAmUN6N
i0saZnkzWOoYw0cUvhNWPjneXJhB5GDOpIgT1Stclg6JGh6CeR1yZtAp/X4s1w0E
WQKNKFfBF6DFFXqvVARZYRf0G2fQ+orDnK6Dnr6igue86yM5PdSNfiN94zycGPhy
14xx6LI8/O3rQzXnLOeZWKWky/GZgvZ8VvfpXxqBZojyTcWitLyWL0k/Rt2Pbj6w
wLxzLBss4UqK7Cw6TrSsPVQ9wxMOevurzei1QqOjiPTTh7nw+yevyoAI7vVkK5c4
s8yBYE0BM9CbFkmQkcF+gMsYopKQVfvXk7uJLnWHTLwQy8mAAvn4broXRqrD0YLx
rDkdKnwetP2ANbp0wz8ZJ/8c6bdTHYNhuvNkkJIZb4P19xbu5YWsIQqeB1hah5Cb
wPhOkgoJG2ntiEt6v/Y1S08SZGMlK190eTy4c3eeIBTtK7Uavv23RI/lsbT9vYXY
4JOf0sIIYcM13u93hFWUzhwI+6u6SrjSs0vBcGUbXjlknwwYZ2sN4oA4P5Pt2aUV
9ndMuN1JfA==
=FoEf
-----END PGP SIGNATURE-----

Attachment: pgpYbM1stJyu0.pgp
Description: PGP signature


Reply to: