The security team acked the request and autopkgtests got added, simple build testcases and upstream tests https://autopkgtest.ubuntu.com/packages/libe/libei
s390x is currently failing but a fix got proposed upstream and it's not considered as a desktop architecture so let's not block on that it should be good to promote so doing it now to avoid extra delays, Lukas let us know if there was something else more you wanted to see done there and will address it in the next upload -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2031406 Title: [MIR] libei Status in libei package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Availability] - The package libei is already in Ubuntu universe. - The package libei builds for the architectures it is designed to work on. - Link to package https://launchpad.net/ubuntu/+source/libei [Rationale] - The package libei is required in Ubuntu main as a new required dependency for Mutter 45 - The package libei will generally be useful for a large part of our user base - The package libei is a new runtime dependency of package mutter that we already support - There is no other/better way to solve this that is already in main or should go universe->main instead of this. The package libei is required in Ubuntu main no later than August 17 due to Ubuntu 23.10 Feature Freeze. Obviously, that's an unrealistic deadline but the dependency is in mantic-proposed now (some other work is necessary for mutter to migrate out of mantic-proposed). It might be possible to temporarily vendor libei into Mutter. [Security] - No CVEs/security issues in this software in the past (new software, only packaged now in Ubuntu) - 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 (filters, scanners, plugins, UI skins, ...) libei is a library for emulated input. It can forward physical or logical device input for use by things like GNOME Remote Desktop or sandboxed apps or for fake input for automated actions (like could be done with xdotool). [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/libei/ - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libei (not in Debian yet) - Upstream https://gitlab.freedesktop.org/libinput/libei/-/issues [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/libei/1.0.0-0ubuntu2 Note that the build test failures are temporarily ignored on s390x which is not a supported Ubuntu Desktop architecture, but the issue has been reported upstream and is being worked on: https://gitlab.freedesktop.org/libinput/libei/-/issues/41 - The package does not run an autopkgtest because we haven't written one yet. We may run upstream's build test with our autopkgtest architecture. - Some tests using libei also have been added to Mutter and we do run Mutter's tests both at build time and as installed tests with autopkgtest https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2628/commits [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/libei/1.0.0-0ubuntu2 - Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug. - 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 will be installed by default, but does not ask debconf questions higher than medium - Packaging and build is easy, link to debian/rules https://salsa.debian.org/jbicha/libei/-/blob/debian-unstable/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be Desktop Packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - The team Desktop Packages is aware of the implications of vendored code and (as alerted by the security team) commits to provide updates and backports to the security team for any affected vendored code for the lifetime of the release (including ESM). Currently, the libei packaging includes a vendored copy of munit since munit is not packaged for Debian or Ubuntu yet. This is an optional build-time dependency only used by the test suite and does not add any run-time dependencies. https://github.com/nemequ/munit - This package uses vendored code, refreshing that code is… … done with uscan's "component" feature for multiple upstream orig tarballs. debian/watch is set to track munit HEAD and updates will be automatically included when packaging new upstream releases of libei. A similar approach was done for editorconfig-core which was promoted to Main last year. - The package has been built in the archive more recently than the lasttest rebuild [Background information] - The Package description explains the package well - Upstream Name is libei - Link to upstream project https://gitlab.freedesktop.org/libinput/libei Timo has agreed to review this package for inclusion in Debian under the Debian X Strike Force team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2031406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
