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

Accepted libcacard 1:2.5.0-2 (source) into unstable



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

Format: 1.8
Date: Sat, 07 Nov 2015 13:03:01 +0300
Source: libcacard
Binary: libcacard0 libcacard-dev libcacard-tools
Architecture: source
Version: 1:2.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Tokarev <mjt@tls.msk.ru>
Changed-By: Michael Tokarev <mjt@tls.msk.ru>
Description:
 libcacard-dev - Virtual Common Access Card (CAC) Emulator (development files)
 libcacard-tools - Virtual Common Access Card (CAC) Emulator (tools)
 libcacard0 - Virtual Common Access Card (CAC) Emulator (runtime library)
Closes: 804289
Changes:
 libcacard (1:2.5.0-2) unstable; urgency=medium
 .
   * add remove-requires.private.patch to remove Requires.private
     from libcacard.pc.  We're not building static library so
     these are not used, but pkg-config wants to see the dependent
     .pc files.  Arguably it is pkg-config bug.  (Closes: #804289)
Checksums-Sha1:
 6735f00d299f9daee9bce439c2835f05ddd5978f 1693 libcacard_2.5.0-2.dsc
 3ae0f00c1f3d7b835be7c03b6fb34349119cd1c4 3588 libcacard_2.5.0-2.debian.tar.xz
Checksums-Sha256:
 b1993da469b1ee49d90247f0d9361e44f3c89280fc7ae528a698ad3b94fca986 1693 libcacard_2.5.0-2.dsc
 0ff0aa42a0f85efc96db56840c2660e6fb7b222461c5ea15ada79d6545ea3f06 3588 libcacard_2.5.0-2.debian.tar.xz
Files:
 7257b840e756ff6201cb0c02d2b9e15b 1693 otherosfs extra libcacard_2.5.0-2.dsc
 892bf2a0dfd27543fe0c22f8c8097eb5 3588 otherosfs extra libcacard_2.5.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWPcynAAoJEL7lnXSkw9fbNEwIAI0SRayABUpWLsB3F4cM2DOu
uFVR0gVkT1sPCT6niTJx7OekAaBAfcpSg+30FamUFhcx16w+0wgSv1ZXV+GPFVbj
UtHPKukO7YTec5s7u+cdMX7lKsa0QwcxPzMkfd/EVVPYCOlqXOT4HsUe3IuBpM+L
ppjf04rXgCFjaXgmkkx7rjGikx90uS64kFqYH/3p0yNHYAcR5shA4HGRlKcpG+Q0
sSg9nwUCqoEwADLfd80wA0js8JrNk/sm2cfETFEn1j1b4gdmu36XrVK0sBvGP1UN
kMPpg2fuo3sh7KiBIfl/UdZFkXNKN5xzJj+nRIZmS6WKKCwcVPKSz8Nd5TzArp0=
=qeHY
-----END PGP SIGNATURE-----


Reply to: