On 22-May-2013, Barry Warsaw wrote: > If the consensus is indeed that upgrading coverage in Debian must block > on packaging the JS components, so be it. I will gladly help with > coverage packaging, including adding Python 3 support, once the JS bits > are done.
The blocking bugs are now being addressed by some helpful Debian developers. So in preparation, I am making the necessary changes to the ‘python-coverage’ packaging. Please have a look at the current packaging work in my Bazaar branch <URL:http://anonscm.debian.org/bzr/collab-maint/python-coverage/python-coverage.debian/> or, if you already have an SSH account at Alioth, much faster is to use <URL:bzr+ssh://bzr.debian.org/bzr/collab-maint/python-coverage/python-coverage.debian/>. I am also removing the now-obsolete “DM-Upload-Allowed” field; can you grant me the required permissions via ‘dak’ <URL:https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html>? The package currently passes Lintian's tests (modulo the missing ECMAScript libraries), so now I'm concerned with the resulting installed packages: * actually work correctly for both Python 2 and 3? * use the new shared-library dependencies correctly per Policy 8.6? * build and separate debug symbols packages correctly? * substitute the system ECMAScript libraries correctly? * explain sufficiently to the user in ‘README.Debian’? * etc. -- \ “Those are my principles. If you don't like them I have | `\ others.” —Groucho Marx | _o__) | Ben Finney <[email protected]>
signature.asc
Description: Digital signature
