Re: sarge planning: interdependent packages

[Brian May <bam@debian.org>]

On Mon, Oct 20, 2003 at 02:02:22PM -0500, Steve Langasek wrote:
> - Installing the new version of heimdal in testing breaks the version of
>   postgresql currently in testing.  The version of postgresql in
>   unstable no longer depends on heimdal (it uses MIT Kerberos instead),
>   so it doesn't have to go in at the same time as the above three
>   packages -- it can go in before them, when it's ready.

errr.... Are you sure?

If you are looking at bug like #216290 and #205592, then the same
version will be broken in testing, too.

> - The new version of coreutils (aside from currently being out-of-date
>   on m68k, which should be remedied soon) cannot be installed in testing
>   until krb4 is updated there, because it's an Essential: yes package
>   with a dependency on libacl1, which conflicts with
>   libacl1-kerberos4kth, with the net result that libacl1-kerberos4kth
>   would be uninstallable.

I thought this problem had been fixed???

Or maybe the version in unstable has been fixed, but not yet entered
testing?

> Please consider this an invitation to a mini-freeze for these packages,
> and also an invitation to help watch over one another's packages over
> the next few weeks to facilitate a smooth transition.  Ideally, all of
> these packages will be eligible for testing in a little over two weeks;
> but one bad upload of a package with a 10-day waiting period could
> easily throw that off.

Bug #216290 still needs to be fixed.

This means recompiling both Heimdal and krb4 with versioned symbols.

This is a bit dodgy, and could cause things to break in the process
(hopefully not).

Before I even start working on versioned symbols though, I want to fix
#213450, which requires libcomerr2 to be uploaded with a simple 1-line
patch, so far the maintainer has not responded though.
-- 
Brian May <bam@debian.org>