Accepted libcgroup 2.0.2-1 (source) into experimental
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 18 May 2022 11:19:48 +0200
Source: libcgroup
Architecture: source
Version: 2.0.2-1
Distribution: experimental
Urgency: medium
Maintainer: Santiago Ruano Rincón <santiago.ruano-rincon@imt-atlantique.fr>
Changed-By: Santiago Ruano Rincón <santiago.ruano-rincon@imt-atlantique.fr>
Changes:
libcgroup (2.0.2-1) experimental; urgency=medium
.
* New upstream version 2.0.2
Checksums-Sha1:
08113581190384664a0aa43a55e78a47d4bad9e0 1766 libcgroup_2.0.2-1.dsc
2072ce4a30c498a09af63a9032d297ce79f0c0c3 1162251 libcgroup_2.0.2.orig.tar.gz
99f8d3488439cfb74d08de7d6fd52859e516419b 833 libcgroup_2.0.2.orig.tar.gz.asc
af283205908abd87ff224ec48f9b78d74811c7a3 63808 libcgroup_2.0.2-1.debian.tar.xz
651e8ba2f6f48d1e4c1d75b3bd8e832b517303f2 6945 libcgroup_2.0.2-1_amd64.buildinfo
Checksums-Sha256:
2bf77d0ebcd3671f5b6a60f47e5e9647fd4f21ca41783e697013f1ed4752ba35 1766 libcgroup_2.0.2-1.dsc
8ef63b32e0aff619547dbb8a25e1f6bab152d7c4864795cf915571a5994d0cf8 1162251 libcgroup_2.0.2.orig.tar.gz
7d75313f7b4da8cd9a026cb939825f5dfb9e2e8a1bb09ba231e8a7ae7b1af9ef 833 libcgroup_2.0.2.orig.tar.gz.asc
e3119b875133b758e911844b68b13881c33568a371b2fdcfde5a94e7d6bdf6a7 63808 libcgroup_2.0.2-1.debian.tar.xz
e7488cf02e2cf700cd4e0c23e2622e265d8e108d815373738be0bca6702d5d9b 6945 libcgroup_2.0.2-1_amd64.buildinfo
Files:
90f97a61b58c41dfee5b2d6a58112fd2 1766 libs optional libcgroup_2.0.2-1.dsc
8df224a1c2f7de71f14ce4a7fb5a0e57 1162251 libs optional libcgroup_2.0.2.orig.tar.gz
4886f4aee28fc6aaf0a37bc605db19af 833 libs optional libcgroup_2.0.2.orig.tar.gz.asc
df1221338b82d365ccb672865352a568 63808 libs optional libcgroup_2.0.2-1.debian.tar.xz
afd686ed61c92de1c2d104cc6799041a 6945 libs optional libcgroup_2.0.2-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCYoTR/QAKCRBitBCJKh26
HUYRAP0TZwVk7XwhXEz1GM4SG8RluxQ87vJmEJa7Uf4fm9in+gEA4A/u+9r0PwwR
gxBni7P8Wf3ej2Lc3vyjRmMM2YgbLwQ=
=/Szv
-----END PGP SIGNATURE-----
Reply to: