On Fri, Oct 11, 2013 at 7:47 AM, Thomas Goirand <z...@debian.org> wrote:
> By the way, I have just added the use of update-alternatives in the
> package so that it provides /usr/bin/coverage for those (upstream code
> or users) who needs it. After this, I think the package is up to shape
> for an upload: I tested it against some of the upstream code I maintain,
> and it generated correctly the expected coverage report.
Did you really test your changes?
----------8<----------
dmitry /tmp/python-coverage-3.7+dfsg.1 > sudo dpkg -i
../python-coverage_3.7+dfsg.1-1_i386.deb
../python3-coverage_3.7+dfsg.1-1_i386.deb
Selecting previously unselected package python-coverage.
(Reading database ... 362808 files and directories currently installed.)
Unpacking python-coverage (from .../python-coverage_3.7+dfsg.1-1_i386.deb) ...
Selecting previously unselected package python3-coverage.
Unpacking python3-coverage (from .../python3-coverage_3.7+dfsg.1-1_i386.deb) ...
Setting up python-coverage (3.7+dfsg.1-1) ...
Setting up python3-coverage (3.7+dfsg.1-1) ...
update-alternatives: error: alternative link /usr/bin/coverage is
already managed by python-coverate
dpkg: error processing python3-coverage (--install):
subprocess installed post-installation script returned error exit status 2
Processing triggers for man-db ...
Errors were encountered while processing:
python3-coverage
---------->8----------
Also, you have a typo in postinst files ('coverate' != 'coverage').
--
Dmitry Shachnev
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
