[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted remrun 0.2.3-1 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 04 Nov 2022 20:55:25 +0200
Source: remrun
Architecture: source
Version: 0.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev <roam@debian.org>
Changed-By: Peter Pentchev <roam@debian.org>
Changes:
 remrun (0.2.3-1) unstable; urgency=medium
 .
   * Adapt to the API change in python3-cfg-diag 0.4:
     - bump the version of the python3-cfg-diag dependency in
       debian/control and debian/tests/control
     - note that the test suite needs changes that are included in
       the new 0.2.3 upstream release
   * New upstream release that includes the cfg-diag 0.4 support changes.
Checksums-Sha1:
 0cc6a796246df686d101ba3c08f6a71f9626700a 2513 remrun_0.2.3-1.dsc
 ed8200b19760748a7a82f1dd8f7640fcebed0549 21136 remrun_0.2.3.orig.tar.xz
 ddb6f6e6b5f6486a603535a14cffdeee01b0ad50 833 remrun_0.2.3.orig.tar.xz.asc
 afdca280b4bc48ac886a324518502bd7b5da08fa 5240 remrun_0.2.3-1.debian.tar.xz
Checksums-Sha256:
 4c41b753991c64fc1a50bb728cf105569f73e977ae2e1a8375f65dba943aee06 2513 remrun_0.2.3-1.dsc
 9e3ac59cc6476bf3fc1dc97c4d2aeaad6a5ccbbe641373f34d250285eae9de3c 21136 remrun_0.2.3.orig.tar.xz
 17a90a2494bc5b223108f960e9bc58023a258b19811a2676a95d715359f86110 833 remrun_0.2.3.orig.tar.xz.asc
 61816cc4dbc5b4c9f5b9aa4ab568ea765a841640563634e51e49a0895a2d5763 5240 remrun_0.2.3-1.debian.tar.xz
Files:
 5f1c324d3104f1804fdd1f76acdfbddd 2513 utils optional remrun_0.2.3-1.dsc
 d09b792b597f49003f14e242c3dba2f4 21136 utils optional remrun_0.2.3.orig.tar.xz
 0ceb1837c7dabe4908ce83c286048f1f 833 utils optional remrun_0.2.3.orig.tar.xz.asc
 322bbf1b50990eb4acc6e755287e4858 5240 utils optional remrun_0.2.3-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmNljKYQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffE97zD/wNy8CW3yafb11HMJrMUgwlKmf0eI3VpvS1
lKE3HgrHyisU5hYT5Wv2/aS3wrb7Dq3sDq9SmDZAmqxAlS8b8+7FBNUPr/nyVTBj
9L6rUseyZe9iWW1kzwR5wRxDs9uaaotTN6ZRaEC0fbNKx6TlgiL1SwkKgtiBj2O8
oXQ5OfgyxNV4zDEE9MOH8v6KmgxoLNhzPAZPZStqzdH+VLPKG5AnBi2lReMpGY7R
j1xi4PScnF5HUCJ8yJrma3/xL2IP3d3IVUxQCfA1YP/NTx7Yslx0poC9s4+rLUlT
QRPN8bNkdemOuG6d+YRjOX8/EbUZpG+tWysKN76rlIEcx2jys1BagOrRNaywpzjn
lfiDwSxZBOx8MHUOqIDiYC8qCx4w7FhV92Sa8MSBXOogxWUedVzPclcmOU01coJ/
Qfn0WCFqRi7ElAoPaTUuAFFDaOMbFjG7fe4ogy1k1F35ee4dvJvs/QfkER/Vc6JV
nP44TmedCZyGuOgEFx5hW2kmFieoI/5m7EpTAb0M2W5NJClVuxzT0SB3323XWucx
F/mGpsdH9ZMmQgk0RP1j1piG8YxKNa/MAniJPamvF73N7dBCGJoBb4mcywlExmy/
NsOEzYQ1v+s58LXyxAyxSl3MRZXvVd8uD9WspZ2HI79umTLdaQBEt+FR4RRAdKaZ
vaDXu7GZcg==
=1HUx
-----END PGP SIGNATURE-----


Reply to: