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

Accepted lcmaps-plugins-verify-proxy 1.5.4-2 (source amd64)



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

Format: 1.8
Date: Mon, 20 Jan 2014 16:36:18 +0100
Source: lcmaps-plugins-verify-proxy
Binary: lcmaps-plugins-verify-proxy
Architecture: source amd64
Version: 1.5.4-2
Distribution: unstable
Urgency: low
Maintainer: Dennis van Dok <dennisvd@nikhef.nl>
Changed-By: Dennis van Dok <dennisvd@nikhef.nl>
Description: 
 lcmaps-plugins-verify-proxy - Proxy verification plugin for LCMAPS
Changes: 
 lcmaps-plugins-verify-proxy (1.5.4-2) unstable; urgency=low
 .
   [ Mischa Salle ]
   * Build-depend on pkg-config to fix globus Multiarch problem
   * Use dh-autoreconf instead of autotools-dev to also fix FTBFS on
     ppc64el by getting new libtool macros (still updates
     config.{sub,guess}). (Thanks to Logan Rosen)
Checksums-Sha1: 
 e79f1756de34397144197a2c4701e7541c7eed1b 2202 lcmaps-plugins-verify-proxy_1.5.4-2.dsc
 0180af2dc77f25a73284c96ee4f67ef22a3c2a94 3712 lcmaps-plugins-verify-proxy_1.5.4-2.debian.tar.xz
 92a3862cb2caec546f7f19eb101e6809d406dfc7 45654 lcmaps-plugins-verify-proxy_1.5.4-2_amd64.deb
Checksums-Sha256: 
 a620202dd0d2870c3fce30587b14575c7d3c0ec0517888f2d3aa9b7a4530f13d 2202 lcmaps-plugins-verify-proxy_1.5.4-2.dsc
 bbb5f7be16a72096dace15974d0225f5f229d7594a8ebd167a868e5ed9ddc9b3 3712 lcmaps-plugins-verify-proxy_1.5.4-2.debian.tar.xz
 a1e9b84e95e8eea32d5c48302f36cc228276cd3fb1f75fd029f078faa8ae8b03 45654 lcmaps-plugins-verify-proxy_1.5.4-2_amd64.deb
Files: 
 1467dfca99d8c407acc66bc06d7a1c12 2202 libs extra lcmaps-plugins-verify-proxy_1.5.4-2.dsc
 5ab0456013bd14be3c297c45a5ea1d38 3712 libs extra lcmaps-plugins-verify-proxy_1.5.4-2.debian.tar.xz
 4526c5f8b6c2638de2b2be73256074c4 45654 libs extra lcmaps-plugins-verify-proxy_1.5.4-2_amd64.deb

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

iQIcBAEBCAAGBQJS4HLKAAoJEI7tzBuqHzL/YTYP/3H41ozpnJwZ2kWlN48EnMaB
a+GSRx91Q7O9pruun/KRuTJKgITjxaa2aMraaV4zs00Y3WDCxuUT1ioOjpjg0565
FJv8NdF2AZTSKV40GAKQpb8hXdSAz9oN1KsXQijTk4vaLIdmcOD7dLva3XovG2iK
3SXvVZJZc4699O+5EfGDLdXz7pqswtjbDjnY/QKud67dnGcxnQOJyyh0H9ngARAZ
R9pGWe+ofj2JsTDafyz2rnMQueiVmitt/hdCuePsPtuuK8x7EL34wtEBFlPH0Ibf
emTolDTMY0y7po4gXXZ7EixDxjyAkZQVXhyH6SEeGeAj7/k5OJNaKJIYhsLo4J3g
EKU4kMspr9tIbO9akoPUpNpGRXvQdy+icjb3JT5KDGRlq9OC/c7GGfroQBxNcWdR
Q7lFVWqvW7mO+TqDb7b+uPRyVzTMo3Zv0KwGEMQS8vD6cPufy/ppWQhGRvh0WJ/H
T4Rx3m0BbVR0FhxCB9Jy/bnrt3PAmx6yhdozZqb4iOnb049w/IXXxOsOMU3S5wjV
Dpi3UP2etbVILDrXM94h+pq74rrWJwzK1++CfXg8ZUbIMq9S/4wJAxtPw+c8SUE+
ZKNbeGOWjQvfjKPT64JWQor0Y6LzeIg10Gp2ZD/OdIrTcmcYivO3HASMX740iE+E
ohxJajVAv+4JCSoPV/xL
=i7Aq
-----END PGP SIGNATURE-----


Reply to: