Package: python-twisted-core Version: 2.2.0-1 Severity: normal The python-twisted-core package introduces a swath of Conflicts entries, but there is no indication in the documentation of what cuases these conflicts or how to address them.
Conflicts: python2.3-twisted (< 2.1.0-4), python2.4-twisted (< 2.1.0-4),
toursst (<= 0.0.3ubuntu1), pymusique
(<= 0.5-0.3), python-textile (<= 2.0.10-3), python-ldaptor (<=
0.0.41), londonlaw (<= 0.2.0-2),
libunderware (<= 0.2.12-1), ardour-session-exchange (<=
0.9beta29-1), apt-proxy (<= 1.9.30),
python-twisted (< 2.1.0-4)
The conflicts against other 'twisted' packages are understandable, but
there's no explanation for why it conflicts against 'toursst',
'pymusique', 'python-textile' et cetera. I was expecting to see
something explaining this change in changelog.Debian, but there's no
mention of it.
For example, the package I want to install which brought this problem
to my attemtion is 'python-textile'. There are no outstanding bugs
against 'python-textile' that relate to python-twisted, and the most
recent release of 'python-textile' is 2.0.10-3, which is exactly the
version you've chosen to Conflicts against.
If there's something the 'python-textile' package maintainer needs to
do, there's no indication of it in the bug tracker. As it is, the
Conflicts entry makes 'python-textile' fail to install. I presume the
situation is similar for 'pymusique' and others.
Please either file bugs against the affected packages, so their
maintainers know what to do to make their packages comply with the new
python-twisted-core, or explain to the user how to work around this
(e.g. in the README.Debian).
--
\ "Firmness in decision is often merely a form of stupidity. It |
`\ indicates an inability to think the same thing out twice." -- |
_o__) Henry L. Mencken |
Ben Finney <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
