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

Accepted spiped 1.6.0-4 (source) into unstable



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

Format: 1.8
Date: Wed, 16 Jan 2019 14:00:04 +0200
Source: spiped
Binary: spiped
Architecture: source
Version: 1.6.0-4
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev <roam@debian.org>
Changed-By: Peter Pentchev <roam@debian.org>
Description:
 spiped     - create secure pipes between socket addresses
Changes:
 spiped (1.6.0-4) unstable; urgency=medium
 .
   * Bring up to compliance with Debian Policy 4.3.0: install the upstream
     release notes (CHANGELOG) as NEWS and not changelog.
   * Drop the Lintian overrides related to B-D: debhelper-compat -
     Lintian 2.5.98 no longer emits these warnings and errors.
   * Bump the debhelper compatibility version to 12 with no changes.
   * Add the year 2019 to my debian/* copyright notice.
   * Move away from git-dpm.
   * Add a trivial git-buildpackage config file.
   * Remove the quotes around pgpmode=none in the watch file.
Checksums-Sha1:
 540a602ecab73b33848a230289a59c0a1e9a56f5 1893 spiped_1.6.0-4.dsc
 9d2c6b322e161f9f5b88b986b480f2b32323ab0a 8584 spiped_1.6.0-4.debian.tar.xz
 718dbfcf516e1541f50728bb071eeb97b0e3e1db 5611 spiped_1.6.0-4_amd64.buildinfo
Checksums-Sha256:
 8c0bf34ece09bdfd51ce5e56f2c0f35047f8947591310b441abcf3a1d77d74f6 1893 spiped_1.6.0-4.dsc
 9004b7673e4064448227909bfd077d2cae05dbbdced28254cb573fb960c917bf 8584 spiped_1.6.0-4.debian.tar.xz
 e0e0508410ffa45d45f654a37b10b28a14abfc54a8ce0190a60e79d2e28dbf2b 5611 spiped_1.6.0-4_amd64.buildinfo
Files:
 5d6023b153b0ebf9a173f3f92a067ba4 1893 utils optional spiped_1.6.0-4.dsc
 f394c52a7c8b58878ea1ef3b28a6eb6d 8584 utils optional spiped_1.6.0-4.debian.tar.xz
 d122dd2b10fa4ac91c5d5d1771d6952c 5611 utils optional spiped_1.6.0-4_amd64.buildinfo

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

iQIzBAEBCAAdFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAlw/HVAACgkQZR7vsCUn
3xN+4BAAxpvAs0F/kSrVfBVQCkJWE1dgDyYJicKxw/8yz/nNO7G+Xd6+YaTLJQ9h
moTy+x04bTMWkIx2uN+lOleqsYCfdFWvqLoYv8+YV/pqnzkI2aygQ4Vm1NhDURn3
14gyO0kGYldij4e3jhHI9e4bFh/3u2g+CcmByOt6gTilIMxjuZALDY6KnNX3pRjK
Crrpy2cIYAi05jsS1m5WDOrNjjr9Dov3UNjPXHMShg4UExQTHmBfpb+jygaOpFJE
sDAhoFEL/pOFT+nXjeBVLg+bdMMsU3xSv+Nf5kymgXnzXN2xZ6jMBAPq/T/eSAmo
bdUrIK3kAqHmY8FG6FkiMqCHz/TgLP8FcP643QLIzCeX3Kzk4etJj2KFD+V/uGDu
yPEnTTKwIC8Suwl3WxcqidErtSn0K+Nz8mGy9nMfcSVtU9vhpx03occyVNkct7of
WJyLpwhdFT7EN75Ytk2lrc45kxhSRRf4dXl9pFH4R9TO5QnzHVcwgMU0UoHQq3uf
JBntWUZmSSyxbaLcuwqknOI0cGyy2hAlLxSS87nB4RVdrQYM9XUyZhvOKyHu4TAr
d5UI8jqk/dg9mw+79+YgBjLTe3Mz7Hg687UicZXC8AFrdei6bNBfY168iNtwNgRP
09iVwScWdxGR2OI2DDDfxtKkii0YVAp0RzeZ7yO3V+nsrydwcnk=
=R5/J
-----END PGP SIGNATURE-----


Reply to: