because:

First: checkouts of z3c.formwidget.query and Products.ExternalEditor (svn) are broken
Second::

The constraint, 2.13.2, is not consistent with the requirement, 'ExtensionClass>=4.1a1'.
While:
  Installing.
  Getting section instance.
  Initializing section instance.
  Installing recipe plone.recipe.zope2instance.
Error: Bad constraint 2.13.2 ExtensionClass>=4.1a1

Plone 5.2 should support both Python2.7 and Python3.X , but Pillow < 8.0.0 cannot find zlib on Macs with the latest OS X and running on the new M1 architecture:

  File "/var/folders/bc/qzs1h_3n2dggkdkm5t07_2m80000gn/T/easy_install-dm3pwbq3/Pillow-6.2.2/setup.py", line 687, in build_extensions
__main__.RequiredDependencyException: zlib

This was fixed in Pillow 8.0.0: (Added homebrew zlib include directory #4842 [radarhere]) But Pillow > 6.2.2 no longer supports Python 2.7

Could we maybe add a specific version override for python3: that pins Pillow to 8.00/8.1.0 for python3 but keeps it to 6.2.2 for python2?

According to jenkins only these packages depend on zope.formlib (in Plone 5.1):

• plone/plone.portlet.static#13
• plone/plone.app.vocabularies#38
• zopefoundation/Products.GenericSetup#31

On plone.portlet.static there are some references, on comments, to it, which most probably should be clarified as well.

https://github.com/plone/buildout.coredev/blob/5.0/plips/plip-toolbar.cfg

Thanks!

The version of zope.app.locales of zope toolkit 1.0.8 is very old. The new versions bring several translations in several languages, including translations of Dexterity error messages.

I just realized that plone.z3cform is not in plone github org but on zopefoundation one. Is there any reason not to move it over to plone github org?

re: plone/documentation#672 and #386

I think the link https://plone.org/foundation/contributors-agreement/agreement.pdf on the page https://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html should point instead to https://plone.org/foundation/contributors-agreement/ rather than directly to the PDF, and the information here on docs.plone.org about the contributor agreement should not be duplicated here; it is best left on plone.org

When running my PLIP job for https://github.com/plone/buildout.coredev/blob/5.2/plips/plip-1653-staticresources.cfg this results in the following error:

https://jenkins.plone.org/view/PLIPs/job/plip-plone-staticresources/14/console

+ return_code=all_right
+ export PATH=/usr/lib/chromium-browser:/home/jenkins/shiningpanda/jobs/dd5c15c8/virtualenvs/d41d8cd9/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/jenkins/.local/bin:/home/jenkins/.local/bin:/home/jenkins/.local/bin
+ export ROBOT_BROWSER=chrome
+ xvfb-run -a --server-args=-screen 0 1920x1200x24 bin/alltests --xml --all
/usr/bin/xvfb-run: 184: /usr/bin/xvfb-run: bin/alltests: not found
+ return_code=127
+ xvfb-run -a --server-args=-screen 0 1920x1200x24 bin/alltests-at --xml
/usr/bin/xvfb-run: 184: /usr/bin/xvfb-run: bin/alltests-at: not found
+ return_code=127
+ [ 127 = all_right ]
+ exit 127
Build step 'Virtualenv Builder' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Robot results publisher started...
-Parsing output xml:
Failed!
hudson.AbortException: No files found in path /home/jenkins/workspace/plip-plone-staticresources@2/parts/test with configured filemask: robot_output.xml
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:78)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:54)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3085)
	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Node5
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
		at hudson.remoting.Channel.call(Channel.java:955)
		at hudson.FilePath.act(FilePath.java:1071)
		at hudson.FilePath.act(FilePath.java:1060)
		at hudson.plugins.robot.RobotParser.parse(RobotParser.java:49)
		at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:224)
		at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:246)
		at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
		at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
		at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
		at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
		at hudson.model.Build$BuildExecution.post2(Build.java:186)
		at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
		at hudson.model.Run.execute(Run.java:1840)
		at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
		at hudson.model.ResourceController.execute(ResourceController.java:97)
		at hudson.model.Executor.run(Executor.java:429)
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Email was triggered for: Always
Sending email for trigger: Always
Sending email to: [email protected]
Finished: FAILURE

Today is used coverage 3.5.2. However, the newer createcoverage requires coverage>=3.7. When used createcoverage we get the error:

Installing createcoverage.
The constraint, 3.5.2, is not consistent with the requirement, 'coverage>=3.7'.
While:
  Installing createcoverage.
Error: Bad constraint 3.5.2 coverage>=3.7

Who pin coverage is zopetoolkit-1-0-8, that is used here. It would not be appropriate to update the zopetoolkit?

On Python 2.7, Plone 5.2 installs trollius==2.2, and Plone 5.1 installs trollius==2.1.

The source distributions (.tar.gz) for both of those releases were recently removed from PyPI. We were able to restore some wheels for both of them, but those do not work on Windows (unfortunately they install just fine, but they fail at runtime with import errors).

