![](https://secure.gravatar.com/avatar/92ede999ab5f6d70c048222e7fdb1f0a.jpg?s=120&d=mm&r=g)
On Wed, Jul 09, 2014 at 07:30 -0700, Steven Willis wrote:
No, it is something else. A Mirror is a pypi mirror which virtually is serving what https://pypi.python.org/simple/ serves. It's a self-updating cache. You cannot upload packages to the mirror, you have to upload them to the public site.
So, should there be exactly one 'mirror' index which is /root/pypi ?
Yes, you cannot create new mirror stages as there (currently) is only one mirror stage: root/pypi
What is a 'mirror stage', I'm assuming typo and you mean 'mirror index' ?
sorry for sloppyness, yes "mirror index" is probably better.
Why didn't 'root/one' list any packages when it had 'root/pypi' as a base.
The list command does not show projects from root/pypi because that would mean >45K entries.
But this shows all 45K entries:
$ devpi use /root/pypi $ devpi list | wc -l
45858
However: $ devpi use /root/one $ devpi list | wc -l
0
Yes, it's inconcistent. But i don't want to list the 45K everytime you ask "list" on an index that inherits root/pypi. The command should probably say that it omits root/pypi listing to give a hint unless you explicitely ask for it. Note that when you do "devpi list NAME" for listing release files for NAME then all base indexes will be considered, including root/pypi, because there is no 45k-style explosion of entries from it. best, holger
-- 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/d/optout.