[MIR] Promote ruby-mime-types-data to main as pcs indirect dependency
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ruby-mime-types-data (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
[Availability]
The package ruby-mime-
The package ruby-mime-
It currently builds and works for architectures: amd64 (arch:all)
Link to package [[https:/
[Rationale]
The package ruby-mime-
Ideally, we expect that ruby-mime-
[Security]
Required links:
https:/
Nothing was found searching for the gem name.
Nothing was found searching in the OSS security mailing list archive.
https:/
Also nothing found in the Ubuntu security tracker.
No CVEs/security issues in this software in the past
No `suid` or `sgid` binaries.
Package does not install services, timers or recurring jobs.
Packages does not open privileged ports (ports < 1024).
Packages does not contain extensions to security-sensitive software
(filters, scanners, plugins, UI skins, ...).
[Quality assurance - function/usage]
The package works well right after install.
[Quality assurance - maintenance]
The package is maintained well in Debian/Ubuntu and has no bugs open:
- Ubuntu https:/
- Debian https:/
The package does not deal with exotic hardware we cannot support.
[Quality assurance - testing]
The package does not run a test at build time because this is just data, not code to be tested.
The package does not run an autopkgtest because of what was explained above.
This package is minimal and will be tested in a more wide reaching
solution context of pcs, details about this testing are here:
https:/
[Quality assurance - packaging]
debian/watch is present and works.
debian/control defines a correct Maintainer field.
`lintian --pedantic` output:
P: ruby-mime-
P: ruby-mime-
P: ruby-mime-
Lintian overrides are not present.
This package does not rely on obsolete or about to be demoted packages.
The package will not be installed by default.
Packaging and build is easy, link to d/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 Server.
Team is not yet, but will subscribe to the package before promotion.
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 explains the package well.
Upstream Name is mime-types-data
Link to upstream project: https:/
Related branches
- Christian Ehrhardt : Approve
- Athos Ribeiro: Approve
- Canonical Server Reporter: Pending requested
-
Diff: 61 lines (+17/-0)1 file modifiedsubscriptions.yaml (+17/-0)
| description: | updated |
| Changed in ruby-mime-types-data (Ubuntu): | |
| assignee: | nobody → Ioanna Alifieraki (joalif) |
| Ioanna Alifieraki (joalif) wrote | #1 |
| Changed in ruby-mime-types-data (Ubuntu): | |
| assignee: | Ioanna Alifieraki (joalif) → nobody |
| status: | New → Incomplete |
| Lucas Kanashiro (lucaskanashiro) wrote | #2 |
| Christian Ehrhardt (paelzer) wrote | #3 |
| Changed in ruby-mime-types-data (Ubuntu): | |
| status: | Incomplete → In Progress |
| Christian Ehrhardt (paelzer) wrote | #4 |
| Changed in ruby-mime-types-data (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Christian Ehrhardt (paelzer) wrote | #5 |
| Changed in ruby-mime-types-data (Ubuntu): | |
| status: | Fix Committed → Fix Released |
Review for Package: ruby-mime-
[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does not need a security review
List of specific binary packages to be promoted to main: ruby-mime-
Notes:
The package does not contain any tests, but this is not a problem since
this is data packaging and no source code.
Required TODOs:
1. The latest upstream release is 2022.0105, the release in Ubuntu and
debian is 2015.1120-1. According to the changelog, there is an update
in 2022 however which pulls in from upstream but the version remains
the same, please take a look at it.
- The package should get a team bug subscriber before being promoted
[Duplication]
There is no other package in main providing the same functionality.
[Dependencies]
OK:
- no other Dependencies to MIR due to this
- mime-types-data checked with `check-mir`
- all dependencies can be found in `seeded-in-ubuntu` (already in main)
- none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
more tests now.
Problems: None
[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code
Problems: None
[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
xml, json, asn.1], network packets, structures, ...) from
an untrusted source.
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates, signing, ...)
Problems: None
[Common blockers]
OK:
- does not FTBFS currently
- no new python2 dependency
Problems: None
[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is sporadic
- promoting this does not seem to cause issues for MOTUs that so far
maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list
Problems:
- the current release is packaged
[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
tests)
- no use of user nobody
- no use of setuid
- no important open bugs (crashe...