On Wed, 2016-08-17 at 21:00 +0000, Michael Terry wrote:
> - Bug 1532358 was worked around by just not running autopkg tests.
> That's not an ideal response (understandable short term, but it's
> been
> six months).  Any word on what it would take to re-enable them?

We still run autopkgtests. We just don't run the integration tests
which depend on the python test harness for scopes, due to a bug. Until
the bug is fixed, we can't really enable them, as they will be
unreliable.

> - How is the default departments.db generated?  I don't see a target
> in
> the source.  It's bad form / against policy to ship binary files in a
> source tarball like that without their source.

With the init-departments-db tool in the source. Hopefully we can get
rid of this tool, and the departments.db in the future, as it appears
we'll have something else for snaps, and the reason we had to do it
this way is no longer valid. This is really just an initial cache
though.

> - This needs a team bug subscriber from our package-subscribers list.
> Maybe phablet-team or unity-api-team?  I see ubuntuone-client-
> engineering is subscribed, but maybe ubuntuone-hackers would work
> then?

I've already subscribed unity-api-team today, but maybe you checked
prior to that.

> - ${python:Depends} should be ${python3:Depends} for the autopilot
> package and --with python3 should be passed to dh to fill that
> variable
> out (with a dh-python build-dep).

Can you file a separate bug for this (fixing it obviously doesn't
resolve the MIR, but would like a bug to link to)?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614203

Title:
  [MIR] unity-scope-click

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1614203/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to