Bug#602471: pymca: package unusable

Teemu Ikonen tpikonen at gmail.com
Mon Nov 15 13:41:11 UTC 2010


Hello Armando,

On Mon, Nov 15, 2010 at 10:33 AM, "V. Armando Solé" <sole at esrf.fr> wrote:
> From the PyMca side, the problem seems to be solved.
>
> By default, PyMca uses the solutions described in previous mail.
>
> On linux systems using glibc, the end user or package maintainer, can choose
> a much cleaner solution based on the use of the strtod_l function. That
> function is only available when the _GNU_SOURCE compiler flag is defined.
>
> I have foreseen a simple way to enable that possibility using setup.py:
>
> SPECFILE_USE_GNU_SOURCE=1 python setup.py ....

Thanks for the fix. The SVN changeset containing this fix (1172) does
not apply cleanly on top of the 4.4.0 release version. Could you make
a patch fixing this problem against the 4.4.0 release, or do you think
that the SVN version is good enough to be used as it is? Or, do we get
a new release of PyMca soon? :)

I would be somewhat hesitant in packaging SVN snapshots, unless you
think it is the most stable and bug-free version available at the
moment.

Best,

Teemu





More information about the debian-science-maintainers mailing list