Hi Lester, You are right about this. Thanks for the correction.
The policy says: Packages must use the ``UNRELEASED`` distribution in ``debian/changelog`` if the current version in the VCS source has not been uploaded yet. Only when a package's new version is about to be uploaded should the distribution be changed to ``unstable`` or another suitable distribution. So UNRELEASED is not a mistake, it is what the team requires. When to flip it: your expectation matches what the policy describes, so don't change anything preemptively. The only thing I would do is raise it explicitly when a sponsor picks this up, because the .changes currently carries Distribution: UNRELEASED and that has to become unstable before the upload can be accepted. Whether they want you to flip it and re-upload to mentors, or would rather do it themselves at upload time, seems to be sponsor preference rather than something the policy settles. On the lintian tags and the test failures: leaving them alone is a defensible call and I would not treat it as a gap. A first upload that adopts a package and changes as little as possible is easier to review than one that also rewrites the packaging. The test results are 5 failing out of 578, all one fixture that does not reach the build tree, but it's pre-existing and not a regression. Sorry for the noise on your first package. I've just started getting into Debian packaging as well. The rest of it looked good to me. Regards, Dustin Kost [email protected]
