[MIR] Promote ruby-mime-types to main as a pcs indirect dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-mime-types (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Availability]
The package ruby-mime-types is already in Ubuntu universe.
The package ruby-mime-types build for the architectures it is designed to work on.
It currently builds and works for architectures: amd64 (arch:all)
Link to package [[https:/
[Rationale]
The package ruby-mime-types is required in Ubuntu main for ruby-ethon
promotion which is a runtime dependency of pcs (the main reason for this
promotion).
Ideally, we expect that ruby-mime-types (and pcs) will be promoted in the
"L" development cycle. The idea is to promote only the ruby-mime-types
binary.
[Security]
Required links:
https:/
3 CVEs were found searching for the gem name, however, all of them related to
PHP related issues, not the ruby gem.
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).
[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 runs a test suite on build time, if it fails
it makes the build fail, link to build log:
The package runs an autopkgtest, and is currently passing on this list of
architectures: amd64, arm64, armhf, ppc64el, s390x.
Link to test logs: https:/
The package does not have failing autopkgtests right now. Only in i386, where some dependencies are not installable.
[Quality assurance - packaging]
debian/watch is present and works.
debian/control defines a correct Maintainer field.
Lintian overrides are not present. Here is the output of `lintian --pedantic` against Kinetic version:
W: ruby-mime-types source: newer-standards
P: ruby-mime-types source: update-
P: ruby-mime-types source: very-long-
P: ruby-mime-types source: very-long-
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]
There are further dependencies that are not yet in main, MIR for them
is at:
- ruby-mime-
[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 ruby-mime-types
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 (Ubuntu): | |
assignee: | nobody → Lukas Märdian (slyon) |
Review for Package: src:ruby-mime-types
[Summary]
ruby-mime-types is a popular and mature Ruby gem, which can be used to query
metadata about a given mime type.
MIR team ACK. types-data MIR, bug #1990568, so I'm tracking it as "Incomplete" for now. I added some
=> This is basically an ACK, but is currently blocked on ruby-mime-
recommendations that should be double-checked or discussed with the Debian
maintainers (see "Notes" below).
This does not need a security review.
List of specific binary packages to be promoted to main: ruby-mime-types
Specific binary packages built, but NOT to be promoted to main: <None>
Notes:
- There are a few issues, which I'd like to see discussed with the Debian
maintainers (#2, #3, #4) - but not blocking the MIR.
- There's a recent FTBFS bug in Debian (#5), which should be investigated, it
built just fine for me on Kinetic, so not blocking the MIR neither.
- Debian/Ubuntu is lacking behind the upstream release by about 1 year (#6),
changelog seems minor, so I'm not blocking the MIR on this, but we should work
with Debian to get this updated.
Required TODOs: types-data MIR, bug #1990568
#0 The package should get a team bug subscriber (Server team) before being promoted
#1 depends on ruby-mime-
Recommended TODOs: types-data -> ruby? /bugs.debian. org/1022302
#2 warning: substitution variable ${shlibs:Depends} used, but is not defined
#3 Add package dependency on 'ruby' instead of just transitively on ruby-mime-
#4 The "smoke-test" (autopkgtest) should be marked "superficial"
#5 FTBFS https:/
#6 the current release is NOT packaged, v3.4.1 is available as of November 2021
[Duplication]
There is no other package in main providing the same functionality.
There is ruby-mime, ruby-mini-mime, ruby-marcel and ruby-mimemagic which
seem to be related, but all are in universe and the ruby-mime-types gem
seems to be most popular according to rubygems.org
[Dependencies]
OK:
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
more tests now.
Problems: types-data MIR, bug #1990568
- depends on ruby-mime-
[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 curre...