> 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. > 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. Yup, I know. "due to a bug" is bug 1532358, that I already linked above. The bug where the plan was to temporarily disable the tests. Six months ago. So who's working on figuring out why the tests are flaky? Is every single test flaky? All of them were disabled. Can we discover which are flaky and can we selectively disable only them? Have things gotten more stable in the last six months? >> - 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. That doesn't really address the issue -- which is binary blobs being distributed without their "preferred form of modification" being a violation of the DFSG. For example, what locales were used on the command line? And it looks like you need a very particular setup with certain packages installed... i.e. someone with just the tarball can't easily reproduce that database See https://ftp-master.debian.org/REJECT-FAQ.html and its "Generated files" entry. Is there a way we can generate the file on first boot? Or ship some .desktop files in the package along with a script so that we can generate the file during build? (Or build-dep on some packages to get access to their desktop files...) >> - ${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)? Sure. Bug 1614679. ** Changed in: unity-scope-click (Ubuntu) Status: New => Incomplete -- 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
