2.6.0 was released publicly at
https://sourceforge.net/projects/opencryptoki/files/libica/

The symbols removed in 2.6.2, were presented in 2.6.1 which is in Ubuntu
and Debian today.

It is an abi break, to ship 2.6.2 I would have to change the soname to a
debian specific one, that would be bad as shared code compiled on
ubuntu/debian would then not link/run on other platforms and/or upstream
builds.

16.04 had feature freeze in Februrary. If libica is so unstable and
cannot maintain an abi, maybe we should not ship it all and wait for the
3.x release then?

The patch between 2.6.1 and 2.6.2 has a lot of noise which is not a
clear performance regression bug fix. Thus falls out of scope. E.g:

-               memcpy(&sha_context->shaHash, output_data, LENGTH_SHA_HASH);
+               memcpy(&sha_context->shaHash, output_data, SHA_HASH_LENGTH);

Cannot possibly be a performance improvement =)

If there is a clean patch, with just actual performance enhancement,
without spurious refactors and wtihout breaking the ABI, it can be
included. Otherwise, upstream need to make an abi breaking release and a
new request for inclusion filed for the 16.10 release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566238

Title:
  Upgrade package to libica 2.6.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1566238/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to