Accepted ros-ros-comm-msgs 1.11.2-4 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 29 Aug 2016 23:36:48 +0200
Source: ros-ros-comm-msgs
Binary: ros-rosgraph-msgs libros-rosgraph-msgs-dev python-rosgraph-msgs cl-rosgraph-msgs ros-std-srvs libstd-srvs-dev python-std-srvs cl-std-srvs
Architecture: source
Version: 1.11.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Jochen Sprickerhof <jspricke@debian.org>
Description:
cl-rosgraph-msgs - Messages relating to the Robot OS Computation Graph, LISP binding
cl-std-srvs - Common service definitions, LISP bindings
libros-rosgraph-msgs-dev - Messages relating to the Robot OS Computation Graph
libstd-srvs-dev - Robot OS Common service definitions
python-rosgraph-msgs - Messages relating to the Robot OS Computation Graph, Python bindi
python-std-srvs - Robot OS Common service definitions, Python bindings
ros-rosgraph-msgs - Messages relating to the Robot OS Computation Graph, definitions
ros-std-srvs - Robot OS Common service definitions, definitions
Closes: 835576
Changes:
ros-ros-comm-msgs (1.11.2-4) unstable; urgency=medium
.
[ Daniele E. Domenichelli ]
* Add missing build dependency (Closes: #835576)
Checksums-Sha1:
c5ac705c504e5ac33642445db3656ceb43f8ec21 2774 ros-ros-comm-msgs_1.11.2-4.dsc
110fdc2c05b6ddb22d28ee65b5bc36bfea2bf5d1 3724 ros-ros-comm-msgs_1.11.2-4.debian.tar.xz
Checksums-Sha256:
0b89a58be223467fb59c7be4b4368af679d80416291d8efc3ef4b5864ed6a2a2 2774 ros-ros-comm-msgs_1.11.2-4.dsc
f235f94a206a569a66e9be9156b660fb0dcc0fe09ff93eedaad86cbab2b59cda 3724 ros-ros-comm-msgs_1.11.2-4.debian.tar.xz
Files:
9c7f20d8583c8bf5d37b6d0177be88f7 2774 libs optional ros-ros-comm-msgs_1.11.2-4.dsc
9f4eb36d65c064215c4e42766c7bf859 3724 libs optional ros-ros-comm-msgs_1.11.2-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIxBAEBCgAbBQJXxKsXFBxqc3ByaWNrZUBkZWJpYW4ub3JnAAoJEFv/3MJY5pQz
9h4P/3y1iCJTfp0ZfBrlOQbvO9F6Hy8ah/royNGJZxZ13slhj8wGEVv+XrJ5IPpa
n7heAWr1mwvG41afBOHLof6AnoJFAIS4Unqb0+akmhHT7/A/LDZaiyN12ctepvic
FguG0dwJtCEgp4v3LM6miRjoWLgintKUeXaoCYBnt9m81kNUrTPnUgJ+lEvgtqTg
EX/nZ/h7JvVF2rZeQZ2HD3cle7JYKRHOdNqq3Obbzk3P0lZv/Bn+Qrn+hrOt27JQ
NMzU58/0BTHBy7kLB3Kq+dcuEKREpeBLYAH7vpC9XbfkowAo7ZMTRtDnoarw99Jl
MjeKBPG/pkR5xasciPvarqOaevfuGOp/gdZHP6dprK6H38KogI8NCa49sbM8OZ4j
1NeSOIhu81Cr0oPWEC7MPiLA6R81BQWDer71uRDcwpJPmWL0vcazk0jIplF790DI
gWeV3/WyJ5x4dHQ2eVZ0bGS2yYU5V4KN24Vwqvqga0VCUifa8eGMr2UYi6hr+Dbz
HAeX6T5JS1E8x88q0iypfw3fjQSioYSaWom+xKOAx0m8/B2U/CbXeD/hTC/Pfe9N
CEy3OVwkHX6mGUHl8hAcB5gSDQUaUnoI2WqrlsvbnESk3oDvO1VJUA93i864HlnJ
/wzg9TuMcG0X/zCH+t6oCUbNo+jUTszTAFbeDKuprAjOTP4X
=25Da
-----END PGP SIGNATURE-----
Reply to: