Accepted bit-babbler 0.3 (source amd64) into unstable, unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 24 Nov 2015 23:15:24 +1030
Source: bit-babbler
Binary: bit-babbler bit-babbler-dbg
Architecture: source amd64
Version: 0.3
Distribution: unstable
Urgency: medium
Maintainer: Ron Lee <ron@debian.org>
Changed-By: Ron Lee <ron@debian.org>
Description:
bit-babbler - BitBabbler hardware TRNG and kernel entropy source support
bit-babbler-dbg - debugging symbols for BitBabbler tools
Closes: 805979
Changes:
bit-babbler (0.3) unstable; urgency=medium
.
* Include a simple example script for reading from the UDP socket.
* Include the documentation for configuring virtual machine pass-through
in the binary package as well.
* Document how to deal with cgroups mandatory access control when using
devices inside libvirt managed virtual machines.
* Initial upload to Debian, Closes: #805979
Checksums-Sha1:
524819951f241c1c9c0344a42d1aa8a4e39ec7c5 1495 bit-babbler_0.3.dsc
27bc3813da138f36b191802e51b88e057a4c797b 278168 bit-babbler_0.3.tar.gz
fe438af0cea089dd70909ebb5f3301e87b1c014e 771372 bit-babbler-dbg_0.3_amd64.deb
c3860325ad0c69ed51266c975331956e2a8506ce 180834 bit-babbler_0.3_amd64.deb
Checksums-Sha256:
96e03d033ac7294419e8fdd744323bdc5ecdf86ed08dd6064d0999c0fb8b79d6 1495 bit-babbler_0.3.dsc
21dfe3c5c281a7a4008b5c314f45d34b3fb21b943976d805618eaa00b586df14 278168 bit-babbler_0.3.tar.gz
0c4310959aeb01165479ae4300bbea2431884b9dfd720835f906291fd2e85156 771372 bit-babbler-dbg_0.3_amd64.deb
8e41be7a1f8fce631c06e0b87673e0eb7b55657ef9093e0756ef8fc53be4a901 180834 bit-babbler_0.3_amd64.deb
Files:
3293e3622cb35f024ccc82279c02225c 1495 admin optional bit-babbler_0.3.dsc
b5d4b7e8ead40247fc7ac2973b9142da 278168 admin optional bit-babbler_0.3.tar.gz
9101c5deaa1655a79bb31f5372d1db60 771372 debug extra bit-babbler-dbg_0.3_amd64.deb
90de2320f74c4f681545e4f42fdbc812 180834 admin optional bit-babbler_0.3_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJWVIMCAAoJECSWn9pgwHEsZQ8P/j1bkZjknU7EQDQNqBSKi5hd
MEBGBn7DPmjDIYcGGY5GVtt7GrH3/CDC5xK+b5rhj0fEJWX36NVLMsx/57q4GvXc
etNsO8ZYajGGsnEfpfP1IXQOSIqcZGmh580mH771RqPoss6BJVa1K9qZHTP/qN6u
gzO2mElC1teBzRN9nLaP22/LgmSb8wENzyPTWCNtjxkMT+mz2ujQTeLaME8EZFcj
5VRHwVF8+3DnJ08ba/JjYgJK1yzSArQ8nRchPzE0zmbDYYBFXL5CXcm97/Q5umC0
hoWasqA3iN84odLOIPmaZhah+5jsF7TZmncMhJgr/Ql2rERaqm6JBaf/gh91FEwo
ki9YZ3faOUKNcSXreXgeKE3bOaiLWC9ZbojuAtKWQbiMaa0W8ghPfep4PMXUMJ2a
+QbylaiKzq9pxVP2nRmTxOY61pYwxMnWikZRJvyeRW4l8BzkzolkNxu/mvcdD8Gk
2VA4W3WfOq1sIW3mJmDq2DEaJSOr2vbUNKqY+Rf0CuwH6ibp9QcB7BRQqlRCISNl
pTGP3Cv2aWi7ze1fEJBvqKz/j53GMyFX46yu9ZpNXoMKZqOF3MTCJXz7e/ZkfJoI
mmbb5UHw9BEEIvIQZa+G8sctHXKcdoFmr8zsHsrRY/K48DSHXMb/2CI5agcUMEho
kw9VG4xVFdXG12m1E0gn
=lIhy
-----END PGP SIGNATURE-----
Reply to: