Hi Achim, On Thu, Jan 16, 2014 at 00:50 -0800, Achim Domma wrote:

Hi,

my machine is configured to use our local devpi server as pypi server. If there's a new package (newer pyramid version in our case), this package is fetched. But it looks like the old, cached versions of dependencies (WebOb in our case) are used by devpi/pip. I saw that some issues, which might be related to that, are fixed in the latest release. But according to "pip freeze", we are already using the latest version:

Pygments==1.6 WebOb==1.3.1 argparse==1.2.1 bottle==0.11.6 devpi-common==1.2 devpi-server==1.2.1 docutils==0.11 eventlet==0.14.0 execnet==1.1 greenlet==0.4.1 itsdangerous==0.23 meld3==0.6.10 py==1.4.19 requests==2.1.0 supervisor==3.0 wsgiref==0.1.2

I checked the server logs, but did not see anything that would be helpful to me, to figure out what's going on. Is there a flag to make server side logging more verbose? Or is there any other hint what might be going on? Or how to figure it out?

"devpi-server --debug" will show more info, in particular about synchronization with pypi.python.org. devpi-server periodically checks with pypi.python.org if there are any changes to the projects currently served/cached. If so, it re-fetches those. A brutal way to refresh the cache is to "rm -rf SERVERDIR/root/pypi" where SERVERDIR defaults to ~/.devpi/server and can be modified with --serverdir. So maybe it's best if you kill the cache and run your server with --debug logging and report back the log when it next fails. cheers, holger