upgradeDepends-directive in Products.GenericSetup doesn't include 'profile' in its discriminator

Bug #876317 reported by Asko Soukka
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Zope CMF buildout
New
Undecided
Unassigned

Bug Description

I think, upgradeDepends-directive in GenericSetup should include "profile" in its discriminator to avoid ConfigurationConflictErrors when registering similar upgrade steps for completely different profiles:

zope.configuration.config.ConfigurationConflictError: Conflicting configuration actions
  For: ('upgradeDepends', '2', '3', None, "[u'cssregistry', u'jsregistry', u'typeinfo']", None, 2)
    File ".../my/product/upgrades.zcml", line 23.2-30.7
        <genericsetup:upgradeDepends
           source="2" destination="3" sortkey="2"
           title="Upgrade my.product 2 to 3"
           description="Upgrades my.product from profile 2 to 3."
           profile="my.product:default"
           import_steps="cssregistry jsregistry typeinfo"
           run_deps="false"
           />
    File ".../my/anotherproduct/upgrades.zcml", line 22.2-29.7
        <genericsetup:upgradeDepends
           source="2" destination="3" sortkey="2"
           title="Upgrade my.anotherproduct 2 to 3"
           description="Upgrades my.anotherproduct from profile 2 to 3."
           profile="my.anotherproduct:default"
           import_steps="cssregistry jsregistry typeinfo"
           run_deps="false"
           />

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.