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

Accepted nvme-cli 2.10-1 (source) into unstable



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

Format: 1.8
Date: Mon, 05 Aug 2024 10:39:08 +0200
Source: nvme-cli
Architecture: source
Version: 2.10-1
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <daniel.baumann@progress-linux.org>
Changed-By: Daniel Baumann <daniel.baumann@progress-linux.org>
Changes:
 nvme-cli (2.10-1) sid; urgency=medium
 .
   * Uploading to sid.
   * Merging upstream version 2.10.
   * Bumping libnvme build-depends to 1.10.
   * Removing avoid-unsupported-arm64-instructions.patch, included
     upstream.
   * Removing fix-ftbfs-t64.patch, included upstream.
   * Adding patch to remove missing manpage in meson.build to fix FTBFS.
Checksums-Sha1:
 41250b4319246c2424a2a6a2e2a63e1af864efa3 2164 nvme-cli_2.10-1.dsc
 d7ff9da5124b1b8ca7497993d6234d51b51e4af5 579384 nvme-cli_2.10.orig.tar.xz
 6f378451b404bade188736a8e8d4fab7196fb59a 5980 nvme-cli_2.10-1.debian.tar.xz
 40cfcda63c5021a09baab56a76bd2a0363261b7c 8891 nvme-cli_2.10-1_amd64.buildinfo
Checksums-Sha256:
 83e6f87c829332064ddec6161300205bf271395f1840a755b67b4c1c1354a116 2164 nvme-cli_2.10-1.dsc
 24cc80d42b5b5daebedc32b90599c4d57a830f2b5a16563683d416b77951bc9e 579384 nvme-cli_2.10.orig.tar.xz
 7c00e746d7a64a7e0d77a1f7c807cc7bf76ee8492472f681822c1548b44bd877 5980 nvme-cli_2.10-1.debian.tar.xz
 8bd7bdc04b4a4adeffee1264f3bf5a71ca0ff141665820e9282f9722258a2cea 8891 nvme-cli_2.10-1_amd64.buildinfo
Files:
 2a7110e73f1a33ca165ede61b3c533fd 2164 admin optional nvme-cli_2.10-1.dsc
 62c83818f66c9f5b054e40d95789e142 579384 admin optional nvme-cli_2.10.orig.tar.xz
 5a9c482f6de872bee72b3877e9ce718d 5980 admin optional nvme-cli_2.10-1.debian.tar.xz
 6f8bedeafb24bf4fb91b30aea0308125 8891 admin optional nvme-cli_2.10-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmawkokACgkQVc8b+Yar
ucf5ww//V5XYNVxFGBoiaQTmTeTt5Jca5SEx2Idz4E7c94ZvVeM1Csj9l3KnLvry
+5jaXkOq5NAlobMJXIWYJrxg8uOgDDstqPNe9khYzQ88iB9vgu3+Wnt6mW1iWAzf
CTYDHH1qs28gXXOgr2Y/LFGeMLyzNbMSaaGP1n6qVRrTyRrbABOl8O82v7VD0ZXp
7O0dMGeQUFzx0k10oZ500xj4BdVTB2XLSQk1i6zX2RAgTX0+TH2fJCl7MimwSaJG
ywTcpUdcA2wPs7Di7O1CZ9CpfQ2SOCU6TBpdopX0rF902E9B5T7VkEmHE+GhSLXF
FoxsxU5C+tZZwEUQNeAbK5jDPtBdcomNvqVFQCyOpoeOhwSmAKSSG+9osJWmIST2
wc+4QhP3xGzJw8LUED3Xy1uvGBQNxbkMK+LA7n+7MJQLhNONH8dx3VPqfy702qQD
octBo3PRaXeFFFoUXccSVmDQBJa9a3mnJ8XBVIwZcSH1clJ4TIuqeIpXZJCvURVi
+VTpJOStJrrZ7NRMGewhwCHwwIrZjfg6BMD+4CgCMQGz09X1OQ5U6laAPxNNa4BG
9PxWaQhTOtFBcST9TSQcuLLe0vyptznIOU9e954lnVKnpcU1ZXcb4INEuwmmI8im
i1QrM1ix8SID858e/mn2Pjk+UMn+kC1GYbrXgPUrRgH8gKX1W5M=
=pslx
-----END PGP SIGNATURE-----

Attachment: pgpPUpMq5TgoD.pgp
Description: PGP signature


Reply to: