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

rss.xml is broken on bioconda #866

Closed
2 tasks done
jaimergp opened this issue Jan 3, 2024 · 7 comments
Closed
2 tasks done

rss.xml is broken on bioconda #866

jaimergp opened this issue Jan 3, 2024 · 7 comments
Labels
type::bug describes erroneous operation, use severity::* to classify the type

Comments

@jaimergp
Copy link
Contributor

jaimergp commented Jan 3, 2024

Checklist

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

What happened?

https://conda.anaconda.org/bioconda/rss.xml is not valid RSS or even XML parsable. Its content seems to be a flat collection of <item> elements:

    <item>
  <title>running sync</title>
  <pubDate>03 Jan 2024 17:08:58 UTC</pubDate>
</item><item>
  <title>linux-64:add:bioconductor-bsseq-1.30.0-r41h399db7b_0.tar.bz2</title>
  <pubDate>08 Nov 2021 01:42:55 UTC</pubDate>
</item><item>
  <title>linux-64:add:bioconductor-fraser-1.6.0-r41h399db7b_0.tar.bz2</title>
  <pubDate>08 Nov 2021 01:42:55 UTC</pubDate>
</item>
    <item>
  <title>running sync</title>
  <pubDate>09 Nov 2021 03:09:56 UTC</pubDate>
</item>

But conda-forge's RSS looks like this:

<?xml version="1.0" ?>
<rss version="2.0">
  <channel>
    <title>anaconda.org/conda-forge</title>
    <link>https://conda.anaconda.org/conda-forge</link>
    <description>The most recent 100 updates for conda-forge.</description>
    <pubDate>Wed, 03 Jan 2024 17:24:54 GMT</pubDate>
    <lastBuildDate>Wed, 03 Jan 2024 17:24:54 GMT</lastBuildDate>
    <item>
      <title>scikit-base 0.7.0 [linux-64, linux-aarch64, osx-64, osx-arm64, win-64]</title>
      <description>Base classes for sklearn-like parametric objects</description>
      <link>https://skbase.readthedocs.io/en/latest/</link>
      <comments>https://github.com/sktime/skbase</comments>
      <guid>https://pypi.io/packages/source/s/scikit-base/scikit-base-0.7.0.tar.gz</guid>
      <pubDate>Wed, 03 Jan 2024 17:07:57 GMT</pubDate>
      <source>https://github.com/sktime/skbase</source>
    </item>
...

Conda Info

N/A

Conda Config

N/A

Conda list

N/A

Additional Context

N/A

@jaimergp jaimergp added the type::bug describes erroneous operation, use severity::* to classify the type label Jan 3, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Jan 3, 2024
@jakirkham
Copy link
Member

Wonder if this shares the same root cause as the Bioconda CDN sync issue: #895

@jaimergp
Copy link
Contributor Author

AFAIU, this is just the CDN backend for bioconda using an older conda-index stack.

@johanneskoester
Copy link

Can it get an update please, so that hopefully the sync works again?

@johanneskoester
Copy link

The immediate issue seems to be gone, but I would really appreciate to finally get the same stack for the CDN as conda-forge. This was promised several times before actually.

@morremeyer
Copy link

We have updated the CDN sync process for all channels by now. Specifically for bioconda, this is the tracking issue: bioconda/bioconda-utils#1008.

With these upgrades, the stack for all channels is the same now.

@jezdez
Copy link
Member

jezdez commented Sep 16, 2024

Closing as fixed via bioconda/bioconda-utils#1008

@jezdez jezdez closed this as completed Sep 16, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Sep 16, 2024
@jaimergp
Copy link
Contributor Author

Confirmed: https://conda-metadata-app.streamlit.app/?q=bioconda now works properly!

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
Archived in project
Development

No branches or pull requests

5 participants