Conda to update the channel index in our web server is outdated

We are using an old conda version to index our channel. The new version requires a lot more space which we don't have in our server.

Related to #31 (closed) and also see https://groups.google.com/a/continuum.io/forum/#!topic/conda/OVlAg6vrcAo

@tiago.pereira I suggest either downgrading conda-build or tackling this issue first before fixing https://gitlab.idiap.ch/bob/bob.blitz/pipelines/31739

I will open a ticket to increase space in our server.

We need how much? 1TB ?

ping @andre.anjos

Guys,

if I do a crontab -l in the b*********est I can't find the conda index commands.

Where this job is located?

It's a systemd service not crontab. Do systemctl status conda use tab completion then.

Guys, looks like there are a lot of changes needed to update to the new infrastructure. https://github.com/AnacondaRecipes/repodata-hotfixes/pull/32

I suggest waiting for the dust to settle down and then updating our infrastructure.

OK - sounds sensible. Can somebody revert !66 (merged), please?

Yeap, let's do this

Done with !69 (merged)

closed

Let's keep this open since we have to do it at some point.

reopened

Things are a mess in upstream conda now:

• https://github.com/conda/conda/issues/8863
• https://www.anaconda.com/how-we-made-conda-faster-4-7/
• https://www.anaconda.com/understanding-and-improving-condas-performance/
• https://medium.com/@marius.v.niekerk/conda-metachannel-f962241c9437

Guys, don't update to conda 4.7 ...

mentioned in merge request !75 (merged)

Hi guys,

this was updated,

closing the issue

closed

mentioned in merge request !111 (merged)

Let's close this when !111 (merged) is merged.

reopened

mentioned in merge request !112 (merged)

closed via merge request !112 (merged)

mentioned in commit c99c3336