lp://staging/~openerp-community/openobject-server/7.0-server-check_for_sha1_collision-redneck

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1185342: Need to check for SHA-1 collision when generating filenames for attachments.

Wishlist

Confirmed

Link a bug report

Related blueprints

4987. By Daniel Hammerschmidt on 2013-05-29

save confiliction file with a new name transparent to the user

4986. By Daniel Hammerschmidt on 2013-05-23

Check for SHA-1 collision on saving attachments to the filesystem.

4985. By Launchpad Translations on behalf of openerp on 2013-05-23

Launchpad automatic translations update.

4984. By Launchpad Translations on behalf of openerp on 2013-05-22

Launchpad automatic translations update.

4983. By Martin Trigaux (OpenERP) on 2013-05-21

[IMP] remove read access to outgoing mail server configuration
forward port of rev 4349 in 6.1

4982. By Launchpad Translations on behalf of openerp on 2013-05-21

Launchpad automatic translations update.

4981. By Launchpad Translations on behalf of openerp on 2013-05-20

Launchpad automatic translations update.

4980. By Launchpad Translations on behalf of openerp on 2013-05-19

Launchpad automatic translations update.

4979. By Olivier Dony (Odoo) on 2013-05-17

[FIX] ir.sequence: add a proper default value for number_next_actual (0 is disallowed by default) + avoid error when trying to alter a sequence during creation

4978. By Olivier Dony (Odoo) on 2013-05-17

[MERGE] ir.sequence: lazily compute next value for PostgreSQL-backed ir.sequences + avoid resetting it at each change to the sequence, courtesy of Ronald Portier (Therp)

The original patch proposed by Ronald has been modified to
make it more suitable to a stable version, in the following
aspects:
- remove all extra physical columns (boolean flags), as they
  would break the stable policy and were actually unnecessary
  to fix the bug
- avoid displaying both the number_next and the number_next_actual,
  the latter is sufficient
- fix a possible bug when setting the number_next to 0