Re: Missing Provides in python-crypto and others

[Matthias Klose <doko@cs.tu-berlin.de>]

Adeodato =?utf-8?B?U2ltw7M=?= writes:
> Hi,
> 
> I noticed that python-crypto had undergone the new Python Policy
> transition thanks to a NMU from Matthias Klose [1]. However, I could not
> update to this version, since python2.4-paramiko Depends: python2.4-crypto,
> but the new python-crypto package does not provide it.
> 
>   [1] http://packages.qa.debian.org/p/python-crypto/news/20060616T020207Z.html
> 
> I thought such Provides field was mandatory under the new policy, and
> although I failed to find this requirement in the policy itself [2],
> it's set pretty straightforwardly in item #5 of the NewPolicy wiki page [3].

it's a bug in python-crypto, missing the Provides field.

> I prepared a python-crypto NMU to fix this, but before uploading I
> had a look

please do, please fix the rules file as well.

> at the archive and saw that several other packages seem to suffer the same,
> which made me doubt of myself having understood the issue correctly. (I'm
> attaching a list of those I found; I left out python-twisted-*, and others
> that my grep-dctrl search may have missed).

Raphael's rationale leaving these out was, that in most cases the
provides are not needed for arch-indep packages with a Python-Version:
all and would need an extra upload if we add or drop a supported
Python version. This decision should be made by the maintainer
(including a Provides fields), so the debhelper tools should generate
it even for binary-indep packages.

Any binary-arch package missing the provides is wrong. Fixing
python-kjbuckets and python-numarray-*.

  Matthias