Accepted zurl 1.7.1-3 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 01 Jan 2017 19:27:07 +0100
Source: zurl
Binary: zurl
Architecture: source
Version: 1.7.1-3
Distribution: unstable
Urgency: critical
Maintainer: Jan Niehusmann <jan@debian.org>
Changed-By: Jan Niehusmann <jan@debian.org>
Description:
zurl - HTTP client worker with ZeroMQ interface
Changes:
zurl (1.7.1-3) unstable; urgency=critical
.
* Update Vcs-Browser URL
* Build-depend on libssl-dev (>= 1.1) and depend on libcurl3 (>= 7.51.0).
This fixes broken SSL support caused by an API incompatible change
without SONAME change in libcurl3. (See #844018).
Because curl 7.51.0-1 migrated to testing even though
there was a new RC bug stating that it breaks other packages, zurl
must be built with OpenSSL 1.1 as well.
* Set urgency to critical because 1.7.1-2 gets broken by libcurl 7.51.0.
Checksums-Sha1:
7c1c6e77f9b7662ed0708b99fe196fb4a89a76b2 1712 zurl_1.7.1-3.dsc
fdce03f472bd4424406171138f3e37fe7839fba2 8244 zurl_1.7.1-3.debian.tar.xz
Checksums-Sha256:
e01061268a3071c226c4b3baaf41513d5a60832d18b6dc69f26388d034f75d33 1712 zurl_1.7.1-3.dsc
b9c75bed6152f25489e567524d9b84273c84a1c7aff39cec99284d03c6dbc47c 8244 zurl_1.7.1-3.debian.tar.xz
Files:
e3a0e0ffccf47f8b45f62ca9a1467ebc 1712 net extra zurl_1.7.1-3.dsc
80f36df65b575fb8922283c4a0628b49 8244 net extra zurl_1.7.1-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQGcBAEBCgAGBQJYaUxfAAoJEMJAzpldAmsR5OML/RxWW+lTarlvL6wBQTz186kS
KwNnFLB4/w6rfEQCDjqsT77LVkzi0RJBlXa+0FW8JAhmbNQmrVPZqoH7OUydl7X3
ndwT/50xdpqKmaSVQiRpPWS1htIroixyt1KE7eBfHRkMst37BQv1BOpj9FFb8W13
AW3rtlNV20VJ4dBn/KmTmnOVcMRO/2By4Lju7dsv1VPYQ9IABQZyYaJ0NWHFSV/3
yRYfvrWFXd3yaEUtTZzhs/VeWnauOfwJjYNXcKlX8Q3DS7/GqvQZVxKKVyG5puGL
3ivN+PrdcIy8K7tc9iEdzbQEm4zhtL2Gs356CKr9Enb9x5fG9jGxi9yue3eDzKNQ
6t9Da4O1QIvtoRS2Cuu9Anasbzk+2tIm1NjdGNj8qleT5/Dducj7/2JdLQWDeX+h
Lou4aQXkNflJEkz1ZXqqPagvrpfOEbJi9SVEiwMaFPUGkBePXFAGkD8ui9Fx8Mhb
DST1LWAdDkKvyUgHS8ErJt9Bbp49daPgfjsQWAxCKw==
=DgFB
-----END PGP SIGNATURE-----
Reply to: