When adding informational attribute, with only one possible value, it used to be skipped.
Instead keep it and add it on every variant.

To avoid dropping and recreating product (and lose eventual customisations), the attributes with only one possible value are set on every product.
This makes sure that in following test, these are not considered in variants_inactive variable.

Fixes #3204

[Fix] ir_translation: fix the problem of base_field object has no attribute model (Maintenance Case:618054)

Fixes #3859

public_categ_ids field was moved to product.template object

closes #3594

[FIX] account: bank statement reconciliation widget: disable buttons which trigger RPC calls until done

closes #3874

closes #3557

It is present in mrp declaration but was not in mrp_production which was problematic if another module inherit as well from action_produce_end.

updated deb-repository URL

[FIX] website: the attachment creation improvment of a3e57806 must be done on res_model

instead of type

Setting 0.0001 as precision used to be converted to 9.999999999999999e-05
precision_digits of 6 is the precision of the field 'rounding' on res.currency
Fixes #3875

This is safer to avoid inadvertently dropping customizations,
and does not impact the normal update/uninstall process, which
is based on the dependency order.

I avoid to change external ids, in case some custom/community modules use it in their own tests

- find a move line whose amount exactly matches the bank statement line amount even if it has no partner
- properly handle multicurrency
- if there's no exact match, look for a set of move line whose amount is <= to the statement line's amount

[FIX] survey: Was browsing a browse record, useless and traceback... https://github.com/odoo/odoo/issues/2383

website introduces two new stored function fields, which depend on the attachment data
The thing is, these two fields are pertinent for website attachments only
Therefore, we avoid to read the datas field when the attachment is not a website attachment(when not needed), as this is the most costly field to read

The issue is that when a default searchview is requested, it is
initialized without its view_id.  Result: debug mode can't edit the
search view.  This commit makes sure that when the field_view_get is
received, the correct view_id is set.

[FIX] api: avoid to return all fields *2many in onchanges

[FIX] fields: in *2many convert_to_write(), return all fields for new records and dirty fields for existing records

Complements bde1a443

This reverts commit 436bbb0a.

The many2many widget is usefull, as it allows to select an existing picking instead of creating a new one when clicking add an item from the list

As it sets the standard_price field, which is defined on product templates only: setting the standard price of a product variant will lead to set the standard price to all the variants of the product template.

There is therefore no meaning to compute and set the standard price of product variants according to the boms

was : openerp.com; new : odoo.com

commit f76d4525 was not actually working: extra keys from
config files are not yet into the config options dict at
import time. The fix is to move the logic inside the method,
like in `find_pg_tool` just below.

Also fix the use of `find_in_path` in report.py: the subprocess
may also raise AttributeError exception, so instead of listing
all the possible ones just re-raise the IOError shallowed by
`find_in_path` when the result is None.

Fixes #3809 #3811