Something wrong with https://conda.anaconda.org/conda-forge/osx-64/arpack-3.6.1-blas_openblash1f444ea_0.tar.bz2

[wolfv]

This package 404's https://conda.anaconda.org/conda-forge/osx-64/arpack-3.6.1-blas_openblash1f444ea_0.tar.bz2

But works from here: https://anaconda.org/conda-forge/arpack/3.6.1/download/osx-64/arpack-3.6.1-blas_openblash1f444ea_0.tar.bz2

[barabo]

I'll have to dig into how this happened, but the cached copy of that package is not correct in the clone.

(base) [ec2-user@cf-clone conda-forge]$ ls osx-64/arpack-3.6.1-blas_openblash1f444ea_0* -l
-rw-r--r-- 1 ec2-user ec2-user 186510 Sep 28  2022 osx-64/arpack-3.6.1-blas_openblash1f444ea_0.tar.bz2.ec52aad18145da1c0da7ac344ba21fd1

It also looks like it's a year or so old. I'll look into it tomorrow and report back.

[jaimergp]

Hey @barabo, I think this is still happening. Do you have any updates? Thanks!

[barabo]

There seems to be a discrepancy in the expected file size for this file. The cache DB lists two different sizes, both with the same md5 - so that's probably why it's been refusing to push the file through the CDN.

Sorry for the delay on this!

[barabo]

Apparently this package is now in the removed section of repodata.json. If it's needed, I believe you can remove it from there and it should propagate.

[jezdez]

@wolfv Can you verify if this resolves your issue please?

[jaimergp]

Hm, I was looking into this last week, and just realized that there are mroe 404s in osx-64:

# https://conda.anaconda.org/conda-forge/osx-64/arpack-3.6.1-blas_openblash1f444ea_0.tar.bz2
https://conda.anaconda.org/conda-forge/osx-64/lammps-2018.03.16-.tar.bz2
https://conda.anaconda.org/conda-forge/osx-64/sundials-3.1.0-blas_openblash0edd121_202.tar.bz2
https://conda.anaconda.org/conda-forge/osx-64/vlfeat-0.9.20-h470a237_2.tar.bz2
https://conda.anaconda.org/conda-forge/osx-64/xtensor-python-0.19.1-h3e44d54_0.tar.bz2

Can you confirm these are caused by the same issue @barabo? IOW, if we mark them as not broken, would that help?

[jaimergp]

cc @morremeyer

[morremeyer]

I'll take a look into this towards the end of the week, thanks for letting me know.

[travishathaway]

Possibly similar issue:

• mambaforge and miniforge 22.11.1-0 through 22.11.1-2 MacOS x64 cannot install due to "libmamba Failed to download package <...> (status 403)" #882

[wolfv]

@morremeyer we unfortunately still see this in https://github.com/channel-mirrors/mirrormirror/actions/runs/8359035248/job/22883691802

Anything we can do to help?

We just shipped OCI mirrors in pixi so it would be amazing if we could also make the actions completely green :)

[wolfv]

Any updates on this? It's still failing the mirror jobs.

[wolfv]

A new package is 404'ing (that was not yet marked as broken): https://conda.anaconda.org/conda-forge/linux-aarch64/spacy-3.7.3-py39hc2250db_0.conda

[wolfv]

Any updates?

[dholth]

We improved the process to be more tolerant of packages missing from anaconda.org. After the improvement, that particular package is not mirrored since it is marked as remove in https://conda.anaconda.org/conda-forge/linux-aarch64/patch_instructions.json

[jakirkham]

Are there other current examples we should be looking at here?

[morremeyer]

We have migrated and upgraded the CDN sync for conda-forge with conda-forge/conda-forge.github.io#2272, so this issue is resolved.

There is a known issue with anaconda.org that some packages that are listed in repodata.json trigger a HTTP 404 response when requested by a client, which is currently being investigated. However, that is separate from this issue.

[jezdez]

@morremeyer Are we tracking the separate issue of files of the 404 errors somewhere that we can link here before closing?

[morremeyer]

I have opened #1031 to track it. We'll provide updates over there.