On Mon, Dec 19, 2016 at 04:53:59PM +0100, Sergio Gelato wrote: > Upstream has renamed two symbols in libroken without bumping the API > version number. These are base64_decode and base64_encode, now known as > rk_base64_decode and rk_base64_encode. The change was made in 2014. > > What I think this means is that newer libroken18-heimdal needs to declare > Breaks: heimdal-clients (<< 1.7~git20150920), > heimdal-kdc (<< 1.7~git20150920), > heimdal-servers-x (<< 1.7~git20150920), > libheimbase1-heimdal ((<< 1.7~git20150920), > libhx509-5-heimdal (<< 1.7~git20150920), > yafc (<< 1.3.7-1~) > > I hope I haven't missed anything; please double-check.
This bug appears to have got missed :-( As far as I can tell, the packages in Jessie contain the old symbol. Anything before Jessie doesn't matter anymore for sid. For the record, I don't plan to do anything for the Stretch release at this (late) stage. yafc in unstable no longer is linked against Heimdal. heimdal-servers-x no longer exists in testing (and probably suffers numerous security issues). It is possible to install the latest libraries from Stretch on a Jessie system and not the clients; you *might* have for example have problems if you continue running the Jessie heimdal-kdc with the libraries from Stretch. However the solution is simple: upgrade the clients too. As it recommended practise when updating from Stretch to Jessie in fact. I have attempted to cause a crash by mixing Jessie heimdal-kdc with the stretch version of libroken. Although not a comprehensive test, it seems to work fine. I suspect the symbol is only used by HTTP operations, which is rare configuration for the KDC. It is not possible to install the latest clients without the latest libraries. After the Stretch release this bug is going to become irrelevant, as we don't support upgrades from Jessie to Buster. -- Brian May <b...@debian.org>
