Replies: 1 comment
-
Your line of thinking was correct. Unfortunately it doesn't work. The keys with a Currently there is no way to yank releases. The next major release will allow that, but will also require an export/import cycle, as the data storage will change to allow for features like this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We run an instance of
devpi-server
internally to act as a pypi.org mirror and to publish our internal packages to for internal users at our company.We had an issue with some recent internal releases, and would like to yank the associated files. I couldn't find any specific documentation from devpi about how to do this. Trying to use
devpi patchjson
hasn't been fruitful -- I consistently get 404s (I am able to usegetjson
on the same resource successfully). For example, if I dopatchjson
with a JSON file containing the contents of theresult
attribute of the JSON returned fromgetjson
I get a 404.If using
devpi patchjson
is a suitable way to do this, what would you expect to be in the JSON file argument? Any examples in tests have an un-nested dictionary in the JSON for updating a single top-level attribute. If the result ofdevpi getjson /user/index/package
is:and I want to yank 0.0.0, I assume I'd want:
{ "hash_spec": "...", "href": "http://server:3141/user/index/.../package-0.0.0.whl", + "data-yanked": "Broken wheel", }, ... ],
is that correct? Apologies if I'm missing something obvious.
Should I be using a JSON patch? I had trouble with that too. Here is an example:
used with
devpi patchjson /user/index/package/0.0.0/ updates.json
also resulted in a 404 response.Thanks in advance for any help!
Beta Was this translation helpful? Give feedback.
All reactions