Bug#1095917: marked as done (ITP: nvmetcli -- CLI for the kernel NVMe target)
"Debian Bug Tracking System" <[email protected]> Tue, 04 Aug 2026 18:01:02 +0000
| Newsgroups | gmane.linux.debian.devel.wnpp |
|---|---|
| Message-ID | <handler.1095917.D1095917.17858664373571411.ackdone@bugs.debian.org> |
This is a multi-part message in MIME format... ------------=_1785866462-3571567-0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Your message dated Tue, 04 Aug 2026 18:00:36 +0000 with message-id <[email protected]> and subject line Bug#1095917: fixed in nvmetcli 0.8+20260713-1 has caused the Debian Bug report #1095917, regarding ITP: nvmetcli -- CLI for the kernel NVMe target to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) --=20 1095917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1095917 Debian Bug Tracking System Contact [email protected] with problems ------------=_1785866462-3571567-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by bugs.debian.org; 13 Feb 2025 18:33:53 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02 (2021-04-09) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-18.6 required=4.0 tests=BAYES_00, BODY_INCLUDES_PACKAGE,HAS_PACKAGE,KHOP_HELO_FCRDNS,SPF_HELO_NONE, SPF_NONE,XMAILER_REPORTBUG autolearn=ham autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 37; hammy, 149; neutral, 39; spammy, 0. spammytokens: hammytokens:0.000-+--H*x:12.0.0, 0.000-+--H*UA:12.0.0, 0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug Return-path: <[email protected]> Received: from triton.nivex.net ([45.79.150.236]:38550 helo=mx.nivex.net) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from <[email protected]>) id 1tie23-00DaTd-Mo for [email protected]; Thu, 13 Feb 2025 18:33:53 +0000 Received: from gemini.home.nivex.net (unknown [IPv6:2605:a601:a6af:6503:5054:ff:feb7:e64]) by mx.nivex.net (Postfix) with ESMTPSA id 499E41F8CF for <[email protected]>; Thu, 13 Feb 2025 18:25:15 +0000 (UTC) Received: from athens.home.nivex.net (unknown [IPv6:2605:a601:a6af:6503:a6ba:dbff:fe32:4c6b]) by gemini.home.nivex.net (Postfix) with ESMTP id 4DD01401E5 for <[email protected]>; Thu, 13 Feb 2025 13:25:13 -0500 (EST) Received: by athens.home.nivex.net (Postfix, from userid 1000) id 3201C5FDDA; Thu, 13 Feb 2025 13:25:13 -0500 (EST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Kevin Otte <[email protected]> To: Debian Bug Tracking System <[email protected]> Subject: RFP: nvmetcli -- Command line interface for the kernel NVMe target Message-ID: <173947111317.9185.8142429171025965202.reportbug@athens.home.nivex.net> X-Mailer: reportbug 12.0.0 Date: Thu, 13 Feb 2025 13:25:13 -0500 X-Greylist: delayed 510 seconds by postgrey-1.36 at buxtehude; Thu, 13 Feb 2025 18:33:51 UTC Delivered-To: [email protected] Package: wnpp Severity: wishlist * Package name : nvmetcli Version : 0.8 Upstream Contact: Christoph Hellwig <[email protected]> * URL : http://git.infradead.org/users/hch/nvmetcli.git * License : Apache 2.0 Programming Lang: Python Description : Command line interface for the kernel NVMe target Long description: This contains the NVMe target admin tool "nvmetcli". It can either be used interactively by invoking it without arguments, or it can be used to save, restore or clear the current NVMe target configuration. Relevance: This would provide feature parity for NVMe as we already have targetcli for configuring iSCSI targets. Maintenance: I imagine maintenance should be relatively straightforward as there is already a debian/ folder in the tree, albeit needing some updates to modern standards. I am not a Debian developer so my perceptions may be flawed in this regard. ------------=_1785866462-3571567-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 1095917-close) by bugs.debian.org; 4 Aug 2026 18:00:37 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-114.2 required=4.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FVGT_m_MULTI_ODD, HAS_BUG_NUMBER,MD5_SHA1_SUM,PGPSIGNATURE,USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 60; hammy, 150; neutral, 94; spammy, 0. spammytokens: hammytokens:0.000-+--HX-Debian:DAK, 0.000-+--H*rp:D*ftp-master.debian.org, 0.000-+--UD:debian.tar.xz, 0.000-+--H*r:sk:fasolo., 0.000-+--H*MI:fasolo Return-path: <[email protected]> Received: from muffat.debian.org ([2607:f8f0:614:1::1274:33]:54262) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <[email protected]>) id 1wrJRM-00Ez5F-2v for [email protected]; Tue, 04 Aug 2026 18:00:37 +0000 Received: via submission from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=fasolo.debian.org,[email protected] (verified) by muffat.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <[email protected]>) id 1wrJRM-000iff-2a for [email protected]; Tue, 04 Aug 2026 18:00:36 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ftp-master.debian.org; s=smtpauto.fasolo; h=Date:Message-Id:Content-Type: Subject:MIME-Version:To:Reply-To:From:Cc:Content-Transfer-Encoding:Content-ID :Content-Description:In-Reply-To:References; bh=Grl1jRWgibl6HL0A+puayWBM2Kazo1FXBh5359pIkzM=; b=ITmfc2MF7B5iyUrmC7KiF81Pmx OVq4mdx5+Z3tc3zGVIoufWVVGCfKKninY24Gn6m2oR4h+nFnDNOctUO0K/r6DBxDjQlSq+bqqYeeP vpRORV1RxF6edf4QOASW81j6iFhahCTG+xrwzNuA6pMLg1nVKt60HWiFXdfEvIQV7Lq6hFb0actUL /Gttm9389J5WGhIZmm5Aamn6MsVw30nKux2Lyv+ZvvBL845FcI8tEtizt7cdPUdX7Tlw1CpHHVQyL /0iEPKTF5ZLzdKSkpvru3csjg9SsKlo1tDxxQzUmYnBCVnSWXGhO4zRbIoAiW9Gfh0h8vHC/ZHWPv w31BuAdA==; Received: from dak by fasolo.debian.org with local (Exim 4.98.2) (envelope-from <[email protected]>) id 1wrJRM-0000000BfJS-01b0; Tue, 04 Aug 2026 18:00:36 +0000 From: Debian FTP Masters <[email protected]> Reply-To: Daniel Baumann <[email protected]> To: [email protected] X-DAK: dak process-policy X-Debian: DAK X-Debian-Package: nvmetcli Debian: DAK Debian-Changes: nvmetcli_0.8+20260713-1_amd64.changes Debian-Source: nvmetcli Debian-Version: 0.8+20260713-1 Debian-Architecture: source all Debian-Suite: unstable Debian-Archive-Action: accept MIME-Version: 1.0 Subject: Bug#1095917: fixed in nvmetcli 0.8+20260713-1 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="===============3494215375948958637==" Message-Id: <[email protected]> Date: Tue, 04 Aug 2026 18:00:36 +0000 --===============3494215375948958637== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Source: nvmetcli Source-Version: 0.8+20260713-1 Done: Daniel Baumann <[email protected]> We believe that the bug you reported is fixed in the latest version of nvmetcli, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann <[email protected]> (supplier of updated nvmetcli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 31 Jul 2026 15:23:31 +0200 Source: nvmetcli Binary: nvmetcli Architecture: source all Version: 0.8+20260713-1 Distribution: unstable Urgency: medium Maintainer: Daniel Baumann <[email protected]> Changed-By: Daniel Baumann <[email protected]> Description: nvmetcli - NVMe management tool for the kernel NVMe target Closes: 1095917 Changes: nvmetcli (0.8+20260713-1) unstable; urgency=3Dmedium . * Initial upload to sid (Closes: #1095917). Checksums-Sha1: 7bf6913dbd91782325316a0058b42beeb5ec2957 1362 nvmetcli_0.8+20260713-1.dsc 1737882e5d72522707b5d5f94210ce76027c410d 23888 nvmetcli_0.8+20260713.orig.ta= r.xz c657a1b3ba76dfb7f1a1a981aa92aa27ba4e967d 1796 nvmetcli_0.8+20260713-1.debian= .tar.xz 4f0e748c566301fcc5ffba2152381898828a3966 20812 nvmetcli_0.8+20260713-1_all.d= eb f0d5655bb304be70ff6a9467adb56b32647d323a 6347 nvmetcli_0.8+20260713-1_amd64.= buildinfo Checksums-Sha256: 98ac1a466297afff0ac308182a41be95036be0da505934e1e7ad7c02ab4efb53 1362 nvmetc= li_0.8+20260713-1.dsc b9136328d50a7b2607871fe4208ac2aba6f519776ca2441cd04d3040496fcd62 23888 nvmet= cli_0.8+20260713.orig.tar.xz 367d4ddc22919cb9659837d25cb375255b4eac7f7369b76d9edded02229055fc 1796 nvmetc= li_0.8+20260713-1.debian.tar.xz 8b43fb2db619e49f700efd9d262879269730fbb6f9f7705ef68f577d61471238 20812 nvmet= cli_0.8+20260713-1_all.deb 5cc59a2149bca2c0e90cff44bcd40dd60d6654e23eb5525a4dd4d12f10f1531c 6347 nvmetc= li_0.8+20260713-1_amd64.buildinfo Files: e261080f4a8a7b327c9c3c56be3d7c41 1362 admin optional nvmetcli_0.8+20260713-1= .dsc d4ef32d5c084ef21e6ad9426cf797a6a 23888 admin optional nvmetcli_0.8+20260713.= orig.tar.xz 3ab09d3992af2eb60e45187f776ad001 1796 admin optional nvmetcli_0.8+20260713-1= .debian.tar.xz b97d0f737723699aeb13683c19d6d530 20812 admin optional nvmetcli_0.8+20260713-= 1_all.deb 6177b3c574e7f3ce5c0bb2ed256c8b2d 6347 admin optional nvmetcli_0.8+20260713-1= _amd64.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCamys2wAKCRD7tPDoCoAi L0d2AQCKUVrLVe3sb76xh00DlC7BxevyuFoau3hguY+OETCUqwD/XD/J59Oxh2CZ 4eUWhv8MiGAtqujM2zOYdfHOdOTSlQU=3D =3DMcvt -----END PGP SIGNATURE----- --===============3494215375948958637== Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQTziqJOuF8J+ZI8pJSb9qggYcy5IQUCanIowwAKCRCb9qggYcy5 IW1gAP9nlKKwRzagO6S3AGwvQAEGzOiFjiXE669QHskP1ezIMwEAunxGC27oUxvI E0Kyu3+t2P5DTnthJX+hVYDFrtbiDwM= =UdI0 -----END PGP SIGNATURE----- --===============3494215375948958637==-- ------------=_1785866462-3571567-0--