A 2.2.post1 and a 2.1.post2 have been uploaded to address this. They restore the source, and for 2.2 they include binary wheels for Windows. Perhaps the version pins here should be updated? (Disclaimer: I'm not a Plone developer or user.)

See zopefoundation/ZEO#146 for more discussion.

I would only report a little issue. In documentation.rst is an old linktarget. The first link in the last paragraph with label "Plone Oriented Shpinx Documentation" refers to nirvana.

A fresh master checkout gives me the following error:

[email protected]:~/sandboxes/buildout.coredev> bin/instance fg
Traceback (most recent call last):
  File "bin/instance", line 265, in <module>
    + sys.argv[1:]))
  File "/home/ajung/.buildout/eggs/plone.recipe.zope2instance-4.2.22-py2.7.egg/plone/recipe/zope2instance/ctl.py", line 610, in main
    options.realize(args, doc=__doc__)
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/Zope2/Startup/zopectl.py", line 162, in realize
    ZDOptions.realize(self, *args, **kw)
  File "/home/ajung/.buildout/eggs/zdaemon-4.2.0-py2.7.egg/zdaemon/zdoptions.py", line 294, in realize
    self.load_schema()
  File "/home/ajung/.buildout/eggs/zdaemon-4.2.0-py2.7.egg/zdaemon/zdoptions.py", line 342, in load_schema
    self.schema = ZConfig.loadSchema(self.schemafile)
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/loader.py", line 49, in loadSchema
    return SchemaLoader().loadURL(url)
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/loader.py", line 83, in loadURL
    return self.loadResource(r)
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/loader.py", line 229, in loadResource
    schema = ZConfig.schema.parseResource(resource, self)
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/schema.py", line 32, in parseResource
    xml.sax.parse(resource.file, parser)
  File "/usr/lib64/python2.7/xml/sax/__init__.py", line 33, in parse
    parser.parse(source)
  File "/usr/lib64/python2.7/xml/sax/expatreader.py", line 107, in parse
    xmlreader.IncrementalParser.parse(self, source)
  File "/usr/lib64/python2.7/xml/sax/xmlreader.py", line 123, in parse
    self.feed(buffer)
  File "/usr/lib64/python2.7/xml/sax/expatreader.py", line 210, in feed
    self._parser.Parse(data, isFinal)
  File "/usr/lib64/python2.7/xml/sax/expatreader.py", line 304, in start_element
    self._cont_handler.startElement(name, AttributesImpl(attrs))
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/schema.py", line 108, in startElement
    getattr(self, "start_" + name)(attrs)
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/schema.py", line 311, in start_import
    src = self._loader.schemaComponentSource(pkg, file)
  File "/home/ajung/.buildout/eggs/ZConfig-3.1.0-py2.7.egg/ZConfig/loader.py", line 246, in schemaComponentSource
    __import__(package)
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZServer/__init__.py", line 41, in <module>
    from HTTPServer import zhttp_server, zhttp_handler
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZServer/HTTPServer.py", line 44, in <module>
    from HTTPResponse import make_response
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZServer/HTTPResponse.py", line 29, in <module>
    from ZPublisher.HTTPResponse import HTTPResponse # XXX WTF?
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZPublisher/__init__.py", line 22, in <module>
    from Publish import publish_module, Retry
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZPublisher/Publish.py", line 21, in <module>
    from Request import Request
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZPublisher/Request.py", line 13, in <module>
    import HTTPRequest
  File "/home/ajung/.buildout/eggs/Zope2-2.13.26-py2.7.egg/ZPublisher/HTTPRequest.py", line 39, in <module>
    from AccessControl.tainted import TaintedString
  File "/home/ajung/.buildout/eggs/AccessControl-3.0.13-py2.7-linux-x86_64.egg/AccessControl/__init__.py", line 16, in <module>
    from AccessControl.Implementation import setImplementation
  File "/home/ajung/.buildout/eggs/AccessControl-3.0.13-py2.7-linux-x86_64.egg/AccessControl/Implementation.py", line 96, in <module>
    setImplementation("C")
  File "/home/ajung/.buildout/eggs/AccessControl-3.0.13-py2.7-linux-x86_64.egg/AccessControl/Implementation.py", line 51, in setImplementation
    from AccessControl import ImplC as impl
  File "/home/ajung/.buildout/eggs/AccessControl-3.0.13-py2.7-linux-x86_64.egg/AccessControl/ImplC.py", line 17, in <module>
    from AccessControl.cAccessControl import rolesForPermissionOn
AttributeError: 'module' object has no attribute 'CAPI2'

When I run this command ./bin/buildout - v as per the instructions on https://buildoutcoredev.readthedocs.org/en/latest/intro.html, I get this on my console :

