Sam Hartman, le lun. 14 août 2023 13:15:49 -0600, a ecrit: > That's problematic, because there is not a strict version dependency > between libk5crypto3 and libkrb5support0.
Ah, I didn't realise you didn't have it. > The dependencies allow an old libk5crypto3 to be installed alongside a > new libkrb5support0. > For that to work, libkrb5support0 needs to not disappear symbols. > > I have three options: > > 1) The option I'm likely to choose is to mark the symbols optional, > break old libk5crypto3 from new libkrb5support0 as a one-time thing, and > create a strict dependency on the binary version from libk5crypto3 to > libkrb5support0. > I *think* this is safe. I believe too. > The ABI of libkrb5support0 will depend on which glibc we build against, > but nothing outside of the krb5 source package is permitted to care > about that ABI, Yes. Samuel
