On Sun, Jan 31, 2010 at 12:27:46PM -0500, Yaroslav Halchenko wrote:
> cool, it seems that a simple
>
> - export PYTHONPATH=$$PWD/`/bin/ls -d build/lib.*`; cd doc; $(MAKE) html pdf
> + export PYTHONPATH=$$PWD/`/bin/ls -d build/lib.*`
> MPLCONFIGDIR=$(CURDIR)/build; cd doc; $(MAKE) html pdf
>
> is
> > > consider setting MPLCONFIGDIR to a writable directory for matplotlib
> > > configuration data
> > The issue seems to have been the use of PWD as opposed to CURDIR, as
> > was pointed out to me by Cyril and Jakub. The new package seems to
> > have built on s390, so I'd presume that that fixe
Dear Yaroslav,
On Sun, Jan 31, 2010 at 11:43:28AM -0500, Yaroslav Halchenko wrote:
> Hi Kumar,
>
> I wonder, have you tried to follow recommendation thrown by matplotlib,
> which was
>
> consider setting MPLCONFIGDIR to a writable directory for matplotlib
> configuration data
The issue seems t
On Sun, 31 Jan 2010, Kumar Appaiah wrote:
> > consider setting MPLCONFIGDIR to a writable directory for matplotlib
> > configuration data
> The issue seems to have been the use of PWD as opposed to CURDIR, as
> was pointed out to me by Cyril and Jakub. The new package seems to
> have built on s3
Hi Kumar,
I wonder, have you tried to follow recommendation thrown by matplotlib,
which was
consider setting MPLCONFIGDIR to a writable directory for matplotlib
configuration data
i.e. instead of exporting HOME, to export MPLCONFIGDIR ?
> ,[ Build log excerpt ]
> | Exception occurred:
>
found 535699 0.1.2+1741-2.1
thanks
(This should reopen the bug, checking my BTS skills. ;))
Debian Bug Tracking System (31/01/2010):
> This is an automatic notification regarding your Bug report
> which was filed against the nipy package:
>
> #535699: nipy: FTBFS: Tries to write to $HOME during
6 matches
Mail list logo