reyha@reyha-Lenovo-Z50:/projects/buidlouts/plone5devel$ ./bin/buildout -v
Installing 'plone.versioncheck', 'mr.developer'.
We have the distribution that satisfies 'plone.versioncheck==1.2.1'.
We have the distribution that satisfies 'mr.developer==1.34'.
Getting required 'requests==2.9.1'
We have the distribution that satisfies 'requests==2.9.1'.
Getting required 'jinja2==2.8'
We have the distribution that satisfies 'jinja2==2.8'.
Getting required 'colorama==0.3.6'
We have the distribution that satisfies 'colorama==0.3.6'.
Getting required 'CacheControl[filecache]==0.11.6'
We have the distribution that satisfies 'CacheControl[filecache]==0.11.6'.
Getting required 'MarkupSafe==0.23'
We have the distribution that satisfies 'MarkupSafe==0.23'.
Getting required 'lockfile==0.12.2'
We have the distribution that satisfies 'lockfile==0.12.2'.
mr.developer: Queued 'Products.CMFPlone' for checkout.
mr.developer: Queued 'Products.PlonePAS' for checkout.
mr.developer: Queued 'mockup' for checkout.
mr.developer: Queued 'plone.app.caching' for checkout.
mr.developer: Queued 'plone.app.contenttypes' for checkout.
mr.developer: Queued 'plone.app.dexterity' for checkout.
mr.developer: Queued 'plone.app.discussion' for checkout.
mr.developer: Queued 'plone.app.event' for checkout.
mr.developer: Queued 'plone.app.intid' for checkout.
mr.developer: Queued 'plone.app.iterate' for checkout.
mr.developer: Queued 'plone.app.layout' for checkout.
mr.developer: Queued 'plone.app.linkintegrity' for checkout.
mr.developer: Queued 'plone.app.locales' for checkout.
mr.developer: Queued 'plone.app.multilingual' for checkout.
mr.developer: Queued 'plone.app.registry' for checkout.
mr.developer: Queued 'plone.app.relationfield' for checkout.
mr.developer: Queued 'plone.app.theming' for checkout.
mr.developer: Queued 'plone.app.upgrade' for checkout.
mr.developer: Queued 'plone.app.vocabularies' for checkout.
mr.developer: Queued 'plone.app.z3cform' for checkout.
mr.developer: Queued 'plone.folder' for checkout.
mr.developer: Queued 'plone.i18n' for checkout.
mr.developer: Queued 'plone.releaser' for checkout.
mr.developer: Queued 'plone.resourceeditor' for checkout.
mr.developer: Queued 'plone.themepreview' for checkout.
mr.developer: Queued 'plonetheme.barceloneta' for checkout.
mr.developer: Updated 'plone.app.caching' with git.
mr.developer: Updated 'Products.PlonePAS' with git.
mr.developer: Updated 'Products.CMFPlone' with git.
mr.developer: Updated 'plone.app.dexterity' with git.
mr.developer: Updated 'plone.app.discussion' with git.
mr.developer: Updated 'mockup' with git.
mr.developer: Updated 'plone.app.contenttypes' with git.
mr.developer: Updated 'plone.app.event' with git.
mr.developer: Updated 'plone.app.intid' with git.
mr.developer: Updated 'plone.app.iterate' with git.
mr.developer: Updated 'plone.app.linkintegrity' with git.
mr.developer: Updated 'plone.app.layout' with git.
mr.developer: Updated 'plone.app.locales' with git.
mr.developer: Updated 'plone.app.relationfield' with git.
mr.developer: Updated 'plone.app.registry' with git.
mr.developer: Updated 'plone.app.multilingual' with git.
mr.developer: Updated 'plone.app.theming' with git.
mr.developer: Updated 'plone.app.vocabularies' with git.
mr.developer: Updated 'plone.app.z3cform' with git.
mr.developer: Updated 'plone.app.upgrade' with git.
mr.developer: Updated 'plone.folder' with git.
mr.developer: Updated 'plone.i18n' with git.
mr.developer: Updated 'plone.resourceeditor' with git.
mr.developer: Updated 'plone.releaser' with git.
mr.developer: Updated 'plone.themepreview' with git.
mr.developer: Updated 'plonetheme.barceloneta' with git.
Installing 'zc.buildout', 'setuptools'.
We have a develop egg: zc.buildout 2.5.0
We have a develop egg: setuptools 20.2.2
Adding find link 'https://pypi.python.org/packages/source/c/certifi/certifi-2015.11.20.tar.gz#md5=25134646672c695c1ff1593c2dd75d08' from setuptools 20.2.2
Adding find link 'https://pypi.python.org/packages/source/w/wincertstore/wincertstore-0.2.zip#md5=ae728f2f007185648d0c7a8679b361e2' from setuptools 20.2.2
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.dexterity'
warning: no files found matching '.txt'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.linkintegrity'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.iterate'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/mockup'
no previously-included directories found matching '.nix'
no previously-included directories found matching 'dist'
no previously-included directories found matching 'mockup/bower_components'
no previously-included directories found matching 'mockup/build'
no previously-included directories found matching 'mockup/coverage'
no previously-included directories found matching 'mockup/docs'
no previously-included directories found matching 'mockup/node_modules'
warning: no previously-included files found matching '.bowerrc'
warning: no previously-included files found matching '.travis.yml'
warning: no previously-included files found matching 'Makefile'
warning: no previously-included files found matching '.sh'
warning: no previously-included files found matching 'Vagrantfile'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.z3cform'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.resourceeditor'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.vocabularies'
warning: no files found matching '' under directory 'docs'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.releaser'
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.upgrade'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.locales'
warning: no files found matching '.mo' anywhere in distribution
warning: no previously-included files matching 'pyc' found anywhere in distribution
warning: no previously-included files matching 'pyo' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/Products.PlonePAS'
warning: no previously-included files matching '.py?' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.intid'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plonetheme.barceloneta'
warning: no previously-included files matching '.pyc' found anywhere in distribution
no previously-included directories found matching 'design'
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.i18n'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.registry'
warning: no files found matching '.txt'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/Products.CMFPlone'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.caching'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.relationfield'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.contenttypes'
warning: no files found matching '.txt'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.theming'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.folder'
warning: no previously-included files matching 'pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.multilingual'
warning: no files found matching '.txt'
warning: no previously-included files matching '.pyc' found anywhere in distribution
warning: no previously-included files matching '.pyo' found anywhere in distribution
warning: no previously-included files matching '.DS_Store' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.discussion'
warning: no files found matching '.txt'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.layout'
warning: no previously-included files matching '.pyc' found anywhere in distribution
Develop: '/home/reyha/projects/buidlouts/plone5devel/src/plone.app.event'
warning: no files found matching '.mo' anywhere in distribution
warning: no previously-included files matching 'pyc' found anywhere in distribution
warning: no previously-included files matching '' found anywhere in distribution
no previously-included directories found matching 'devsrc'
Installing 'zc.recipe.egg'.
We have the distribution that satisfies 'zc.recipe.egg==2.0.3'.
Installing 'collective.xmltestreport'.
We have the distribution that satisfies 'collective.xmltestreport==1.3.3'.
Getting required 'zope.testrunner==4.4.4'
We have the distribution that satisfies 'zope.testrunner==4.4.4'.
Getting required 'zope.testing==3.9.7'
We have the distribution that satisfies 'zope.testing==3.9.7'.
Getting required 'zope.interface==3.6.7'
We have the distribution that satisfies 'zope.interface==3.6.7'.
Getting required 'zope.exceptions==3.6.2'
We have the distribution that satisfies 'zope.exceptions==3.6.2'.
Getting required 'six==1.10.0'
We have the distribution that satisfies 'six==1.10.0'.
Installing 'plone.recipe.zope2instance'.
We have the distribution that satisfies 'plone.recipe.zope2instance==4.2.19'.
Getting required 'ZODB3==3.10.5'
We have the distribution that satisfies 'ZODB3==3.10.5'.
Getting required 'Zope2==2.13.24'
We have the distribution that satisfies 'Zope2==2.13.24'.
Getting required 'mailinglogger==3.8.0'
We have the distribution that satisfies 'mailinglogger==3.8.0'.
Getting required 'zope.event==3.5.2'
We have the distribution that satisfies 'zope.event==3.5.2'.
Getting required 'zdaemon==2.0.7'
We have the distribution that satisfies 'zdaemon==2.0.7'.
Getting required 'ZConfig==2.9.3'
We have the distribution that satisfies 'ZConfig==2.9.3'.
Getting required 'zc.lockfile==1.0.2'
We have the distribution that satisfies 'zc.lockfile==1.0.2'.
Getting required 'transaction==1.1.1'
We have the distribution that satisfies 'transaction==1.1.1'.
Getting required 'Products.StandardCacheManagers==2.13.1'
We have the distribution that satisfies 'Products.StandardCacheManagers==2.13.1'.
Getting required 'Products.PythonScripts==2.13.2'
We have the distribution that satisfies 'Products.PythonScripts==2.13.2'.
Getting required 'Products.MIMETools==2.13.0'
We have the distribution that satisfies 'Products.MIMETools==2.13.0'.
Getting required 'Products.MailHost==2.13.2'
We have the distribution that satisfies 'Products.MailHost==2.13.2'.
Getting required 'Products.ExternalMethod==2.13.1'
We have the distribution that satisfies 'Products.ExternalMethod==2.13.1'.
Getting required 'Products.BTreeFolder2==2.14.0'
We have the distribution that satisfies 'Products.BTreeFolder2==2.14.0'.
Getting required 'zope.viewlet==3.7.2'
We have the distribution that satisfies 'zope.viewlet==3.7.2'.
Getting required 'zope.traversing==3.13.2'
We have the distribution that satisfies 'zope.traversing==3.13.2'.
Getting required 'zope.testbrowser==3.11.1'
We have the distribution that satisfies 'zope.testbrowser==3.11.1'.
Getting required 'zope.tales==3.5.3'
We have the distribution that satisfies 'zope.tales==3.5.3'.
Getting required 'zope.tal==3.5.2'
We have the distribution that satisfies 'zope.tal==3.5.2'.
Getting required 'zope.structuredtext==3.5.1'
We have the distribution that satisfies 'zope.structuredtext==3.5.1'.
Getting required 'zope.size==3.4.1'
We have the distribution that satisfies 'zope.size==3.4.1'.
Getting required 'zope.site==3.9.2'
We have the distribution that satisfies 'zope.site==3.9.2'.
Getting required 'zope.sequencesort==3.4.0'
We have the distribution that satisfies 'zope.sequencesort==3.4.0'.
Getting required 'zope.sendmail==3.7.5'
We have the distribution that satisfies 'zope.sendmail==3.7.5'.
Getting required 'zope.security==3.7.4'
We have the distribution that satisfies 'zope.security==3.7.4'.
Getting required 'zope.schema==4.4.2'
We have the distribution that satisfies 'zope.schema==4.4.2'.
Getting required 'zope.publisher==3.12.6'
We have the distribution that satisfies 'zope.publisher==3.12.6'.
Getting required 'zope.ptresource==3.9.0'
We have the distribution that satisfies 'zope.ptresource==3.9.0'.
Getting required 'zope.proxy==3.6.1'
We have no distributions for zope.proxy that satisfies 'zope.proxy==3.6.1'.
Getting distribution for 'zope.proxy==3.6.1'.
While:
Installing.
Getting section instance.
Initializing section instance.
Installing recipe plone.recipe.zope2instance.
Getting distribution for 'zope.proxy==3.6.1'.
Error: Couldn't find a distribution for 'zope.proxy==3.6.1'.

