> The so-version didn't change. 1.7.3 and 1.7.4 are two different packages in debian.
thats how soversion changes are handled in debian packages
it is not difficult to get 1.7.4 into precise (assuming everything builds), it just needs to go by the release team. Given that 1.7.3 is broken its unlikely they will reject updating to either 1.74 or 1.7.3-6
Can you provide a simple testcase reproducing the issue?
> The so-version didn't change. 1.7.3 and 1.7.4 are two different packages in debian.
thats how soversion changes are handled in debian packages
it is not difficult to get 1.7.4 into precise (assuming everything builds), it just needs to go by the release team. Given that 1.7.3 is broken its unlikely they will reject updating to either 1.74 or 1.7.3-6
Can you provide a simple testcase reproducing the issue?