-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Extend anaconda copy
to allow name & version changes
#11613
Comments
anaconda copy
to allow name changesanaconda copy
to allow name & version changes
Hi folks did someone manage to take a look at this issue? I've settled on trying out something like this but it's not nearly as But it unfortunately doesn't quite work A repro
Which fails and I probably need to spend more time figuring out what I'm doing wrong
|
Hey @msaroufim thanks for the request! I'm not able to transfer this as it's a different org, so can you open this on the Anaconda Client repo? That is what the 'anaconda` command is and will put it in the right queue to be sorted through. Thanks! |
Checklist
What is the idea?
I'd like to be able to download some conda binaries from https://anaconda.org/pytorch-nightly/torchserve-nightly and then promote them to https://anaconda.org/pytorch/torchserve. Version numbers for nightly scripts will include some date like
20220709
and the official release versions will look something like0.6.0
https://docs.anaconda.com/anaconda-repository/user-guide/tasks/pkgs/copy-pkg/So basically I'd like an extension of
anaconda copy --old-name conda-forge/glueviz/20220101 --to jsmith/glueviz/0.23
But I'm not sure how to go about renaming a conda package even manually (would happily do so if an automated solution is ways out)
Why is this needed?
My team has a Github Action that takes care of uploading conda binaries for our package on a nightly basis pytorch/serve#1685
When that PR is landed we will be able to do official releases by using another manually triggerable Github Action which takes in as arguments a nightly release date to promote from and an official release version to promote to. The script will work by downloading a nightly release, renaming it and then reuploading to an official channel. This is somewhat easy to do with PyPi https://github.com/pytorch/serve/blob/master/binaries/pip/retag_pypi_binary.sh and especially easy with Docker with their
docker tag
What should happen?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: