Magnus Holmgren wrote:
> Adeodato Simó <email@example.com> writes:
>> * Russ Allbery [Mon, 04 Aug 2008 21:38:44 -0700]:
>>> It looks correct to me for the krb5 interface. It looks like some of the
>>> internal libraries that Heimdal uses (maybe libroken and libasn1,
>>> although I'm not sure) aren't using symbol versioning, but since that
>>> isn't the API that's shared with MIT Kerberos, that shouldn't matter in
>>> practice. I doubt this is a regression from the previous state; they
>>> were probably never using symbol versioning.
>> Ok, thank you; I scheduled the binNMUs now, which are mostly ready now,
>> and will migrate the new version next.
> How is the heimdal transition going? Are all the hints in place? I though you
> had to put all the packages that are to go in together on the same hint line.
heimdal is already hinted, the only remaining problem is that
cyrus-sasl2-heimdal-dbg gets broken:
The following packages have unmet dependencies:
cyrus-sasl2-heimdal-dbg: Depends: cyrus-sasl2-dbg (= 2.1.22.dfsg1-22)
but it is not going to be installed
E: Broken packages
This is a serious bug in cyrus-sasl2-heimdal.
- Re: heimdal
- From: Magnus Holmgren <firstname.lastname@example.org>