Re: Bug#868640: hdb_generate_key_set_password broke ABI
- Date: Tue, 18 Jul 2017 08:30:55 +1000
- From: Brian May <bam@xxxxxxxxxx>
- Subject: Re: Bug#868640: hdb_generate_key_set_password broke ABI
I have this tricky situation. It appears in 2011, upstream made a change
to Heimdal that broken the shared library ABI, and didn't change the
=== cut ===
Author: Roland C. Dowdeswell <elric@xxxxxxxxxx>
Date: Mon Nov 28 15:18:52 2011 +0000
Provide server side kadm5_chpass_principal_3() with ks_tuple implementation.
We enable kadm5_chpass_principal_3() in the server side of the
library. The client kadm5 library calls will still return the
Signed-off-by: Nicolas Williams <nico@xxxxxxxxxxxxxxxx>
=== cut ===
This change was undetected, and included in Debian in Wheezy, Jessie,
Now Upstream has realized their
There response was to restore the ABI to the previous state. This change
is now in testing and unstable.
What should I do? It appears patch the ABI back to the previous state,
and break compatability with other distributions. Or I can keep it as it
and break upgrades.
Please read the bull details of 868640 for more information, and for
details of similar situation that occured before the Stretch
Brian May <bam@xxxxxxxxxx>