[request-tracker-maintainers] Bug#691701: request-tracker4: Lack of transactional database code can result in duplicate correspondence

[Dominic Hargreaves]

Package: request-tracker4
Version: 4.0.7-2
Severity: important

The following commit appears in 4.0.8:

commit b99af56fa6fed07f2ea055e0abed393ce3c6fb4a
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Fri Mar 16 16:57:07 2012 -0400

    Lock transaction updates so scrips get a consistent snapshot
    
    Previously, nothing prevented multiple transactions from being run on
    the system concurrently, and making identical changes.  This could lead
    to multiple Corrrespondences, followed by multiple "Status changed from
    new to open" transactions.  Prevent this by always running
    ->_NewTransaction in a database transaction, and ensuring that it takes
    a write lock on the row before running scrips and purges the cache.
    This ensures a coherent and serial execution of scrips.

This correctness bug should probably be included in wheezy.