[MIR] Promote ruby-tilt to main as a pcs indirect dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-tilt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Availability]
The package ruby-tilt is already in Ubuntu universe.
The package ruby-tilt 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-tilt is required in Ubuntu main for ruby-sinatra promotion which is runtime dependency of pcs (the main reason for this promotion).
Ideally, we expect that ruby-tilt (and pcs) will be promoted in the "L" development cycle. The idea is to promote only the ruby-tilt binary.
[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 not too many
and long term critical 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 have not 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:
P: ruby-tilt source: maintainer-
P: ruby-tilt source: update-
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: tilt
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-tilt (Ubuntu): | |
assignee: | nobody → Didier Roche-Tolomelli (didrocks) |
[Summary]
MIR team ACK. Keep in mind that you need to subscribe the server team before promotion. Note the recommended TODOs though.
Recommended TODO:
- tilt is one path version behind, release in July. This is multiple months old and before last Ubuntu feature freeze. Debian sid hasn’t updated it too. Maybe the reason is that every patches have been backported via patches in the debian uploads, but it would be good to realign with upstream.
- there are multiple warnings during the package build. To clear out the logs, it would be good to take some time to clean them so that newer warnings are easier to inspect.
[Duplication]
There is no other package in main providing the same functionality.
[Dependencies]
OK:
- no other Dependencies to MIR due to this
- ruby-tilt checked with `check-mir`
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
more tests now.
[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
[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, ...)
[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- autokpgtests are running and passing (those are apparently autogenerated)
- test suite fails will fail the build upon error.
- no new python2 dependency
[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
- Upstream update history is good
- Debian/Ubuntu update history is good
- promoting this does not seem to cause issues for MOTUs that so far
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list
KO:
- tilt is one path version behind, release in July. This is multiple months old and before last Ubuntu feature freeze. Debian sid hasn’t updated it too. Maybe the reason is that every patches have been backported via patches in the debian uploads, but it would be good to realign with upstream.
[Upstream red flags]
OK:
- no Errors 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 (crashers, etc) in Debian or Ubuntu
- no dependency on webkit,...