Public bug reported: Availability: PMDK is rather new (Cosmic) and builds for amd64 (main purpose) There also is arm code in the lib, but lacking any request as well as arm-nvdimm HW it isn't built there.
Rationale: - There is a request to enhance qemu nvdimm support (bug 1745900) which is reasonable looking forward to the potential future with nvdimms. - It would not be useful to a "large" part of the user base as nvdimms will be rare for a while. But huge installations might converge to them for some cases soon. - The mentioned qemu change would make qemu (main) require libpmem1 (currently universe). Security: - there are no CVEs yet to prove how the projects will behave by looking at the past - The project is rather active in general => http://pmem.io/ => https://github.com/pmem/pmdk/pulse Quality assurance: - The package builds helper tools as well as a lib "libpmem1". Both work out-of the box (if you have the HW below for more) - no debconf questions - Due to beign so recent we have no good insight on potential long term bugs, obviously thre are none atm. - Bug trackers are clear, but mostly due to being new => https://bugs.launchpad.net/ubuntu/+source/pmdk (Well maintained in Ubuntu; not in Debian) - the nature of this package is to support nvdimms which are still rare HW, so not everybody can easily test these things completely. IMHO to some extend we rely on our partners asking for these features. - Unit tests exist and run on build - debian/watch is in place - no obsolete or demoted packages in the dependencies UI standards: - not a UI package Dependencies: - The libs don't have a lot of runtime dependencies and for now it seems we only want to pull in libpmem1 (not all the others, but that might change with more adoption of that code) - The associated pmdk-tools would imply further MIRs on src:libfabric and src:ndctl which we are currently not intending to push Standards compliance: - follows FHS rules - is under rather new standards 4.1.5 Maintenance: - maintained by the server Team (atm in universe) - ownign team would be the ubuntu-server Team Background information: persistent memory can be hard, this library abstracts special differences in CPUs/Architectures/devices and provides a single API to handle those. Applications that want to use pmem/nvdimm should use PMDK instead of re-implementing things everywhere with the same mistakes. ** Affects: pmdk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790856 Title: [MIR] pmdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1790856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
