Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CDN sync setup outdated for Bioconda #950

Open
2 tasks done
mbargull opened this issue Jun 2, 2024 · 3 comments
Open
2 tasks done

CDN sync setup outdated for Bioconda #950

mbargull opened this issue Jun 2, 2024 · 3 comments
Labels
type::bug describes erroneous operation, use severity::* to classify the type

Comments

@mbargull
Copy link
Member

mbargull commented Jun 2, 2024

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

It looks like the CDN sync for bioconda uses a pretty outdated setup:

  1. https://conda.anaconda.org/bioconda/rss.xml is still the old cut-off-XML <item><title>...</title><pubDate>...</pubDate></item> format.
  2. https://conda.anaconda.org/bioconda/noarch/repodata.json.zst is not being generated.
  3. https://anaconda.org/bioconda/bioconda-utils/3.2.0/download/noarch/bioconda-utils-3.2.0-pyh7cba7a3_0.conda is not being sync'd.

I wanted us to finally start using .conda packages, hence the last point is the most pressing issue.

What can I do to expedite the CDN sync setup update for bioconda?


This is really a dupe of gh-866 and probably just needs the same handling as nvidia: #945 .
I'm no fan of opening duplicate issues, but doing this for visibility in due to #866 (comment) .

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response

@mbargull mbargull added the type::bug describes erroneous operation, use severity::* to classify the type label Jun 2, 2024
mbargull added a commit to bioconda/bioconda-common that referenced this issue Jun 2, 2024
@jezdez
Copy link
Member

jezdez commented Jun 3, 2024

Thanks for opening this ticket, I concur this should be improved. CCing @chenghlee.

@morremeyer
Copy link

@mbargull With the migration to the new cloning infrastructure, number 2 and 3 should be resolved.

Can you verify this from your side?

@dholth
Copy link
Contributor

dholth commented Sep 16, 2024

Do you mean the old cut off RSS was improperly formed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::bug describes erroneous operation, use severity::* to classify the type
Projects
Status: 🆕 New
Development

No branches or pull requests

4 participants