On 21 Nov, 23:09, Steven Samuel Cole <[EMAIL PROTECTED]>
wrote:
>
> 1. I must use a 'higher-level' tool than dpkg to install the package
> which automatically resolves and installs dependency packages. There has
> got to be a way to use apt-get for .deb files which do not reside
> (yet) in a repo
Steven,
apt-get uses /etc/apt/sources.list file to know where packages must be
downloaded from. Usually from a http repository. But, you can use a file
destination:
deb file:/path/to/file unstable main contrib non-free
I advise you to read the debian maintainer guide and the apt-get and
sources.l
That's exactly the piece of information I needed! :-)
The control file created by setdeb (stdeb_run_setup, to be precise)
looks like this (some lines will get wrapped):
Source:
Maintainer:
Section: python
Priority: optional
Build-Depends: python-setuptools (>= 0.6b3-1), python-all-dev (>=
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
Hey Paul
thanks for your reply! :-)
2008/11/21 Paul Boddie <[EMAIL PROTECTED]>:
> 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
Hi Stephane,
thanks for your reply! :-)
I do not get any notification or warning or whatever from dpkg, all
output I get when running
# sudo dpkg -i python-_0.0.1-4927-1_all.deb
is
Selecting previously deselected package python-.
(Reading database ... 15026 files and directories cur
On 20 Nov, 02:14, "Steven Samuel Cole" <[EMAIL PROTECTED]>
wrote:
>
> I am trying to build a debian package for my python modules using
> stdeb and dpkg-buildpackage. The package building itself works, I also
> managed to have an entry point created and I can use my python modules
> on the Ubuntu v
Hi Steven,
This is a normal behaviour for dpkg. If there is a failing dependancy, dpkg
will not install dependancies, it will notify only and will not install the
package. Dependancies installations are managed by the front-end to dpkg
(aptitude or apt). This is not a python issue that you are faci
