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

Accepted seqdiag 3.0.0+dfsg-1 (source) into unstable



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

Format: 1.8
Date: Tue, 04 Jun 2024 19:58:53 +0200
Source: seqdiag
Architecture: source
Version: 3.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Alexandre Detiste <tchet@debian.org>
Changes:
 seqdiag (3.0.0+dfsg-1) unstable; urgency=medium
 .
   * Team Upload
   * New upstream version 3.0.0+dfsg
   * Use new dh-sequence-python3
   * Remove egg patch
   * Move to Salsa & DPT alike what as done for blockdiag
     (Reasoning in commit 9a83fc59ca2e57167a47bb3d2fa4740583de08cb)
Checksums-Sha1:
 c645b47a85d9107ff9d0ccd984c35c44915d0b25 2182 seqdiag_3.0.0+dfsg-1.dsc
 cab1ef56faf03844695845558ae1bcf0c4d89bc0 57760 seqdiag_3.0.0+dfsg.orig.tar.xz
 608b7fbf210b34bd1c0b251bbc95198a848cf8f4 4736 seqdiag_3.0.0+dfsg-1.debian.tar.xz
 b91a6df2639a44047ed188d9ee198c2754eb45a7 9024 seqdiag_3.0.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 cc7cc416a4f02fe31b5b9ec020186172664de6b158b4288a88a4dfebf94b1957 2182 seqdiag_3.0.0+dfsg-1.dsc
 3e7d5854f9a6b9853b51f90a40a647fa2be85be3d59934606ec52cafaf64e41d 57760 seqdiag_3.0.0+dfsg.orig.tar.xz
 1f0adb789f7b0dddbbe861b16259d9595d2d8217bf3c609f1d5272fa356d4e1a 4736 seqdiag_3.0.0+dfsg-1.debian.tar.xz
 f49a1753079de01db670c60a11ac9e73108a99afd7aa980095ca363074c79794 9024 seqdiag_3.0.0+dfsg-1_source.buildinfo
Files:
 eeca7ea879db8cf7c057633807ad503e 2182 python optional seqdiag_3.0.0+dfsg-1.dsc
 53c1680429fb3bfc2dadf70ac4b6962b 57760 python optional seqdiag_3.0.0+dfsg.orig.tar.xz
 d2849095d649fd04f44b20614991fdfd 4736 python optional seqdiag_3.0.0+dfsg-1.debian.tar.xz
 3c9289c94c14fb018bbf1676dd9cd857 9024 python optional seqdiag_3.0.0+dfsg-1_source.buildinfo

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

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmZfWHIRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBr98w//bJqbU9blYChmzgkARtHA0BaDQWAuLJp2
Br+8DvJLkNngpSOByAQd5hu+CnOFU7NNrK7ZAGRVq1qOV8kUYlXXCmy5DFjW+eDA
/BSL01fiiw0oSH76d55LG24jz9n78MxqaUQBdFViEsJkN2eX0ktmEeEXKcsPWLrr
i6DXT8+c4bAEQwbjC6BqSPEX8+bb42hlUJi3bAJEWQXVJ+XNt9qlCMmz9w8TlmwN
OQdKP0vtCtFt6FpUeT1MJaSfY/qesau5eXU/FLo3wWtIRICfX8/pqUSnRc1ywCr5
NSHrx/ikk/TVVVB0VUbKw49Xwzw4gyU7U6qsmBDgmyY7UunGj4hdtUVP7Vskwous
ty0czwgaaAkDSwLrge1jOSligvjNR392ogdxTwsocL5Fzwk6YBW+7n93kn4JnZmK
gMjZ7nPc+8mZGtQ0vGUWzq5dOYUHrEHtBvCDUi0JqXghv82udS1IYm4TNcki6kLW
bfszphT27UGm0+vsu4hvNxJKMfCIORTQfdty4rdNIkeRkLB+i41OUvMoovk1Ebfs
GUdKehrZLsurzvmWrdxDJ14Lf/R6HrUK6t97cT5bQxgK/tbM4bU+qe5oSZs0K1Yf
JcP1Hpr9weQiBTC1Fedjo/in01SMCn0PeFhP99ypZgLDroKLFRVlCOhrRaY5Yn8z
uhTrD6QUMC8=
=y/Cm
-----END PGP SIGNATURE-----

Attachment: pgpStHE5v0daM.pgp
Description: PGP signature


Reply to: