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

Accepted rust-async-lock 3.4.0-5 (source) into unstable



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

Format: 1.8
Date: Thu, 06 Feb 2025 12:35:08 +0100
Source: rust-async-lock
Architecture: source
Version: 3.4.0-5
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <dr@jones.dk>
Changed-By: Jonas Smedegaard <dr@jones.dk>
Changes:
 rust-async-lock (3.4.0-5) unstable; urgency=medium
 .
   * stop mention dh-cargo in long description
   * declare rust-related build-dependencies unconditionally,
     i.e. drop broken nocheck annotations
   * add metadata about upstream project
   * update git-buildpackage config:
     + filter out debian subdir
     + simplify usage comments
   * update watch file:
     + improve filename mangling
     + use Github API
   * update copyright info: update coverage
Checksums-Sha1:
 6c6966da98eaa3405e9a4e74c5bb1be6ba4cb79e 2544 rust-async-lock_3.4.0-5.dsc
 857784dd8ec235623550b5c1dff071b4da3cf248 4920 rust-async-lock_3.4.0-5.debian.tar.xz
 f26c3557282aee1fc060fc1e2a14ea74ae99005b 10388 rust-async-lock_3.4.0-5_amd64.buildinfo
Checksums-Sha256:
 ad661be1c0a833ff1bc9fd1ff18283cd0cde2f474c3dcc127b7678f80aaf8cf0 2544 rust-async-lock_3.4.0-5.dsc
 c66e7380358e0b6378063e4306e3b9d659589f2d1cc50e706af97f32487e67ff 4920 rust-async-lock_3.4.0-5.debian.tar.xz
 f91e101ef56cbb0bfd6bf49d73916b80cdff024e6d634a6c00ba5afd7af6c798 10388 rust-async-lock_3.4.0-5_amd64.buildinfo
Files:
 8fab75d5d8a58c7ac5f6be1917a641c9 2544 rust optional rust-async-lock_3.4.0-5.dsc
 a1f37f741a1502a71c6732fd57eb2c1b 4920 rust optional rust-async-lock_3.4.0-5.debian.tar.xz
 9648205902e43ccdb659e3cee6f3a877 10388 rust optional rust-async-lock_3.4.0-5_amd64.buildinfo


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

wsG7BAEBCgBvBYJnpJ6pCRAsfDFGwaABIUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmdsdnYrSNbe8IE7iRMFqIGsHu6+yx0sm2GE4EJDlc1u
WxYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAABvUQ//b7HH2I6ORsik2NL2ObFqKTTB
UcOs5Q/+LlhzeseUD9GiYdjPBdHTQpyDRhiea0SojEk2zk00V0XJ09qIz3eFXc2G
LArqr8p5X8HbVEzUs7N7RFT44ZR1ppEopjuRD0B99s4IPWkN9myzfhszpJLkYA6x
fuX5SkbvCZNfHXKBO7kltVIGUnnjblNL3U3jPPP5qjqOV7IkWvPyqomILN2ug1mn
n2PeALOwKeWCOW7u7ZOGd1RDmELxNn0rjPGjNd9u8L6U4Gu0CUP/pVDNpYf1mRQ2
Nh89Vt9CiNOlWfo0o+VOXHpEcvI+M8YqHZrzFIWpl9t2t6xa/gtzLHcDC3yBtG4z
CW6B/vGgoEQ/L8WCG8pQowY/v04CNWNx0xxUooAsWiCIT3ILR9lIrlxIknZ6/CDK
R7db6rEtwAM2aS0YlcyVtZwrD9dKefKDECqzHjiHzJhaHhHmnSCzsNJDrLkP4QBd
0/TX3wxFyE7zXBO33SLp4xjNyJcGNyY62IP01oAmlig2JcQuJZp3118hTxWw6CNp
ZfjJXGSnDBp2UU69/zyJBQDc1Q2BFDvEThut85XkYIGav6Jk3fikgiVEGwHWKXEP
Yc4T9eG3hOoXU8U4q3di8iFyLRN6mxek7+1LZKCJwBUN3WFlIXXHa29u9s3Zf9EZ
vjiseQN1LnekztEXWMQ=
=Y1p0
-----END PGP SIGNATURE-----

Attachment: pgpJxlBQC6zYF.pgp
Description: PGP signature


Reply to: