>>>>> "Nico" == Nico Golde <n...@debian.org> writes:
Nico> Hi, * Eike Sauer <eikesa...@t-online.de> [2009-02-27 17:47]:
>> Am Freitag, 27. Februar 2009 schrieb Nico Golde: > libkrb5-3 is
>> in experimental so I dont see the problem on the fetchmail >
>> package side.
>>
>> Ah, I see. libkrb5-3 states it "Replaces: libkrb53", but it
>> doesn't provide libgssapi_krb5 anymore, which has been
>> "outsourced" to libgssapi-krb5-2. So either libkrb5-3 or
>> fetchmail will have to adjust its dependencies. If the
>> oursourcing was done to reduce size/dependencies on the libs
>> side, I guess it will be fetchmail...?
First, this is all in experimental, not unstable:-) I'm allowed to
break things in experimental.
If I had uploaded that package to unstable, I would expect fetchmail to
continue to work for anyone who already had it installed.
If you only install libkrb5-3 then you'll still have the libgssapi_krb5 from
libkrb53.
However if you install libgssapi-krb5-3, then you'd again have libgssapi_krb5.
However, that set of packages will never make their way to unstable.
Instead, I'm going to be adding a libkrb53 that depends on the other
libs. So, since you have an install dependency on libkrb53, then
you'll pull in libgssapi-krb5-3 because libkrb53 will pull that in.
libkrb5-dev will also pull in libgssapi-krb5-3.
After you next rebuild fetchmail, you'll end up with a dependency on
libgssapi-krb5-3 not on libkrb53.
Nico> Sam or Anibal, any idea about that? I wasn't notified
Nico> because of any change, currently fetchmail has a
Nico> build-dependency for libkrb5-dev and libgssglue-dev.
Why do you want libgssglue? Do you support gss-api mechanisms other
than kerberos? Using libgssglue may make some other transitions more
difficult in the future, although that is very much a workstill being thought
about.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
