** Description changed: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506 [Availability] There is an on-going MIR for a package whose ndctl is a dependency: pmdk (LP: #1790856) * Package exists since bionic (-updates) in universe: 61.2-0ubuntu1~18.04.1 | bionic-updates/universe 63-1.3 | disco/universe 65-1 | eoan/universe 67-1 | focal/universe * Packages: ndctl libndctl6 libndctl-dev daxctl libdaxctl1 libdaxctl-dev ndctl: dctl is utility for managing the "libnvdimm" kernel subsystem. The "libnvdimm" subsystem defines a kernel device model and control message interface for platform NVDIMM resources like those defined by the ACPI 6.0 NFIT (NVDIMM Firmware Interface Table). Operations supported by the tool include, provisioning capacity (namespaces), as well as enumerating/enabling/disabling the devices (dimms, regions, namespaces) associated with an NVDIMM bus. daxctl: The daxctl utility provides enumeration and provisioning commands for the Linux kernel Device-DAX facility. This facility enables DAX mappings of performance / feature differentiated memory without need of a filesystem. * Architectures: source, amd64, arm64, armhf, i386, ppc64el, s390x PMEM: A system-physical-address range where writes are persistent. A block device composed of PMEM is capable of DAX. A PMEM address range may span an interleave of several DIMMs. BLK: A set of one or more programmable memory mapped apertures provided by a DIMM to access its media. This indirection precludes the performance benefit of interleaving, but enables DIMM-bounded failure modes. DAX: File system extensions to bypass the page cache and block layer to mmap persistent memory, from a PMEM block device, directly into a process address space. Binary Packages: ndctl libndctl6 libndctl-dev daxctl libdaxctl1 libdaxctl-dev [Rationale] - This is part of the MIR activity for all dependencies of pmdk. + This is part of the MIR activity for all dependencies of pmdk. "ndctl" + and "daxctl" are userland tools used to configure NVDIMMs and should be + supported and put in main pocket (and server). The "main" MIR of it is at: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1790856 Package was introduced in bionic after bionic was released (19.04.1) in universe and it is still in universe until now. [Security] - TODO: check the security History of the package - - http://people.ubuntu.com/~ubuntu-security/cve/universe.html - - http://cve.mitre.org/cve/cve.html + - No related CVEs found at: cve.mitre.org [Quality assurance] * Documentation: - https://docs.pmem.io/ndctl-users-guide - https://nvdimm.wiki.kernel.org/ - Both packages (ndctl and daxctl) and its libraries (libndctl6, libndctl-dev, libdaxctl1, libdaxctl-dev) install fine and are operational (check comment #1). - There are no debconf templates and/or questions in this package. - TODO: There are no long-term outstanding bugs which affect the usability - of the program to a major degree. To support a package, we must be - reasonably convinced that upstream supports and cares for the package. - - TODO: The status of important bugs in Debian's, Ubuntu's, and upstream's - bug tracking systems must be evaluated. Important bugs must be pointed - out and discussed in the MIR report. - - TODO: The package is maintained well in Debian/Ubuntu (check out the - Debian PTS) - - TODO: The package should not deal with exotic hardware which we cannot - support. - - TODO: If the package ships a test suite, and there is no obvious reason - why it cannot work during build (e. g. it needs root privileges or - network access), it should be run during package build, and a failing - test suite should fail the build. - - TODO: The package uses a debian/watch file whenever possible. In cases - where this is not possible (e. g. native packages), the package should - either provide a debian/README.source file or a debian/watch file (with - comments only) providing clear instructions on how to generate the - source tar file. - - TODO: It is often useful to run lintian --pedantic on the package to - spot the most common packaging issues in advance - - TODO: The package should not rely on obsolete or about to be demoted - packages. That currently includes package dependencies on Python2 - (without providing Python3 packages), and packages depending on GTK2. + - The only existing/opened bug affecting the package was LP: #1811785 + and I have already provided 2 MRs fixing that issue. No other long-term + outstanding bug affecting it. Upstream seems well maintained and + isolating fix commits, making them easy to cherry-pick and/or backport. + + - There are no current Debian bugs for ndctl (https://bugs.debian.org + /cgi-bin/pkgreport.cgi?dist=unstable;package=ndctl) + + - Upstream has 25 cases opened (almost all of them with comments and + discussions) and 77 cases already closed, leading to a conclusion that + is actively maintained and provides good feedback to reporters. + + - Package does not deal with exotic hardware, but, indeed, it deals with + NEW type of hardware, getting more common every day (NVDIMMs). DAX + support is already included in EXT4 and XFS filesystems, allowing + NVDIMMs to be transparently used as block devices (without page cache). + The userland libraries allow applications to get all benefits with a new + memory (non-volatile) layer. + + - Package has a minimum DEP8 support (for obvious issues with the + binaries, as the utils need NVDIMMs to be present in the running + environment). + + - Package uses debian/watch. + + - No lintian errors (pedantic). + + - Package does not rely on obsolete packages: + + $ apt-cache rdepends ndctl + ndctl + Reverse Depends: + daxctl + ndctl-dbgsym + daxctl + + $ apt-cache depends ndctl + ndctl + PreDepends: init-system-helpers + Depends: libc6 + Depends: libdaxctl1 + Depends: libjson-c4 + Depends: libkeyutils1 + Depends: libndctl6 + Depends: libuuid1 [UI standards] - TODO: End-user applications must be internationalized (translatable), - using the standard intltool/gettext build and runtime system and produce - a proper PO template during build. - - TODO: End-user applications must ship a standard conformant desktop - file. + N/A [Dependencies] - Some dependencies are not in main, but we drive MIR for all related - packages that are not in main at the same time. - - Please check the list of bugs from the main Mailman3 MIR to get an - overview. + $ apt-cache depends ndctl + + ndctl + PreDepends: init-system-helpers + Depends: libc6 + Depends: libdaxctl1 (itself) + Depends: libjson-c4 - main (exists since eoan) + Depends: libkeyutils1 - main + Depends: libndctl6 (itself) + Depends: libuuid1 - main [Standards compliance] - TODO: The package should meet the FHS and Debian Policy standards. - - TODO: Major violations should be documented and justified. - - TODO: Also, the source packaging should be reasonably easy to understand - and maintain. + - Package follows FHS. + + - Debian Standards 4.4.1 + + - Source package is clear and well done. [Maintenance] The Server team will subscribe for the package for maintenance [Background] The Persistent Memory Development Kit (PMDK) is a collection of libraries and tools for System Administrators and Application Developers to simplify managing and accessing persistent memory devices. The libraries build on the Direct Access (DAX) feature which allows applications to directly access persistent memory as memory-mapped files. This is described in detail in the Storage Network Industry Association (SNIA) NVM Programming Model. PMDK depends on libndctl. The Non-Volatile Device Control (ndctl) is a utility for managing the LIBNVDIMM Linux Kernel subsystem. The LIBNVDIMM subsystem defines a kernel device model and control message interface for platform NFIT (NVDIMM Firmware Interface Table). This interface was first defined by the ACPI v6.0 specification. Later versions may enhance or modify this specification. The latest ACPI and UEFI specifications can be found at http://uefi.org/specifications. The latest ACPI and UEFI specifications can be found at uefi.org. Operations supported by ndctl include: - Provisioning capacity (namespaces) - Enumerating Devices - Enabling and Disabling NVDIMMs, Regions, and Namespaces - Managing NVDIMM Labels The LIBNVDIMM subsystem provides support for three types of NVDIMMs, namely, PMEM, BLK, and NVDIMM devices that can simultaneously support both PMEM and BLK mode access. These three modes of operation are described by the "NVDIMM Firmware Interface Table" (NFIT) in ACPI v6.0 or later. Linux Kernel documentation can be found at: https://www.kernel.org/doc/Documentation/nvdimm/nvdimm.txt.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853506 Title: [MIR] ndctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
