You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a private quetz server on an ECS cluster using the latest docker image and installed the quetz client on my dev instance.
I'm attempting to upload the xtensor test package to a channel I created (channel0). I exported the quetz api key per the README and then tried both the README way to upload and the other way described in this issue (which doesn't use full api path) https://github.com/mamba-org/quetz/issues/535#issuecomment-1198166208. The upload succeeds but neither way is generating the noarch/repodata.json file and when I attempt to install the same package the I receive this error:
I believe the path to the repodata.json is incorrect. I think it should be https://<quetz-server>/get/channel0/noarch/repodata.json. Can you give that a try and let us know if that worked for you?
Also, we've recently released a new version of the Quetz client. You can find it here.
Hello,
I created a private quetz server on an ECS cluster using the latest docker image and installed the quetz client on my dev instance.
I'm attempting to upload the xtensor test package to a channel I created (channel0). I exported the quetz api key per the README and then tried both the README way to upload and the other way described in this issue (which doesn't use full api path) https://github.com/mamba-org/quetz/issues/535#issuecomment-1198166208. The upload succeeds but neither way is generating the noarch/repodata.json file and when I attempt to install the same package the I receive this error:
mamba install --strict-channel-priority -c https://<quetz-server>/get/channel0 xtensor
Multi-download failed. Reason: Transfer finalized, status: 404 [https://<quetz-server>/files/channels/channel0/noarch/repodata.json]
Upload commands I've used:
I would really appreciate any guidance on what I might be doing wrong or missing in order to get the repodata.json generated. Thank you for your time!
The text was updated successfully, but these errors were encountered: