Yes, lets go with route 2. It's fine to deviate from upstream in that way, especially in a stable release. Unless there is a good reason to expose new API in a library via SRU, my preference is to always keep it private.
Long term (i.e. devel and forward), it will be public like expected. Rejecting so it can be re-worked in that way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2150202 Title: p11tool returns duplicate entries when pkcs URIs are the same for multiple pkcs11 objects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/2150202/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
