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

Accepted yaml-cpp 0.5.2-3 (source amd64) into unstable



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

Format: 1.8
Date: Mon, 30 Nov 2015 16:53:57 -0500
Source: yaml-cpp
Binary: libyaml-cpp0.5v5 libyaml-cpp-dev
Architecture: source amd64
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Lifeng Sun <lifongsun@gmail.com>
Changed-By: Paul Novotny <paul@paulnovo.us>
Description:
 libyaml-cpp-dev - YAML parser and emitter for C++ - development files
 libyaml-cpp0.5v5 - YAML parser and emitter for C++
Changes:
 yaml-cpp (0.5.2-3) unstable; urgency=medium
 .
   * Fix error in yaml-cpp-config.cmake
   * Disable gtest's use of pthread on hurd and kfreebsd
Checksums-Sha1:
 1084091b17b034e8214a9c9e405acf24ba221702 2004 yaml-cpp_0.5.2-3.dsc
 00abb68d3c1c6a28ad7f4c515fb982c6a1b575f1 4340 yaml-cpp_0.5.2-3.debian.tar.xz
 588c34f5f64a41da0d1da50585736f3906b69a95 201764 libyaml-cpp-dev_0.5.2-3_amd64.deb
 26bfea1f421051f2e9d3d94bd210e083c1e9c0f0 158862 libyaml-cpp0.5v5_0.5.2-3_amd64.deb
Checksums-Sha256:
 15ec5d71e6f076e6a7f891afc91e4a442d3f42ff91d4cb1cd4a610de9da1f18a 2004 yaml-cpp_0.5.2-3.dsc
 05a6e6fbe7f36cf09c0d4a8e21aa5e1a13d8f134c101f08183f6cfa88df64b05 4340 yaml-cpp_0.5.2-3.debian.tar.xz
 534df7713aec826c7114a737530e1c60a99a56bdfc67e4eeb6dac67be211b7f7 201764 libyaml-cpp-dev_0.5.2-3_amd64.deb
 0e01acff133662d62f308e682c2fcf783913e5e8aa943829264ba2e4dd72fcfc 158862 libyaml-cpp0.5v5_0.5.2-3_amd64.deb
Files:
 d6bb029c14b92676917a1e8127862cb2 2004 devel optional yaml-cpp_0.5.2-3.dsc
 3f2d02ecd4d99e149ecda7a6df8cb79f 4340 devel optional yaml-cpp_0.5.2-3.debian.tar.xz
 9ea0ac184f74117299e66c79580f543b 201764 libdevel optional libyaml-cpp-dev_0.5.2-3_amd64.deb
 0e16d2a8c63b021d2b6a8364d5b7b9b5 158862 libs optional libyaml-cpp0.5v5_0.5.2-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWXMo2AAoJEP6qEy+YMZHqxccP/3qM5d7AmRcTjQapOAjLCWud
XNV+hviYHdcbas83v/NiV3gjjWwrwmTOnvq1pipivcxSJb8DX/GQeDU8VoD86Svk
rx1QGcylG9dWhkXJ5tCyHzstp191g3naRFTAD5D+sJCNRR7h3w5dHn97Pah7Zx0S
pBWqVrtPub6h68TmiR8btvi9MHnyMfTo+jujRs7EjsPwBnG5Iq6MYEMI0BlzPC6V
qTD+zzACxzLcuBYDbvsHYxhbvQs1daLzZCN+FOKY1sdoi5ro0YnxvonteReGN2Ed
6PQUkJ9P3e9sA8D+yDKLd3noTbdRNSi/sI9Okd1DEwzQAbOxV79ia3FafqeClWSR
7BScrF3IwhGf3bkm7qRrT+a74jBnY0EIFqdfNY/Mvf8jpZ+SZS8nkqwCWdJKpi4p
Ccbz1wKoVAJXumdaRuTdHzBlWbttb5zVHwDdXqp254rl4b5Ia/KonzZ38FAaDA1N
yDTlGDVc9LwBwpfv8MqlVzCDYAYCRR6TpKGypbOoSrE79P6kfGU/TbvWZiGIbEAX
X2bMkqFaby8hgT206vyWob6acEH8cY65UPInehxPvDCO3rCZ6wVEOvT1nnm8Sz9U
T6yxj/H4OgEt0/kEPTne8MCUJAtEPx6asKSWc34IVb3J647wFUuoaxBTIUkRg0uL
JKWiXvQiGn3SDQgny73v
=h56d
-----END PGP SIGNATURE-----


Reply to: