Looking at the changelog:
20111025: Drop bogus c_rehash on upgrades, ...
20110421: * Depend on openssl 1.0.0 and force a call of c_rehash so that we have both the old and new style of symlinks. (Closes: #611102)
I fully suspect that the bug was introduced upstream in oct 2011.
If that's the case, then ubuntu introduced it 2014-03-05 with the security update to 20130906ubuntu0.12.04.1.
At this point in time, this bug only affects machines upgrading from lucid to precise, and can be worked around by running c_rehash manually after do-release-upgrades finishes. It probably deserves to languish without fixes until precise EOL in 2017, and then get closed as fully uninteresting.
Looking at the changelog:
20111025: Drop bogus c_rehash on upgrades, ...
20110421: * Depend on openssl 1.0.0 and force a call of c_rehash so that we have both the old and new style of symlinks. (Closes: #611102)
I fully suspect that the bug was introduced upstream in oct 2011. .12.04. 1.
If that's the case, then ubuntu introduced it 2014-03-05 with the security update to 20130906ubuntu0
At this point in time, this bug only affects machines upgrading from lucid to precise, and can be worked around by running c_rehash manually after do-release-upgrades finishes. It probably deserves to languish without fixes until precise EOL in 2017, and then get closed as fully uninteresting.