[MIR] libyuv (transitive dependency of libheif)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libyuv (Ubuntu) |
Incomplete
|
Undecided
|
Vladimir Petko | ||
Bug Description
[Availability]
The package libyuv is already in Ubuntu universe.
The package libyuv build for the architectures it is designed to work on.
It currently builds and works for architectures:
amd64 arm64 armhf i386 ppc64el riscv64 s390x
Link to package https:/
[Rationale]
- The package libyuv will not generally be useful for a large part of
our user base, but is important/helpful still because it provides color
format conversion and scaling which is important for video processing
- The package libyuv is a transitive dependency of package libheif that
we intend to support
- It would be great and useful to community/processes to have the
package libyuv in Ubuntu main, but there is no definitive deadline.
[Security]
- No CVEs/security issues in this software in the past
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024)
- Packages does contain extensions to security-sensitive software:
the package colorspace conversion library which processes untrusted input
[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 has no important open bugs.
Note: patches need to be refreshed.
- 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:
https:/
Note: unit tests are disabled for architectures:
arm64 armel s390x powerpc ppc64 sparc64
- The package does not run an autopkgtest because it is not implemented
[Quality assurance - packaging]
- debian/watch is present and works
- debian/control does not define a correct Maintainer field
- This package does not yield massive lintian Warnings, Errors
- Please link to a recent build log of the package
https:/
- 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 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)
- End-user applications without desktop file, not needed because
it does not provide any GUI
[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 Team
- 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 successfully built during the most recent test rebuild
Note: Build on lunar takes extremely long time compiling
unit_
https:/
Is it a known GCC issue?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
0x000000000
(gdb) where
#0 0x0000000000917faf in bitmap_
#1 0x0000000000f62ed2 in ?? ()
#2 0x0000000000f636d1 in compute_
#3 0x0000000000cc0fad in ?? ()
#4 0x0000000000cc156f in ?? ()
#5 0x0000000000cc45f7 in execute_
#6 0x0000000000cc4af0 in ?? ()
#7 0x0000000000cc4b02 in ?? ()
#8 0x0000000000cc4b2d in execute_
#9 0x0000000000984e68 in cgraph_
#10 0x0000000000986397 in ?? ()
#11 0x00000000009888ac in symbol_
#12 0x0000000000d92060 in ?? ()
#13 0x00000000006a48fe in toplev::main(int, char**) ()
#14 0x00000000006a5fef in main ()
[Background information]
The Package description explains the package well
Upstream Name is libyuv
Link to upstream project https:/
| Vladimir Petko (vpa1977) wrote | #1 |
| description: | updated |
| description: | updated |
| Changed in libyuv (Ubuntu): | |
| assignee: | nobody → Ioanna Alifieraki (joalif) |
| Ioanna Alifieraki (joalif) wrote | #2 |
| Changed in libyuv (Ubuntu): | |
| status: | New → Incomplete |
| assignee: | Ioanna Alifieraki (joalif) → nobody |
| Changed in libyuv (Ubuntu): | |
| assignee: | nobody → Vladimir Petko (vpa1977) |
Review for Package: libyuv
[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 need a security review, so I'll assign ubuntu-security once required TODOs
are resolved.
List of specific binary packages to be promoted to main: libyuv0, libyuv-dev, libyuv-utils
Notes:
TODO: - add todos, issues or special cases to discuss
Required TODOs:
1. Please add autopkgtests, the test running at build time can be used for this.
2. Ubuntu current release is behind debian by 8 versions, please sync.
In newer versions debian has disabled lto because of some tests failing.
Recommended TODOs:
3. Not sure this is a problem wrt MIR but I'll mention it to take a look at just in case.
I was not able to build the package because it would complain:
"dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address".
Looking at d/control
"Maintainer: Debian Multimedia Maintainers <email address hidden>".
This does not seem to be a problem when building on launchpad.
- The package should get a team bug subscriber before being promoted
[Duplication]
This package is required in main as a dependency of libheif package.
[Dependencies]
OK:
- no other Dependencies to MIR due to this
- libuyv 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 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:
- does parse data formats (files [images, video, audio,
xml, json, asn.1], network packets, structures, ...) from
an untrusted source.
[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- test suite fails will fail the build upon error.
- This does not need special HW for build or test
- no new python2 dependency
Problems:
- does not have a non-trivial test suite that runs as autopkgtest
[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
control
- symbols tracking is in...