On Tue, 2016-09-20 at 16:57 +, Michael Terry wrote:
> OK, so with [1] I'm feeling a little better about the departments.db
> mystery. There still doesn't seem to be information about which
> clicks
> are listed in the database, and thus which clicks you should have
> installed before running t
I've been trying to explain that there really is no reason to need to
perform an update of this file, unless we are releasing a new
phone/tablet in a new country. However, I have made a branch which more
clearly states how to update the file with new languages, in an MP:
https://code.launchpad.net
On Fri, 2016-08-19 at 14:11 +, Michael Terry wrote:
> OK, maybe I was overly grumpy last time I commented, I didn't mean to
> sound hostile.
>
> ---
>
> As for the autopkg tests, you're right that building the package is
> something.
>
> But one of the goals of a MIR is to ensure that packag
On Thu, 2016-08-18 at 19:52 +, Michael Terry wrote:
> >
> > We still run autopkgtests.
> OK, in the most technical sense, you still run autopkgtests. But the
> script you run only has some exports and a commented out exec line.
>
> So lets not be pedantic; there are no autopkgtests right now
On Wed, 2016-08-17 at 21:00 +, 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 ju
