MIR review:
Does it FTBFS currently? it builds on supported architectures (i386, amd64,
armhf)
Does it have a test suite? yes, currently disabled in the build
Does it have a team bug subscriber? yes, oxide-developers
Is the code translatable (if user visible)? N/A
If it's a Python package, does it use dh_python? N/A
If it's a Python package going on the desktop CD, will it pull in Python
2? N/A
Does Ubuntu carry a delta? no
If it's a library, does it either have a symbols file or use an empty
argument to dh_makeshlibs -V? uses standard dh packages which uses
dh_makeshlibs
Does it have a watch file? No, Canonical is upstream and we will likely
do autolandings
Is its update history slow or sporadic? chromium content api is fast and
oxide is Canonical-developed. We have merged with upstream scores of
times already. Oxide currently is on upstream's devel branch but we
should transition to stable (likely via beta)
Is the current release packaged? yes
Will entering main make it harder for the people currently keeping it up
to date? (i.e. are they only MOTUs?) not with autolandings
Lintian warnings: there are some warnings:
- old-fsf-address-in-copyright-file: fixed in packaging branch
- binary-without-manpage usr/bin/oxideqmlscene: this binary is temporary and
will be removed soon
- several embedded libraries: libpng, libjpeg, sqlite, libxml2, libavutil. This
is consistent with our other supported browsers and is 'ok' since we track
upstream chromium content api
- setuid-binary usr/lib/x86_64-linux-gnu/oxide-qt/chrome-sandbox. This is
setuid so it can setup various security features. This has been reviewed in the
past and it drops privileges correctly and quickly
Is debian/rules a mess? uses dh7 and is very small
Errors/warnings during the build: just one that isn't in the chromium-
content-api: /build/buildd/oxide-
qt-1.0.0~bzr437/qt/quick/api/oxideqquickscriptmessagehandler_p.h:65:
Warning: Class OxideQQuickScriptMessageHandler implements the interface
QQmlParserStatus but does not list it in Q_INTERFACES. qobject_cast to
QQmlParserStatus will not work!
Uses of sudo, gksu, pkexec, or LD_LIBRARY_PATH: ok
Important bugs (crashers, etc) in Debian or Ubuntu: there are, but they
are assigned with fixes being developed
Dependency on webkit, qtwebkit, seed or libgoa-*: chromium-content-api
uses blink internally, which is a fork of webkit. Oxide is meant to
track the chromium content api very closely so we can track upstream
fixes in a timely fashion
If this is a scope for the Unity Dash, does it honor the privacy
settings? N/A
Conditional ACK provided:
- the testsuite is enabled in the build or as part of autopkgtests (your choice)
- the transition plan of moving Oxide off of upstream devel to beta, and then
beta to stable is outlined in this bug along with outlining plans to make sure
Oxide tracks upcoming code drops in devel/beta so we are never unprepared when
a security update lands
- a statement is made as to why the community architectures FTBFS and any plans
to address them
** Changed in: oxide-qt (Ubuntu)
Status: Triaged => Incomplete
** Changed in: oxide-qt (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => Chris Coulson (chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293681
Title:
[MIR] oxide
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1293681/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
