** Description changed: - Note: - This is a preparation MIR only - Right now we will keep it as a suggest and in universe. - - The reason isn't mdevctl (which is fine) but that we'd also need - `src:jq` and for that `src:libonig` whcih currently (at least the server team) - does not want to own (just for this use case). - - jq had no past MIR afaik, libonig was denied (bug 675757) but the old - issues resolved. - - This decision can change and then the MIR is prepared. - Until then this is incomplete. - - --- - MDEVCTL [Availability] The package is in the Ubuntu universe, and builds arch-neutral Just one binary package `mdevctl` [Rationale] This has two reasons: 1. it is a very nice tool to handle meidiated devices in general. It more and more becomes the one tool people refer to (other than fully manual working through sysfs) 2. libvirt with coming version 6.5 starts to use it and it will become a recommends. https://www.libvirt.org/news.html https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/55/diffs?commit_id=b8a07b4b19e3ba03b2d36b6def4c5e4527ec2f11 [Security] No open bugs or CVEs (nor any in the past). [Quality assurance] Packaging wise it seems sage it doesn't ask debconf questions, has no long-term outstanding bugs and upstream has a bug tracker. OTOH it is just a pumped up shell script these days, there is no upstream testsuite or anything like it. I have personally used it to manage vGPUs of nvidia and intel and it worked for both - due to the very HW specific nature of the tools use case there can't be autopkgtests or other easy tests. Package is maintained in Debian and Ubuntu by the server team. No outstanding bugs: https://tracker.debian.org/pkg/mdevctl The HW the package deals with is not really exotic - while everyone wants to use it (pro users) for nvidia - it does work with almost any i915 laptop GPU of the last decade. Only you need to reboot/reconfig your laptop which makes it a bit harder. Lintian is happy with the package. No obsolete or demoted dependencies. [UI standards] No end user UI Just a few CLI bits used by admins and parsable output used by tools. [Dependencies] Fine except for `jq` which also need `libonig` (see below) [Standards compliance] The package meets the FHS and Debian Policy standards. [Maintenance] The Server team will subscribe for the package for maintenance --- - JQ [Availability] The package is in the Ubuntu universe, and builds for all architectures. It has a commandline tool in pkg:jq and a lib/devel package libjq1/libjq-dev. For the current case only the commandline-tool will be promoted. [Rationale] Obviously one rational is the dependency from mdevctl (see above), but TBH `jq` is a quite common tool. You'll find in almost any howto dealing with json on the commandline. [Security] No open bugs or CVEs right now, but it has a CVE history. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8863 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4074 Both fixed nowadays and about crafted JSON file leading to a crash. The handling of these issues in the past LGTM, but security team will have a better insight to that. [Quality assurance] Packaging wise it seems sage it doesn't ask debconf questions, has no long-term outstanding bugs in Ubuntu and upstream has a bug tracker. It has build time tests that run and would break build. Lintian is rather happy with the package and no special HW is needed to work with it No obsolete or demoted dependencies. [UI standards] No end user UI Just a few CLI bits used by admins and parsable output used by tools. [Dependencies] Fine except that is also needs `libonig` (see below) [Standards compliance] The package meets the FHS and Debian Policy standards. [Maintenance] The Server team will subscribe for the package for maintenance. Although TBH while "needed as dep for a server package" this is clearly not a server package from it's own use case, so ownership might be re-discussed. --- - LIBONIG [Availability] The package is in the Ubuntu universe, and builds for all architectures. It has a commandline tool in pkg:jq and a lib/devel package libjq1/libjq-dev. For the current case only the commandline-tool will be promoted. [Rationale] There are other regexp libraries, but JQ (above) can only use this one. There was an old denied MIR in bug 675757, but the old issues identified back then (packaging issues and rare updates) both seem to be good now. Also symbols trackign wasn't done back then, but is now. https://github.com/kkos/oniguruma/tags https://tracker.debian.org/pkg/libonig [Security] No open bugs or CVEs right now, but it has a CVE history most found in 2019. [Quality assurance] Packaging wise it seems sage it doesn't ask debconf questions, has no long-term outstanding bugs in Ubuntu and upstream has a bug tracker. It has build time tests that run under dh_auto_test. No special HW is needed to work with it No obsolete or demoted dependencies. [UI standards] No end user UI, just a lib to build against. [Dependencies] No further non-main dependencies. [Standards compliance] The package meets the FHS and Debian Policy standards. [Maintenance] The Server team will subscribe for the package for maintenance. Although TBH while "needed as dep for a server package" this is clearly not a server package from it's own use case, so ownership might be re-discussed.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889248 Title: [MIR] mdevctl, jq, libonig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jq/+bug/1889248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
