software/neoppod: Use buildout.hash.cfg
runTestSuite.in uses _update_hash_filename_ compatbility to avoid clash with section's filename key. As software.cfg is extended by other software releases rename the template part to template-neo in order to avoid clash of sections.
Showing
-
Owner
As software.cfg is extended by other software releases rename the template part to template-neo in order to avoid clash of sections.
I don't see where there would be a clash.
-
Maintainer
I don't see where there would be a clash.
Without renaming
[template]
to[template-neo]
here the ERP5 SR fails with:Installing template. While: Installing template. Error: MD5 checksum mismatch for local resource at '/opt/slapos.git/stack/erp5/instance.cfg.in'.
ERP5 SR defines template section too and extends neoppod which the same section name.
-
Owner
Now I see. The commit message was misleading because ERP5 SR actually does not extend NEO software.cfg
Please register or sign in to comment