Comment 2 for bug 1964600

Review for Package: gnome-bluetooth3

[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:
libgnome-bluetooth-3.0-13
libgnome-bluetooth-ui-3.0-13
libgnome-bluetooth-3.0-dev
libgnome-bluetooth-ui-3.0-dev
gir1.2-gnomebluetooth-3.0
libgnome-bluetooth-doc
gnome-bluetooth-3-common

Notes:

Required TODOs:
1. Add some autopackage tests
2.The package should get a team bug subscriber before being promoted

Recommended TODOs:
- Fix the the build warnings upstream ( https://pastebin.canonical.com/p/dKrn86DtDY/ )

[Duplication]
- There is no other package in main providing the same functionality
IIUC gnome-bluetooth which is already in main provides the same functionality, however the analysis in the [Background information] in bug description seems convincing to promote gnome-bluetooth3 to main along side gnome-bluethooth which will be demoted in 20.10.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- 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 odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main

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 parse data formats
- 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)

Problems: None

[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.
- no new python2 dependency

Problems:
- does not have test suite that runs as autopkgtest

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- 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: None

[Upstream red flags]
OK:
- 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, qtwebkit, seed or libgoa-*
- part of the UI, desktop file is ok
- translation present

Problems:
- Errors/warnings during the build
  - Upstream build produces the following warnings :
    https://pastebin.canonical.com/p/dKrn86DtDY/