Accepted xymon 4.3.17-6 (source amd64) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 13 Feb 2015 21:59:49 +0100
Source: xymon
Binary: xymon xymon-client
Architecture: source amd64
Version: 4.3.17-6
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg <myon@debian.org>
Changed-By: Axel Beckert <abe@debian.org>
Description:
xymon - monitoring system for systems, networks and applications
xymon-client - client for the Xymon network monitor
Closes: 775590 776126 778343
Changes:
xymon (4.3.17-6) unstable; urgency=medium
.
[ Axel Beckert ]
* Add CVE ID to the previous changelog entry.
* Debconf translations, thanks!
+ ru by Yuri Kozlov (Closes: #776126)
* Cherry pick two patches from upstream to fix multiple memory leaks.
(Closes: #778343)
.
[ Christian Kastner ]
* Document license of sha?.* files in debian/copyright (Closes: #775590)
Checksums-Sha1:
7a3b82edc9b500af4fc2574e9d5a274005ba5b98 2067 xymon_4.3.17-6.dsc
b6e317b12259961bf1efb54d43f3400829cff530 94824 xymon_4.3.17-6.debian.tar.xz
8cd64063270797b5a80322a5c9055e11980f55dc 2258238 xymon_4.3.17-6_amd64.deb
ae87054821947835aca69658bde8bedd1299d6d6 248604 xymon-client_4.3.17-6_amd64.deb
Checksums-Sha256:
d894ccb0c865f1657870c011912c99c57272b8befbab8af61c48c28c498a8b8f 2067 xymon_4.3.17-6.dsc
ffeb000908a05c152afb82934a151b1938ffeac0080b882eae57d4d5b8a50c6e 94824 xymon_4.3.17-6.debian.tar.xz
67acc246f8b79f61b7a9cf7dcc12d74e109dc4a63b490dd209f867929a2b84fa 2258238 xymon_4.3.17-6_amd64.deb
546daa323b6cb9d3a2673afa4068f3a9ffb4091e43d4fb0b366ef3953e218396 248604 xymon-client_4.3.17-6_amd64.deb
Files:
a4c359b4b05aec8321a05d29743bb89b 2067 net extra xymon_4.3.17-6.dsc
c5e760ed298f7e9a60bbb577102fbc39 94824 net extra xymon_4.3.17-6.debian.tar.xz
2dc0a4ba43eb871078541d7da9b0aeae 2258238 net extra xymon_4.3.17-6_amd64.deb
62b9a97d94ba64698c24a029a5e57692 248604 net extra xymon-client_4.3.17-6_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJU3mxPAAoJEGvmY8daNcl15ngQAIV8qMxvfXe83y47dy3XE894
QptXdKZSHAbDRgevVnKkUHd6lEVpDEhkVEO0BBiohR47SRlYENrZF/axjX8TC01w
iHvAeJ+ZdSw/5//unikFm4RPcyeRGpsTujgrwYjV3C70X5lgLboDn8+qwaY4O0Q1
cloXvE0IWPiCGWtXWoMrr79hVgG6kp/omUudnadegUoXY0Gz0Yz2oRxG2niPUZLd
SeC6+adfg5dVDaCNT6+cEgxwPjkPUbAciLLfNEHotN/EosME3EEvJRqSi+qYFv2R
Wt64GbrRhGyj5kH80iYLtCNcrcz8gKyoAmpuK5uy4zZuDT7ZjsFDUm5+5isQzzgs
dKVg2J2/OUjNEgJro8cNUWV8gSuGY3la+vwAXUY1M1Pz4gdE6vkH/CwfDcN4JO2O
Ulx22LKt49f4W70veS9zDF+GxPk0clx4ZbsqierQs1lyDfP6Zqrnhr+tpqFjogFs
2AbF1WwMvCTdPZUo2BWn7bNcybdZd0POXzpV6mnan7V0gQFd7Hi54r/qHPVgDVGf
31Aj42utny/QQQR0fUvEAOoBdAWeSmu4c1pI0H07UwV9Y4No7XPe+NxTqZC6HzJP
2mcTGkpg9VDuNg2lJKiJwfmB6U2I766mVpgXwcIeU4fbfyGVvtqur32+0yIEiKne
9/Z9znOn/crbRIqzz2UQ
=4vUI
-----END PGP SIGNATURE-----
Reply to: