Accepted datalad 0.2.2-1 (source all) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 20 Jun 2016 17:47:16 -0400
Source: datalad
Binary: datalad python-datalad
Architecture: source all
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team <team@neuro.debian.net>
Changed-By: Yaroslav Halchenko <debian@onerussian.com>
Description:
datalad - data files crawler and data distribution
python-datalad - data files crawler and data distribution (Python 2)
Changes:
datalad (0.2.2-1) unstable; urgency=medium
.
* Fresh upstream release
Checksums-Sha1:
bf7b3bfd357d8c74f452dbe7e91c9b7e449595ee 2400 datalad_0.2.2-1.dsc
cc9960b2b63360d60367955c036db33677761c5e 369714 datalad_0.2.2.orig.tar.gz
6a5144367ce6435707b18e77fdcf5fb470e574ed 5268 datalad_0.2.2-1.debian.tar.xz
8b047d8245cb028fcebd9efd5acf1c723cdf7083 27610 datalad_0.2.2-1_all.deb
4484edfa72f7d9a76751748e98396b56f429af16 250618 python-datalad_0.2.2-1_all.deb
Checksums-Sha256:
471d0c261ecbaeaf2c3d1b5e30797b20a1f06cf72558edf056340f87d31bdfaa 2400 datalad_0.2.2-1.dsc
9bfafcefea73f9142f7e6716c9a2ba616e4fb97f45ff0b27119f8b74d1287ed5 369714 datalad_0.2.2.orig.tar.gz
4304560ecf545bf64fa13b7352c05dad4e9eb21201da732e59acc72245929d1f 5268 datalad_0.2.2-1.debian.tar.xz
1dfa4c728cbb0733486d1a4e83c48c227d6c8cc6540ffda7018492977a8ded28 27610 datalad_0.2.2-1_all.deb
f4ab0dc6a7758c0c5ebc9bd3bb1bd46433bcad6887207d7739d905bf7394abc6 250618 python-datalad_0.2.2-1_all.deb
Files:
71ded8e70b50c4d0bd4a7bc8638d83b8 2400 science optional datalad_0.2.2-1.dsc
84852c066b5c4a9a4d9701bb8cc21720 369714 science optional datalad_0.2.2.orig.tar.gz
4ba3846c42266b53ad0199dc132dfeb1 5268 science optional datalad_0.2.2-1.debian.tar.xz
016c7916ea4621ff47248d893884135d 27610 science optional datalad_0.2.2-1_all.deb
c95cbd03f93e500b603637baf35a4ff7 250618 python optional python-datalad_0.2.2-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJXaKDtAAoJEKLeI1Bi2jP6Zf8QALlAeG5UbIk5xdRkxQf1yk98
GuSi/LBj7sOGkYutvkKFLmcekEdBS66bl2OIGdhTY4GR5WsxkMCyi5hVoraLE7u4
PBUmv4AkjHnm/4+BnKO3VqnI7dYjvdAtgK79MzL4z891Sz3PzQq7PK1orMgr+Owm
GEEbXWRK1DmkiuaVkJHgRhle0eBuMDJkWpRut9i/5FuJDl5z6INwl0rlq8/3sfoO
fHLMf+bBRKChSzBdVk82t+WIswd1MbctBUsEr+rdMS8W30TBOS8HoGz9J5VoCTGa
7U5n7IxL7YVsCVRkUxS5m0UykHmy9JBQOjB8wVxIdUy7Emoy7tI8BAZiANnSbJ39
Kfn4QCmLyRacXuDY77f9te/0ODZXaPbvvlRG0ti9ZvVvoptyLQO1nrVIVJBrOT7x
oH8jSbO+utOlMpJLEkN94WCrA6tWHoEo5TfYzrfIsWspRS+qdu/Ln0nixDm6xDre
Cy6jxTwUl574XUIXF/CTdwi1AfzXNuJCS8+ol8/OttZ7WVVbjBQxpLbfcCK8tUa4
b5V7v0fs256H9KiidP8rExoBgcNwhYHDM21GB4H7kz4VPPjoIgJ0YpX6bTW8jQ9p
1hTEoGNN0PNWfbcQdnP7jdDEuWhQSiviMBjRjKh3HEXspVlA2DYV+SlKHAUnsx1S
splWTlruFa17rzYW1xK4
=ctH0
-----END PGP SIGNATURE-----
Reply to: