Re: Bug#118916: wajig: should depend on python, not python-base
Dirk Eddelbuettel writes:
>
> "Ben" == Ben Burton <benb@acm.org> writes:
> Ben> Package: wajig Version: N/A; reported 2001-11-09 Severity: serious
> Ben>
> Ben> Hi. Package wajig cannot be installed because it depends on the
> Ben> non-existant "python-base". Python packages have recently been
> Ben> changed according to the new python policy. Wajig should depend on
> Ben> "python" instead.
>
> Yes, I goofed. The only lame excuse is that it worked on my testing box.
>
> Now, as I read the python-policy.txt, I should Depends / Build-Depends as in
>
> Source: wajig
> [...]
> Build-Depends: debhelper (>> 3.0.0), python2.1-dev
> [...]
> Package: wajig
> Depends: python (>= 2.1), python (<< 2.2), wget, apt
>
> However wajig is a "mere" Python app, and a package providing modules. I have
> verified that my 1.5.2 build works with /usr/bin/python2.1 -- so could I
> not use
No. It depends on a specific version of python, as it includes the
.py[co] files, which are version specific. The package works with any
Python version >= 1.5, but if the version for generating the compiled
files and the version for running the compiled files are different,
then the compiled files aren't used. And running wajig as root, writes
new compiled files ...
> Source: wajig
> [...]
> Build-Depends: debhelper (>> 3.0.0), python-dev
> [...]
> Package: wajig
> Depends: python, wget, apt
>
> instead? Please advise as I am unable to make up my mind here. Python Policy
> seems clear enough, but overly restrictive for this case.
yes, we may want to have something like a python-register-files, which
is called in the postinst/prerm, which compiles these files for the
current version, but nobody yet volunteered ...
What you already can do is to call py_compile in the postinst. See the
/usr/doc/python2.1/sample.p* files for an example.
> My current changelog draft is:
>
> wajig (0.2.8-2) unstable; urgency=low
>
> * Adapted Python Policy (as of version 0.3.7)
> * debian/control: Depends python (>= 2.1), python (<< 2.2) (Closes: #118916)
> * debian/control: Added Build-Depends on python2.1-dev (Closes: #19009)
>
> -- Dirk Eddelbuettel <edd@debian.org> Sat, 10 Nov 2001 20:18:38 -0600
I didn't look at the new source, but build-depending on python2.1-dev
means that you have to call python2.1 during the build. `python' may
point to something else, if we change the python version to 2.2. So
either build-depend on python (>= 2.1), python (<< 2.2) or use
`python2.1'.
Matthias
Reply to: