On Thu, 23 Nov 2006, Alexandre Fayolle wrote:
> > This module provides python2.[1234]-pymacs but it should instead provide
> > ${python:Provides} to avoid providing versions of the module that it is no
> > more providing because we dropped them from the set of supported versions
> > (as
> > is the case with python2.3 in unstable).
>
> Hi,
>
> I'm not sure about this one. The source package currently in unstable
> ships python2.1-pymacs, python2.2-pymacs and python2.3-pymacs, and
> subsequent changes lead to a single binary package called pymacs. The
> Provides is here to ensure a smooth upgrade for sarge -> etch. Am I
> missing something? Should I do this in a different way (e.g. shipping
> empty python2.X-pymacs packages depending on pymacs)?
Given that nobody uses python2.X-pymacs to depend on your package, I think
it's ok to leave it as is.
Post-etch though, you might want to drop some cruft in the Provides: header
as the Provides from the technical side is wrong: your package only
provides the modules for the current python-version and not for all the
versions listed.
Note that ${python:Provides} wouldn't help much in this case AFAIK since
the package is named pymacs and not python-pymacs and only the latter case
is supported by dh_pycentral.
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