How do I fix this?

I'm experiencing an issue with the watchdog dependency:

...
Generated script '/Applications/buildout/buildout.coredev-4.3/bin/test'.
Updating zopepy.
Installing robot.
Getting distribution for 'watchdog'.
warning: no files found matching '*.h' under directory 'src'
cc1: error: -Werror=unused-command-line-argument-hard-error-in-future: No option -Wunused-command-line-argument-hard-error-in-future
error: Setup script exited with error: command '/usr/bin/gcc-4.2' failed with exit status 1
An error occurred when trying to install watchdog 0.8.3. Look above this message for any errors that were output by easy_install.
While:
  Installing robot.
  Getting distribution for 'watchdog'.
Error: Couldn't install: watchdog 0.8.3

Installing watchdog with macports is not helping as the module is an explicit dependency of plone.app.robotframework

plone.restapi uses semantic versioning. Right now we use a combination of milestones and labels to mark issues and pull requests. Would it be possible to add some additional labels that we can use for semantic versioning? Something like:

1. Breaking Change
2. New Feature
3. Bugfix

This would make it a lot easier for me to plan new releases.

cc @jensens

I'm trying to run translation updates to do some fixes for Plone 4.3 but they're also missing in 5.0/5.1 .

When I run bin/buildout -c experimental/i18n.cfg in the 4.3 branch to create the translation scripts, I get a warning that Babel is unpinned and version 2.5 (latest from pypi) is used in all bin/* scripts. When I run the same for coredev 5.1 I get no warning and the pinned version 1.3 is used.

@vincentfretin You ran the i18n update scripts at the end of 2016 for the last time for Plone 4.3 Did you notice this, Is it problematic?

I'd like to sync the translations again for Plone 4.3 again to do some translation updates. I see there are others missing, but it started with plone/plone.app.contenttypes@a428777

Testing plone/Products.CMFPlone#1734 see http://jenkins.plone.org/view/PLIPs/job/plip-1734-icons-and-thumbs I get failures (Products.PortalTransforms is checked out).

Same results I get locally for 5.1 coredev (without PLIP!) - but when I pin Products.PortalTransforms to last Release ( 2.2.3 Feb20) Failures are gone.

The README for plone.app.upgrade states that 2.0.0 is for Plone 5.
The pending release 4.3.13 is pointing to 1.4.1 of plone.app.upgrade.
This breaks our builds and forces us to pin 1.4.1 manually

coming over from #253 (discussion started there) I turn this into an issue:

I sketched my idea of the annotations over here:
plone/plone.versioncheck#25

@gforcada: plone.versioncheck as an extension collecting information about the versions we use in a buildout its just minimal overhead while buildout runs and its already part of buildout.coredev.

To generate the report I'd do a ./bin/versioncheck -prb > dependencies.html. This shows all versions.

I would let it run everytime when in buildout.coredev one of the main cfg files are changing (but not for PRs, only main branches). A cfg file mostly changes after PR merges (new checkout), after releases or rare other changes.

Generating the report fires some requests (488 at the moment) to PyPI in order to get the json with the release-information for each package used. This takes only about 30 seconds on my local machine. Given jenkins has a better internet connectivity it should be faster. I think the html report can be part of the test result output. I have to admit I have no idea how this in detail need to configured in jenkins.

Would this make sense?

cc @mauritsvanrees

Requirement of plone4.csrffixes==1.1: plone.protect>=3.0.19

https://github.com/plone/buildout.coredev/blob/4.3/versions.cfg#L208

@vincentfretin @mauritsvanrees as you are the current experts on version pins regarding i18ndude, could you resolve the problem in buildout.coredev 5.0 branch?

As you can see on the jenkins job it fails due to a constraint mismatch for zope.tal:

https://jenkins.plone.org/view/Translations/job/plone-5.0

@jensens Can you apply the new labels in buildout.coredev as well?
They look pretty clear. Thanks!

The link to readthedocs.org in the readme is broken. I get a 500 ("Fail. Check back in a bit!").

Current link is

https://readthedocs.org/docs/buildoutcoredev

We probably want one of these intstead:

https://readthedocs.org/projects/buildoutcoredev
http://buildoutcoredev.readthedocs.org/en/latest/

in sources.cfg remote section https://github.com/plone/buildout.coredev/blob/5.1/sources.cfg#L7-L17 we use for read access the git:// Urls.

Why not https://? Advantage of https:// easier to get through firewalls at customer sites.

(I prefer to stick with ssh for write, key-auth is so convenient.)

Document usage of new style resources, grunt, etc. in the core development section:

http://docs.plone.org/develop/plone-coredev/index.html

@gforcada @tisto can either of you do this for me quick? Thank you.

Looking at sources.cfg from 5.0 branch these are the repositories still hosted on subversion:

• z3c.formwidget.query
• Products.CMFCore
• Products.CMFDefault
• Products.CMFUid
• Products.DCWorkflow
• Products.ExternalEditor

I see that @tdesvenain @do3cc have been moving some packages lately, would it be possible to move those as well?

As requested by @tisto (and actually I have been thinking of it for quite a few times), add some docs regarding git best practices.

Since about yesterday I get a version constraint conflict, both when I bootstrap towards Pyhon 2 and Python3.

  Requirement of z3c.caching: zope.interface>=3.8.0
While:
  Installing instance.
Error: The requirement ('Zope>=4.1.2') is not allowed by your [versions] constraint (4.1.1)

I wrote some new jenkins jobs (we already had one but was only tracking latest branch, i.e. 5.2 right now) that check if there are strings not marked for translation on each major branch (4.3, 5.0, 5.1 and 5.2).

It is using the fantastic i18n-find-untranslated on experimental/i18n.cfg.

It is missing on 4.3 though. Do we want that there as well?

/cc @vincentfretin @plone/release-team

https://dist.plone.org/release/5.0-latest/versions.cfg has outdated versions of both, setuptools and zc.buildout.

it lists:

setuptools = 26.1.1
zc.buildout = 2.5.3

it should be:

setuptools = 33.1.1
zc.buildout = 2.9.5

• https://github.com/plone/buildout.coredev/blob/5.0/versions.cfg#L33-L35
• https://github.com/plone/buildout.coredev/blob/5.0/requirements.txt

Getting distribution for 'watchdog'.
cc1: error: -Werror=unused-command-line-argument-hard-error-in-future: No option -Wunused-command-line-argument-hard-error-in-future
error: Setup script exited with error: command '/usr/bin/gcc-4.2' failed with exit status 1
An error occurred when trying to install watchdog 0.8.2. Look above this message for any errors that were output by easy_install.
While:
Installing test.
Getting distribution for 'watchdog'.
Error: Couldn't install: watchdog 0.8.2

See also http://blog.manbolo.com/2014/03/26/xcode-5.1-breaks-python-native-extensions-and-ruby-gems

Hi all, specially @tisto

Anyone has any insight regarding the status of this file? https://github.com/plone/buildout.coredev/blob/5.1/TEST-FIXES-TODO.rst

Last update was 3 years ago, so I'm not so sure if the packages still on the TODO list need to be updated...

Currently we only test against Python 2 on PLIP jobs. We probably need a way to test against Python 3 and Python 2.
The easiest way to do this might be to provide 2 buildout configurations per PLIP.

Just taking a look at https://github.com/plone/buildout.coredev/tree/5.0/plips shows lots of really old plips (5+ years some of them).

Is there any need to keep all of them around?

With the work that we are doing on the new jenkins.plone.org setup, one approach to make it easier for plips to be merged successfully would be to create a jenkins job for each plip. So a jenkins job would be monitoring buildout.coredev and keep creating/deleting jobs as they would be found on the plips folder, hence a clean up on it would be nice to not create lots of garbage jobs.

/cc @tisto

I think it makes sense to add a pin for plone.api in coredev 4.3. I had created a new package with bobtemplates.plone for Plone 5, but wanted to test it on 4.3 as well, and plone.api was the only missing version pin.

Add it to the sources and tests too. It is tested on its own on Travis, and tests pass on 4.3, but testing on Jenkins with the latest stuff seems good.
Well... I wonder about Python 2.6 support. That might be a problem. In that case we can skip the sources and only add the version pin.

Possible downside of pinning: if someone accidentally starts using plone.api in the core of Plone 4.3, it is harder to notice.

the docs for buildout.coredev are already included in docs.plone.org, can someone take the down from rtd, we worked really hard to gather all our official plone docs in one place,this one is still on rtd too.

When you go to https://github.com/plone/buildout.coredev or make a clone, you see branch 4.3 by default. This should become 5.0. I guess it takes someone with admin rights to change this.

Create a new Plone 5 site and edit the front-page.
The default size of the editor window of the editor window is much bigger than the visual error.
In the general the TinyMCE toolbar should be visible at any time when you edit a richtext field. The default size of the editor should limited to the visual area.

On http://buildoutcoredev.readthedocs.io/en/5.2/updateme.html the 'Edit on GitHub' link in the breadcrumbs/header of the page points to https://github.com/plone/buildout.coredev/blob/origin/5.2/docs/updateme.rst but should be https://github.com/plone/buildout.coredev/blob/5.2/docs/updateme.rst (without 'origin').

The line that generates that URL is https://github.com/plone/plone.themepreview/blob/master/source/_templates/breadcrumbs.html#L10 but I don't see where github_version or conf_py_path are set... (one of those contains the extraneous 'origin' string)

Is not being used on 4.3 nor 5.1, but is used on 5.0 (master branch). This seems odd... If I remember correctly @sneridagh noticed that as well when upgrading plone.org to the latest 5.1...

It says:

• Plone Core Development Buildout http://docs.plone.org/develop/plone-coredev/index.html

But the link is broken.

A better choice is:

• http://docs.plone.org/develop/coredev/docs/

For coredev 4.3, 5.0 and 5.1 we need a new versions file at http://dist.plone.org/versions/.

See small changelog at https://zope.readthedocs.io/en/2.13/CHANGES.html#id1
and the versions file: http://dist.plone.org/versions/zope-2-13-27-versions.cfg

diff with 2.13.27 is:

1a2
> Zope2 = 2.13.28
32d32
< Zope2 = 2.13.27
43a44
> six = 1.11.0

mr.roboto doesn't add checkouts to checkouts.cfg automatically at the moment.

There were changes in core packages. The changeset was commited, but not added in checkouts.cfg in 5.1:
d79ebcd
aec1cdd

I had added them manually to checkouts.cfg here:
d586c4a

Same for 5.0.

/cc @gforcada @mauritsvanrees

See for example this Plone 5.2 Python 3.6 job:

Getting distribution for 'buildout.requirements==0.2.2'.
WARNING: The easy_install command is deprecated and will be removed in a future version.
Traceback (most recent call last):
  File "/home/jenkins/shiningpanda/jobs/65a48de5/virtualenvs/d41d8cd9/lib/python3.6/site-packages/setuptools/sandbox.py", line 154, in save_modules
    yield saved
  File "/home/jenkins/shiningpanda/jobs/65a48de5/virtualenvs/d41d8cd9/lib/python3.6/site-packages/setuptools/sandbox.py", line 195, in setup_context
    yield
  File "/home/jenkins/shiningpanda/jobs/65a48de5/virtualenvs/d41d8cd9/lib/python3.6/site-packages/setuptools/sandbox.py", line 250, in run_setup
    _execfile(setup_script, ns)
  File "/home/jenkins/shiningpanda/jobs/65a48de5/virtualenvs/d41d8cd9/lib/python3.6/site-packages/setuptools/sandbox.py", line 45, in _execfile
    exec(code, globals, locals)
  File "/tmp/easy_install-pi5g09vi/buildout.requirements-0.2.2/setup.py", line 11, in <module>
    description='Plone Core Development Buildout',
  File "/tmp/easy_install-pi5g09vi/buildout.requirements-0.2.2/setup.py", line 7, in read
    
  File "/home/jenkins/shiningpanda/jobs/65a48de5/virtualenvs/d41d8cd9/lib/python3.6/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 35: ordinal not in range(128)

This is because the setup.py of this package reads a CONTRIBUTORS.rst which contains non-ascii code. But locally I can read it just fine with Python 3.6. And usually Jenkins has no problems with it either.

Any idea?
I am half inclined to just remove it in the Jenkins config, if possible.

...also mentioned as part of this discussion plone/documentation#14

In commit 1fc5ca4 yesterday, @pbauer updated Products.ZSQLMethods from 3.0.6 to 3.0.7. Seems to be used only on Python 2.7 with Archetypes. But there we then have a version conflict:

Installing instance-archetypes.
Version and requirements information containing documenttemplate:
  [versions] constraint on documenttemplate: 3.0b6
  Requirement of Zope>=4.0b1: DocumentTemplate>=3.0b5.dev0
  Requirement of DocumentTemplate>=3.0b5.dev0: zope.structuredtext
  Requirement of DocumentTemplate>=3.0b5.dev0: zope.sequencesort
  Requirement of DocumentTemplate>=3.0b5.dev0: zExceptions
  Requirement of DocumentTemplate>=3.0b5.dev0: six
  Requirement of DocumentTemplate>=3.0b5.dev0: RestrictedPython>=4.0a1
  Requirement of DocumentTemplate>=3.0b5.dev0: ExtensionClass>=4.1a1
  Requirement of DocumentTemplate>=3.0b5.dev0: Acquisition
  Requirement of DocumentTemplate>=3.0b5.dev0: AccessControl>=4.0a5
  Requirement of Products.ZCatalog>=2.13.4: DocumentTemplate
  Requirement of Products.PythonScripts: DocumentTemplate
  Requirement of Products.MailHost>=4.0: DocumentTemplate
  Requirement of Products.ZSQLMethods: DocumentTemplate>=3.0b7
While:
  Installing instance-archetypes.
Error: The requirement ('DocumentTemplate>=3.0b7') is not allowed by your [versions] constraint (3.0b6)

Okay, so I update DocumentTemplate to 3.0b7 (or b8). Buildout then finishes. But the instance won't start, neither with nor without Archetypes:

  File "/Users/maurits/community/plone-coredev/5.2/src/Products.CMFPlone/Products/CMFPlone/patches/__init__.py", line 6, in <module>
    from . import addzmisecuritywarning    # Add a warning to the ZMI security tab
  File "/Users/maurits/community/plone-coredev/5.2/src/Products.CMFPlone/Products/CMFPlone/patches/addzmisecuritywarning.py", line 26, in <module>
    normal._v_cooked = normal.cook()
  File "/Users/maurits/shared-eggs/cp27m/DocumentTemplate-3.0b7-py2.7.egg/DocumentTemplate/DT_String.py", line 379, in cook
    self._v_blocks = self.parse(self.read())
  File "/Users/maurits/shared-eggs/cp27m/DocumentTemplate-3.0b7-py2.7.egg/DocumentTemplate/DT_String.py", line 187, in parse
    tag, l_, args, command)
  File "/Users/maurits/shared-eggs/cp27m/DocumentTemplate-3.0b7-py2.7.egg/DocumentTemplate/DT_String.py", line 249, in parse_block
    text[:l_], sstart)
  File "/Users/maurits/shared-eggs/cp27m/DocumentTemplate-3.0b7-py2.7.egg/DocumentTemplate/DT_String.py", line 187, in parse
    tag, l_, args, command)
  File "/Users/maurits/shared-eggs/cp27m/DocumentTemplate-3.0b7-py2.7.egg/DocumentTemplate/DT_String.py", line 262, in parse_block
    r = scommand(blocks, encoding=self.encoding)
zope.configuration.xmlconfig.ZopeXMLConfigurationError: File "/Users/maurits/community/plone-coredev/5.2/src/Products.CMFPlone/Products/CMFPlone/overrides.zcml", line 10.4-13.10
    File "/Users/maurits/community/plone-coredev/5.2/parts/instance/etc/site.zcml", line 20.2-20.32
    AttributeError: 'DTMLFile' object has no attribute 'encoding'

With a Pdb:

(Pdb++) self
<App.special_dtml.DTMLFile object at 0x10fe90dd0>
(Pdb++) self.name()
'_normal_manage_access'

The encoding attribute is used since zopefoundation/DocumentTemplate#44. Maybe the DTML patch is Plone needs to change something. Or maybe this requires more package updates than just DocumentTemplate.

For now I will revert Products.ZSQLMethods back to 3.0.6. Then the buildout succeeds and both instances start.
But this might need more changes in the future.

Please add a job for: https://github.com/plone/buildout.coredev/blob/73a22b75e19482b205ff41559a398f24bdb357e2/plips/plip-extensible-fc.cfg

I need tests running against this plip file: https://github.com/plone/buildout.coredev/blob/5.0/plips/email-registration.cfg

From https://community.plone.org/t/how-http-dist-plone-org-release-4-3-latest-versions-cfg-is-generated/3357/. We think this would be a nice addition to beginners. Feel free to reject the idea if you think this is bloating the versions file or will give too much false warnings at buildout.coredev.

So, instead of

[buildout]
extends = http://dist.plone.org/versions/zopetoolkit-1-0-8-zopeapp-versions.cfg
          http://dist.plone.org/versions/zope-2-13-26-versions.cfg

We would have

[buildout]
# This file is part of buildout.coredev and it's carefully crafted by the core 
# developers. If you have a suggestion for a package here open an issue at 
# https://github.com/plone/buildout.coredev/issues
extends = http://dist.plone.org/versions/zopetoolkit-1-0-8-zopeapp-versions.cfg
          http://dist.plone.org/versions/zope-2-13-26-versions.cfg

As suggested by @jensens. The explanation

This file is part of buildout.coredev. It is carefully crafted by the core developers. Any changes are made on a branch, which is tested via our jenkins.plone.org CI before it gets merged. Our Release Manager takes this file, checks it and copies it as part of the release.

Would be a nice addition as well in docs.plone.org.