"Donovan Baarda" <[EMAIL PROTECTED]> wrote:
> G'day,
Hi,
> I was going to reply "this is why many packages sanitize PATH in their
> scripts", but after checking through /var/lib/dpkg/info/* it seems they
> don't.
Indeed, Policy ยง 6.1 says they should not:
,
| Programs called from maintaine
Donovan Baarda wrote:
I have a feeling PYTHONPATH should be unset in all python postinst and
maybe prerm scripts (something to add to the python policy?). A manually
set PYTHONPATH can do evil things to any python package's postinst and
prerm.
A manually set PATH can do evil things to any package'
day, February 05, 2004 7:29 PM
Subject: Re: Bug#230704: zope-testcase: SOFTWARE_HOME and INSTANCE_HOME can
break install.
> Donovan Baarda wrote:
> > I have a feeling PYTHONPATH should be unset in all python postinst and
> > maybe prerm scripts (something to add to the python policy?). A
On Tue, Feb 03, 2004 at 07:34:30AM +0100, Andreas Tille wrote:
> On Tue, 3 Feb 2004, Donovan Baarda wrote:
[...]
> I'll do an upload in the next couple of hours with this changes.
[...]
BTW, thanks for doing the package... nice work :-)
> > Unsetting of http_proxy is only there to bypass a bug in
On Tue, 3 Feb 2004, Donovan Baarda wrote:
> I just tested it, and found there was another problem with a set PYTHON
> path. By adding the following to the top of the postinst, I got
> "zope-testcase.postinst configure" to run properly with my development
> environment in place;
>
> unset PYTHONPAT
I'm Cc'ing this to debian-python because it has stuff that can impact on
other python packages.
On Tue, 2004-02-03 at 06:20, Andreas Tille wrote:
> On Tue, 3 Feb 2004, Donovan Baarda wrote:
>
> > Yeah, if the postinst simply "unset" them both before running at least
> > "$PYTHON runalltests.py" i
6 matches
Mail list logo
