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

Accepted grpc 0.11.0.0-1~bpo8+2 (source amd64) into jessie-backports



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 23 Sep 2015 06:36:30 +1000
Source: grpc
Binary: libgrpc-dev libgrpc0
Architecture: source amd64
Version: 0.11.0.0-1~bpo8+2
Distribution: jessie-backports
Urgency: unstable
Maintainer: Andrew Pollock <apollock@debian.org>
Changed-By: Andrew Pollock <apollock@debian.org>
Description:
 libgrpc-dev - high performance general RPC framework (development)
 libgrpc0   - high performance general RPC framework
Changes:
 grpc (0.11.0.0-1~bpo8+2) jessie-backports; urgency=unstable
 .
   * Build backport against stable, not unstable
Checksums-Sha1:
 5a671048872de16606e1d2cc3ec75ad9f8ec4b47 2018 grpc_0.11.0.0-1~bpo8+2.dsc
 0217cf451a5a8c6c0b97897602b81ccb89dbc07e 2892 grpc_0.11.0.0-1~bpo8+2.debian.tar.xz
 b2d0e1343494f94e8212eaddabd019bbdc7d4c9c 237118 libgrpc-dev_0.11.0.0-1~bpo8+2_amd64.deb
 82fb4f3f8b484a33756aff2ef9c14d470a400b76 179236 libgrpc0_0.11.0.0-1~bpo8+2_amd64.deb
Checksums-Sha256:
 3a76e3d99d6dad378e84169e71efd7d48388a79343da44effee059207484218d 2018 grpc_0.11.0.0-1~bpo8+2.dsc
 1f56d490c88b9432221d3802a256f0d3f8621a68588a208e23b8079c938903f9 2892 grpc_0.11.0.0-1~bpo8+2.debian.tar.xz
 b57f92ab618ce1baca7d3d9f8a320c4023a94ffe6ec0b3a6f33173c0d673b653 237118 libgrpc-dev_0.11.0.0-1~bpo8+2_amd64.deb
 5b4c58c54c2c92fbf49f9f0b8fe00502f0137514abe1b9a1591294fa294132d3 179236 libgrpc0_0.11.0.0-1~bpo8+2_amd64.deb
Files:
 d99af96e197f3e8c1f39d0987f0075bc 2018 libs optional grpc_0.11.0.0-1~bpo8+2.dsc
 a778b8d7c9cfb7340784a3fcc05bf130 2892 libs optional grpc_0.11.0.0-1~bpo8+2.debian.tar.xz
 620ca4ad51901c7e749250e312d1756a 237118 libdevel optional libgrpc-dev_0.11.0.0-1~bpo8+2_amd64.deb
 5822cc2a1dcf5e63f3491030c11dfce4 179236 libs optional libgrpc0_0.11.0.0-1~bpo8+2_amd64.deb

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

iQIcBAEBAgAGBQJWAcH9AAoJEFHf2Ts++3nv6VQP/Artbs3JV7CUr5UCu2azDvM3
lCPY5bO7ClHh2sqZkxxmc2Q3P0QtFh5kf0FRQysalJHM93GNKir9oQOBSwgHU9pn
OnJxFlEbmXiu/rOSTZD9COxy19Q37BUBL5mUH17bEjOjbXXnASNXll8RlSVuf24K
mS+M4gtUtcJe+ZMVbZjK0fsHmNTcZsmEsYUGO0U9K03Z1w9mB5T2ZoonNew3gTPi
JPMZMh6RM6TAIuiXe9lWCgRarSONiLimh8tNKJT65EJXmUjHn+8riByTSdhs4nRb
IiSVquDA9HeQIjWC3HzOyzlYL+/LDSR5TqWRW1a0CSRdXOI456bL1ooYZBUi/G//
8ZvmuBcW00TyJoiofGI2lT2LvFeWeAnou4qkOTUkQE6tCKY29b8gix7WUhrjuISG
SFeljIHVxXysdu7zJ6FRoZHEhElxO9BPFVttmImwJEdcgt3xemX9Fcl0CqvNUoh6
kYKazYqYYI5W0ehUKxVZ9uxIEzMNxJ9NTc98ONQ72b7RfEJJhAHmmja2LCUKpZRe
kTX4Tn0VlXkFzSqhI6UQwtqE9t8UFCU1ErV/E1jwzAuLMBgMeoPTadagcuuOomGD
ryflShJDuwnBgAXaneUgMDme+ZJ+gz3n6bSWbsHUPmYSBqpuVd30Ubq8xtQ0od+Z
hNN4ZPAxtilAKlWtfxvQ
=0Y0M
-----END PGP SIGNATURE-----


Reply to: