Accepted kim-api 2.0~beta2.gita734d1-3 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 09 Feb 2019 15:59:09 +0100
Source: kim-api
Binary: libkim-api-v2-dev libkim-api-v2-fortran libkim-api-v2-headers libkim-api-v2-2 libkim-api-v2-models libkim-api-v2-doc
Architecture: source
Version: 2.0~beta2.gita734d1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Anton Gladky <gladk@debian.org>
Description:
libkim-api-v2-2 - Shared library for KIM-API
libkim-api-v2-dev - Development files for KIM-API
libkim-api-v2-doc - Documentation and examples for KIM-API
libkim-api-v2-fortran - Fortran files for KIM-API
libkim-api-v2-headers - Header files for KIM-API
libkim-api-v2-models - Models and model-drivers for KIM-API
Changes:
kim-api (2.0~beta2.gita734d1-3) unstable; urgency=medium
.
* [f9aa137] Use gfortran for autopkgtests
Checksums-Sha1:
724d902bf1fd03576e1f874a206db2bcda89c723 2462 kim-api_2.0~beta2.gita734d1-3.dsc
bcfc020ae9ab8c39b9a7599edcc0affc10138b7b 9480 kim-api_2.0~beta2.gita734d1-3.debian.tar.xz
4f7b10017288d679207f3ebdb0a884842988ddab 6419 kim-api_2.0~beta2.gita734d1-3_source.buildinfo
Checksums-Sha256:
029082579ffa3c0203142893b0b7a618e812764b7df290cfe6f7c6c44d266614 2462 kim-api_2.0~beta2.gita734d1-3.dsc
11db4271bd110b9b8939ccd90d587a4c74e83ab6d170245a2ae64479924768f2 9480 kim-api_2.0~beta2.gita734d1-3.debian.tar.xz
43de6f86b91fa8b48711fc2c313e96bf3e5b2d462a14ee3bc74a2ff2a6fcd922 6419 kim-api_2.0~beta2.gita734d1-3_source.buildinfo
Files:
0f1782caad083ca38e4d566ce73f66d0 2462 libs optional kim-api_2.0~beta2.gita734d1-3.dsc
1f85b09aceb77a220a262eb341fda917 9480 libs optional kim-api_2.0~beta2.gita734d1-3.debian.tar.xz
61d51604d6ef510d9478c5a1e683a73f 6419 libs optional kim-api_2.0~beta2.gita734d1-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlxe6s0ACgkQ0+Fzg8+n
/waeGg//fi3I3NbvOZlY9uQwpRElmOsvx2Tvaz2ACVmHEn5WHe79kN8ywKAZbUri
6NSRsC/Y3FDJr3Y+vmdwQg0POVfQMOoqE3lNji0GoB53MEPez0j289ebSFnrhjPg
7qkX3er1gVAJhZ/mvDfWaqMH+ZYk67EvtAG6Cbq/sQcQLhPLZWLXla1MKdSmDWXu
GazvtXc2YH1KNeWi3Dy8pdrvzN323C+SJGwjGLzOKhtD5w9TVIlVLQ2oD+TsxLRB
+1JG0eftMTw83KLhJ1GWpGbvuxcQbOFPUMS646WFpHsv2HXaPVd7FsfXPN7uErAM
50ujpMdcC1MkWy1gP+YwpCIyxviAQtm0D7uNYpGg5WikHPZEznYMwmCNtNW/hfhW
hNYya2JZyjHWJz4OIgCGQoF4sSFhTF5zCRIFvlVF9PR0eZjvSJBq1vdvnR/SuiND
6CKmyoLdMp7sfm7tllqDwlml4QYLbIklNTjCKQe8BIt03FVhbvzVcqGp43OM1kJ8
8eyhibOBR6+QZ1ba/UBf2kl3pEkJuJ6bO90l7w9jcnNBGYvxP8obBeING0K//ZDC
/sBTD1fHTvgLs8xVSGhK5GIAfFLpKqwtzf5bIXhnPEtxa3yQrrSdg3pYujei3Jyu
EZe8bB056CW6DjXsEsWexJOZXT0YRdF1BBrjfb3GJQVCX6N+CxQ=
=mJ25
-----END PGP SIGNATURE-----
Reply to: