Commit bbd70f7d authored by Julien Muchembled's avatar Julien Muchembled

version up: zc.buildout 2.7.1+slapos002

parent b59a44d3
Pipeline #8668 failed with stage
in 0 seconds
...@@ -102,7 +102,7 @@ eggs = ...@@ -102,7 +102,7 @@ eggs =
[versions] [versions]
setuptools = 44.0.0 setuptools = 44.0.0
# Use SlapOS patched zc.buildout # Use SlapOS patched zc.buildout
zc.buildout = 2.7.1+slapos001 zc.buildout = 2.7.1+slapos002
# Use SlapOS patched zc.recipe.egg (zc.recipe.egg 2.x is for Buildout 2) # Use SlapOS patched zc.recipe.egg (zc.recipe.egg 2.x is for Buildout 2)
zc.recipe.egg = 2.0.3+slapos003 zc.recipe.egg = 2.0.3+slapos003
# Use own version of h.r.download to be able to open .xz and .lz archives # Use own version of h.r.download to be able to open .xz and .lz archives
......
  • I had already checked locally that several SR instantiate but not all those in slapos-sr-testing.

    @luke We have preliminary results in https://nexedi.erp5.net/test_result_module/20200331-6606AAA and we see that caddy-frontend needs fixes similar to a7a36453 & 0f0695e7.

  • Shouldn't we revert in the meantime and finalize this in a branch ?

  • I prefer not. I find that developing in a branch is annoying when it's difficult to test locally and one need to set up a test suite. The failures should be quite quick too fix.

    The only other broken SR that's tested is nextcloud.

    I forgot to mention in the commit message that it fixes the zodbpack script that's installed in ERP5 SR (and maybe other scripts in this SR or elsewhere).

    /cc @alain.takoudjou

  • I started to fix caddy and nextcloud in !726 (merged)

    DREAM was also affected, but it was broken for several other reasons, it will be fixed by !724 (merged)

  • mentioned in merge request !726 (merged)

    Toggle commit list
  • mentioned in commit 6d123f21

    Toggle commit list
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment