Python / Debian package dependencies

[Stephane Bulot]

I'm not familiar with stdeb, but dpkg-buildpackage needs a file called
"control". This is this file that will be used to generate deb archive with
the good dependancies. Into this file, there are two fields, Build-Depends
and Depends, that give to dpkg-buildpackage what are the package
dependancies.
Check this "control" file content, you should have psycopg2 and setuptools
(if it is really a dependancy) in the Depends field. If it not the case, do
it manually. Do not forget to check and notify the version of this
dependancies.
Regards.
Stephane

2008/11/21 Steven Samuel Cole <steven.samuel.cole at gmail.com>

> Hey Paul
>
> thanks for your reply! :-)
>
> 2008/11/21 Paul Boddie <paul at boddie.org.uk>:
> > Are you saying that psycopg2 needs setuptools for the setup.py script
> > to work? This isn't generally the case (or wasn't), but maybe the
> > "entry point" is a setuptools thing which would then demand that
> > software's presence.
>
> Not exactly. My package requires psycopg2 to run and (from what it
> looks like to me) setuptools must be available in order to use its
> installation mechanism (setup.py, entry points, etc.)
>
> > How does stdeb know which package provides psycopg2? I'm not really
> > familiar with stdeb - I write my own packaging files - but might it be
> > the case that you need to specify python-psycopg2 instead?
>
> I tried python-psycopg2, but that caused a ValueError in stdeb about a
> 'parenthesized list' -psycopg2.
> By trial & error I found out that I seem to have to use the package
> name without the python- bit, because then stdeb does run without
> error.
>
> If the name was really the issue, I would at least expect stdeb to
> report an error about an unknown package or so...
>
> Cheers,
>
> Stefan
>
> 2008/11/21 Steven Samuel Cole <steven.samuel.cole at gmail.com>:
> > Hey Paul
> >
> > thanks for your reply! :-)
> >
> > 2008/11/21 Paul Boddie <paul at boddie.org.uk>:
> >> Are you saying that psycopg2 needs setuptools for the setup.py script
> >> to work? This isn't generally the case (or wasn't), but maybe the
> >> "entry point" is a setuptools thing which would then demand that
> >> software's presence.
> >
> > Not exactly. My package requires psycopg2 to run and (from what it
> > looks like to me) setuptools must be available in order to use its
> > installation mechanism (setup.py, entry points, etc.)
> >
> >> How does stdeb know which package provides psycopg2? I'm not really
> >> familiar with stdeb - I write my own packaging files - but might it be
> >> the case that you need to specify python-psycopg2 instead?
> >
> > I tried python-psycopg2, but that caused a ValueError in stdeb about a
> > 'parenthesized list' -psycopg2.
> > By trial & error I found out that I seem to have to use the package
> > name without the python- bit, because then stdeb does run without
> > error.
> >
> > If the name was really the issue, I would at least expect stdeb to
> > report an error about an unknown package or so...
> >
> > Cheers,
> >
> > Stefan
> >
> --
> http://mail.python.org/mailman/listinfo/python-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20081121/196f14c2/attachment-0001.html>