With devpi you can mark repositories as non-volatile:


This prevents you from uploading foo.bar 0.1 twice, forcing you to do foo.bar 0.1.1 (or whatever your versioning scheme is) if you make a mistake.

On Tue, Feb 11, 2014 at 12:53 PM, Marcus Smith <qwc...@gmail.com> wrote:

From my understanding, it's possible for a pypi project owner to delete, and then re-upload a different distribution with the same version.
how does devpi handle this?  update the cache?  ignore this kind of update?
I'm guessing devpi updates the cache, which makes sense.  It's not devpi's job to do more than pypi is doing.
Just want to know devpi's stance on this, and know that it's intentional.
If this is in the docs, let me know.
P.S. I'm aware of peep as a client-side solution, and at some pt, pip will grow "lock files" as well I think.

You received this message because you are subscribed to the Google Groups "devpi-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com.
To post to this group, send email to devp...@googlegroups.com.
Visit this group at http://groups.google.com/group/devpi-dev.
For more options, visit https://groups.google.com/groups/opt_out.