"Ben" == Ben Burton <[EMAIL PROTECTED]> 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 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. 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 <[EMAIL PROTECTED]> Sat, 10 Nov 2001 20:18:38 -0600 Thanks, Dirk -- Better to have an approximate answer to the right question than a precise answer to the wrong question. -- John Tukey