** Description changed: - Enchant is showing on component mismatch, it is a source package rename - from a package already in main: enchant-2 -> enchant + [Availability] + The package enchant is already in Ubuntu. + The package enchant builds for the architectures it is designed to work on. + It currently builds and works for architectures: amd64, amd64v3, arm64,armhf, i386, ppc64el, riscv64, s390x + Link to package https://launchpad.net/ubuntu/+source/enchant - Historically enchant and then enchant-2 had been in main from before the - "modern" MIR process. We would like to go through a (re-)review at some - point and will add an item in the Debcrafters backlog for it but are - asking to not block the enchant promotion on it. + [Rationale] + - enchant is already in main. This MIR is a re-review of the package as described in comment 3 + + + [Security] + - The Ubuntu CVE Tracker shows CVE-2019-16707, which is mainly a Hunspell issue. For enchant, it only shows older releases + needing evaluation, and enchant is not listed as present in the newer maintained releases shown there + + - no `suid` or `sgid` binaries + - no executables in `/sbin` and `/usr/sbin` + - Package does not install services, timers or recurring jobs + - Packages does not open privileged ports (ports < 1024). + - Package does not expose any external endpoints + - Packages does not contain extensions to security-sensitive software + + [Quality assurance - function/usage] + - The package works well right after install + + [Quality assurance - maintenance] + - The package is maintained well in Debian/Ubuntu/Upstream and does + not have too many, long-term & critical, open bugs + - Ubuntu https://bugs.launchpad.net/ubuntu/+source/enchant/+bugs + - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=enchant + - The package does not deal with exotic hardware we cannot support + + [Quality assurance - testing] + - The package runs a test suite on build time. Test failures make the build fail + on most architectures. There is an exception for i386, where test failures are + ignored because libunittest++-dev is not available there. + + - An autopkgtest has been added for libenchant-dev. The test passes locally. I also tested the change in a PPA: + https://launchpad.net/~zineb/+archive/ubuntu/stonking-enchant-autopkgtest-2155203 + The PPA build succeeded, and the autopkgtests passed on amd64, arm64, armhf, i386 and riscv64. + ppc64el and s390x are currently showing `testbed BAD`. From the logs, this looks like remote LXD/testbed connectivity issues rather than a package failure. I will keep retrying. + + [Quality assurance - packaging] + - A mechanism to detect and fetch new upstream versions is present and works + + - debian/control defines a correct Maintainer field + + - This package does not yield massive lintian Warnings, Errors + + - full output you have got from 'lintian --pedantic` : + W: enchant source: missing-debian-watch-file-standard [debian/watch] + W: enchant source: newer-standards-version 4.7.4 (current is 4.6.2) + W: enchant source: recommended-field (in section for source) Priority [debian/control:1] + P: enchant source: silent-on-rules-requiring-root [debian/control] + + - Minor problems, none that are blockers for the promotion + - Lintian overrides are not present + - This package does not rely on obsolete or about to be demoted packages. + - This package has no python2 or GTK2 dependencies + - The package does not ask debconf questions higher than medium + - Packaging and build is easy, link to debian/rules https://salsa.debian.org/gnome-team/enchant/-/blob/debian/latest/debian/rules + + [UI standards] + - Application is not end-user facing (does not need translation) + + - End-user applications without desktop file, not needed because it is + not a graphical desktop application. + + [Dependencies] + - Used check-mir from ubuntu-dev-tools to validate + all dependencies or recommends are in main. + + + [Standards compliance] + - This package correctly follows FHS and Debian Policy + + - Based on a reasonable review of information available at the time of + this report, no expiry, time-limited grants, or obvious legal + encumbrances have been identified that would be expected to affect + promotion + + [Maintenance/Owner] + - The owning team will be debcrafters-packages and the team has + acknowledgment for that commitment + - The future owning team is already subscribed to the package + + + - This does not use static builds + + - This does not use vendored code + + - This package is not rust based + + - The package has been built within the last 3 months in the archive + - Build link on launchpad: https://launchpad.net/ubuntu/+source/enchant/2.8.16+dfsg-3 + + - This change will not impact other teams + + [Background information] + - The Package description explains the package well + - Upstream Name is Enchant + - Link to upstream project https://rrthomas.github.io/enchant/ + - This MIR is for the source package rename/reorganization from enchant-2 to + enchant. The previous enchant-2 source/package stack was already in main, and + this review carries that forward under the new source package name.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155203 Title: [MIR] enchant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/2155203/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
