Hi,

The fix has landed in addons 7.0 at revision 9454 rev-id:
[email protected].

Changing the dependencies of `project_mrp` was not the desired solution,
as neither `sale_stock` nor `mrp` modules are supposed to be required
for `project_mrp` as of version 7.0 (despite the module's legacy name).
Changing dependencies is also not a good idea in a stable series.

Instead, the missing process node was re-injected in the `project_mrp`
module itself, as a copy of the process node that has been moved to the
`sale_stock` module. For more details please see the commit diff and
message.

In v8 we will rename the module to make its dependencies and purpose
more obvious (e.g. `sale_project`).

Thanks for reporting!

** Changed in: openobject-addons
       Status: Confirmed => Fix Released

** Changed in: openobject-addons
    Milestone: None => 7.0

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1223276

Title:
  [7.0] Invalid mrp.process_node_productionorder0 after update 9413

Status in OpenERP Addons (modules):
  Fix Released

Bug description:
  After pull of update 9413 I receiving

  "ValueError: No such external ID currently defined in the system:
  mrp.process_node_productionorder0" for module project_mrp

  The error is strictly related to the update 9413 because this changes field 
reference from "sale_stock.process_node_saleprocurement0" to 
"mrp.process_node_productionorder0"
  See: http://bazaar.launchpad.net/~openerp/openobject-addons/7.0/revision/9413

  may be this change requires some other additional module dependence ?

  please review this.

  regds

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1223276/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~openerp-india
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openerp-india
More help   : https://help.launchpad.net/ListHelp

Reply via email to