On 12-Oct-2013, Thomas Goirand wrote:
> On 10/11/2013 01:42 PM, Dmitry Shachnev wrote:
> > Also, you have a typo in postinst files ('coverate' != 'coverage').
>
> This seems to be changed (by ben), though there's now other problems in
> the bzr version.
>
> […]
> Setting up python-coverage (3.7+dfsg.1-1) ...
> update-alternatives: error: alternative link /usr/bin/coverage is
> already managed by python-coverate
> dpkg: error processing python-coverage (--install):
> subprocess installed post-installation script returned error exit status 2
That error is reporting an existing “python-coverate” name managing the
command. This is only going to be a problem on systems that have that; the
released package won't have that. You can fix it on yours by deleting that
association.
> First, Ben changed from /usr/bin/coverage to /usr/bin/coverage3 in the
> python3-coverage.postinst. This loose the point! The point was to be
> able to have python-coverage and python3-coverage both provide
> /usr/bin/coverage...
Python 2 and Python 3 are being sdtrictly treated as separate run-time
systems in Debian. So my position is that ‘/usr/bin/coverage’ should not be
provided for Python 3.
> If you want python3-coverage to provide a /usr/bin/coverage3, you do not
> need to use update-alternative. Simply add a symlink and we are good to
> go.
Okay. So I shall remove the use of ‘upsate-alternatives’ altogether.
> Also, Ben replaced what I wrote by:
>
> master_link_path=/usr/bin/coverage
> package_name=python-coverage
> alternative_path=/usr/bin/python2-coverage
> priority=200
>
> update-alternatives --install ${master_link_path} ${package_name} \
> ${alternative_path} ${priority}
>
> which is wrong.
Does it behave incorrectly? How?
> link is the generic name for the master link
> name is the name of its symlink in the alternatives directory
> path is the alternative being introduced for the master link.
>
> Never, the man page talks about a package name, but about the name of
> the link in /etc/alternatives.
Right. I'm making clear, with the above, that the package name is being
used as the name of the link in the alternatives directory.
> Also, Ben, please do not add new variables if they are used only once.
I do not agree with that. Variables are useful for making explicit the
*meaning* of a value where it is used. So I'll continue to set variables
where they give a meaningful name to a value to make the packaging
configuration sufficiently explicit.
> It is also very annoying that you insist in removing the last line of
> the changelog in the BZR. Doing this, the package can't build, as
> dpkg-parsechangelog fails. Please don't do that, that's irritating. ! :)
Thanks for the feedback, but I also disagree on this one as detailed
earlier in bug#635476.
--
\ “I would rather be exposed to the inconveniences attending too |
`\ much liberty than those attending too small a degree of it.” |
_o__) —Thomas Jefferson, 1791-12-23 |
Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
