[Availability]
The package boot-managed-by-snapd is already in Ubuntu universe.
The package boot-managed-by-snapd build for the architectures it is designed to work on.
It currently builds and works for architetcures: amd64, arm64
Link to package https://launchpad.net/ubuntu/+source/boot-managed-by-snapd
[Rationale]
- The package boot-managed-by-snapd is required in Ubuntu main for subiquity so that when the user does a hybrid install, it installs the replacement package.
- The package boot-managed-by-snapd will generally be useful for a large part of
our user base
- The package boot-managed-by-snapd is a new runtime dependency of package subiquity 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.
- There is no definitive deadline, but it would be great and useful for testing testing of the canary iso to have the
package boot-managed-by-snapd in Ubuntu main (the sooner the better).
[Security]
- Because this package new (exists since May 2023) there is
no security history at all.
- 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)
TODO - Packages does not contain extensions to security-sensitive software
[Quality assurance - function/usage]
- The package works well right after install
[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 Foundations
TODO: - 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 in the archive more recently than the last
test rebuild
[Background information]
- The Package description and included README explains the package well
[Availability] by-snapd is already in Ubuntu universe. by-snapd build for the architectures it is designed to work on. /launchpad. net/ubuntu/ +source/ boot-managed- by-snapd
The package boot-managed-
The package boot-managed-
It currently builds and works for architetcures: amd64, arm64
Link to package https:/
[Rationale] by-snapd is required in Ubuntu main for subiquity so that when the user does a hybrid install, it installs the replacement package. by-snapd will generally be useful for a large part of by-snapd is a new runtime dependency of package subiquity that by-snapd in Ubuntu main (the sooner the better).
- The package boot-managed-
- The package boot-managed-
our user base
- The package boot-managed-
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.
- There is no definitive deadline, but it would be great and useful for testing testing of the canary iso to have the
package boot-managed-
[Security]
- Because this package new (exists since May 2023) there is
no security history at all.
- 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)
TODO - Packages does not contain extensions to security-sensitive software
[Quality assurance - function/usage]
- The package works well right after install
[Quality assurance - maintenance] /bugs.launchpad .net/ubuntu/ +source/ boot-managed- by-snapd/ +bug
- The package is new and does not have too any open bugs
- Ubuntu https:/
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing] /autopkgtest. ubuntu. com/results/ autopkgtest- mantic/ mantic/ amd64/b/ boot-managed- by-snapd/ 20230605_ 154742_ 4fb6d@/ log.gz /autopkgtest. ubuntu. com/results/ autopkgtest- mantic/ mantic/ arm64/b/ boot-managed- by-snapd/ 20230605_ 155040_ 4fb6d@/ log.gz
- The package does not run a test at build time because it contains
autopkgtests that test for regressions when in proposed.
- The package runs an autopkgtest, and is currently not passing because of unmet dependencies on:
- mantic arm64: https:/
- mantic amd64: https:/
TODO: How does Foundations plan to fix this?
- This package is minimal and will be tested implicitly together with the canary ISOs, details about this testing are here TODO
[Quality assurance - packaging] /launchpad. net/ubuntu/ +source/ boot-managed- by-snapd/ 1/+build/ 26277455 /launchpad. net/ubuntu/ +source/ boot-managed- by-snapd/ 1/+build/ 26277456 /git.launchpad. net/ubuntu/ +source/ boot-managed- by-snapd/ tree/debian/ rules
- debian/watch is not present because it is a native package
- debian/control defines a correct Maintainer field
- This package does not yield massive lintian Warnings, Errors
- Recent build logs of the package <TBD>
- mantic amd64: https:/
- mantic arm64: https:/
- 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:/
[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 Foundations
TODO: - 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 in the archive more recently than the last
test rebuild
[Background information]
- The Package description and included README explains the package well