Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Andreas Tille-5
Hi,

I'd like to ask for help with packaging Conda.  I think its good to have
it packaged since several users use it and finally we want to support
our users as best as possble.  I have commited an initial packaging to

  https://salsa.debian.org/med-team/conda

To build and install you need python-pycosat which is in new queue
currently.  You can clone and build it for your local tests from

  https://salsa.debian.org/med-team/python-pycosat

The Conda build has 5 remaining failures which I do not understand.  I
wonder if some volunteer is sure that these failures either can be
ignored since it makes no sense to run this test in a pbuilder chroot or
possibly fix the test to make it pass.

Kind regards

      Andreas.

----- Forwarded message from Andreas Tille <[hidden email]> -----

Date: Thu, 04 Apr 2019 22:00:12 +0200
From: Andreas Tille <[hidden email]>
To: Debian Bug Tracking System <[hidden email]>
Subject: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
X-Debian-PR-Message: report 926416
X-Debian-PR-Package: wnpp
X-Debian-PR-Keywords:

Package: wnpp
Severity: wishlist

Subject: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
Package: wnpp
Owner: Andreas Tille <[hidden email]>
Severity: wishlist

* Package name    : conda
  Version         : 4.6.10
  Upstream Author : xx-20yy <upstream>
* URL             : https://conda.io/
* License         : <license>
  Programming Lang: Python
  Description     : OS-agnostic, system-level binary package manager and ecosystem
 Conda is a cross-platform, language-agnostic binary package manager. It
 is the package manager used by Anaconda installations, but it may be
 used for other systems as well. Conda makes environments first-class
 citizens, making it easy to create independent environments even for C
 libraries.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/conda

_______________________________________________
Debian-med-packaging mailing list
[hidden email]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

----- End forwarded message -----

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Tony Travis
On 04/04/2019 21:30, Andreas Tille wrote:

> Hi,
>
> I'd like to ask for help with packaging Conda.  I think its good to have
> it packaged since several users use it and finally we want to support
> our users as best as possble.  I have commited an initial packaging to
>
>    https://salsa.debian.org/med-team/conda
>
> To build and install you need python-pycosat which is in new queue
> currently.  You can clone and build it for your local tests from
>
>    https://salsa.debian.org/med-team/python-pycosat
>
> The Conda build has 5 remaining failures which I do not understand.  I
> wonder if some volunteer is sure that these failures either can be
> ignored since it makes no sense to run this test in a pbuilder chroot or
> possibly fix the test to make it pass.

Hi, Andreas.

I want to volunteer to help, but I don't know how to use pbuild
properly! I'll give it a try and let you know how I get on ;-)

Bye,

   Tony.

--
Minke Informatics Limited, Registered in Scotland - Company No. SC419028
Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK)
tel. +44(0)19755 63548                    http://minke-informatics.co.uk
mob. +44(0)7985 078324        mailto:[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Olivier Sallou
In reply to this post by Andreas Tille-5

On 4/4/19 10:30 PM, Andreas Tille wrote:
> Hi,
>
> I'd like to ask for help with packaging Conda.  I think its good to have
> it packaged since several users use it and finally we want to support
> our users as best as possble.  I have commited an initial packaging to
>
>   https://salsa.debian.org/med-team/conda
I think indeed it is a good catch, but I wonder if it should be in
med-team. Should not it rather be in python team?

>
> To build and install you need python-pycosat which is in new queue
> currently.  You can clone and build it for your local tests from
>
>   https://salsa.debian.org/med-team/python-pycosat
>
> The Conda build has 5 remaining failures which I do not understand.  I
> wonder if some volunteer is sure that these failures either can be
> ignored since it makes no sense to run this test in a pbuilder chroot or
> possibly fix the test to make it pass.
I'll try to get a look

>
> Kind regards
>
>       Andreas.
>
> ----- Forwarded message from Andreas Tille <[hidden email]> -----
>
> Date: Thu, 04 Apr 2019 22:00:12 +0200
> From: Andreas Tille <[hidden email]>
> To: Debian Bug Tracking System <[hidden email]>
> Subject: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
> X-Debian-PR-Message: report 926416
> X-Debian-PR-Package: wnpp
> X-Debian-PR-Keywords:
>
> Package: wnpp
> Severity: wishlist
>
> Subject: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
> Package: wnpp
> Owner: Andreas Tille <[hidden email]>
> Severity: wishlist
>
> * Package name    : conda
>   Version         : 4.6.10
>   Upstream Author : xx-20yy <upstream>
> * URL             : https://conda.io/
> * License         : <license>
>   Programming Lang: Python
>   Description     : OS-agnostic, system-level binary package manager and ecosystem
>  Conda is a cross-platform, language-agnostic binary package manager. It
>  is the package manager used by Anaconda installations, but it may be
>  used for other systems as well. Conda makes environments first-class
>  citizens, making it easy to create independent environments even for C
>  libraries.
>
> Remark: This package is maintained by Debian Med Packaging Team at
>    https://salsa.debian.org/med-team/conda
>
> _______________________________________________
> Debian-med-packaging mailing list
> [hidden email]
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
>
> ----- End forwarded message -----
>
--
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Olivier Sallou

On 4/5/19 8:59 AM, Olivier Sallou wrote:
> On 4/4/19 10:30 PM, Andreas Tille wrote:
>> Hi,
>>
>> I'd like to ask for help with packaging Conda.  I think its good to have
>> it packaged since several users use it and finally we want to support
>> our users as best as possble.  I have commited an initial packaging to
>>
>>   https://salsa.debian.org/med-team/conda

I think also that there will be a need of additional patch (no idea yet
where the issue is in code) to disable auto-update.

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.


> I think indeed it is a good catch, but I wonder if it should be in
> med-team. Should not it rather be in python team?
>> To build and install you need python-pycosat which is in new queue
>> currently.  You can clone and build it for your local tests from
>>
>>   https://salsa.debian.org/med-team/python-pycosat
>>
>> The Conda build has 5 remaining failures which I do not understand.  I
>> wonder if some volunteer is sure that these failures either can be
>> ignored since it makes no sense to run this test in a pbuilder chroot or
>> possibly fix the test to make it pass.
> I'll try to get a look
>> Kind regards
>>
>>       Andreas.
>>
>> ----- Forwarded message from Andreas Tille <[hidden email]> -----
>>
>> Date: Thu, 04 Apr 2019 22:00:12 +0200
>> From: Andreas Tille <[hidden email]>
>> To: Debian Bug Tracking System <[hidden email]>
>> Subject: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
>> X-Debian-PR-Message: report 926416
>> X-Debian-PR-Package: wnpp
>> X-Debian-PR-Keywords:
>>
>> Package: wnpp
>> Severity: wishlist
>>
>> Subject: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem
>> Package: wnpp
>> Owner: Andreas Tille <[hidden email]>
>> Severity: wishlist
>>
>> * Package name    : conda
>>   Version         : 4.6.10
>>   Upstream Author : xx-20yy <upstream>
>> * URL             : https://conda.io/
>> * License         : <license>
>>   Programming Lang: Python
>>   Description     : OS-agnostic, system-level binary package manager and ecosystem
>>  Conda is a cross-platform, language-agnostic binary package manager. It
>>  is the package manager used by Anaconda installations, but it may be
>>  used for other systems as well. Conda makes environments first-class
>>  citizens, making it easy to create independent environments even for C
>>  libraries.
>>
>> Remark: This package is maintained by Debian Med Packaging Team at
>>    https://salsa.debian.org/med-team/conda
>>
>> _______________________________________________
>> Debian-med-packaging mailing list
>> [hidden email]
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
>>
>> ----- End forwarded message -----
>>
--
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Andreas Tille-5
Hi Olivier,

On Fri, Apr 05, 2019 at 08:59:57AM +0200, Olivier Sallou wrote (in another mail which I merged in here):
> >   https://salsa.debian.org/med-team/conda
> I think indeed it is a good catch, but I wonder if it should be in
> med-team. Should not it rather be in python team?

I do not mind about what team the package is in.  We have several
packages in Debian Med that also could be there.  My main motivation is
that I'm observing issues in Debian Med really close and issues on
packages in other teams might slip through my attention.  If I could be
sure that somebody else in Python team would feel responsible for the
package that would be fine.  If not - I'd prefer to keep it where it is
now.

On Fri, Apr 05, 2019 at 09:12:16AM +0200, Olivier Sallou wrote:
>
> >>   https://salsa.debian.org/med-team/conda
>
> I think also that there will be a need of additional patch (no idea yet
> where the issue is in code) to disable auto-update.
>
> 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.

Kind regards

       Andreas.

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Dylan Aïssi-3
Hi,

If we have some questions regarding conda, we can ask to upstream,
they should be happy to help us.

  https://github.com/conda/conda/issues/1235

Best,
Dylan

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Andreas Tille-5
In reply to this post by Andreas Tille-5
On Fri, Apr 05, 2019 at 09:23:22AM +0200, Andreas Tille wrote:

> Hi Olivier,
>
> On Fri, Apr 05, 2019 at 08:59:57AM +0200, Olivier Sallou wrote (in another mail which I merged in here):
> > >   https://salsa.debian.org/med-team/conda
> > I think indeed it is a good catch, but I wonder if it should be in
> > med-team. Should not it rather be in python team?
>
> I do not mind about what team the package is in.  We have several
> packages in Debian Med that also could be there.  My main motivation is
> that I'm observing issues in Debian Med really close and issues on
> packages in other teams might slip through my attention.  If I could be
> sure that somebody else in Python team would feel responsible for the
> package that would be fine.  If not - I'd prefer to keep it where it is
> now.
>
> On Fri, Apr 05, 2019 at 09:12:16AM +0200, Olivier Sallou wrote:
> >
> > >>   https://salsa.debian.org/med-team/conda
> >
> > I think also that there will be a need of additional patch (no idea yet
> > where the issue is in code) to disable auto-update.
> >
> > 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/

 

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Olivier Sallou

On 4/5/19 9:55 AM, Andreas Tille wrote:

> On Fri, Apr 05, 2019 at 09:23:22AM +0200, Andreas Tille wrote:
>> Hi Olivier,
>>
>> On Fri, Apr 05, 2019 at 08:59:57AM +0200, Olivier Sallou wrote (in another mail which I merged in here):
>>>>   https://salsa.debian.org/med-team/conda
>>> I think indeed it is a good catch, but I wonder if it should be in
>>> med-team. Should not it rather be in python team?
>> I do not mind about what team the package is in.  We have several
>> packages in Debian Med that also could be there.  My main motivation is
>> that I'm observing issues in Debian Med really close and issues on
>> packages in other teams might slip through my attention.  If I could be
>> sure that somebody else in Python team would feel responsible for the
>> package that would be fine.  If not - I'd prefer to keep it where it is
>> now.
>>
>> On Fri, Apr 05, 2019 at 09:12:16AM +0200, Olivier Sallou wrote:
>>>>>   https://salsa.debian.org/med-team/conda
>>> I think also that there will be a need of additional patch (no idea yet
>>> where the issue is in code) to disable auto-update.
>>>
>>> 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  ;-)


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

* /tmp/54d6 75cc (example) <= what looks strange here is there is a
space in temp dir....

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

Olivier



>
>  
>
--
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Andreas Tille-5
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 | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Olivier Sallou

On 4/5/19 10:09 AM, Andreas Tille wrote:

> 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.


It tries to switch from different environments and fails at default one
which is /usr (no write access)


si I think tests calling self.basic_posix should be disabled in
test_activate.py

>
> Thanks a lot for looking into this
>
>        Andreas.
>
--
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438


Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Andreas Tille-5
On Fri, Apr 05, 2019 at 12:00:29PM +0200, Olivier Sallou wrote:
> It tries to switch from different environments and fails at default one
> which is /usr (no write access)
>
>
> I think tests calling self.basic_posix should be disabled in
> test_activate.py

Done and pushed - feel free to change it yourself in case you want to
make further changes.

Kind regards

       Andreas.

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: Please help with Conda packaging [Was: Bug#926416: ITP: conda -- OS-agnostic, system-level binary package manager and ecosystem]

Andreas Tille-5
On Fri, Apr 05, 2019 at 02:31:53PM +0200, Andreas Tille wrote:

> On Fri, Apr 05, 2019 at 12:00:29PM +0200, Olivier Sallou wrote:
> > It tries to switch from different environments and fails at default one
> > which is /usr (no write access)
> >
> >
> > I think tests calling self.basic_posix should be disabled in
> > test_activate.py
>
> Done and pushed - feel free to change it yourself in case you want to
> make further changes.

Any more hints for the remaining test failures?

Kind regards

       Andreas.

--
http://fam-tille.de