This repository has been archived by the owner on Sep 11, 2023. It is now read-only.
pyemma on conda omnia channel not up to date #1033
Comments
|
I think we didn't upgrade pyemma-dev ever, did we? If we don't pursue
this line consistently, we should get rid of it to avoid confusion.
Am 01/02/17 um 22:03 schrieb João M. Damas:
…
A fork from issue #1032
<#1032>
It's currently on version 2.2.7. pyemma-dev is also much more outdated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1033>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AGMeQgG7RZ800DO8Voa5H_AOMpdyJAfuks5rYPMUgaJpZM4L0YgL>.
--
----------------------------------------------
Prof. Dr. Frank Noe
Head of Computational Molecular Biology group
Freie Universitaet Berlin
Phone: (+49) (0)30 838 75354
Web: research.franknoe.de
Mail: Arnimallee 6, 14195 Berlin, Germany
----------------------------------------------
|
|
I remember in the past @marscher mentioning it as a good way to test the latest version of pyemma, and I understood it got automatically/periodically updated. Actually, I haven't been using it and I just noticed it because of the issue with the main package |
|
Sorry guys, something went wrong copying over the files from conda-forge. Now the files are in place. (for documentation: anaconda copy --to-owner omnia conda-forge/pyemma/2.3) |
|
Thanks, but hold on:
|
|
On 02.02.2017 11:08, Frank Noe wrote:
Thanks, but hold on:
* this issue is also about pyemma-dev being outdated. What do we do
with that?
delete it. If anybody ever used it-he/she would have dropped it after
very short period. The problem was mainly to inquire a sane versioning
(deriving it from git would have been the most preferable solution,
however near to impossible to implement with the conda-dev-recipes
solution). It took me lots of time to try to get this working properly.
Installing a dev-version with pip takes 5 minutes for the first install
and 30 seconds to upgrade. I think there is even a section in the docs
about it.
* what do you mean by the line for documentation: anaconda copy
--to-owner omnia conda-forge/pyemma/2.3
It is the command to copy the conda-forge packages to omnia.
|
|
Am 02/02/17 um 12:57 schrieb Martin K. Scherer:
On 02.02.2017 11:08, Frank Noe wrote:
> Thanks, but hold on:
>
> * this issue is also about pyemma-dev being outdated. What do we do
> with that?
delete it. If anybody ever used it-he/she would have dropped it after
very short period. The problem was mainly to inquire a sane versioning
(deriving it from git would have been the most preferable solution,
however near to impossible to implement with the conda-dev-recipes
solution). It took me lots of time to try to get this working properly.
Installing a dev-version with pip takes 5 minutes for the first install
and 30 seconds to upgrade. I think there is even a section in the docs
about it.
I'm fine with this. Delete it.
> * what do you mean by the line for documentation: anaconda copy
> --to-owner omnia conda-forge/pyemma/2.3
It is the command to copy the conda-forge packages to omnia.
OK. Should this go to the developer docs?
…
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1033 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGMeQihqDPkkf-G6ngrxi2_88j1M4UZVks5rYcSTgaJpZM4L0YgL>.
--
----------------------------------------------
Prof. Dr. Frank Noe
Head of Computational Molecular Biology group
Freie Universitaet Berlin
Phone: (+49) (0)30 838 75354
Web: research.franknoe.de
Mail: Arnimallee 6, 14195 Berlin, Germany
----------------------------------------------
|
|
I've made the dev-package private, so it can't be used anymore. I don't think this single command should go to dev docs, because we only need it for the transition to conda-forge, which shouldn't take so long. I just posted it here, to have it somewhere (searchable). |
|
ok
Am 02/02/17 um 14:28 schrieb Martin K. Scherer:
…
I've made the dev-package private, so it can't be used anymore. I
don't think this single command should go to dev docs, because we only
need it for the transition to conda-forge, which shouldn't take so
long. I just posted it here, to have it somewhere (searchable).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1033 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGMeQjJ89_XD46AfxJ3RrWX7nrq7_H88ks5rYdn0gaJpZM4L0YgL>.
--
----------------------------------------------
Prof. Dr. Frank Noe
Head of Computational Molecular Biology group
Freie Universitaet Berlin
Phone: (+49) (0)30 838 75354
Web: research.franknoe.de
Mail: Arnimallee 6, 14195 Berlin, Germany
----------------------------------------------
|
|
Hi, So the pyemma conda package will disappear from omnia and only be available in the conda-forge channel? @mj-harvey, be need to change our sync of pyemma from omnia to conda-forge if that's the case. cc: @giadefa @stefdoerr |
|
On 02/02/2017 02:33 PM, João M. Damas wrote:
Hi,
So the pyemma conda package will disappear from omnia and only be available in the conda-forge channel?
In the long-term, yes. But you don't need to change everything by now, because there is a transition phase.
Follow the updates of the omnia Github organization.
|
|
what's conda-forge? an open channel?
On Thu, Feb 2, 2017 at 2:36 PM, Martin K. Scherer <[email protected]>
wrote:
… On 02/02/2017 02:33 PM, João M. Damas wrote:
> Hi,
>
> So the pyemma conda package will disappear from omnia and only be
available in the conda-forge channel?
In the long-term, yes. But you don't need to change everything by now,
because there is a transition phase.
Follow the updates of the omnia Github organization.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1033 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHaqOksK-duO4g9mrzbng6covt4Zx7Y4ks5rYdvVgaJpZM4L0YgL>
.
|
|
On 02/02/2017 02:38 PM, Gianni De Fabritiis wrote:
what's conda-forge? an open channel?
It is a tool to build tools :) Basically its goal is to provide all packages of Anaconda and beyond, but in an open manner (e.g the recipes are public and free)
|
We don't want to allow packages to be build on conda-forge and copied to omnia at this time. Once we migrate to CentOS 6 to harmonize with conda-forge's linux-anvil build system (in progress, see omnia-md/conda-recipes#667) this will be fine, but until then, we cannot allow it since it will break any builds that use pyemma under the hood. See omnia-md/conda-recipes#666. The switch should happen very soon now that OpenMM 7.1 is done and FAH cores are fixed, but we need to restore a working build recipe in omnia for the moment. |
|
Maybe this is related to #1034
Am 02/02/17 um 19:03 schrieb John Chodera:
…
Sorry guys, something went wrong copying over the files from
conda-forge. Now the files are in place.
We don't want to allow packages to be build on conda-forge and copied
to omnia at this time. Once we migrate to CentOS 6 to harmonize with
conda-forge's linux-anvil build system (in progress, see
omnia-md/conda-recipes#667
<omnia-md/conda-recipes#667>) this will be
fine, but until then, we cannot allow it since it will break any
builds that use pyemma under the hood. See omnia-md/conda-recipes#666
<omnia-md/conda-recipes#666>.
The switch should happen very soon now that OpenMM 7.1 is done and FAH
cores are fixed, but we need to restore a working build recipe in
omnia for the moment.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1033 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGMeQu5Ro33aFKE9eSUeWWcZBICe5XAzks5rYhp2gaJpZM4L0YgL>.
--
----------------------------------------------
Prof. Dr. Frank Noe
Head of Computational Molecular Biology group
Freie Universitaet Berlin
Phone: (+49) (0)30 838 75354
Web: research.franknoe.de
Mail: Arnimallee 6, 14195 Berlin, Germany
----------------------------------------------
|
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A fork from issue #1032
It's currently on version 2.2.7. pyemma-dev is also much more outdated.
The text was updated successfully, but these errors were encountered: