Hi! I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666 For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough. I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this. I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x. Regards, Florian Schulze
I forgot to mention, the pip cache can interfere with the fix. Either delete the cache, or wait a while (I think 600 seconds is the default timeout in pip). Regards, Florian Schulze On 11 May 2016, at 14:16, Florian Schulze wrote:
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Thanks for your quick reaction. Great work! ________________________________________ From: devp...@googlegroups.com <devp...@googlegroups.com> on behalf of Florian Schulze <florian...@gmx.net> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2 Hi! I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666 For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough. I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this. I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x. Regards, Florian Schulze -- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Hey Stephan, all, FYI we are aiming today (around lunch) for pre-publishing: devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow. current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly. Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1". best, holger On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: devp...@googlegroups.com <devp...@googlegroups.com> on behalf of Florian Schulze <florian...@gmx.net> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
We made release candidates for testing of devpi-server 3.1.2, devpi-common 3.0.0 and devpi-server 4.0.0 available here: https://devpi.net/fschulze/devpi400 Keep backups of your actual current server state, since export might be affected! Use pip install -i https://devpi.net/fschulze/devpi400/+simple/ ... to install the packages. Please note that devpi-server 4.0.0 is a bug fix/compatibility release as it only changes project name normalization compared to 3.1.x. The internal use of the normalization requires an export/import cycle, which is the reason for the major version increase. There are no other big changes and so everyone who used devpi-server 3.x.y should be fine just using 4.0.0. It's also fine to export from 2.6.x and import with 4.0.0. How to upgrade: Keep backups of your actual current server state, since export might be affected! When running 2.x, upgrade to devpi-common 2.0.10 and export your state. When running 3.x, upgrade to devpi-common 2.0.10 and devpi-server 3.1.2. Now export your state. Import your data into a new instance with devpi-server 4.0.0 which automatically requires devpi-common 3.0.0. Check that everything is in place and report back here, so we know whether we can release to PyPI or need more fixes. If you used devpi-server 2.x and there were any uploads of packages with a dot in their name while you had devpi-common 2.0.9 installed, then those uploads won't show up. Either just reupload them, or if you need the exact same files, do an additional export with devpi-server 2.x and devpi-common 2.0.9. This export will include the new uploads, but none of the old ones. You have to pick the files from the export folder afterwards. Regards, Florian Schulze On 12 May 2016, at 11:37, holger krekel wrote:
Hey Stephan, all,
FYI we are aiming today (around lunch) for pre-publishing:
devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state
devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states
We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow.
current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly.
Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1".
best, holger
On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: devp...@googlegroups.com <devp...@googlegroups.com> on behalf of Florian Schulze <florian...@gmx.net> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Really appreciate all the work you guys have been putting in on such short notice. The 8.1.2 change broke a lot of things for me -- has not been fun. Anyways, went ahead with testing. Running devpi-server --help or just devpi-server gives me this traceback: Traceback (most recent call last): File "/space/devpi/venv/bin/devpi-server", line 11, in <module> sys.exit(main()) File "/space/devpi/venv/lib/python2.7/site-packages/devpi_server/main.py", line 54, in main pluginmanager = get_pluginmanager() File "/space/devpi/venv/lib/python2.7/site-packages/devpi_server/config.py", line 24, in get_pluginmanager pm.load_setuptools_entrypoints("devpi_server") File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 504, in load_setuptools_entrypoints self.register(plugin, name=ep.name) File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 369, in register self._verify_hook(hook, hookimpl) File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 477, in _verify_hook _formatdef(hookimpl.function), ", ".join(hook.argnames))) pluggy.PluginValidationError: Plugin 'devpi-web' hook 'devpiserver_on_changed_versiondata' argument 'projectname' not available plugin definition: devpiserver_on_changed_versiondata(stage, projectname, version, metadata) available hookargs: __multicall__, stage, project, version, metadata I upgraded from 2.x. If there is any other relevant information that can help let me know and I'll provide it. On Thursday, May 12, 2016 at 8:06:26 AM UTC-7, Florian Schulze wrote:
We made release candidates for testing of devpi-server 3.1.2, devpi-common 3.0.0 and devpi-server 4.0.0 available here: https://devpi.net/fschulze/devpi400
Keep backups of your actual current server state, since export might be affected!
Use
pip install -i https://devpi.net/fschulze/devpi400/+simple/ ...
to install the packages.
Please note that devpi-server 4.0.0 is a bug fix/compatibility release as it only changes project name normalization compared to 3.1.x. The internal use of the normalization requires an export/import cycle, which is the reason for the major version increase. There are no other big changes and so everyone who used devpi-server 3.x.y should be fine just using 4.0.0. It's also fine to export from 2.6.x and import with 4.0.0.
How to upgrade:
Keep backups of your actual current server state, since export might be affected!
When running 2.x, upgrade to devpi-common 2.0.10 and export your state.
When running 3.x, upgrade to devpi-common 2.0.10 and devpi-server 3.1.2. Now export your state.
Import your data into a new instance with devpi-server 4.0.0 which automatically requires devpi-common 3.0.0.
Check that everything is in place and report back here, so we know whether we can release to PyPI or need more fixes.
If you used devpi-server 2.x and there were any uploads of packages with a dot in their name while you had devpi-common 2.0.9 installed, then those uploads won't show up. Either just reupload them, or if you need the exact same files, do an additional export with devpi-server 2.x and devpi-common 2.0.9. This export will include the new uploads, but none of the old ones. You have to pick the files from the export folder afterwards.
Regards, Florian Schulze
On 12 May 2016, at 11:37, holger krekel wrote:
Hey Stephan, all,
FYI we are aiming today (around lunch) for pre-publishing:
devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state
devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states
We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow.
current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly.
Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1".
best, holger
On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: dev...@googlegroups.com <javascript:> <dev...@googlegroups.com <javascript:>> on behalf of Florian Schulze <flori...@gmx.net <javascript:>> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Do you use devpi-web? Did you upgrade that to 3.1.0? Regards, Florian Schulze On 12 May 2016, at 17:55, cand...@domaintools.com wrote:
Really appreciate all the work you guys have been putting in on such short notice. The 8.1.2 change broke a lot of things for me -- has not been fun. Anyways, went ahead with testing. Running devpi-server --help or just devpi-server gives me this traceback:
Traceback (most recent call last): File "/space/devpi/venv/bin/devpi-server", line 11, in <module> sys.exit(main()) File "/space/devpi/venv/lib/python2.7/site-packages/devpi_server/main.py", line 54, in main pluginmanager = get_pluginmanager() File "/space/devpi/venv/lib/python2.7/site-packages/devpi_server/config.py", line 24, in get_pluginmanager pm.load_setuptools_entrypoints("devpi_server") File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 504, in load_setuptools_entrypoints self.register(plugin, name=ep.name) File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 369, in register self._verify_hook(hook, hookimpl) File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 477, in _verify_hook _formatdef(hookimpl.function), ", ".join(hook.argnames))) pluggy.PluginValidationError: Plugin 'devpi-web' hook 'devpiserver_on_changed_versiondata' argument 'projectname' not available plugin definition: devpiserver_on_changed_versiondata(stage, projectname, version, metadata) available hookargs: __multicall__, stage, project, version, metadata
I upgraded from 2.x. If there is any other relevant information that can help let me know and I'll provide it.
On Thursday, May 12, 2016 at 8:06:26 AM UTC-7, Florian Schulze wrote:
We made release candidates for testing of devpi-server 3.1.2, devpi-common 3.0.0 and devpi-server 4.0.0 available here: https://devpi.net/fschulze/devpi400
Keep backups of your actual current server state, since export might be affected!
Use
pip install -i https://devpi.net/fschulze/devpi400/+simple/ ...
to install the packages.
Please note that devpi-server 4.0.0 is a bug fix/compatibility release as it only changes project name normalization compared to 3.1.x. The internal use of the normalization requires an export/import cycle, which is the reason for the major version increase. There are no other big changes and so everyone who used devpi-server 3.x.y should be fine just using 4.0.0. It's also fine to export from 2.6.x and import with 4.0.0.
How to upgrade:
Keep backups of your actual current server state, since export might be affected!
When running 2.x, upgrade to devpi-common 2.0.10 and export your state.
When running 3.x, upgrade to devpi-common 2.0.10 and devpi-server 3.1.2. Now export your state.
Import your data into a new instance with devpi-server 4.0.0 which automatically requires devpi-common 3.0.0.
Check that everything is in place and report back here, so we know whether we can release to PyPI or need more fixes.
If you used devpi-server 2.x and there were any uploads of packages with a dot in their name while you had devpi-common 2.0.9 installed, then those uploads won't show up. Either just reupload them, or if you need the exact same files, do an additional export with devpi-server 2.x and devpi-common 2.0.9. This export will include the new uploads, but none of the old ones. You have to pick the files from the export folder afterwards.
Regards, Florian Schulze
On 12 May 2016, at 11:37, holger krekel wrote:
Hey Stephan, all,
FYI we are aiming today (around lunch) for pre-publishing:
devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state
devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states
We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow.
current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly.
Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1".
best, holger
On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: dev...@googlegroups.com <javascript:> <dev...@googlegroups.com <javascript:>> on behalf of Florian Schulze <flori...@gmx.net <javascript:>> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
We do and that was still on 2.5.0. I've upgraded and now devpi-server works. Easy enough fix. I'll continue testing, but everything looks good so far. Data imported and am able to pull packages with pip 8.1.2 with dots in the name. Will report back if I find anything. Thanks again. On Thursday, May 12, 2016 at 8:58:02 AM UTC-7, Florian Schulze wrote:
Do you use devpi-web? Did you upgrade that to 3.1.0?
Regards, Florian Schulze
On 12 May 2016, at 17:55, can...@domaintools.com <javascript:> wrote:
Really appreciate all the work you guys have been putting in on such short notice. The 8.1.2 change broke a lot of things for me -- has not been fun. Anyways, went ahead with testing. Running devpi-server --help or just devpi-server gives me this traceback:
Traceback (most recent call last): File "/space/devpi/venv/bin/devpi-server", line 11, in <module> sys.exit(main()) File "/space/devpi/venv/lib/python2.7/site-packages/devpi_server/main.py", line 54, in main pluginmanager = get_pluginmanager() File "/space/devpi/venv/lib/python2.7/site-packages/devpi_server/config.py", line 24, in get_pluginmanager pm.load_setuptools_entrypoints("devpi_server") File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 504, in load_setuptools_entrypoints self.register(plugin, name=ep.name) File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 369, in register self._verify_hook(hook, hookimpl) File "/space/devpi/venv/lib/python2.7/site-packages/pluggy.py", line 477, in _verify_hook _formatdef(hookimpl.function), ", ".join(hook.argnames))) pluggy.PluginValidationError: Plugin 'devpi-web' hook 'devpiserver_on_changed_versiondata' argument 'projectname' not available plugin definition: devpiserver_on_changed_versiondata(stage, projectname, version, metadata) available hookargs: __multicall__, stage, project, version, metadata
I upgraded from 2.x. If there is any other relevant information that can help let me know and I'll provide it.
On Thursday, May 12, 2016 at 8:06:26 AM UTC-7, Florian Schulze wrote:
We made release candidates for testing of devpi-server 3.1.2, devpi-common 3.0.0 and devpi-server 4.0.0 available here: https://devpi.net/fschulze/devpi400
Keep backups of your actual current server state, since export might be affected!
Use
pip install -i https://devpi.net/fschulze/devpi400/+simple/ ...
to install the packages.
Please note that devpi-server 4.0.0 is a bug fix/compatibility release as it only changes project name normalization compared to 3.1.x. The internal use of the normalization requires an export/import cycle, which is the reason for the major version increase. There are no other big changes and so everyone who used devpi-server 3.x.y should be fine just using 4.0.0. It's also fine to export from 2.6.x and import with 4.0.0.
How to upgrade:
Keep backups of your actual current server state, since export might be affected!
When running 2.x, upgrade to devpi-common 2.0.10 and export your state.
When running 3.x, upgrade to devpi-common 2.0.10 and devpi-server 3.1.2. Now export your state.
Import your data into a new instance with devpi-server 4.0.0 which automatically requires devpi-common 3.0.0.
Check that everything is in place and report back here, so we know whether we can release to PyPI or need more fixes.
If you used devpi-server 2.x and there were any uploads of packages with a dot in their name while you had devpi-common 2.0.9 installed, then those uploads won't show up. Either just reupload them, or if you need the exact same files, do an additional export with devpi-server 2.x and devpi-common 2.0.9. This export will include the new uploads, but none of the old ones. You have to pick the files from the export folder afterwards.
Regards, Florian Schulze
On 12 May 2016, at 11:37, holger krekel wrote:
Hey Stephan, all,
FYI we are aiming today (around lunch) for pre-publishing:
devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state
devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states
We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow.
current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly.
Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1".
best, holger
On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: dev...@googlegroups.com <javascript:> <dev...@googlegroups.com <javascript:>> on behalf of Florian Schulze <flori...@gmx.net <javascript:>> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Hi Florian, I just tried upgrading our devpi server to 3.1.2 (from https://devpi.net/fschulze/devpi312), and I still can't access the simple index for repoze-lru (aka repoze.lru). I have exported contents from devpi-server 2.3.1/devpi-common 2.0.7 and imported into 3.1.1, then deployed 3.1.2 in place. After that, I tried wiping out the serverdir, and re-importing (from the same export from 2.3.1), and I get the same results. Interestingly, searching (using the text box in the web UI) for "repoze-lru" gives me the right results; but visiting the index pages for "repoze-lru" don't show anything. On Thursday, May 12, 2016 at 11:06:26 AM UTC-4, Florian Schulze wrote:
We made release candidates for testing of devpi-server 3.1.2, devpi-common 3.0.0 and devpi-server 4.0.0 available here: https://devpi.net/fschulze/devpi400
Keep backups of your actual current server state, since export might be affected!
Use
pip install -i https://devpi.net/fschulze/devpi400/+simple/ ...
to install the packages.
Please note that devpi-server 4.0.0 is a bug fix/compatibility release as it only changes project name normalization compared to 3.1.x. The internal use of the normalization requires an export/import cycle, which is the reason for the major version increase. There are no other big changes and so everyone who used devpi-server 3.x.y should be fine just using 4.0.0. It's also fine to export from 2.6.x and import with 4.0.0.
How to upgrade:
Keep backups of your actual current server state, since export might be affected!
When running 2.x, upgrade to devpi-common 2.0.10 and export your state.
When running 3.x, upgrade to devpi-common 2.0.10 and devpi-server 3.1.2. Now export your state.
Import your data into a new instance with devpi-server 4.0.0 which automatically requires devpi-common 3.0.0.
Check that everything is in place and report back here, so we know whether we can release to PyPI or need more fixes.
If you used devpi-server 2.x and there were any uploads of packages with a dot in their name while you had devpi-common 2.0.9 installed, then those uploads won't show up. Either just reupload them, or if you need the exact same files, do an additional export with devpi-server 2.x and devpi-common 2.0.9. This export will include the new uploads, but none of the old ones. You have to pick the files from the export folder afterwards.
Regards, Florian Schulze
On 12 May 2016, at 11:37, holger krekel wrote:
Hey Stephan, all,
FYI we are aiming today (around lunch) for pre-publishing:
devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state
devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states
We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow.
current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly.
Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1".
best, holger
On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: dev...@googlegroups.com <javascript:> <dev...@googlegroups.com <javascript:>> on behalf of Florian Schulze <flori...@gmx.net <javascript:>> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
The 3.1.2 release is only meant for exporting, it doesn't fix the pip issue. Thanks for pointing out that this wasn't clear. You have to upgrade to 4.0.0 after exporting. Regards, Florian Schulze On 12 May 2016, at 18:02, Dan Crosta wrote:
Hi Florian,
I just tried upgrading our devpi server to 3.1.2 (from https://devpi.net/fschulze/devpi312), and I still can't access the simple index for repoze-lru (aka repoze.lru). I have exported contents from devpi-server 2.3.1/devpi-common 2.0.7 and imported into 3.1.1, then deployed 3.1.2 in place.
After that, I tried wiping out the serverdir, and re-importing (from the same export from 2.3.1), and I get the same results.
Interestingly, searching (using the text box in the web UI) for "repoze-lru" gives me the right results; but visiting the index pages for "repoze-lru" don't show anything.
On Thursday, May 12, 2016 at 11:06:26 AM UTC-4, Florian Schulze wrote:
We made release candidates for testing of devpi-server 3.1.2, devpi-common 3.0.0 and devpi-server 4.0.0 available here: https://devpi.net/fschulze/devpi400
Keep backups of your actual current server state, since export might be affected!
Use
pip install -i https://devpi.net/fschulze/devpi400/+simple/ ...
to install the packages.
Please note that devpi-server 4.0.0 is a bug fix/compatibility release as it only changes project name normalization compared to 3.1.x. The internal use of the normalization requires an export/import cycle, which is the reason for the major version increase. There are no other big changes and so everyone who used devpi-server 3.x.y should be fine just using 4.0.0. It's also fine to export from 2.6.x and import with 4.0.0.
How to upgrade:
Keep backups of your actual current server state, since export might be affected!
When running 2.x, upgrade to devpi-common 2.0.10 and export your state.
When running 3.x, upgrade to devpi-common 2.0.10 and devpi-server 3.1.2. Now export your state.
Import your data into a new instance with devpi-server 4.0.0 which automatically requires devpi-common 3.0.0.
Check that everything is in place and report back here, so we know whether we can release to PyPI or need more fixes.
If you used devpi-server 2.x and there were any uploads of packages with a dot in their name while you had devpi-common 2.0.9 installed, then those uploads won't show up. Either just reupload them, or if you need the exact same files, do an additional export with devpi-server 2.x and devpi-common 2.0.9. This export will include the new uploads, but none of the old ones. You have to pick the files from the export folder afterwards.
Regards, Florian Schulze
On 12 May 2016, at 11:37, holger krekel wrote:
Hey Stephan, all,
FYI we are aiming today (around lunch) for pre-publishing:
devpi-server-3.1.2 using devpi-common-2.0.10 to export 3.1 state
devpi-server-4.0.0 using devpi-common-3.0 to import 3.1 and 2.6.X states
We now determined it's best to make a clean cut and not introduce special-casing into the code. We'll make the releases available shortly on a special index and would appreciate if you could perform a test on real life data. Florian and me aim to fully publish releases later today or tomorrow.
current background view: since the 3.0 server series we are using the normalized project name for internal DB storage. That name is also used when specifying whitelists etc. Since pip/pypi changed normalization details with the pip-8.1.2 release suddenly commands like "pip install zope.interface" would fail because pip now effectively requests ".../+simple/zope-interface" which in turns asks pypi.python.org/simple/zope-interface. Some time ago pypi.python.org pypi would redirect this to the previous normalization .../simple/zope.interface and the listed files there are named like "zope.interface-1.0.tar.gz" and would be matched. Today, through the combined pip/pypi changes "pypi.python.org/simple/zope-interface" serves the "zope.interface-*.tar.gz" files and devpi does not match the links anymore (because of the "." versus "-" difference) leading to aborted installs which people have been seeing. It's possible we could have fixed things differently than going for a new major release requiring import/export but there are 20 or more places which use normalization and it would be hard to be sure that things work correctly.
Please note that devpi-server-4.0 is really a bug fix/compatibility release as it only changes this normalization issue compared to 3.1.X. There are no other big changes and so everyone who used 3.1/0 should be fine just using 4.0. It's also fine to export from 2.6.X and import from 4.0. If you want to continue using 2.6.X for a while you'll need to keep pip pinned e.g. with "pip==8.1.1".
best, holger
On Wed, May 11, 2016 at 13:25 +0000, Erb, Stephan wrote:
Thanks for your quick reaction. Great work! ________________________________________ From: dev...@googlegroups.com <javascript:> <dev...@googlegroups.com <javascript:>> on behalf of Florian Schulze <flori...@gmx.net <javascript:>> Sent: Wednesday, May 11, 2016 14:16 To: devpi-dev Subject: [devpi-dev] Fix for pip 8.1.2
Hi!
I released devpi-common 2.0.9 and devpi-server 3.1.1 to fix https://github.com/pypa/pip/issues/3666
For devpi-server 2.6.1 the update to devpi-common 2.0.9 is enough.
I only released devpi-server 3.1.1 because of a change in the import code in 3.1.0 which was also affected by this.
I tested devpi-common 2.0.9 with devpi-server/web 2.6.x and devpi-server/web 3.1.x.
Regards, Florian Schulze
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com <javascript:>. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- 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 https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
OK -- just tested with 4.0.0 and it seems the dot/dash issue is now fixed for us. Any idea when this will be published to the cheeseshop?
On Thu, May 12, 2016 at 11:06 -0700, Dan Crosta wrote:
OK -- just tested with 4.0.0 and it seems the dot/dash issue is now fixed for us. Any idea when this will be published to the cheeseshop?
we aim for tomorrow after we hopefully heart back from some larger installations. H.
participants (6)
-
cand...＠domaintools.com -
Dan Crosta -
Erb, Stephan -
Florian Schulze -
Florian Schulze -
holger krekel