Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]
On Fri, Apr 05, 2019 at 10:05:09AM +0200, Olivier Sallou wrote:
>
> >>> Frequently, on conda package update, it checks and propose to update
> >>> conda. If it is installed via debian package, it should not self update
> >>> from conda web site.
> >> Sure, conda packaged for Debian should run self updates.
> > s/should/should NOT/
>
> I had understood ;-)
My correction was just for people without mind reading capabilities. ;-)
> I looked at failing tests.
>
> Some *could* be skiped I think as related to issue to capture
> stdout/stderr , might be linked to build with pbuild/gbp , ...
>
>
> Some other tests of install/activate/deactivate fail however due to
> other setup stuff (don't find where/why for the moment).
>
> It tries to exec conda from /usr/bin/conda instead of *build
> prefix*/bin/conda
>
> And logs show that CONDA_PREFIX is set to
>
> * /usr
May be CONDA_PREFIX can be set for the build process in d/rules?
> * /tmp/54d6 75cc (example) <= what looks strange here is there is a
> space in temp dir....
+1
> It may explain that it tries to use /tmp prefix , fail for not finding
> it, then use fallback prefix /usr (and fail too because not installed on
> system, which is fine as it is not yet installed).
>
>
> before skipping those, I'd better understand why and if only related to
> tests condition
I fully agree. It might be perfectly possible that I skiped to much
of these. I'd be really happy about proof reading of my patches.
Thanks a lot for looking into this
Andreas.
--
http://fam-tille.de
Reply to: