From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
To: Bastian Germann <bage@debian.org>,
XFS Development Team <linux-xfs@vger.kernel.org>
Subject: xfsprogs_6.7.0-3_source.changes ACCEPTED into unstable
Date: Sun, 12 May 2024 17:55:20 +0000 [thread overview]
Message-ID: <E1s6DPs-000EWi-Tm@fasolo.debian.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]
Thank you for your contribution to Debian.
Accepted:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 12 May 2024 17:03:34 +0000
Source: xfsprogs
Architecture: source
Version: 6.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: XFS Development Team <linux-xfs@vger.kernel.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1070795
Changes:
xfsprogs (6.7.0-3) unstable; urgency=medium
.
* Fix empty xfsprogs-udeb (Closes: #1070795)
Checksums-Sha1:
eb095522ba437f27eae583448be35e5952b91c54 2034 xfsprogs_6.7.0-3.dsc
12716845067eede5c50261c3052d9f7137c16e88 14884 xfsprogs_6.7.0-3.debian.tar.xz
8a49ac6c79aaea35cadf4a8bd2f14374ee0e77d2 6350 xfsprogs_6.7.0-3_source.buildinfo
Checksums-Sha256:
00c6fb0d0a734561583a3fc522aa5c5547b9af80cca217aad2e658a20cd0cade 2034 xfsprogs_6.7.0-3.dsc
e1890152c36827dc0a19183e5e706346d51b8b4e85f1993ea5451e76b7225f10 14884 xfsprogs_6.7.0-3.debian.tar.xz
86f8a32b063dcbaba71d1510e94d95d83713a0cc2bd28fe40764235b1465bacc 6350 xfsprogs_6.7.0-3_source.buildinfo
Files:
bcffa221aff4395099a8ab4523e29e57 2034 admin optional xfsprogs_6.7.0-3.dsc
6f31e1d62cc2e6945239c2e28461a976 14884 admin optional xfsprogs_6.7.0-3.debian.tar.xz
3ed5f4f3968c59720aa857926f251ed1 6350 admin optional xfsprogs_6.7.0-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZA+NMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCXDC/96k/V7dLlqlvhhevTYdZLwxfmlwNhGQ1Lt
SCrrIOtcSEvks5vR+XNVfCvgtiDTRf2ymr5xuMzq+GEbT+L25j2+yqBdLIDSJDn/
bpAJF7RWEFZSzzXYfnwFymeJeaevDmC+6dE7M97SwKgxgozOJY1jL48Sa4JQDOv1
Pfmp17w8vyNoSi1KtNhSB2MLbtzCNq2ok/eQ37k41M+2rW1rLe569rXJBViEfepW
TJrX4gyKJgV1IKN4A7VoC5Fqb2lyzDTNc7hcOe4R/AF1uaBbuA3Ca+9tstK/2eBm
4LnXwLEY8J7D3BSPB0ApUSUYhVvqoSvd3wDrc+i9puZ+/VNQehWO6S4tpfHciuz/
RMDm2t5N8P1Wbvvw+Yrdnvh1O1LniJlMPhYGqxRf1AbziDIFmow8U9CDohk1ho3f
Xq0aD+LzAm+94ebCHxhtDnWSJr97dx3cLLTC8PsC7phlg/QcxAvfFSVtAcfAOjNI
R+tsLBEJ9o5Os3RwT/pSlJFiXgXmpqU=
=DtC9
-----END PGP SIGNATURE-----
[-- Attachment #2: Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2024-05-12 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1s6DPs-000EWi-Tm@fasolo.debian.org \
--to=ftpmaster@ftp-master.debian.org \
--cc=bage@debian.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.