-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update resources for plone.app.event #166
Conversation
ba80d8c
to
770e111
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
plone/app/upgrade/v51/configure.zcml
Outdated
@@ -243,12 +243,19 @@ Add image scaling options to image handling control panel. | |||
destination="5113" | |||
profile="Products.CMFPlone:plone"> | |||
|
|||
<gs:upgradeDepends | |||
title="Run to512 upgrade profile." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@agitator title should be changed to "Run to513.."
@agitator FYI - I will fix the title and rebase on 5.1 (will do a rebase and a force push) |
changelog
770e111
to
31dba25
Compare
@jensens same procedure as "Remove jquery-highlightsearchterms" - except this one can go in 5.1.3 because it is independent of any additional changes to CMFPlone |
jenkins 5.2 is currently failing for other reasons |
@thet I'm on the failing test... |
When running the tests of p.a.upgrade, on this PR together with
In the to50alpha1 step, when installing p.a.event Full traceback:
|
same problem as here: plone/Products.CMFPlone#1187 |
Problem described and solved in #1187 and plone/Products.CMFPlone#1412, was reintroduced in plone/Products.CMFPlone@932334391 We can either: do as in PR 1412 and make plone more forgiving (useful in upgrades and tests), or install the needed portal_resources, that means install plone.resource. @thet @mauritsvanrees any opinions on this? |
@sunew awesome, I saw you fixed it! At the same time I was fixing it too :D here is my git diff:
Basically what differs from yours is that I install plone.app.event after plone.app.theming, which itself might install plone.resource. But installing plone.resouce explicitly is definitely nice. If it runs green, go ahead an merge it. |
@thet :D we currently fail on plone 5.0 (when running all three PR's in the same jenkins run) because of this requirement in pa.event: plone.app.z3cform>=2.0.1.dev0 Latest version of pa.event is not for plone 5.0 - and this PR is about upgrade steps for 5.1 - so I guess this failure is ok. If we run this PR alone on 5.0 it should work - I'll do that. If it succeeds, I'll merge. |
No description provided.