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

anaconda copy --replace did not actually replaced old packages #581

Closed
malfet opened this issue Aug 10, 2021 · 1 comment
Closed

anaconda copy --replace did not actually replaced old packages #581

malfet opened this issue Aug 10, 2021 · 1 comment

Comments

@malfet
Copy link

malfet commented Aug 10, 2021

anaconda copy malfet/torchvision/0.10.0 --replace --to-owner pytorch were used to replace packages with extraneous dependency to the ones without it. But apparently this command just updated the metadata, while links to packages in CDN still pointed to the old version, which were reported in pytorch/vision#4261 and pytorch/vision#4262

Expected outcome: anaconda copy --replace should either update the packages or return an error if it could not be done for some reason.
Workaround: Deleting old version of packages first and then copying new ones resolved the issue.

@bkreider
Copy link
Contributor

I'm closing this as stale. If this is still a problem, please reopen.

This sounds like a CDN cache invalidation problem on the anaconda.org side and not an anaconda-client issue. I believe some of those bugs have been addressed in the last few months to properly invalidating and recaching in cloudflare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants